Announcement

Collapse
No announcement yet.

Rain8 X10 control not functioing after installation of HS3Pro

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

  • Rain8 X10 control not functioing after installation of HS3Pro


    Hi Michael,

    It has been many years since I have posted but since retiring I am upgrading from your very old MCS SW.

    I have install HS3Pro and MCS and find that the Rain8 Net units are functioning but the Rain8X10 unit is not.

    Below is the log entries. It appears that the X10 I1 On and OFF commands are not sent?

    I would have thought that the CAPI Handler would have received the I1 command versus the name of the valve.

    I tried to upload the INI file but was prevented.

    Note that if I send the I1 On and Off commands through a key pad the rain 8 unit functions fine.

    There are also some other MCS messages that may provide info below:

    I was one of your earlier beta testers and corresponded with you many time in the past.

    Many Thanks, Rick

    ----------------------------------------------------------
    Sep-28 3:34:24 PM Device Control Device: X10 Piazza Plants South to Off (0) by/from: CAPI Control Handler
    Sep-28 3:34:17 PM Device Control Device: X10 Piazza Plants South to Off (0) by/from: CAPI Control Handler
    Sep-28 3:34:16 PM mcsSprinklers CheckManualControlIndex was outside the bounds of the array.
    Sep-28 3:31:32 PM Device Control Device: X10 Piazza Plants South to On (100) by/from: CAPI Control Handler
    Sep-28 3:29:39 PM Warning File does not exist: C:\Program Files (x86)\HomeSeer HS3\html\mcsSprinklers\images\images\no.gif
    Sep-28 3:29:36 PM Info System connected to MyHS Service successfully with license ID 661500.
    Sep-28 3:29:36 PM Info System connected to MyHS Service, waiting for acknowledge...
    Sep-28 3:29:36 PM Startup Start up complete.
    Sep-28 3:29:36 PM Info No device issues found
    Sep-28 3:29:36 PM Info Checking device parent child relationships...
    Sep-28 3:29:36 PM Startup HSSentry is disabled in Setup, sentry will not be started.
    Sep-28 3:29:36 PM TTS Speak ():Welcome to Home-Seer
    Sep-28 3:29:36 PM Startup (Startup.vb script) Scripting is OK and is now running Startup.vb
    Sep-28 3:29:36 PM Startup Starting Event Scheduler...
    Sep-28 3:29:36 PM Speaker Speaker host added, Name: HOMESECURITY Instance: Default IP address: 127.0.0.1
    Sep-28 3:29:35 PM Startup Running the startup script Startup.vb
    Sep-28 3:29:35 PM Startup Starting Find service...
    Sep-28 3:29:35 PM Startup Updater services starting...
    Sep-28 3:29:35 PM Database Opening (Mode=Read/Write) up HomeSeer Energy database C:\Program Files (x86)\HomeSeer HS3\Data\Energy\Energy.hsd
    Sep-28 3:29:35 PM Speech Listening for remote speaker connections on port 10401
    Sep-28 3:29:35 PM Startup Initializing Speaker Client Interface
    Sep-28 3:29:35 PM Startup Start automation engine...
    Sep-28 3:29:35 PM Startup HStouch server started, waiting for clients to connect.
    Sep-28 3:29:35 PM HSTouch Server Server started on port 10200
    Sep-28 3:29:35 PM Plug-In Finished initializing plug-in MCSSPRINKLERSP
    Sep-28 3:29:35 PM Starting Plug-In MCSSPRINKLERSP loaded in 3769 milliseconds
    Sep-28 3:29:35 PM Starting Plug-In Plugin MCSSPRINKLERSP started successfully in 3571 milliseconds
    Sep-28 3:29:33 PM mcsSprinklers Version 2.19.11.0 | V2.19.11.0/2.19.11.0 (Professional) Copyright 2004-2019 mcsSolutions Registered with Homeseer
    Sep-28 3:29:31 PM Starting Plug-In Initializing plugin MCSSPRINKLERSP ...
    Sep-28 3:29:31 PM Info Plugin MCSSPRINKLERSP has connected. IP:127.0.0.1:55980
    Sep-28 3:29:31 PM Plug-In Interface MCSSPRINKLERSP is running as a trial, 30 days remaining.


  • #2
    Which X10 interface are you using?
    -Rupp
    sigpic

    Comment


    • #3
      Ti103 through the RFXCOM
      Sep-28 3:29:31 PM Plug-In Finished initializing plug-in RFXCOM
      Sep-28 3:29:31 PM Starting Plug-In RFXCOM loaded in 520 milliseconds
      Sep-28 3:29:31 PM RFXCOM 40 (RecRxChar) receiver #1 successfully initialized to 32 bit mode
      Sep-28 3:29:31 PM Starting Plug-In Plugin RFXCOM started successfully in 205 milliseconds
      Sep-28 3:29:31 PM RFXCOM 40 (InitVariables) No correct Telegram Token available
      Sep-28 3:29:31 PM RFXCOM 40 (InitIO) RFXCOM version is:30.0.0.40
      Sep-28 3:29:31 PM Starting Plug-In Initializing plugin RFXCOM ...
      Sep-28 3:29:31 PM Info Plugin RFXCOM has connected. IP:127.0.0.1:55978
      Sep-28 3:29:31 PM Plug-In Interface RFXCOM is running as a trial, 29 days remaining.
      Sep-28 3:29:31 PM Plug-In Finished initializing plug-in X10
      Sep-28 3:29:31 PM Starting Plug-In X10 loaded in 418 milliseconds
      Sep-28 3:29:31 PM Starting Plug-In Plugin X10 started successfully in 79 milliseconds
      Sep-28 3:29:31 PM Info TI103 Plug-in, Version 3.0.36
      Sep-28 3:29:31 PM ACT TI103 Calling initIO in TI103 with port:COM7
      Sep-28 3:29:31 PM Starting Plug-In Initializing plugin X10 ...
      Sep-28 3:29:30 PM Info Plugin X10 has connected. IP:127.0.0.1:55976
      Sep-28 3:29:30 PM Startup Initializing Plug-Ins
      Sep-28 3:29:30 PM Plug-In Found plug-in: X10, version: 3.0.0.36
      Sep-28 3:29:30 PM Plug-In Found plug-in: RFXCOM, version: 30.0.0.40

      Comment


      • #4
        The easiest way to proceed forward is with your \Config\mcsSprinklers.ini file and a debug file for when you tried to control an X10 valve. The debug is enabled from the Others page and the file is in \data\mcsSprinklers. The Other page has a control to write the debug file cache that should be used. You can email to mcsSolutions at CenturyTel dot net.

        Comment


        • #5
          Another consideration is that the mcsSprinklers X10 is based on the CM11A interface. With the TI103 it will look like a HS Virtual Device in the mcsSprinklers setup. For HS devices the following is the code executed when issuing a valve control (sState = on or off)

          Code:
                      For Each CAPIcontrol As HomeSeerAPI.CAPIControl In oHS.CAPIGetControl(iRef) '5/15/2014
          
                          If CAPIcontrol.Label.ToLower = sState.ToLower Then
                              oHS.CAPIControlHandler(CAPIcontrol)
                              If rtbDebugLog Then
                                  hsWritelog(PLUGIN_DEBUG, "SendHS Status Returned for " & sDC & " is " & oHS.DeviceStatus(sDC).ToString)
                              End If
                              Exit Sub ' 10/11/14 no longer set DeviceStatus if CAPI successful
                          End If
                      Next
          
                      If rtbDebugLog Then
                          hsWritelog(PLUGIN_DEBUG, "SendHS NoCAPIControl for " & sDC & "=" & iHSCommand.ToString)
                      End If
                      oHS.SetDeviceStatus(sDC, iHSCommand) 'Value(sDC, nCommand)

          Comment


          • #6
            I looked at your email prior to the last post. It confirmed that you are setup to use X10 managed by the HS X10 plugin. In the debug I see at the top the HSEvent to acknowledge that I1 changed to 2 (ON). Below that I see where the CAPI control handler was called and I1 status was ON. The logging sequence is reversed but that is likley just an artifact of a multi-threaded system. From my perspective everything is working as expected
            Code:
            9/28/2019 8:05:28 PM 637052979284236206 | mcsSprinklers Debug | Commanding I1 to 2, is an Ailias=False,LastChange=9/28/2019 8:05:28 PM, Status=2
            9/28/2019 8:05:28 PM 637052979284236206 | mcsSprinklers Debug | Rain8 X10-2 status check Current=2, new=2
            9/28/2019 8:05:28 PM 637052979284236206 | mcsSprinklers Debug | Zone Manual On=False, zones ubound=16, alias zone=1, StatusRespone=False, iX10CommandedZone=-1, iX10CommandedStatus=-1, iStatus=2, iZone=1
            
            
            9/28/2019 8:05:28 PM 637052979284236206 | mcsSprinklers Debug | LogAction INSERT INTO log (SampleDate,Device,Status) VALUES('2019-09-28 20:05:28','I1','External ON')
            9/28/2019 8:05:28 PM 637052979284548687 | mcsSprinklers Debug | SendItNow I1=ON , DictionaryExists=True, Type=2, Interface=2
            9/28/2019 8:05:28 PM 637052979284548687 | mcsSprinklers Debug | SendHS Device I1=2
            9/28/2019 8:05:28 PM 637052979284548687 | mcsSprinklers Debug | SendHS Status Returned for I1 is 2
            Later I see the I1 OFF command with a similar behavior with status and control being reflecting 3 (OFF).

            Code:
            9/28/2019 8:05:39 PM 637052979394531777 | mcsSprinklers Debug | Commanding I1 to 3, is an Ailias=False,LastChange=9/28/2019 8:05:39 PM, Status=3
            9/28/2019 8:05:39 PM 637052979394531777 | mcsSprinklers Debug | Rain8 X10-2 status check Current=3, new=3
            9/28/2019 8:05:39 PM 637052979394531777 | mcsSprinklers Debug | Zone Manual On=False, zones ubound=16, alias zone=1, StatusRespone=False, iX10CommandedZone=-1, iX10CommandedStatus=-1, iStatus=3, iZone=1
            9/28/2019 8:05:39 PM 637052979394531777 | mcsSprinklers Debug | LogAction INSERT INTO log (SampleDate,Device,Status) VALUES('2019-09-28 20:05:39','I1','External OFF')
            9/28/2019 8:05:39 PM 637052979397006001 | mcsSprinklers Debug | SendItNow I1=OFF , DictionaryExists=True, Type=2, Interface=2
            9/28/2019 8:05:39 PM 637052979397006001 | mcsSprinklers Debug | SendHS Device I1=3
            9/28/2019 8:05:39 PM 637052979397161945 | mcsSprinklers Debug | SendHS Status Returned for I1 is 3
            From your original post the log shows that CAPI control of ON and OFF are being sent and these correspond to values of 100 and 0. The "Device Control" message comes from HS and is exactly what I would expect. HS expands the device in the log to include location and name for easier user recognition vs. the Device Reference. Ref and not Location & Name do not go to the CAPI handler.. I think the next step is looking into the plugin that is supporting the TI103 as it looks as if it is not responding to the CAPI control values of 100/On and 0/Off. Since you are able to control the valve via keypad it indicates that the TI103 handler responds to this input source. (i.e. from powerline or from RF depending upon what keypad you are using).

            The I1 and I2 devices should have been created by the RFXCOM plugin which means you should have a HS Device Management On/Off buttons. These buttons, when used, should provide the same CAPI interface to RFXCOM as is being done by mcsSprinklers.

            The red text in the HS log indicates that whatever email was setup in HS did not have the correct security credentials. The email was initiated trying to upload the debug file. You should confirm your email settings in HS as HS is doing the email transaction.




            Comment


            • #7
              Ok I think I found the problem. The I Valves are now functioning.

              What I found was that the RAIN8 x10 I Valves created by
              mcsSprinklers were not created properly. In the device manger window they were identified as I-1 through I-8. However I check the X10 tab for these and found that they were configured as X10 devices A-1 through A-8. I corrected these and restarted and things seem to be right. I though that mcsSprinklers would have created the correct X10 devices?

              Comment


              • #8
                It has been a long time since I worked with X10 and I am surprised that mcsSprinklers would create the devices if they are not managing the interface. I would expect the RFXCOM plugin to have created them as that is the one that is defining the CAPI interface to control them. I will look to see what I have implemented.

                Comment


                • #9
                  I looked at the X10 setup and what I observed is that mcsSprinklers first looks to see if the X10 device exists in HS and if not then it creates it. It assumes it will belong to the HS3 X10 plugin.. There are other consistency checks later when the device is assigned to a valve on the Wiring page. In my testing, when no X10 devices existed it did create the correct device code in HS, but may not be functional depending upon the CAPI definition.

                  To avoid the issues then whatever pluign is managing X10 should have already created its devices before mcsSprinklers is requested to perform irrigation with those X10 devices.

                  Comment

                  Working...
                  X