Time Node (Beta Version)

[zachowj]

place holder

[hvddrift]

Would you please have an example of the 'Time Node'?

I would like to test it, but cant find the right combinations.

[zachowj]

Check out the cookbook https://zachowj.github.io/node-red-contrib-home-assistant-websocket/cookbook/using-date-and-time-entities-to-trigger-flows.html.

I converted several flows to use the time node.

[arretx]

Lol...FYI, the statement "Beta version: Config should be stable and hopefully not to many bugs.
Found an issue? Post it in issues . Have questions or comments? Post them here ." contains a bug itself. not "too" many bugs.

[rikki78]

Nice feature this time node, saves some additional nodes after an input_date_time. A nice feature would be if the days when this event is fired can be selected somewhere.

[Michelobb]

Hello and thanks for this great node.

I got a strange issue.

I'm using the node to set my home status (day or night) in an INPUT_SELECT HA variable.

The node is supposed to fire at a scheduled daily time, stored in an INPUT_NUMBER HA variable.

Things work remarkably well in the evening, when the house'status changes from "day" to "night".

But in the morning, it hasn't yet worked a single time.

However, if I simulate being in the morning, setting the HA variable to the next minute, in order to be able to check it, the change occurs perfectly well.

So, do I have to be awake to make it work ? (haha)

Seriously, should I trigger some event before this one, just to "wake up" the system ? This doesn't sound quite rational, does it ?

Any help would be really appreciated here.

Thanks,

Michel

[{"id":"083494addd03ef2a","type":"api-call-service","z":"20594c77ddba82b2","name":"Mode jour !","server":"e5371104.417d5","version":3,"debugenabled":false,"service_domain":"input_select","service":"select_option","entityId":"input_select.mode_maison","data":"{\"option\":\"Jour\"}","dataType":"jsonata","mergecontext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":450,"y":600,"wires":[[]]},{"id":"75ee502e6f5e913c","type":"ha-time","z":"20594c77ddba82b2","name":"Heure du mode Jour ?","server":"e5371104.417d5","version":0,"exposeToHomeAssistant":false,"haConfig":[{"property":"name","value":""},{"property":"icon","value":""}],"entityId":"input_datetime.mode_jour_time","property":"state","offset":0,"offsetType":"num","offsetUnits":"minutes","randomOffset":false,"repeatDaily":false,"payload":"$entity().state","payloadType":"jsonata","debugenabled":false,"x":190,"y":600,"wires":[["083494addd03ef2a"]]},{"id":"e5371104.417d5","type":"server","name":"Home Assistant","version":1,"addon":true,"rejectUnauthorizedCerts":true,"ha_boolean":"y|yes|true|on|home|open","connectionDelay":true,"cacheJson":true}]

[Michelobb]

No I don't, but on the "evening" node neither.

Now I've checked it, and I'll see what's happenning tomorrow, but then, I don't understand why the evening node is working without that...

[Michelobb]

Now that I believe having understood the node's logic, I've also checked my HA input_select variables, and they both send HH:MM:SS without DAY. I thought this could 've been responsible of the divergent behavior, but it's not.

[zachowj]

Are you updating the evening input_select daily by some means?

[Michelobb]

I don't... I only changed manually a couple of time, to test it. But it seems to fire even if I don't touch it the whole day.

Something I'm not sure, but I think having seen the mention "In the past" only on the morning node status. But that's something I couldn' t certify.

[Michelobb]

I think I need to check very carefully a whole new day without updating the evening node time after its first shot, just to be sure we can discard that possibility.