You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if there was a way to re-trigger the most recent event in the schedule .
That way, if things get out of sync downstream of the node, and you just want to get back to what the state should be right now, you would fire this method off.
E.g.
You are using this node to trigger settings on a light, and there was a power outage. After the outage, the light came back on in the state it was in when it lost power, but it missed 3 cron events during the outage, and is therefore in the wrong state. Now I want to set it back to what it should currently be, based on the cron events. So I want to trigger "last" or "previous" or something to that effect.
Hope this makes sense :-)
The text was updated successfully, but these errors were encountered:
Hello, have you solved your problem ? I'm interested. Thanks.
Hi @Karine005, I am currently using Node-Red context variables to store the 'previous' preset, which can then be recalled at will. It works without too much fuss, but I'd still prefer a solution within the node itself. :-)
It would be great if there was a way to re-trigger the most recent event in the schedule .
That way, if things get out of sync downstream of the node, and you just want to get back to what the state should be right now, you would fire this method off.
E.g.
You are using this node to trigger settings on a light, and there was a power outage. After the outage, the light came back on in the state it was in when it lost power, but it missed 3 cron events during the outage, and is therefore in the wrong state. Now I want to set it back to what it should currently be, based on the cron events. So I want to trigger "last" or "previous" or something to that effect.
Hope this makes sense :-)
The text was updated successfully, but these errors were encountered: