earnest goblet
Trying to use a time node as an alarm using the time from a cell phone
Entity looks good when an alarm is set, node red has an error one second before the alarm is supposed to go off
It appears that the entity goes to unavailable 1 second before the time is supposed to match.
Worked a few times in November, but should have nearly every workday of the month
2024/11/05 05:15:00
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
nodered logs
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
digital smelt
Once your phone reaches the time of next_alarm, the next_alarm sensor goes to unavailable, because there is no next alarm.
Using that sensor is always unstable/racy, you would want to do something 10/20/30 seconds before that time if you want to make sure it occurs.
Or you can trigger 30s before the next alarm, add a 30s delay, and then do something.
earnest goblet
oh interesting
I did n't know it was a known thing
it seemed to work really well until it didn't
I like that idea
I'm gonna test with a 15 sec offset delay combo
hopefully this is correct
earnest goblet
Confirmed fix