Replies: 2 comments
-
@hoontune I've updated the gist to work with the latest version of the state machine. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks, but I think the gist is emulating the end_stop? My situation is a little different. I have no physical buttons for a user to press, everything is handle via HA.
I need the state machine to handle the closed->opening->open -> closing ->closed but to understand that the Contact Sensor has the final say I maybe asking too much |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So I have a few gates/garage doors that are connected to a Shelly1 to toggle a switch on the controller
GPIO4 - Is the relay that toggles the controller
GPIO5 - is a reed switch that closes when the gate/door is closed
State transitions:
- CLOSED -> OPENING
- OPENING -> OPENING_INTERRUPTED
- OPENING_INTERRUPTED -> CLOSING
- OPEN -> CLOSING
- CLOSING -> CLOSING_INTERRUPTED
- CLOSING_INTERRUPTED -> OPENING
I have a few automations open and closing theses gates/doors and what I'd like is that if the door is closing and another automation sends a CLOSE command, the new CLOSE command is ignored, rather than triggering 'CLOSING_INTERRUPTED'
I have built something using standard espHome template cover using current_operation and delays (10 seconds to close or open), but the delays mean that you can't 'STOP' the gate/door quickly.
Would you have a template for this situation? I tried looking at the example here: https://gist.github.com/muxa/68a6e8f8cdbb734c9e0d06a9b87d0147
but I think your state machine has changed since then as it gives errors about action being deprecated etc.
Beta Was this translation helpful? Give feedback.
All reactions