Having problems with schedules

I’m having problems for about the past week or so with schedules for my home blinds and the PLEG programming. According to the status report, all conditions are being met (true), but the overall condition that controlls that action isn’t functioning.

This morning after sunset, so long as it is a weekday, my blinds should open.

Triggers

Name Description State Last True Last False
tHome Home true 2020-03-04 05:00:00.345 2020-03-03 23:30:00.292

Conditions

Name Options Logic Expression Value Last True (or Last Change) Last False (or Previous Change)
cBlindsOpen cItsDay AND tHome AND cWakeHours false 2020-03-03 15:42:12.346 2020-03-03 22:50:53.192
cItsDay pSunElevation > 0 true 2020-03-04 06:37:39.166 2020-03-03 18:02:00.158
cWakeHours sBlindsOpenWeekDay OR sBlindsOpenWeekEnd true 2020-03-04 06:00:00.150 2020-03-03 18:03:23.157

Schedules

Name On Type On Time On Days Random On Delay Off After Type Off Time Off Days Random Off Delay State Last True Last False
sBlindsOpenWeekDay Day of Week 06:00:00 1,2,3,4,5 None Day of Week +00:00:00t 1,2,3,4,5 None true 2020-03-04 06:00:00.100 2020-03-03 18:03:23.101

They also did not close last night without manual intervention.

There have been two recent firmware updates, and I’m wondering if that is interfering with PLEG programming.

I have other actions that aren’t dependent on schedules that seem to function just fine (cSouthWestSun), which adjusts the blinds so I’m not blinded in the afternoon when the sun is low and glaring in our southern facing windows.

Home Blinds[328].pdf (101.0 KB)

I do have a problem with my blinds as well but is seems to be caused by rfxcom (I have a temp workaround in place). Do you happen to use rfxcom for your blinds?

No, they are straight z-wave blinds from MyIBlinds. Something about scheduling is causing this issue.

The PLEG Core (PLC) may have become “infected”.
THis occurred to me once.
Unistall, then reinstall and see what happens.
Don’t forget to backup/export the PLEG first.
Otherwise, it could be something in the updates that caused this, however it hasn’t been widely reported so it’s pure speculation.