Simple Automation Rules throwing groovy errors

[toddunder]

I have a simple automation rule that Seems to not be working and is throwing groovy errors. I wondered if this is a FAQ.

The rule is simply trying to turn on a group at a particular time. The following error keeps showing up in the logs:

app:3002020-11-24 09:19:00.157 errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.setTimeZone() is applicable for argument types: (sun.util.calendar.ZoneInfo) values: [sun.util.calendar.ZoneInfo[id="US/Eastern",offset=-18000000,dstSavings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[id=US/Eastern,offset=-18000000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]]] on line 855 (doAction)

I also note that since the update to 2.2.4.145 the simple automation rules web interface is almost unusable for specific times, since the text boxes for entering hours and minutes are too narrow to actually see the numbers. If you enter them on faith, though, they work out.

any pointers or suggestions for what to investigate??

[toddunder]

Aha, this might be a new bug:

Motion Sensor Rule Issue with Simple Automations

Since upgrading to 2.2.4.139 (I have since updated to 2.2.4.143) I am no longer able to trigger a light switch with a motion sensor. This all worked as expected in 2.2.3.148. I have been triggering lights with Simple Automation Rules. This happens with two brands of motion sensors, one Samsung and one Linkind. The Samsung motion sensor is tied to a GE Zigbee switch and the Linkind is tied to a Lutron switch. Both sensors show active in Hubitat and both lights work from the hubitat interface. Wh…

caused by time restrictions.

when i eliminate the day of the week restriction it works.

i guess i'll wait for a new release to fix this.

[toddunder]

New release does seem to have fixed this.