Announcement

Collapse
No announcement yet.

HELP PLEASE! - Rain8UPB sprinkler controller not responding to HS

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

    HELP PLEASE! - Rain8UPB sprinkler controller not responding to HS

    I would greatly appreciate some advice on why the following isn't working.

    I am attempting to replace my X-10 sprinkler controller with a Rain8UPB sprinkler controller (1 master and 1 expansion module). I have already written all the HS control scripts, so I'd like to keep controlling everything through HS directly and simply substitute one the UPB devices for the X-10 devices. I have about 90 other UPB devices controlled through HS, and they are working well.

    I am running HS 2.0.4.11 on a Dell computer as a 'server'.
    I have the UPB plugin 1.0.3.0 installed.
    I have an SA PIM.


    I used the special rain8upb configuration software to program the two units. I set the master as ID 21 and the expansion as ID 22. This was successful.

    I wired up the two units to an SA serial PIM (I had a spare) as per the instructions, and plugged it into the powerline for testing.

    I ran the special rain8upb demo software on my server. It successfully communicated out from the PIM on my server through the separate PIM to the rain8upb units, turning on and off each of the zones, and could read the status.

    I opened UPStart on my server, ran it in offline mode, created appliance devices for each zone.

    Then I put UPStart back online, tested the 'devices', and could turn each of them on and off, and query status. This was successful. I hooked a voltmeter to the output of these devices, and verified that indeed it was turning the zones on (24 volts) and off (0 volts).

    I exported the UPStart file, and imported into HS. This was successful. The new devices were assigned addresses $1-$16. It picked up the correct device names, and UPB device addresses (161-176).

    Since the Rain8UPB won't send an ACK back, I unchecked "Resend UPB command if no acknowledgement is received" in the UPB plug in configuration.

    So I figured I was home free...but read on...

    When I go to the Status screen for these devices in HS, and click "ON", the lights on the Rain8upb flash - so it's seeing something - but the zones don't turn on.

    So presumably there's some difference between the signals that HS is sending, and what UPStart is sending. It's the same computer (server), the same PIM, and both HS and UPStart can control all other UPB devices without any problem.

    I set the plug-in to "detailed debugging log entries". Attempted to turn $6 ON, I got the following (read from bottom to top):


    4/29/2010 7:32:25 PM - UPB - PIM-->Received PIM NoAck
    4/29/2010 7:32:24 PM - UPB - Waiting for ACK/NAK from PIM
    4/29/2010 7:32:24 PM - UPB - PIM-->Received PIM Accept
    4/29/2010 7:32:24 PM - UPB - PIM<--Sending 0A100AA1FF22640001B5 to PIM (Try # 1)
    4/29/2010 7:32:24 PM - UPB - Ignoring SetIO (Device Housecode) for $6 Cmd: 19 Bright: 100 Data1: 0 Data2: 0 because the device table shows that it is being updated by the plug-in.
    4/29/2010 7:32:24 PM - UPB - In SetIO:$6 Cmd: 19 Bright: 100 Data1: 0 Data2: 0
    4/29/2010 7:32:24 PM - UPB - Setting value for $6
    4/29/2010 7:32:24 PM - UPB - Processing SetIO (Device Housecode) for $6 Cmd: 2 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:32:24 PM - UPB - In SetIO:$6 Cmd: 2 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:32:24 PM - Device Control - Device: Sprinklers Garage Lawn ($6) ON


    Here's what the same output looks like for one of my lights ('36) - this command worked:


    4/29/2010 7:34:43 PM - UPB - PIM-->Received PIM Ack
    4/29/2010 7:34:43 PM - UPB - Waiting for ACK/NAK from PIM
    4/29/2010 7:34:43 PM - UPB - PIM-->Received PIM Accept
    4/29/2010 7:34:43 PM - UPB - PIM<--Sending 0A100A24FF2264000132 to PIM (Try # 1)
    4/29/2010 7:34:42 PM - UPB - Ignoring SetIO (Device Housecode) for `36 Cmd: 19 Bright: 100 Data1: 0 Data2: 0 because the device table shows that it is being updated by the plug-in.
    4/29/2010 7:34:42 PM - UPB - In SetIO:`36 Cmd: 19 Bright: 100 Data1: 0 Data2: 0
    4/29/2010 7:34:42 PM - UPB - Setting value for `36
    4/29/2010 7:34:42 PM - UPB - Processing SetIO (Device Housecode) for `36 Cmd: 2 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:34:42 PM - UPB - In SetIO:`36 Cmd: 2 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:34:42 PM - Device Control - Device: Basement Bsmnt Back Rm (`36) ON


    I have no idea what any of the above means, but the results look very similar for the device that works and the one that doesn't.

    Looking at the configuration details for device $6, I see the following:

    Device Name: Garage Lawn
    Device Type: UPB Load/Light Controller
    Reference ID 2865
    Status 2 = ON
    Value 100
    String
    Supports Status True
    Dimmable False
    Interface UPB
    Misc IO Settings LC ID: 161 CH: 0 NCH: 1 KIND: 3
    Misc Settings Status Set Notify, Value Set Notify

    The initialization of the UPB plugin in the HS log is as follows:

    4/29/2010 7:27:11 PM - Plug-In - Finished initializing plug-in UPB
    4/29/2010 7:27:11 PM - UPB - Exit InitIO
    4/29/2010 7:27:11 PM - UPB - ----------------------
    4/29/2010 7:27:11 PM - UPB - (Message Mode Enabled)
    4/29/2010 7:27:11 PM - UPB - PIM Options: 11110011
    4/29/2010 7:27:11 PM - UPB - Firmware Version: 10.0
    4/29/2010 7:27:11 PM - UPB - Product ID: 032
    4/29/2010 7:27:11 PM - UPB - Manufacturer ID: 04
    4/29/2010 7:27:11 PM - UPB - UPB Version: 1
    4/29/2010 7:27:11 PM - UPB - UPB Options: 00000000
    4/29/2010 7:27:11 PM - UPB - Module ID: 32
    4/29/2010 7:27:11 PM - UPB - Network ID: FF
    4/29/2010 7:27:11 PM - UPB - --- PIM IFORMATION ---
    4/29/2010 7:27:10 PM - UPB - PIM-->Received PIM Reg Report (70F300FFFFFFFFFFFFFFFFFFFFFFFFFF)
    4/29/2010 7:27:10 PM - UPB - PIM<--Sending 700F81 to PIM (Try # 1)
    4/29/2010 7:27:10 PM - UPB - PIM-->Received PIM Reg Report (00FF3212340001000400321000000000)
    4/29/2010 7:27:10 PM - UPB - PIM<--Sending 000FF1 to PIM (Try # 1)
    4/29/2010 7:27:10 PM - UPB - Done starting communication Threads, requesting PIM reg report...
    4/29/2010 7:27:09 PM - UPB - In TimedPollThread
    4/29/2010 7:27:09 PM - UPB - In WriteSerialThread
    4/29/2010 7:27:09 PM - UPB - In ReadSerialThread
    4/29/2010 7:27:09 PM - UPB - Starting PIM Read/Write Threads...
    4/29/2010 7:27:09 PM - UPB - Initializing UPB PIM on COM port 1
    4/29/2010 7:27:09 PM - UPB - 115 Matching HS device records were found and updated for the device database.
    4/29/2010 7:27:06 PM - UPB - [HCM] Registered house code '$' as a new code for device class 'LoadHouseCode' because an existing HomeSeer device was found using it.
    4/29/2010 7:27:06 PM - UPB - [HCM] There are existing 'LoadHouseCode' class HomeSeer devices currently using the previously allocated base house code of: '`'.
    4/29/2010 7:27:06 PM - UPB - 17 Matching HS device records were found and updated for the link database.
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #17 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#17 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #14 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#14 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #16 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#16 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #15 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#15 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #13 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#13 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #12 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#12 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #11 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#11 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #10 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#10 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #9 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#9 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #8 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#8 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #7 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#7 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #6 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#6 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #5 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#5 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #4 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#4 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #3 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#3 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #2 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#2 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - Ignoring SetIO for #1 Cmd: 19 Bright: 0 because the global Ignore SetIO flag is set.
    4/29/2010 7:27:06 PM - UPB - In SetIO:#1 Cmd: 19 Bright: 0 Data1: 0 Data2: 0
    4/29/2010 7:27:06 PM - UPB - [HCM] There are existing 'LinkHouseCode' class HomeSeer devices currently using the previously allocated base house code of: '#'.
    4/29/2010 7:27:06 PM - UPB - Done Parsing UPStart Export file.
    4/29/2010 7:27:06 PM - UPB - Done Checking for suspect UPStart export records.
    4/29/2010 7:27:06 PM - UPB - Repairing I/O module record, should only be 3 inputs
    4/29/2010 7:27:06 PM - UPB - Repairing I/O module record, should only be 3 inputs
    4/29/2010 7:27:06 PM - UPB - Checking for suspect UPStart export records...
    4/29/2010 7:27:06 PM - UPB - Parsing UPStart Export file...
    4/29/2010 7:27:06 PM - UPB - Attempting to load UPStart export file: C:\Program Files\UPB\logs\Kaplan House.upe



    I'm stumped. Does anyone have some thoughts as to what's going on??

    #2
    Last I knew the Rain8UPB Homeseer plugin was not compatible with the Rain8UPB. With mcsSprinklers I do not use the HS UPB plugin interface to drive the Rain8UPB, but use UPB logic internal to mcsSprinklers. Jon and I discussed making a passthrough available via the UPB plugin, but it never happened.

    Comment


      #3
      Michael -

      I purchased the Standard edition of mcsSprinlers, installed it with a separate PIM, and everything works like a charm. It does everything I need and more. Nice work on this package and thanks for the tip!

      Comment


        #4
        Excellent. A lot of user feedback with good ideas has made mcsSprinklers what it is today.

        Comment

        Working...
        X