One major limitation of the join node is the lack of a timeout. For example, two paths should be received within 10 seconds. I feel this is important enough that it should be a core feature. It has enormous potential, especially in the home automation space -- e.g, turn light on if 1) motion detecte…

Basic requirement: Turn light on if 1) motion detected, and 2) door closed within 10 seconds. Note that "motion detected" and "door closed" are from independent sources and can fire multiple times in a row. The flow should complete immediately once the conditions are satisfied Advanced requi…

How about this? It uses node-red-contrib-simple-gate to allow or stop the door close event through to switch the light on. [image] [{"id":"a0a4582c.c1a8","type":"inject","z":"bdd7be38.d3b55","name":"Motion event","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"…

I haven't played with node-red-contrib-simple-gate, but I really like this approach @Colin ! I made one small edit to your flow - essentially to close the gate immediately after a successful run. This is needed to avoid multiple door close events from firing the light on again. I'm not sure if there…

This becomes a bit mind stretching if more items are added (e.g., 4 sequential events), Then indeed it will become more complex to manage, I am not sure that it is so "common". Your original approach (node) was to combine messages based on timeframes and that part does not appear necessary, albe…

I still think that a DSM would be the best way, I haven't used those nodes enough to knock off the solution in 5 minutes. I imagine that @cflurin would come up with a solution in no time at all if he were to have a few minutes to look at it.

I haven't read the thread yet but this might help, otherwise I'll have a deaper look. [image] Directional door sensor General A first dsm-implementation with a door contact inside and a motion sensor outside. Note: install the dsm.node first. [{"id":"6190347.b7639cc","…

[image] dxdc: This is needed to avoid multiple door close events from firing the light on again. How can you get another door close event without an open in between?

@cflurin this flow is cool for state tracking, but it doesn't seem to track timing. E.g., both events need to happen within a specific timeframe.

@Colin I realize this is non-ideal, but it has to do with the sensor. Sometimes - esp. depending on speed of movement and sensitivity - the open event may not fire. These sensors are all battery powered, so the latency is non-zero.

Understood. An RBE on the way in might be the easiest way to sanitise that rather than complicating the later logic.

Node-RED

Node-RED Forum

Join/Wait Node: Timeout Feature request

Core Development Feature Requests

cflurin 3 June 2020 08:23 22

I haven't read the thread yet but this might help, otherwise I'll have a deaper look.

Topic		Replies	Views
How to Only respond to 2nd message (within time window) General	14	1689	28 April 2025
Simple settimeout function General	24	6353	8 January 2021
Delay loop and reset General	10	7514	28 March 2020
Multiple inputs with external conditions from Home-Assistant Developing Nodes	8	2882	4 November 2020
Can I have a delay / sleep inside Function node General	34	44281	7 February 2024

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Join/Wait Node: Timeout Feature request

Related topics