Closed stewielabs closed 2 years ago
Same here, but with a little difference (buffer overflow):
[11.6.2022, 07:44:25] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (buffer overflow)
These errors indicate that there are one or more devices in your network that send out invalid mDNS messages. Unfortunately the mDNS library that I'm using doesn't allow for disabling these warnings. The best advice I can give you is to turn off the mDNS service from this plugin and only turn it on when you have a new Shelly device that needs to be added to HomeKit.
Hi,
I'm getting these very frequently in logs: [30/05/2022, 17:08:07] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer) [30/05/2022, 17:08:07] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad label) [30/05/2022, 17:08:16] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer) [30/05/2022, 17:08:16] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad label) [30/05/2022, 17:08:43] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad label)
I've disabled mDNS, since I add my devices manually, but the errors still come. { "name": "Shelly NG", "mdns": { "enable": false }, "devices": [ { "id": "shellypro1-30c6f7847ed0", "name": "Shelly Pro 1", "exclude": false, "hostname": "172.21.1.92" } ], "platform": "ShellyNG" }
I have only the one device right now, testing on the bench, but things seem to work. There are just a lot of log entries.