Unusual OFF Behaviour

[beerygaz]

Hi Michael, I'm experiencing some unusual behaviour when clicking "Pause Area" from the Area Touch interface.

Front & Back Lawn are part of the same area. Front Lawn ran fine, when Back Lawn started to run I pressed "Pause Area" on the Area Touch page, it seemed to stop "Front Lawn" even though "Back Lawn" was the currently active Zone in the area. As you can see from the log, the Back Lawn then started up again by itself, and I pressed "Pause" again, same issue.

I had to "Pause Program" to get it to actually stop. Thoughts? What more detail can I send through to try and get to the bottom of this?

23/09/2018 07:30:02 PM	A1:R1	Sprinklers Front Lawn	ON
23/09/2018 07:40:03 PM	A1:R1	Sprinklers Front Lawn	OFF
23/09/2018 07:42:02 PM	A1:R3	Sprinklers Back Lawn	ON
23/09/2018 07:43:02 PM	A1:R1	Sprinklers Front Lawn	OFF
23/09/2018 07:44:02 PM	A1:R3	Sprinklers Back Lawn	ON
23/09/2018 07:44:48 PM	A1:R1	Sprinklers Front Lawn	OFF
23/09/2018 07:46:02 PM	A1:R3	Sprinklers Back Lawn	ON
23/09/2018 07:46:39 PM	A1:R1	Sprinklers Front Lawn	OFF

[Michael McSharry]

Pause control is a site-level control unless I forgot something. Never use the Area touch page. The general debug will contain the sceduling logic to understand what is happening.

[beerygaz]

Hi Michael, I removed all of my config, INI filed, database, etc and started again from scratch. I'm still seeing very strange behaviour.

Zones set to start at 03:00 but are starting at 02:59
Zones are coming on but the OFF command seems to be going to the wrong valve.
An area seems to get stuck in a loop, constantly running rather than following the correct schedule. What should have been a 10 minute cycle turned into a 3 hour cycle!!
The plugin created all of the house code "R" devices for the valves (but these are never updated)
The plugin didn't seem to create any of the house code "S" devices for the status data - how do I tell the plugin to try and recreate these devices?

27/09/2018 02:59:00 AM	A1:R1	Rain8 Lawn - Front	ON
27/09/2018 03:09:01 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 03:09:01 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 03:19:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 03:19:01 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 03:29:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 03:29:01 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 03:39:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 03:39:01 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 03:49:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 03:49:00 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 03:59:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 03:59:00 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 04:09:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 04:09:00 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 04:19:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 04:19:00 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 04:29:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 04:29:00 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 04:39:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 04:39:00 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 04:49:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 04:49:00 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 04:59:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 04:59:01 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 05:09:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 05:09:01 AM	A1:R3	Rain8 Lawn - Back	ON
27/09/2018 05:19:00 AM	A1:R1	Rain8 Lawn - Front	OFF
27/09/2018 05:19:01 AM	A1:R3	Rain8 Lawn - Back	ON

[Michael McSharry]

Shown below is the debug for valve control. The storyline is:
Command Valve 3 ON for 10 minutes
Get Status but EtherRain indicates to wait
4 seconds later get status again
ri status indicates that valve index 0 was last one completed, but by this time the valve 3 program should be running and ri should indicate 1 because 0 and 1 have completed and 2 is busy
mcsSprinklers records status as valve 0 is running (R1)
Since R1 was running it was the valve that is turned off. R3 status never showed ON so that is why it was rescheduled at 10 minute intervals.

27/09/2018 02:59:00 AM 636736139403576819 | mcsSprinklers Debug | ExecX10 R1=on for 10
27/09/2018 03:09:01 AM 636736145412380503 | mcsSprinklers Debug | ExecX10 R1=off for 0
27/09/2018 03:09:01 AM 636736145418690864 | mcsSprinklers Debug | ExecX10 R3=on for 10
27/09/2018 03:19:00 AM 636736151409383512 | mcsSprinklers Debug | ExecX10 R1=off for 0
27/09/2018 03:19:01 AM 636736151415183844 | mcsSprinklers Debug | ExecX10 R3=on for 10
27/09/2018 03:29:00 AM 636736157407896608 | mcsSprinklers Debug | ExecX10 R1=off for 0
27/09/2018 03:29:01 AM 636736157413466926 | mcsSprinklers Debug | ExecX10 R3=on for 10

27/09/2018 03:09:02 AM 636736145424801214 | mcsSprinklers Debug | SendEtherCommand{0} http://192.168.1.33:80/result.cgi?xi=0:0:0:10:0:0:0:0:0, GetStatus=True
27/09/2018 03:09:02 AM 636736145427081344 | mcsSprinklers Debug | SendEtherCommand{0} Response <html>    <head>    </head>    <body>        EtherRain Device Status <br>        un:EtherRain1        ma: 0.4.163.1.1.193  <br>        ac:  <br>        os: WT <br>        cs: OK <br>        rz: OK <br>        ri: 0 <br>        rn: 0 <br>    </body></html>
27/09/2018 03:09:06 AM 636736145463703439 | mcsSprinklers Debug | SendEtherCommand{0} http://192.168.1.33:80/result.cgi?xs, GetStatus=True
27/09/2018 03:09:06 AM 636736145466263585 | mcsSprinklers Debug | SendEtherCommand{0} Response <html>    <head>    </head>    <body>        EtherRain Device Status <br>        un:EtherRain1        ma: 0.4.163.1.1.193  <br>        ac:  <br>        os: BZ <br>        cs: OK <br>        rz: OK <br>        ri: 0 <br>        rn: 0 <br>    </body></html>
27/09/2018 03:19:01 AM 636736151418084010 | mcsSprinklers Debug | SendEtherCommand{0} Response <html>    <head>    </head>    <body>        EtherRain Device Status <br>        un:EtherRain1        ma: 0.4.163.1.1.193  <br>        ac:  <br>        os: RD <br>        cs: OK <br>        rz: OK <br>        ri: 2 <br>        rn: 0 <br>    </body></html>
27/09/2018 03:19:05 AM 636736151459986407 | mcsSprinklers Debug | SendEtherCommand{0} http://192.168.1.33:80/result.cgi?xs, GetStatus=True
27/09/2018 03:19:06 AM 636736151462536553 | mcsSprinklers Debug | SendEtherCommand{0} Response <html>    <head>    </head>    <body>        EtherRain Device Status <br>        un:EtherRain1        ma: 0.4.163.1.1.193  <br>        ac:  <br>        os: BZ <br>        cs: OK <br>        rz: OK <br>        ri: 0 <br>        rn: 0 <br>    </body></html>

I was not able to reproduce the 1 minute early start

Valve and Status devices are created at plugin startup. Look for errors in the HS Log. The Debug from startup may have other info, but more likely in the HS log. Also assure that R & S are selected on the Other page for the device house codes.

I have changed the method to determine which valve is ON in the build at http://mcsSprinklers.com/mcsSprinklers_21881.zip. Confirm it does solve this part of your issues. I'm also guessing somewhat of your setup. Having mcsSprinklers.ini would help.

[beerygaz]

Hi Michael, sorry for the delay, I wanted to run a full cycle before I confirmed anything. The new build you posted is working like a charm, I don't see any more of the erratic OFF commands. I'm still not seeing HS3 devices changing status (weather, area status, water meters, etc.) so i'm going to try and remove them all and change house code and see if I can get the plugin to re-create them.

The most important thing is the valves are all working as expected - thank very much for your help.

[Michael McSharry]

I,ll put this version in Updater. When I run this or prior version with my Etherrain I get the same result. Not clear what is different about yours. It works so don’t need to look any further until the next anomaly appears.