I have created a rule (rm 5.0) to play a certain radio station on my Sonos speaker every weekday at 7 o'clock. The rule has worked flawlessly till the end of October, but ever since it stopped suddenly without any reason. The log doesn't show any information and i can't figure out the reason why the rule is no longer run. Note that everything works fine when i test the rule via the "Run Actions" button on the rule card. Any clue on what's wrong? It rather looks like the rule machine misses the trigger. I also attach two images with additional info.
It's possible the scheduled job (every weekday at 7 AM) got messed up. If you're curious about that, the "Scheduled Jobs" section on the "App Status" page (gear icon towards the top of your first screenshot) will show you. You should see something there, likely with a cron string that reads something like "0 0 7 ? * MON,TUE,WED,THU,FRI *" (for every weekday at 7 AM--but don't trust me exactly on that!).
It is likely that just hitting "Done" (at the bottom of your first sceenshot) will fix this. It will re-schedule that job. Even if you do see something like that scheduled already, it can't hurt to try either way.
I was hitting the "Done" button and tested the action a million times during the last month. No success so far and the issue is driving me crazy. The job is shown as being scheduled properly, but nothing really happens when the time comes.
That is odd. Maybe try re-creating the rule entirely to see if that helps?
I play radio stations via Sonos using Hubitat (and RM) a lot -- one thing I always check when there are issues: does the URL still work? I check just by entering its URL in the browser.
That said, I tried "http://astreaming.edi.ro:8000/EuropaFM_aac" and the stream worked. Do you need all of those parameters in that very long URL?
Maybe try simplifying it to just "aac://http://astreaming.edi.ro:8000/EuropaFM_aac" and see if it works.
Another data point: here's how I play my radio stations:
"Master Bedroom Sonos: Play Track: 'x-rincon-mp3radio://http://pnj-01.stream101.com:9035/stream'"
/shot in the dark
Thanks bertabcd1234, i'm very stubborn when it comes to re-doing things which are properly done (however i would have done that in no time with a beta product, but i'm not a beta-tester and refuse doing it). Right now i have to understand why/what caused this behaviour and how to avoid it in the future.
Thanks roofone! That was my first thought as well, but the url has always been working (i tried it in a web browser countless times). In the rule i used the entire url as displayed by the device in the HE and never had any issue with it. If i test the rule by clicking on the "Run Actions" button everything runs smoothly. The rule is scheduled to be run every weekday at 7 am, however the log is always empty. I would say that this is an obvious sign that the rule is not triggered...but why is the rule not triggered? I have a C-7 hub, software version 2.2.8.152. I didn't update the software or installed any new device since august, thus i don't really understand why all these bugs.
Gotcha.
Yeah, no āprevious run timeā in the Scheduled Jobs either.
Only remaining thought is to use a Days of the Week trigger instead of periodicā¦ I have seen unusual/buggy behavior with periodic triggers myself, though that was several versions ago.
Doesnāt tell you why it started not working, but may fix it.
(Though, may be a clue: if Iām reading your logs right, it looks like it stopped working when Europe DST ended.)
No idea why it would matter but 11/1 was when daylight savings ended. You said it had worked until the end of October. 
Thanks roofone, I replaced the Periodic Scheduler trigger with Days of the Week trigger and the rule has started working again.
Your observation is right, the rule stopped working when the DST time ended. If your speculation is right (it is most likely), then DST and Periodic Scheduler are not properly implemented in the hub.
I have no idea either why all this behavior...probably due to poor implementation of the DST and Periodic Scheduler (a wild guess)
Agreed -- possibly something quirky under the hood. I've had the periodic trigger exhibit unusual behavior more than once, so I avoid it. It seems fairly redundant anyway.
Glad it's working again.
