Hi, During the development and testing of IoTivity-based servers and clients, we face from time to time many problems related to the reliability of the multicast discovery.
In short, while everything being connected over the Wifi, a client tries multicast /oic/res, and does not get back a response from the server. The server is up and running, no experiencing any "health" issues. Sometimes, it happens after a server was connected to a different WiFi network (should IoTivity handle this automatically?). But sometimes servers stop responding just in the middle, without any network change. In the server, there is no application code we can debug, it's all handled by IoTivity framework. In the client, we jsut don't get the expected resources in the callback. So application-side debugging isn't helpful. Most of our servers and clients are Android-based. May I kindly ask the IoTivity community: 1. Is it a familiar issue? 2. Do you know a specific cause for the issue? (WiFi roouter, configuration etc.) 3. What's the efficient way to debug it, on Android devices? (like, essential IoTivity traces implementing it) Thanks and best regards Max
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
