Open ggaljoen opened 3 months ago
i'm not following.
we should only look at the velbus for the state, so not sure what is wrong here
Indeed not easy to understand. Made a small clip to clearify:Left side is VelbusLink, middle is Home Assistant status, right is selection box in Home Assistant
Does this make more sense now?
Think I found the cause...
It is correctly intercepted from / and set by 0xB3
: velbusaio/messages/select_program.py
Since this is transmitted from velbusaio, it is not possible to update from this packet.
But in velbusaio/messages/module_status.py
0xED
there is no selected_program
for the majority of the modules.
This issue is present on all my VMBELx and one VMBGPOD-2.
Just checked and it works fine for my VMBPIRC, there it is present:
@register(COMMAND_CODE, ["VMBPIRO", "VMBPIRM", "VMBPIRC", "VMBELPIR"])
self.selected_program = data[5] & 0x03
self.selected_program_str = PROGRAM_SELECTION[self.selected_program]
there is this:
Will wait on the april release. Get back at this in a few days.
velbusaio/messages/module_status.py PROGRAM_SELECTION is only updated from Velbus. It can be set correctly and written to Velbus but the value is not updated to selection made.