#[Node Red] Time node works sometimes
1 messages · Page 1 of 1 (latest)
for whatever reason it worked great on the 27th, but not since
okay upon furthe log inspection this error is when the entity flips to unavailable becasue the alarm just went off, so I actually have no insight into what is letting it skip the time
22 Nov 05:15:00 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
24 Nov 20:33:30 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
25 Nov 05:32:37 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
25 Nov 05:44:59 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
26 Nov 05:44:59 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
26 Nov 08:46:25 - [error] [ha-time:CW Phone Alarm] ConfigError: Unavailable
26 Nov 08:46:25 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
27 Nov 05:45:00 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
27 Nov 09:02:40 - [error] [ha-time:CW Phone Alarm] ConfigError: Unavailable
27 Nov 09:02:40 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
2 Dec 05:29:59 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
2 Dec 05:50:06 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
2 Dec 14:08:27 - [error] [ha-time:CW Phone Alarm] ConfigError: Unavailable
2 Dec 14:08:27 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
3 Dec 05:29:58 - [error] [ha-time:LW Phone Alarm] ConfigError: Unavailable
3 Dec 15:00:18 - [error] [ha-time:CW Phone Alarm] ConfigError: Unavailable
alarm log shows the node info for the successes
Worked a few times in November, but should have nearly every workday of the month
2024/11/07 05:00:00
2024/11/08 05:15:00
2024/11/12 05:35:00
2024/11/14 05:15:00
2024/11/21 05:15:00
2024/11/21 05:35:00
2024/11/27 05:45:00```
Is nodered getting the unavailable state faster than its triggering the output
so it stops before it starts?