I'm not sure, sorry. The automation I'm trying to get running doesn't work, and so I've been massaging the rules that use the "kitchen automation state" global variable for some time, and I'm not sure when this error cropped up.
However, I suspect the problem is related to the "handle physical switch" rules.
When I hit the switch, the rule doesn't appear to fire, and the variable doesn't change.
[dev:108](http://192.168.0.108/logs/past#dev108)2020-06-20 05:03:02.673 pm [info](http://192.168.0.108/device/edit/108)Living Room Motion Sensor is inactive
[dev:10](http://192.168.0.108/logs/past#dev10)2020-06-20 05:02:45.948 pm [info](http://192.168.0.108/device/edit/10)Cooking lights is 99% [physical]
[dev:10](http://192.168.0.108/logs/past#dev10)2020-06-20 05:02:45.945 pm [info](http://192.168.0.108/device/edit/10)Cooking lights is on [physical]
[dev:206](http://192.168.0.108/logs/past#dev206)2020-06-20 05:02:39.762 pm [info](http://192.168.0.108/device/edit/206)Office Motion Sensor temperature is 72.99°F
...but the error doesn't appear. I did trigger run the rule "action" via the "run actions" button and the rule runs and functions and sets the variable correctly, so that is probably about me still not really understanding how events work.
Given that the rules don't work anyway, my plan was to delete them and start over, so if there's something you'd like me to try to repro, happy to do anything you suggest.