Wait not working - Solved - user error!


#1

The following piston detects when the hot water has been boosted (switched on manually) then waits 60 mins before turning it off and cancelling the timer, which is reactivated at midnight. This used to work with the hive plugin, but following the deprication of that, I’ve used the HADB plugin. Watching the piston run, it seems ok, the countdown timer starts, but then it just runs into the next command turning the boost & schedule off

20/08/2024, 14:46:07 +151ms
+1ms ╔Received event [Hotwater Boost].valueStr = off with a delay of 132ms, canQueue: true, calledMyself: false
+15ms ║Runtime (8131 bytes) initialized 13 LockT > 0ms > r9T > 1ms > pistonT > 0ms (first state access 11 m:1 1 12) (v0.3.114.20240115_HE)
+16ms ║╔Execution stage started
+20ms ║║Previous value changed from on (string) to off (string)}
+21ms ║║Comparison (string) off changes_to (string) on = false (1ms)
+22ms ║║Condition #2 evaluated false (3ms)
+23ms ║║Cancel condition #1’s schedules…10 (st:11)
+23ms ║║Condition group #1 evaluated false (condition changed) (5ms)
+26ms ║╚Execution stage complete. (9ms)
+69ms ║Setting up scheduled job for Wed, Aug 21 2024 @ 12:00:00 AM BST (in 33232809ms)
+70ms ╚Event processed successfully (70ms)
20/08/2024, 14:45:52 +93ms
+2ms ╔Received event [Hotwater Boost].valueStr = on with a delay of 109ms, canQueue: true, calledMyself: false
+13ms ║Runtime (8067 bytes) initialized 11 LockT > 0ms > r9T > 1ms > pistonT > 0ms (first state access 8 m:2 2 9) (v0.3.114.20240115_HE)
+14ms ║╔Execution stage started
+23ms ║║Previous value changed from off (string) to on (string)}
+23ms ║║Comparison (string) on changes_to (string) on = true (1ms)
+25ms ║║Condition #2 evaluated true (8ms)
+26ms ║║Comparison (integer) 14 is_inside_of_range (integer) 0 … (integer) 14 = true (1ms)
+27ms ║║Condition #3 evaluated true (2ms)
+28ms ║║Condition group #1 evaluated true (condition changed) (11ms)
+111ms ║║Executed virtual command sendPushNotification (81ms)
+113ms ║║Executed virtual command setVariable (1ms)
+116ms ║║Executed virtual command [Home Assistant Device Bridge (192.168.0.75)].wait [3600000] (1ms)
+118ms ║║Requesting wake up at Tue, Aug 20 2024 @ 3:45:52 PM BST (in 3599999ms) for 10 (st:11)
+120ms ║╚Execution stage complete. (106ms)
+184ms ║Setting up scheduled job for Tue, Aug 20 2024 @ 3:45:52 PM BST (in 3599968ms), with 1 more job pending
+184ms ╚Event processed successfully (183ms)


#2

Solved….

There was another test piston running which was also firing when the heating mode changed and setting the schedule to eco.