Hello,
based on
https://knx-user-forum.de/forum/%C3%B6ffentlicher-bereich/knx-eib-forum/1992352-korrekte-status-anzeige-bei-gesperrtem-aktor/page2#post1992693
If a channel in KNX-Actor is locked, the Status in HA may not reflect the status of the Actor-Channel.
Example:
- Channel is Locked and Off
- Status in HA is correct (off)
- User switches Channel externally on --> all good, status remains off in HA
- User switches Channel in HA UI on --> Switch in UI turns ON, but Actor stays OFF and does not send a status (as it only sends on change; as per KNX Standard the old value remains valid - state driven)
To fix this, the following would be needed:
- UI does not react directly on User interaction
- Instead UI waits for Status from Actor
A workaround could be to request the status after pressing the button. This would mean that the UI is wrong for a brief moment (ON in the example above) and correct after the status comes (OFF).
In both cases, I think it makes sense to make this behaviour configurable.
Considering that this issue is rare and the full fix seems quite laborous to implement, whilst the workaround seems fairly easy, I think the workaround is worth considering.
Whilst the issue may be rare, I think it is important to fix, as I see the impact of a wrong status quite high.
- A door may be unlocked, while it shows locked
- A water pump may be running, while it shows not running
- A Sauna Oven may be running, while it shows not running
Greetings,
Hendrik
Hello,
based on
https://knx-user-forum.de/forum/%C3%B6ffentlicher-bereich/knx-eib-forum/1992352-korrekte-status-anzeige-bei-gesperrtem-aktor/page2#post1992693
If a channel in KNX-Actor is locked, the Status in HA may not reflect the status of the Actor-Channel.
Example:
To fix this, the following would be needed:
A workaround could be to request the status after pressing the button. This would mean that the UI is wrong for a brief moment (ON in the example above) and correct after the status comes (OFF).
In both cases, I think it makes sense to make this behaviour configurable.
Considering that this issue is rare and the full fix seems quite laborous to implement, whilst the workaround seems fairly easy, I think the workaround is worth considering.
Whilst the issue may be rare, I think it is important to fix, as I see the impact of a wrong status quite high.
Greetings,
Hendrik