-
Notifications
You must be signed in to change notification settings - Fork 81
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
inconsistency between pushbutton and trigger #941
Comments
The trigger doesn't read anything from the bus as it's completely stateless - just like a normal "Taster". Is there something that you are missing here for the pushbutton? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
when I have a trigger set to "readwrite" for an KNX address, it doesn't act on the value read back from the bus. Therefore, a mapping given for the button does never change.
Otoh, a pushbutton reads back the value from the bus and mappings are valid according to the actual state of the actor.
This difference in behavior is not reflected in the docs with the appropriate clarity. I would therefore recommend either
My favorite would be the second option. If this will be the way to go, both (all?) widgets would need a new format attribute to format a numeric value in absence of a mapping.
Greetings
Marc
The text was updated successfully, but these errors were encountered: