Announcement

Collapse
No announcement yet.

GoControl - Program Not Functioning

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • GoControl - Program Not Functioning

    Hi Michael,

    I'm running mcsSprinklers Pro v2.19.2.0 on HS3 v3.0.0.531 and just installed a GoControl WI15VZ-1. HS3 and mcsSprinklers communicates just fine with the device and I'm able to manually turn on and off all 4 of my valves.

    I have 3 areas setup:

    Area 1 has 2 valves [GOC 1 Valve 1] and [GOC 1 Valve 2] and is programmed to run for 5 minutes, one after the other, once every 3 days at 06:00
    Area 2 has 1 valve [GOC 1 Valve 3] and is programmed to run twice every day for 5 minutes at 07:00 and 19:00.
    Area 3 has 1 valve [GOC1 Valve 4] and is programmed to run four times once a week for 59 minutes each beginning at 00:00 on Monday.

    My issues is this:

    The first valve of Area 1 [GOC 1 Valve 1] turns on as expected and then turns off after 5 minutes. One minute later the same valve turns on for another 5 minutes and then turns off again. This sequence is repeated continuously until I manually shut down mcsSprinklers. It never advances to the second valve [GOC 1 Valve 2]. I found this out the hard way this morning when my lawn over-watered and had water flowing out my side yard and down the driveway.

    I'm attaching some of my configuration screens, mcsSprinklers.ini and a snippet of the HS3 log showing the valves being controlled.

    Any thoughts on what might be going on here and what the fix may be?

    Thanks in advance,
    Craig
    Attached Files

  • #2
    The easiest way for me to investigate is with the General Debug file. It is enabled from the bottom of the Other Page. The data will be located at \HTML\mcsSprinklers\Data in a .txt file with date stamp embedded. Include sufficient duration so the described behavior is captured.

    Comment


    • #3
      Thanks Michael, the attached debug log represents a little more than an hour of operation. For most of the time, valve 1 cycled on for 5 minutes then turned off. At one point, valve 3 ran for 5 minutes but only once. It also looks like the program started to open valves 2 and 4 at different times but shut them off immediately. I will leave the program run for the balance of the afternoon... with the water input to the valves turned off until I can sort this out.

      Almost forgot.... I started the program by selecting Start All Manual from the Zone Status page.

      Thanks,
      Craig
      Attached Files

      Comment


      • #4
        I started looking at the debug and see where the status for being watered today is not being updated so I tried to run your mcsSprinklers.ini file. The only thing I ever did with Wave was this gocontrol unit about 9 months ago and I forgot how to get the root zwave address of the unit. I looked at the node info page of Zwave plugin and see the screenshot, but it does not contain the address. How do I get it?

        Click image for larger version

Name:	Capture.PNG
Views:	95
Size:	85.7 KB
ID:	1303366

        Comment


        • #5
          Hi Michael, the Root Address is a combination of your Home ID and the ZWave Node number. I suspect yours is C54BC2D6-003, assuming your GoControl Zwave Controller is node 3.

          You can also get the complete address by going into Device Management and viewing the Address for the device. A picture of mine is attached.

          Click image for larger version

Name:	In Device Manager.JPG
Views:	90
Size:	49.1 KB
ID:	1303372

          Comment


          • #6
            It looks like HS has forgotten my GoControl. There are no devices with an address similar to a zwave one. I tried pushing the button on the GoControl for about 10 seconds but that did not make any difference. What is the process for HS to learn the GoControl irrigation controller?

            Comment


            • #7
              If you had it working previously and it no longer sees it, you may need to remove the node from HS3 and then reset the GoControl and then re-add it back to the network. The steps to reset and add to the network are on page 3 of the attached manual.
              Attached Files

              Comment


              • #8
                Thank You for the manual. I was able to reset it and remove it and now when powered it has a red status light. Click on the button and the light flashes for awhile and then returns to steady red. How do I tell HS that it needs to learn the new device? The Zwave plugin now shows the 3rd node with red text "No command class information available" so it does recognize that something has changed. I restarted HS and it mad no difference. I also looked at the zwave2.db and zwave.ini and neither seemed to have anything about the GoControl unit.

                Comment


                • #9
                  If the GoControl recognizes HS3 as it's hub, the light should be solid green. You Add/Include the GoControl as one of the Actions: from the ZWave Controller Managment page. Press the GoControl button once after you've started the Add/Include Node process from within HS3. If all goes well, it should create 4 devices: Irrigation Controller, Irrigation Valve, Irrigation Notification and Irrigation System Enable. The Irrigation Controller address (from the Device Management page) is the address you plug into mcsSprinklers.

                  Comment


                  • #10
                    Thank you with the Zwave help. Is there a reference document that comes with HS that describes the process you outlined for adding nodes?

                    The issue was specific to GoControl in toggling between auto and manual modes. Seems like I should have seen this with the original development. It is corrected in http://mcsSprinklers.com/mcsSprinkle...19_4_2_HS3.zip where the desired HSPI_MCSSPRINKLERSP.exe or HSPI_MCSSPRINKLERSS.exe along with mcsSprinklers_2009.dll contain the update. If you confirm it works as you desire then I will submit to updater.

                    Comment


                    • #11
                      Hi Michael, I'll check out the update this evening and report back. Here is a link from the Homeseer Help Desk for setting up ZWave and adding nodes, etc. Hope this helps.

                      https://helpdesk.homeseer.com/category/268-z-wave

                      Thanks,
                      Craig

                      Comment


                      • #12
                        Hi Michael, I had a chance to run it and it still isn't working correctly... but isn't running the same zone over and over again like it was before. I left the areas and zones setup the way they were but changed all the run times to 1 minute so I could observe the results more quickly.

                        The results were:

                        07:40:52 Area 1 Zone 1: Ran for 1 minute and then turned off

                        07:41:54 Area 1 Zone 2: Attempted to run then immediately shut off.

                        07:41:54 Area 2 Zone 3: Ran for 1 minute and then turned off.

                        07:42:56 Area 3 Zone 4: Attempted to run then immediately shut off.

                        07:42:56 Area 2 Zone 3: Attempted to run then immediately shut off.

                        07:43:00 Area 2 Zone 3: Ran for a minute and then turned off.


                        I would have expected Valve 1 to run for a minute, shut off and then Valve 2 to run for another minute. Then Valve 3 for a minute and so on. Attached are the mcsSprinklers.ini and debug files.
                        Attached Files

                        Comment


                        • #13
                          I looked at the debug and see the following. Of particular interest is the HS Event callback (Lines starting with "Commanding". The first line shows R1 being turned on (2). All is good with this one where HS is informing that R1 is now on (2).

                          The second line is when mcsSprinklers determines it is time to turn off R1. mcsSprinklers delivers a R1 OFF followed shortly by a R2 ON. There was a single HS callback that only reported R2 status, but it reported the last change of R1 to off (3) for the status of the R2 device. This indicates that there are timing issues between HS, Zwave, GoControl, and mcsSprinklers.

                          I did not see this behavior when I evaluated both manual and auto control a day or two ago using your .ini. I will try again today. Since it does seem to be timing I may not be able to replicate, but will give it a try.

                          It is also odd that this was fully functional 9 months ago and nothing has changed in this area of mcsSprinklers code and there are others that have used this configuration last year successfully. I may need to do something in mcsSprinklers to give the other components additional time to migrate through their states and provide a good feedback.


                          5/9/2019 7:40:53 AM 636929844535068909 | mcsSprinklers Debug | Commanding R1 to 2, is an Ailias=False,LastChange=5/9/2019 7:40:52 AM, Status=2
                          5/9/2019 7:41:54 AM 636929845141441974 | mcsSprinklers Debug | CommonExecX10, Rain8NetUPB HouseCode=R, Device=R1, State=OFF, rtoX10CollectionCount=0, iType=9
                          5/9/2019 7:41:54 AM 636929845142221975 | mcsSprinklers Debug | CommonExecX10, Rain8NetUPB HouseCode=R, Device=R2, State=ON, rtoX10CollectionCount=0, iType=9
                          5/9/2019 7:41:54 AM 636929845142689976 | mcsSprinklers Debug | Commanding R2 to 3, is an Ailias=False,LastChange=5/9/2019 7:41:54 AM, Status=2

                          5/9/2019 7:41:54 AM 636929845142845977 | mcsSprinklers Debug | CommonExecX10, Rain8NetUPB HouseCode=R, Device=R2, State=OFF, rtoX10CollectionCount=0, iType=9
                          5/9/2019 7:41:54 AM 636929845143625978 | mcsSprinklers Debug | Commanding R2 to 2, is an Ailias=False,LastChange=5/9/2019 7:41:54 AM, Status=3
                          5/9/2019 7:41:54 AM 636929845144405979 | mcsSprinklers Debug | Commanding R2 to 3, is an Ailias=False,LastChange=5/9/2019 7:41:54 AM, Status=2
                          5/9/2019 7:41:55 AM 636929845150645990 | mcsSprinklers Debug | Commanding R3 to 2, is an Ailias=False,LastChange=5/9/2019 7:41:54 AM, Status=2
                          5/9/2019 7:42:56 AM 636929845762947066 | mcsSprinklers Debug | Commanding R4 to 3, is an Ailias=False,LastChange=5/9/2019 7:42:56 AM, Status=2
                          5/9/2019 7:42:56 AM 636929845763883067 | mcsSprinklers Debug | Commanding R4 to 2, is an Ailias=False,LastChange=5/9/2019 7:42:56 AM, Status=3
                          5/9/2019 7:42:56 AM 636929845764663069 | mcsSprinklers Debug | Commanding R4 to 3, is an Ailias=False,LastChange=5/9/2019 7:42:56 AM, Status=2

                          Comment


                          • #14
                            I updated the program times to be two minutes and collected data with good results. What is different in my case is HS is returning status of Q1, which is the zwave device "Irrigation Valve" for the OFF change while it returns the R1 (mcsSprinklers device) for the ON change. It did not deliver a R1 OFF status or a Q1 ON status. Same for the second zone R2. I see in your debug some Q59 devices. IS Q59 one of the GoControl devices?

                            I am running the test with a remote connection between a Windows I7 running the plugin and an old Windows laptop running HS with the Zwave plugin and interface. In my case there is more wall-clock time between when a valve is commanded OFF to when the next on is commanded ON vs. the data in your log. This slower environment may be providing sufficient time for handshakes to complete.

                            5/9/2019 5:35:00 PM 636930201006054909 | mcsSprinklers Debug | CommonExecX10, Rain8NetUPB HouseCode=R, Device=R1, State=ON, rtoX10CollectionCount=0, iType=9
                            5/9/2019 5:35:00 PM 636930201007304980 | mcsSprinklers Debug | Commanding R1 to 2, is an Ailias=False,LastChange=5/9/2019 5:35:00 PM, Status=2
                            5/9/2019 5:37:00 PM 636930202208033658 | mcsSprinklers Debug | CommonExecX10, Rain8NetUPB HouseCode=R, Device=R1, State=OFF, rtoX10CollectionCount=0, iType=9
                            5/9/2019 5:37:00 PM 636930202209423738 | mcsSprinklers Debug | Commanding Q1 to 3, is an Ailias=False,LastChange=5/9/2019 5:36:51 PM, Status=17

                            5/9/2019 5:37:01 PM 636930202210613806 | mcsSprinklers Debug | CommonExecX10, Rain8NetUPB HouseCode=R, Device=R2, State=ON, rtoX10CollectionCount=0, iType=9
                            5/9/2019 5:37:01 PM 636930202212103891 | mcsSprinklers Debug | Commanding R2 to 2, is an Ailias=False,LastChange=5/9/2019 5:37:01 PM, Status=2
                            5/9/2019 5:39:00 PM 636930203408752335 | mcsSprinklers Debug | CommonExecX10, Rain8NetUPB HouseCode=R, Device=R2, State=OFF, rtoX10CollectionCount=0, iType=9
                            5/9/2019 5:39:01 PM 636930203410022408 | mcsSprinklers Debug | Commanding Q1 to 3, is an Ailias=False,LastChange=5/9/2019 5:38:51 PM, Status=17

                            Comment


                            • #15
                              Yes, Q59 is the GoControl Irrigation Valve. Same as your Q1. In my case, HS3 is running on a HomeTroller S6.

                              Comment

                              Working...
                              X