Jump to content

Upgrade Hub to ISY frustrating...


sandpiper

Recommended Posts

Posted (edited)

Hi all,

 

I need some help. I am upgrading my hub installation to the ISY. I could add pretty much all my devices, create my scenes, write my programs, setup port forwarding and get MobiLinc up and running. So far, so good. But I seem to have communication problems.

 

Some questions:

 

1. Occasionally, when writing to a device, ISY complains "cannot communicate". The device is then marked with a red symbol. When I select "query" on that device, the red symbol disappears. Does that mean the write was successful? Or did I just remove the error flag?

 

2. Randomly, some devices do not respond to a scene command.

 

3. I have setup a fanlinc with a keypadlinc. The scenes do not start the fan. The Lamp is coming up after a while, though. Setup should be okay, see attachment. (Lamp is not connected to the KPL load wire)

 

4. I was trying to improve communication with 2 Access Points (#2443). Apparently I can not add them to the ISY - it only says unsupported device. Is this true? I also could not find a matching line in the "Device Type"-Dropdown in the "New Insteon Device"-Window. Are they really not supported?

 

5. I did the 4 tap test and found pretty much all devices (that I can see, some are in boxes or behind the wall) on one leg. Only one device was on the other leg. Some were not responding at all. What does that (no response) tell me?

 

6. Is there an easy way to troubleshoot communication? Like the houselinc function that pings all devices 100 times and shows successful replies? Or where do I start?

 

Thanks for your help!

post-5626-0-88883600-1412531523_thumb.jpg

Edited by sandpiper
Posted

Hi sandpiper,

 

I am so very sorry to hear about the problems you are having. The best thing to do would be to submit a ticket so that we can address all these issues more expeditiously rather than the wait/reply paradigm in the forum. The links are below.

 

With kind regards,

Michel

Posted (edited)

First converting the Hub is a waste of time.   That effort applies to folks not on 120v/60 cycle power.   It does not apply to your situation.  If more RF coverage is needed add a Range Extender.

 

1. Occasionally, when writing to a device, ISY complains "cannot communicate". The device is then marked with a red symbol. When I select "query" on that device, the red symbol disappears. Does that mean the write was successful? Or did I just remove the error flag?

 

No.  That clears the error indicator.   If there are pending updates a green 1011 Icon appears to the left of the node.

 

2. Randomly, some devices do not respond to a scene command.

 

Indicates marginal comm.

 

3. I have setup a fanlinc with a keypadlinc. The scenes do not start the fan. The Lamp is coming up after a while, though. Setup should be okay, see attachment. (Lamp is not connected to the KPL load wire)

 

If the light works and Fan motor does not start it is more likely a wiring issue 

 

4. I was trying to improve communication with 2 Access Points (#2443). Apparently I can not add them to the ISY - it only says unsupported device. Is this true? I also could not find a matching line in the "Device Type"-Dropdown in the "New Insteon Device"-Window. Are they really not supported?

 

Access Point (now called Range Extender) is not added to the ISY.  They have no options, nothing for the ISY to handle.  They are active as soon as plugged in.

 

5. I did the 4 tap test and found pretty much all devices (that I can see, some are in boxes or behind the wall) on one leg. Only one device was on the other leg. Some were not responding at all. What does that (no response) tell me?

 

A Dual Band device that did not respond to the 4 tap Set button test was not in range of the device where the Set button was pressed.

 

6. Is there an easy way to troubleshoot communication? Like the houselinc function that pings all devices 100 times and shows successful replies? Or where do I start?

 

Using HouseLinc is difficult because it adds the same type of links the ISY does.   You can Factory reset a device, add it to HouseLinc, run the test and then do a Restore Device to get it functional under ISY.

 

I would run Tools | Diagnostics | Event Viewer at LEVEL 3.  Issue commands to the device(s) that are in question and look at the Hops Left value.   A message with max hops=3 and hops left=2 is good comm.  hops left=1 is fine if that count is stable.  A hops left count that is frequently changing or a hops left=0 indicate comm issues.  

Edited by LeeG
Posted (edited)

Thanks, Michel! I'll do that, but I would prefer to cover as much as possible today, because I am only once a month at the Inn and I have to leave town tomorrow. I can access the ISY remotely, but as soon as I have to physically do things, it will be difficult.

Lee, I am not converting the hub. The hub is removed, the isy is installed and all devices were added using the delete links-option. Sorry for not being clear.
There is no green 1011 icon next to anything. So the devices should have their correct status, right?

 

No wiring issue on the fan. It worked great with the hub. The fanlinc, though, was one of the devices with comm problems. Is there a way to force an update on all devices?

 

I'll try the event viewer, thanks.

Edited by sandpiper
Posted

In order to initiate the 4-tap test.

Posted (edited)

"There is no green 1011 icon next to anything. So the devices should have their correct status"

 

If there are no green 1011 Icons no updates are pending.   All updates have been written to the devices.  There is no update all devices as once one device has completed its update the ISY moves to the next one marked for update.

 

It is odd that the KPL would turn the Fan On when a Hub is installed but not turn the Fan On when the ISY is installed.

Edited by LeeG
Guest
This topic is now closed to further replies.

×
×
  • Create New...