Skip to content
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

Open
ggaljoen opened this issue Apr 1, 2024 · 11 comments
Open

PROGRAM_SELECTION is not read back when set #96

ggaljoen opened this issue Apr 1, 2024 · 11 comments

Comments

@ggaljoen
Copy link
Collaborator

ggaljoen commented Apr 1, 2024

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.

@cereal2nd
Copy link
Owner

i'm not following.

we should only look at the velbus for the state, so not sure what is wrong here

@ggaljoen
Copy link
Collaborator Author

ggaljoen commented Apr 1, 2024

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?
PROGRAM_SELECTION bigger

@ggaljoen
Copy link
Collaborator Author

ggaljoen commented Apr 1, 2024

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]

image

@cereal2nd
Copy link
Owner

there is this:
afbeelding

@ggaljoen
Copy link
Collaborator Author

ggaljoen commented Apr 2, 2024

Will wait on the april release.
Get back at this in a few days.

@cereal2nd
Copy link
Owner

any update on this?

@ggaljoen
Copy link
Collaborator Author

ggaljoen commented Oct 29, 2024

Still active with the most recent version.
If I add the program selection to the dashboard and change it; it is in the velbus logs BUT on the dashboard it stays unchanged. It does not show in the HA entity logs.
When it is changed in velbuslink it follows right away.

@cereal2nd
Copy link
Owner

can you show me the logs?

That would help me in pointing in what area to look

@ggaljoen
Copy link
Collaborator Author

ggaljoen commented Nov 4, 2024

What logs do you mean? Velbuslink or HA or both?

@cereal2nd
Copy link
Owner

both if possible

@ggaljoen
Copy link
Collaborator Author

ggaljoen commented Nov 4, 2024

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
B3 01 = summer
B3 02 = winter
B3 04 = holiday

And the device confirmation goes like this:

ED 00 0F 00 00 00 D4 = none
ED 00 0F 00 00 00 D5 = summer
ED 00 0F 00 00 00 D6 = winter
ED 00 0F 00 00 00 D7 = holiday

Same thing happens in velbuslink (11.2.2), if you open a device operate window and changed a setting in HA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants