Communications

[TheWabit]

Hi Guys,

 

I am trying to better my communications. I don't have big issues but want to improve. It started when I just added and IO Linc. It took awhile for the ISY to add it (in my experience, when there is good comm, it finds it right away). Then when it did add it, the communications with it was hit and miss.

 

I have 2 access points. I have done the "tap" tests many times. I do get some green lights. But what I did was move the PLM/ISY really close to the electrical box. The IO Linc was found right away. My scene tests all succeed but my Hops Left are 1 or 0. What is the current version of the PLM? It has been a few years since I bought mine - I think it like version 1.3?

 

Would it help if I upgraded the PLM?

[Teken]

Hi Guys,

 

I am trying to better my communications. I don't have big issues but want to improve. It started when I just added and IO Linc. It took awhile for the ISY to add it (in my experience, when there is good comm, it finds it right away). Then when it did add it, the communications with it was hit and miss.

 

I have 2 access points. I have done the "tap" tests many times. I do get some green lights. But what I did was move the PLM/ISY really close to the electrical box. The IO Linc was found right away. My scene tests all succeed but my Hops Left are 1 or 0. What is the current version of the PLM? It has been a few years since I bought mine - I think it like version 1.3?

 

Would it help if I upgraded the PLM?

 

If your PLM is a 2413S its a dual band unit. If its a 2412S its a single band unit and should be updated to DB. The latest hardware is 2.XX, which addresses the early two year failures due to dried capacitors. This release also removes the ALL ON / ALL OFF command lines from the device table.

 

As some people have reported insteon devices turning all on by themselves with no ISY awareness of these events. To date there have been a few people reporting back even with this removal of the ALL ON / ALL OFF command line this problem persists.

 

I am unsure how that can be since the actual command line no longer exists. So, have to gather there are other factors at play here. This also does  not address the fact no other controller has ever seen this problem before.

[TheWabit]

I have confirmed it is a 2413S V 1.3

[Teken]

I have confirmed it is a 2413S V 1.3

 

If you have confirmed proper coupling / bridging I would be looking at noise makers / signal suckers instead. As you're aware the I/O Linc is not a dual band device but future releases will be.

 

You can replicate one by adding a AP / Range Extender on to the face of the I/O Linc.

[TheWabit]

Thanks Teken!

 

As I mentioned, I am no longer having issues with that IO Linc since I moved the ISY/PLM next to the electric box BUT It is more of a general concern when I look at error traces/scene tests. I do plan on getting some range extenders. I have about 3600 Sq feet of house.