Even when there's suddenly no more next alarm because the last alarm already occurred or the next alarms are turned off the Alarm Changed event should trigger. All variables like na_time should be not set in the event to indicate there's no next alarm.
Description
Thanks for the update! It seems to be working sometimes when the last alarm is disabled in the (Alarm) Clock app, but it seems to work every time an alarm gets enabled there. I also noticed the Alarm Changed event gets triggered every time I open the (Alarm) Clock app.
Hhmm, and that didn't happen before?
No, the context never triggered before with no alarms so triggering 2 out of 3 times for no alarms is better. I don't know if the context activated before when opening the clock app.
My use case is a scene showing the next alarm and is just displayed on the home screen.
I think that's the reason why I don't trigger when no alarm is set. Too many false positives unfortunately...
Ok, changed that. Can you please test if this version works OK?
https://drive.google.com/file/d/1UfMEt1H6wjlMDdsqByn-flCRqE45PdJ1/view?usp=sharing
