I have a piston that runs a watering routine in my greenhouse. The relays get out of sync with the ST hub. Some times the relays are on but are dispalyed as “OFF” in the App and vice versa. I know that Z-wave is comunication is bi directional. so can’t figure out what is going wrong.
Setup:
Smartthings HUB/Webcore
2 x Fibaro Switch 2
Network healing has been run after last addition of devices. Routing tables should be OK.
Range extender + pluged-in Z-wave devices are present in the signal path to the greenhouse.
The Fibaro Range test output “Green” (Device is communicating directly with the controller)
2) What is the expected behaviour?
Smartthings/webcore should be able to turn on/off relays according to Pistons programming.
3) What is happening/not happening?
Seems that Relays/Smartthings/Webcore get out of sync. the relays are turned on, but they never register as being on, when the pistons try to turn off the Relay the the state is falsely registered as OFF so the routine is skipped.
**4) Post a Green Snapshot of the piston![image|45x37]
5) Attach logs after turning logging level to Full
7/28/2019, 12:02:06 PM +66ms
+1ms ╔Received event [Mit hjem].time = 1564308126628 with a delay of -563ms
+69ms ║RunTime Analysis CS > 18ms > PS > 30ms > PE > 22ms > CE
+73ms ║Runtime (40832 bytes) successfully initialized in 30ms (v0.3.10e.20190628) (71ms)
+74ms ║╔Execution stage started
+139ms ║║Skipped execution of physical command [Drivhus Switch 1].off([]) because it would make no change to the device. (3ms)
+140ms ║║Executed [Drivhus Switch 1].off (5ms)
+167ms ║╚Execution stage complete. (93ms)
+173ms ║Setting up scheduled job for Sun, Jul 28 2019 @ 12:03:26 PM CEST (in 80.369s), with 3 more jobs pending
+180ms ╚Event processed successfully (180ms)
7/28/2019, 12:01:26 PM +483ms
+1ms ╔Received event [Aeotec Door/Window Sensor Gen5].contact = open with a delay of 82ms
+76ms ║RunTime Analysis CS > 17ms > PS > 36ms > PE > 24ms > CE
+79ms ║Runtime (40853 bytes) successfully initialized in 36ms (v0.3.10e.20190628) (77ms)
+80ms ║╔Execution stage started
+91ms ║║Condition #2 evaluated false (7ms)
+92ms ║║Condition group #1 evaluated false (state did not change) (8ms)
+101ms ║║Condition #6 evaluated false (5ms)
+102ms ║║Condition group #5 evaluated false (state did not change) (7ms)
+108ms ║║Comparison (enum) open changes_to (string) open = true (1ms)
+110ms ║║Cancelling condition #10’s schedules…
+111ms ║║Condition #10 evaluated true (6ms)
+113ms ║║Cancelling condition #9’s schedules…
+114ms ║║Condition group #9 evaluated true (state changed) (9ms)
+116ms ║║Cancelling statement #11’s schedules…
+121ms ║║Executed virtual command [Drivhus Switch 1].wait (1ms)
+123ms ║║Requesting a wake up for Sun, Jul 28 2019 @ 12:03:26 PM CEST (in 120.0s)
+131ms ║╚Execution stage complete. (51ms)
+133ms ║Setting up scheduled job for Sun, Jul 28 2019 @ 12:02:06 PM CEST (in 40.012s), with 4 more jobs pending
+145ms ╚Event processed successfully (144ms)
7/28/2019, 11:59:59 AM +54ms
+0ms ╔Received event [Mit hjem].time = 1564308000000 with a delay of -946ms
+79ms ║RunTime Analysis CS > 21ms > PS > 37ms > PE > 21ms > CE
+82ms ║Runtime (40839 bytes) successfully initialized in 37ms (v0.3.10e.20190628) (80ms)
+83ms ║╔Execution stage started
+146ms ║║Cancelling statement #18’s schedules…
+7567ms ║║Executed physical command [Drivhus Switch 1].on() (7418ms)
+7568ms ║║Executed [Drivhus Switch 1].on (7419ms)
+7572ms ║║Executed virtual command [Drivhus Switch 1].wait (1ms)
+7573ms ║║Requesting a wake up for Sun, Jul 28 2019 @ 12:02:06 PM CEST (in 120.0s)
+7668ms ║╚Execution stage complete. (7585ms)
+7681ms ║Setting up scheduled job for Sun, Jul 28 2019 @ 12:02:06 PM CEST (in 119.894s), with 3 more jobs pending
+7691ms ╚Event processed successfully (7690ms)
Will the Task Cancellation policy have any effect on the Switch off not being run?
I have a second piston checking in on the relays, this piston will flash the the relay on/off and the turn it off again, if the relay is detected as being on. (Detection via a Door window sensor on a float) This piston seems to catch the problem, but I would rather like the first piston to work all the time.
The Piston run the watering cycle 24-36 times a day (depending on temperature) and fails every 1-2 days. so around 1-3% fail rate.