Strange UPB problem

[BobS0327]

You have to go in to the device in UPStart and delete scene 85 from your zone 21.

I had to manually add all my Rain8 UPB zones as Appliance Modules since I it appears that none of the zones can be put into setup mode for discovery by Upstart.  I'm not sure if the above can be done since none of the Rain8 zones can be put into setup mode.  It appears that Upstart can transmit only to the Rain8 zones.  Upstart cannot receive any configuration data.  I don't see any way to delete scene 85 from Rain8 zone 21 if I cannot receive configuration data.  My HLC switches indicate transmit and receive options.
 
I can turn the Rain8 zones on and off from Upstart but I don't know of anyway to receive the configuration and delete the scene.
 
I've attached a image of my upstart.

 

[Desert_AIP]

Try this

Create a blank configuration and run network discovery.

 

[BobS0327]

Try this

Create a blank configuration and run network discovery.

I've already tried Network Discovery.  It only picks up my Leviton HLC switches.  Doesn't pick up any of my Rain8's.
 
I've also done a fairly extensive internet search on this issue and discovered that the HomeSeer folks determined the only way to get Upstart to recognize the Rain8's is to manually add them as appliance modules.  I used their solution and it works for turning the Rain8 zones off and on and getting the status of the Rain8 zones. 
 
My interpretation of the various threads on the Rain8 UPB and Upstart issue is that Upstart does not fully support the Rain8's.  Thus, the reason, Upstart does not get the Rain8 configuration info.

 

[BobS0327]

Now I'm really pulling at straws to resolve this issue.  I wrote a small C# util to delete Link 86 From DID 86 in an attempt to delete the Link from my Rain8 zone 22 which is DID 86.   Fired off the command to the DID and it didn't work.  The code does work since I can turn Rain8 zones off and on with it as well as HLC switches.  Posted the code for review...
 
 
 

using System;
using System.IO.Ports;

class UPBCommunication
{
    static byte[] cr = { 0x0D };
    static    byte[] ctlt = { 0x14 };
    static byte[] ctlw = { 0x17 };
   
   public static void Main()
    {
         SerialPort mySerialPort = new SerialPort("COM4");

        mySerialPort.BaudRate = 4800;
        mySerialPort.Parity = Parity.None;
        mySerialPort.StopBits = StopBits.One;
        mySerialPort.DataBits = 8;
        mySerialPort.Handshake = Handshake.None;
        mySerialPort.DataReceived += new SerialDataReceivedEventHandler(DataReceivedHandler);
        mySerialPort.ReadTimeout = 1500;
        mySerialPort.WriteTimeout = 1500;
        mySerialPort.RtsEnable = false;
        mySerialPort.DtrEnable = true;

         if (!mySerialPort.IsOpen)
                    {
                        mySerialPort.Open();
                    }
                      // Place in message mode
        mySerialPort.Write(ctlw, 0, ctlw.Length);
        mySerialPort.Write("70028E");
        mySerialPort.Write(cr, 0, cr.Length);
        
        mySerialPort.Write(ctlt, 0, ctlt.Length);
                mySerialPort.Write("09040101FF030000EF");  // Start setup mode
                    //  mySerialPort.Write("080001410122642F");
                    mySerialPort.Write(cr, 0, cr.Length);
        
        
        
        mySerialPort.Write(ctlt, 0, ctlt.Length);
        mySerialPort.Write("08040156FF0C563C");  // Delete link  #86 on WGL zone #86 rain 22
                    mySerialPort.Write(cr, 0, cr.Length);
        
        
        
        mySerialPort.Write(ctlt, 0, ctlt.Length);
                mySerialPort.Write("07040101FF04F0");  // End setup mode
                    //  mySerialPort.Write("080001410122642F");
                    mySerialPort.Write(cr, 0, cr.Length);
        
        
        
        mySerialPort.Close();
    }
    
    private static void DataReceivedHandler(
        object sender,
        SerialDataReceivedEventArgs e)
    {
        SerialPort sp = (SerialPort)sender;
        string indata = sp.ReadExisting();
        Console.WriteLine("Data Received:");
        Console.Write(indata);
    }
}

 
 

 

[JonW]

It's been a while since I programmed one of the Rain8's, but as I recall, they use a PIM for communication and don't actually get configured via UPSTART. You have to plug the serial cable from the Rain8 into a PC to configure it.

 

[BobS0327]

It's also been a while since I programmed the Rain8's.  But IIRC,  the WGL configuration software only sets up the network id and the individual device id's (DIDs).  It was very basic  configuration software.  AFAIK, there weren't any options to create and/or delete links (scenes).

 

[Desert_AIP]

If you can't deprogram the link, the kludgy way to do it would be to watch for the link, and send the unit off command to the zone in question.

 

[BobS0327]

If you can't deprogram the link, the kludgy way to do it would be to watch for the link, and send the unit off command to the zone in question.

Yep, it is kludgy but it works!  I guess I'll just have to live with this quirk.
 
Thanx all for your help.

 

[BobS0327]

FYI
 
I sent an email to Warren at WGL concerning this issue. He informed me that currently, a link cannot be deprogrammed (deleted) from a Rain8Pro zone since the firmware would have to be modified to separate the link and direct command function.  He did indicate that it was a good idea and he will probably incorporate this in the next firmware upgrade.
 
 
 

 

[Desert_AIP]

You could also push the Rain 8 unit numbers to the far end of the allocation (make them very high numbers) to prevent the HLC links from triggering action on the Rain 8 zones.

 

[Desert_AIP]

FYI
 
I sent an email to Warren at WGL concerning this issue. He informed me that currently, a link cannot be deprogrammed (deleted) from a Rain8Pro zone since the firmware would have to be modified to separate the link and direct command function.  He did indicate that it was a good idea and he will probably incorporate this in the next firmware upgrade.

 
Good to know, thanks.