anotherjulien / OWNd

OpenWebNet daemon
GNU Lesser General Public License v3.0
30 stars 11 forks source link

Incoming message `*#1*11*13*0*100**1##` breaks OWNd for incoming messages #7

Closed michnovka closed 1 month ago

michnovka commented 1 month ago

All my other lights work without issues. But I have a weird problem with my light 11: When I turn it on, its fine, the BUS sends *1*1*11## to let me know its ON. But turning it off (using the switch, or any openwebnet extension like openhab OR homeassist) results in weird message. First I get *1*0*11## - this is expected and fine. But then, the BUS sends *#1*11*13*0*100**1## which is not understood by OWNd.

See log:

homeassistant  | 2024-08-29 16:44:31.488 DEBUG (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Message received: `*1*1000#1*11##`
homeassistant  | 2024-08-29 16:44:31.489 DEBUG (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Ignoring translation message `*1*1000#1*11##`
homeassistant  | 2024-08-29 16:44:31.519 DEBUG (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Message received: `*1*1*11##`
homeassistant  | 2024-08-29 16:44:31.519 INFO (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Light 11 is switched on.
homeassistant  | 2024-08-29 16:44:32.484 DEBUG (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Message received: `*1*1000#0*11##`
homeassistant  | 2024-08-29 16:44:32.484 DEBUG (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Ignoring translation message `*1*1000#0*11##`
homeassistant  | 2024-08-29 16:44:32.519 DEBUG (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Message received: `*1*0*11##`
homeassistant  | 2024-08-29 16:44:32.519 INFO (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Light 11 is switched off.
homeassistant  | 2024-08-29 16:44:32.523 DEBUG (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Message received: `*#1*11*13*0*100**1##`
homeassistant  | 2024-08-29 16:44:32.523 INFO (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] *#1*11*13*0*100**1##

And after that, ownd stops working. It does not see any other messages on the BUS as received. See e.g. when I try to turn on or off another buttons:

homeassistant  | 2024-08-29 16:49:07.737 INFO (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Message `*1*1*91##` was successfully sent.
homeassistant  | 2024-08-29 16:49:08.438 DEBUG (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Message `*1*1*91##` was successfully queued.
homeassistant  | 2024-08-29 16:49:08.439 DEBUG (MainThread) [custom_components.myhome] MH202 Gateway (192.168.1.40) Message `*1*1*91##` was successfully unqueued by worker 0.
homeassistant  | 2024-08-29 16:49:08.517 INFO (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Message `*1*1*91##` was successfully sent.
homeassistant  | 2024-08-29 16:49:09.135 DEBUG (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Message `*1*1*91##` was successfully queued.
homeassistant  | 2024-08-29 16:49:09.135 DEBUG (MainThread) [custom_components.myhome] MH202 Gateway (192.168.1.40) Message `*1*1*91##` was successfully unqueued by worker 0.
homeassistant  | 2024-08-29 16:49:09.216 INFO (MainThread) [custom_components.myhome] [MH202 gateway - 192.168.1.40] Message `*1*1*91##` was successfully sent.

No responses.

I have to reload the custom integration in HA in order to get it working again.

Even if I turn the switches manually in my home, no messages are received by OWNd until it is restarted.

The message *#1*11*13*0*100**1## breaks it

michnovka commented 1 month ago

I did some digging. For some reason I had Delayed OFF for Slave (s) = 2 enabled on this button.

image

No idea what it does, I have disabled it and it works fine now. But still, the daemon should not just stop working when it sees such unsupported message. It should gracefully ignore it.

michnovka commented 1 month ago

I believe this is undocumented dimension 13. I have tested enabling it on another button with ID=31 and I got this message when turning it off *#1*31*13*0*100**1##

So the WHERE =31 in this case, but the 13 stays.

michnovka commented 1 month ago

I am closing this issue as this is MyHOME HA integration bug. https://github.com/anotherjulien/MyHOME/issues/143

Will open another issue about the dimension 13 not being supported, but it is not critical

michnovka commented 1 month ago

Closing as https://github.com/anotherjulien/OWNd/issues/12 supersedes this