# Allow Events: State node "output on connect" option to start timers

**URL:** <https://discourse.nodered.org/t/allow-events-state-node-output-on-connect-option-to-start-timers/93081>\
**Category:** Feature Requests\
**Tags:** home-assistant\
**Created:** [11 November 2024 21:02 UTC](https://discourse.nodered.org/t/allow-events-state-node-output-on-connect-option-to-start-timers/93081 "2024-11-11T21:02:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jbwiden](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@jbwiden](https://discourse.nodered.org/u/jbwiden)\
**Post date:** [11 November 2024 21:02 UTC](https://discourse.nodered.org/t/allow-events-state-node-output-on-connect-option-to-start-timers/93081/1 "2024-11-11T21:02:36Z")

</div>

My understanding is that when "output on connect" is selected, it will not start timers that would allow the node to signal if the "For" option is populated with a time.

I believe this would be good functionality to have, or at least some option to allow for it.

For instance I use the Events: State node to send a notification when say the garage door is open for more than 1 hour or if a node is missing for a day. If I restart in that time, the timer will not be reset and I will miss that notification entirely. I could workaround this in some other manner, but the pattern is very common at least for me and having the built in functionality would be really nice to have.

I do see it mentioned in the docs that it isn't supported:  
"Warning: Output on Connect state changes will not start a timer."

> **[Events: state | node-red-contrib-home-assistant-websocket](https://zachowj.github.io/node-red-contrib-home-assistant-websocket/node/events-state.html#entity)**
>
> A suite of nodes that seamlessly integrates Home Assistant with Node-RED

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [11 November 2024 21:10 UTC](https://discourse.nodered.org/t/allow-events-state-node-output-on-connect-option-to-start-timers/93081/2 "2024-11-11T21:10:25Z")

</div>

This node is not maintained by node-red core team. You will need to ask either in the home assistant forum or on [the nodes repository](https://github.com/zachowj/node-red-contrib-home-assistant-websocket).

---

<div class="post-metadata">

**Author:** ![jbwiden](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@jbwiden](https://discourse.nodered.org/u/jbwiden)\
**Post date:** [11 November 2024 21:16 UTC](https://discourse.nodered.org/t/allow-events-state-node-output-on-connect-option-to-start-timers/93081/3 "2024-11-11T21:16:45Z")

</div>

Thanks for pointing me in the right direction.  
I have reposted here: [Allow Events: State node "output on connect" option to start timers · zachowj/node-red-contrib-home-assistant-websocket · Discussion #1692 · GitHub](https://github.com/zachowj/node-red-contrib-home-assistant-websocket/discussions/1692)  
Hopefully that is the right spot...

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [10 January 2025 21:17 UTC](https://discourse.nodered.org/t/allow-events-state-node-output-on-connect-option-to-start-timers/93081/4 "2025-01-10T21:17:01Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.