Robert Klep

@R-Nav looks like the unresponsive devices are mostly routed through node 17 ("Onbekend Zigbee apparaat") and/or node 4 ("Wandlampen hal"), so I would start suspecting those.

I can reproduce the problem using the method below. I forgot to mention that this probably only happens with "unidirectional" devices, devices that Homey can send a signal to, but...

Reopening the issue because it still exists, and it prevents me from being able to use Homekit at all. Homekit should never assume that the internal state that it keeps...

@harry71019 if you pass the specific device file(s) to the container (`--device=/dev/foo:/dev/foo`) you don't need privileged mode, but if I understand correctly (not a user), octoprint may require full access...

Find the device here: https://tools.developer.homey.app/tools/devices, then post the "Class" and all capabilities here. If it has a capability called `alarm_motion`, then that's the reason why it's showing up as a...

I'm missing the list of capabilities.

Not sure that I see the problem?

Homey doesn't provide any logging, all you can do is run HomeyKit from the commandline to see what's happening with the app, but it probably won't give you a lot...

Homey firmware updates _always_ cause issues 🙄

Nothing yet, been busy with other things. Don't get your hopes up though: we also implemented Speaker support, but it looks like it only works with a very limited number...