Open BergenSoft opened 8 months ago
The only way to disable controls would be to set the entity "unavailable". This is currently the case when the Knx interface is disconnected, but I could imaging adding a binary GA for such things would be a good idea.
All my wall switches (binary sensors) do not control any actors and only trigger automations. This has the advantage that i can switch off automations if i e.g. want to disable a wall switch.
One thing to consider is that a user may even want to be able to use the entity while eg. a wind alarm is set. Some actuators process incoming telegrams to dive to that position as soon as the alarm is off. So on a windy day blinds are open, wind alarm active. An automation sets blinds down at dusk. When the alarm ends blinds close. This wouldn't work when the entity was unavailable as the automation was running.
Good point, but in this case you wouldn’t need the disable feature. You can always let the control activated.
Some covers or blinds aren't allowed to be moved in some cases. E.g. if it is raining or it is too windy. Of course a knx module has to make that sure, but the controls in Hassio can still be pressed.
Is there any possibility to disable them in case of an alert or would it make sense to implement this feature as a separate sensor address (or multiple addresses for raining and windy at the same time)?