-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PROGRAM_SELECTION is not read back when set #96
Comments
i'm not following. we should only look at the velbus for the state, so not sure what is wrong here |
Think I found the cause... But in Just checked and it works fine for my VMBPIRC, there it is present: |
Will wait on the april release. |
any update on this? |
Still active with the most recent version. |
can you show me the logs? That would help me in pointing in what area to look |
What logs do you mean? Velbuslink or HA or both? |
both if possible |
Somehow it sounds kind of logical; HA set the new states on the velbus THUS will not react on that change/message, because no status change is at that time received. One of these is send by HA: B3 00 = none And the device confirmation goes like this: ED 00 0F 00 00 00 D4 = none Same thing happens in velbuslink (11.2.2), if you open a device operate window and changed a setting in HA. |
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.
The text was updated successfully, but these errors were encountered: