You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
documenting the difference or
having both (all?) widgets read back the value from the bus so that a mapping can be used
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:
The trigger doesn't read anything from the bus as it's completely stateless - just like a normal "Taster".
But isn't a pushbutton exactly what you are looking for?
Is there something that you are missing here for the pushbutton?
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: