Hello you awesome brain trust group!
I have a RM routine which has been working great for years, but recently stopped part of its function. I rewrote the routine in an attempt to diagnose it so a screenshot would not be helpful, but here's the jest of the original app:
When time is (sunset -00:30), set Lamp#1, Lamp#2 dimmer level to (50%) over 15 minutes, in 10 sec intervals.
Wait until time is 2200, then
Set Lamp#1, Lamp#2, dimmer level to (0%) over 15 minutes, in 10 second intervals.
No conditions are included at all. This app drives two Shelly Dimmer2 modules imbedded in table lamp bases.
Rule has been great for years as stated, using the "wait" feature allows me to use another rule - "Goodnight" to stop pending routines and turn off the dimmers regardless of time, which prevents the unwanted behavior during nights with an early off to have the lamps turn back on in order to dim down.
Recently, likely at one of the recent platform updates the rule broke: Dimming up works just fine, no way to check the "wait" function but I assume it is fine. When 2200 comes, there is no dimming down at all. No errors in the logs.
I tried nudging the time and re-saving the rule = no joy
I tried changing the after-wait trigger to a mode-change to night = No joy
I tested a completely separate basic rule app, which can only turn off (not dim down over time) the dimmers, and it works fine!!
I edited out the dim-down from the original rule, and wrote a separate RM app to try the dim down function triggered at time, and also at mode change, NO JOY!
Dim up works fine, but in RM, dim down will not work and leaves no trace of failure in the logs.
I am using the only driver available for the Dimmer2's, and the shelly firmware is updated to the latest version.