node-red-contrib-home-assistant-websocket icon indicating copy to clipboard operation
node-red-contrib-home-assistant-websocket copied to clipboard

Time node triggering an hour early

Open AndLindemann opened this issue 1 year ago • 0 comments

Describe the bug

I think something is wrong with the Time trigger node. I have an input_datetime helper in HA which I use to set our wake-up time. It only captures hours and minutes for that purpose, so I set it to like 05:30 and the Time trigger will pick it up and start our Alarm flow at that time. However since the last update (I believe the changes in 0.62.3), it triggers twice. Once at 04:30 (exactly 1 hour early) and then again at 05:30. I'm trying to reproduce it genericly, but so far haven't been successful. It happened two days in a row for us now and I checked and the node itself says that it will trigger next at the correct time, but it then actually triggers an hour early and then again a second time at the correct time.

To Reproduce

Still trying to find a way to easily reproduce. Currently it seems to only happen for me when the input_datetime helper is being set to a time that would make the node trigger on the next day earliest. We set our input_datetime helper in the evening to trigger next morning and that seems to make the issue more likely to appear.

I tried setting the helper to just a few minutes in advance, but that doesn't seem to trigger the issue.

Expected behavior

Time node triggers at the correct time from an input_datetime helper.

Screenshots

No response

Example Flow

No response

Environment Information

Version: 0.62.3

Home Assistant version: 2024.2.1 Companion version: 17.0.6

Node-RED version: Docker: no Add-on: no

Node.js version: OS: HAOS 11.5

Additional context

No response

AndLindemann avatar Feb 15 '24 05:02 AndLindemann