Conditions fail


Since the latest upgrade, most of my piston conditions seem to fail on their evaluation. Below is a piston example - this used to work flawlessly until recently.

The piston triggers if any of the devices in the IF statement turn off, it waits 10 seconds and then turns the respective device back on.

Now the event fires and registers as ‘off’ and seems to be a type mismatch? This was never an issue and the condition is developed using the wizard - HELP? I have 80+ pistons with lots of conditions and they are now malfunctioning at various conditions.

8/26/2019, 7:59:49 AM +582ms
+2ms ╔Received event [Gym Homekit Hub].switch = off with a delay of 188ms
+152ms ║RunTime Analysis CS > 20ms > PS > 81ms > PE > 50ms > CE
+154ms ║Runtime (40822 bytes) successfully initialized in 81ms (v0.3.10f.20190822) (151ms)
+155ms ║╔Execution stage started
+191ms ║║Comparison (enum) off changes_to (string) off = false (0ms)
+194ms ║║Condition #5 evaluated false (34ms)
+195ms ║║Condition group #1 evaluated false (state did not change) (36ms)
+223ms ║╚Execution stage complete. (68ms)
+236ms ╚Event processed successfully (235ms)


Please see related discussion here where we are debugging a similar report.


Thanks. Yes, this is a dupe and unfortunately my doing as I opened up the other issue which seems to have the concentration of traffic. If possible, please close this one as to avoid confusion?

closed #4