search

alexryd / homebridge-shelly-ng

Homebridge plugin for the next generation of Shelly devices
GNU General Public License v3.0
124 stars 49 forks source link

[Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer) #138

Open RobbieTT opened 1 month ago

RobbieTT commented 1 month ago

I am running just a single Shelly Plus 1PM with a child bridge. The accessory works fine in HomeKit (controlling an immersion heater) but the logs are filled with the message above.

Details:

[10/2/2024, 12:55:09 PM] [Shelly NG] Launched child bridge with PID 18567 [10/2/2024, 12:55:09 PM] Registering platform 'homebridge-shelly-ng.ShellyNG' [10/2/2024, 12:55:09 PM] [Shelly NG] Loaded homebridge-shelly-ng v1.6.0 child bridge successfully [10/2/2024, 12:55:09 PM] Loaded 1 cached accessories from cachedAccessories.0EDDE24E1700. [10/2/2024, 12:55:09 PM] Homebridge v1.8.4 (HAP v0.12.2) (Shelly NG) is running on port 54718. [10/2/2024, 12:55:09 PM] [Shelly NG] mDNS device discovery started [10/2/2024, 12:55:10 PM] [Shelly NG] [shellyplus1pm-d48afc599f50] Device added [10/2/2024, 12:55:33 PM] [Shelly NG] An error occurred in the mDNS device discovery service: Cannot decode name (bad pointer)

Presumably it does not like something in mDNS land. Is there a way of either fixing this error message, identifying the cause or just getting Shelly NG to ignore it (as everything seems to work just fine)?

Regards

apartmedia commented 1 month ago

Did you try using the forked plugin homebridge-shelly-ds9 from cubi1337 as this one from @alexryd seems to be no longer maintained (at least it got no updates in the last 2 years).

RobbieTT commented 1 month ago

Did you try using the forked plugin homebridge-shelly-ds9 from cubi1337 as this one from @alexryd seems to be no longer maintained (at least it got no updates in the last 2 years).

Ok, thanks for the tip as I didn't notice that fork. Cheers.

RobbieTT commented 1 month ago

Did you try using the forked plugin homebridge-shelly-ds9 from cubi1337 as this one from @alexryd seems to be no longer maintained (at least it got no updates in the last 2 years).

The newer fork has been installed and works. Still have the same error message though! I've turned mDNS off in the config for now.

apartmedia commented 1 month ago

Strange, I‘m using the exact same device, Shelly Plus1PM with FW 1.4.2 and I haven’t any error message about it in the log. Curious if this could have something to do with your (other) devices in the network and is not purely an issue with the plugin itself. See here…

RobbieTT commented 1 month ago

That was my first thought but all my devices are well-behaved and not fringe products. The pcaps all look fine and the data to mDNS 'Discovery' app all looks clean too.

What I am less sure of is the impact of using an mDNS repeater to span 2 subnets. In my case I am using Avahi (2.2_5) hosted on pfSense. It's a bit odd that only the plugin is impacted but it may be worth me spinning-up another Shelly Plus 1 PM and placing it on a subnet that does not need Avahi.

apartmedia commented 1 month ago

That might be a good test… Report back if possible.

RobbieTT commented 1 month ago

Reporting back:

I'm still getting the same error when connecting via the main subnet, rather than through my Avahi mDNS repeater. I also tried changing Homebridge itself from HAP to Avahi mDNS, just in case it preferred the all 'Avahi' approach but that prompted a wider connectivity issue, so I switched back to Homebridge HAP.

It was worth a try I guess.