Discovered device did not respond to query

[techo91]

Hi, I have this log entry on a new installation of Hoobs version: 3.3.3. Node version: 15.10.0 [homebridge-magichome-dynamic-platform] Warning! Discovered device did not respond to query. This is usually due to an unresponsive device. Please restart homebridge. If the problem persists, ensure the device works in the "Magichome Pro" app. File an issue on github with an uploaded log. { ipAddress: '192.168.xxx.xxx', uniqueId: '18B905C0xxxx', modelNumber: 'AK001-ZJ2145'

My device responds perfectly in the Magic Home app. I'm not sure how can I diagnose this. Can anyone help me with this?

Thanks.

[bwp91]

Might not sort this issue but I wouldn’t recommend node version 15. Try downgrading to v14.16.0.

Homebridge doesn’t support odd numbered versions of node

[techo91]

I tried, unfortunately hoobs 3.3.3 installed in a jail in TrueNAS system (FreeBSD) does not work with older version of node. I'm not sure what the reason is though. Can I try something else?

[Zacknetic]

Most likely not. The issue is, for some reason, the responses from the devices aren’t reaching the hoobs instance.

This type of setup is outside the scope of this plugin.

My suggestion to you would be to install hoobs / Homebridge in a less locked off environment.

[bwp91]

Node v14 isn’t an “old” version it’s a very current version. strange that you can’t downgrade?

[techo91]

I have a sonoff plugin installed as well and it communicates with several different devices without any issue. I can try the docker version a bit later and see how it goes there.

[bwp91]

Sonoff plugin uses a cloud connection whereas i believe magichome uses a different local connection method. Worth trying the docker version. The magichome plugin is a popular plugin and i think there would be a lot of chatter if something was wrong with the plugin with connecting to devices

[tom-23]

This issue actually helps a lot.

If you look at #88, I had the same issue using macOS. There must be some similarity in the way networking is handled in these UNIX operating systems which is different from Linux or Windows (or we haven't implemented something correctly). I think we need to look into this further...

EDIT: just been looking into this a bit more and found out XNU (darwin's kernel) has some stuff to do with FreeBSD. It probably doesn't have much to do with this issue though.

[techo91]

I tested the docker version and it looks like the plug-in partially works there. It has node 14.16.0. What works is commands via HomeKit, what doesn’t work is commands via the Hoobs GUI.

[bwp91]

if it works though homekit it must work through the hoobs ui. any log entries when you use the hoobs ui?

[techo91]

This is my logic as well but strangely it is not the case. The only thing in the log that I can see is this:

[HOOBS 420A@GRB Strip@@Hardware Revision] characteristic was supplied illegal value: number instead of string, supplying illegal values will throw errors in the future 12/03/2021, 22:01:38 [HOOBS 420A@GRB Strip@@Firmware Revision] characteristic was supplied illegal value: number instead of string, supplying illegal values will throw errors in the future 12/03/2021, 22:01:38 [HOOBS 420A@GRB Strip@@Configured Name] Characteristic not in required or optional characteristic section for service Lightbulb. Adding anyway.

When toggling on or off, there are no log messages.

[Zacknetic]

Could you please update to version 1.9.4. (just released, may take some time to appear on Hoobs). Let me know how that goes.

Thank you -Z

[mbinax]

I use this plugin with OMV, in a docker, to control a couple of led strips. For a long time (months) everything was OK. Now, it's a few weeks that I get the same error/issue reported in this thread... Of course, everything works fine in Magic Pro app.

[Zacknetic]

Hello, please update to version 1.9.7 and ensure you are upgraded to node 16. This should fix your issues.

Please let me know. -z

[mbinax]

Hello, please update to version 1.9.7 and ensure you are upgraded to node 16. This should fix your issues.

Please let me know. -z

Yeah! That's right! It works. Thank you so much ;-)

[Zacknetic]

@mbinax great to hear it!

Closing this issue as solved.