Techman

RE: ISY and Motion Sensor II. Just saw this post on the Smarthome website. Can anyone confirm this? Smarthome Reply: You are able to add this device by Insteon ID number and instead of using Auto Discover, you would want to select the device option: [10.01] (2842-222) INSTEON Motion Sensor. This will allow the same functionality as the previous model 2842-222 Insteon Motion Sensor. Posted on 6/28/2017

Smarthome was recently sold and they are in the process of transitioning. It will probably be several months before we know exactly what direction they will be taking. . Hopefully the new owners will take a more open approach in reaching out to its developers and end users.

Thanks for the clarification. I'm hopeful that the new ownership will be more accommodating. I just found out that Smarthome is moving to a new location in Irvine, once they get settled in maybe they'll be more open in working with developers.

It appears that your signal quality has improved based on the number of hops left versus the first scene test.

UDI has marginal support (motion only) for the sensor in firmware 4.6.2. It's supposed to be fully supported in the 5.x.x release. I would hold off buying them until they're fully supported.

You scene test appears to not have any errors. Take a physical look at all the lights in your scene to verify that they all turned off after the test turned them on. The scene does indicate marginal communications in several of the entries such as the one below: Tue 07/25/2017 03:38:51 PM : [std-Cleanup Ack] 13.4C.71-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 As Paul suggested, upgrading your devices to dual band should greatly improve your communication problem.

Renaldo, I believe the 2476S is a single band device, so you lose the advantage of RF Almost all LED bulbs have a driver circuit. If the circuit in one of the bulbs failed it could interfere with the Insteon OFF signal You can run a Scene Test by right clicking on the scene. This will give you a detailed readout of any issues. Post the results after you run the test. As BrianH mentioned above it can also be a problem with another device. The latest Dual Band devices have updated firmware and hardware which helps improve the network reliability.

Here's a tutorial on Insteon communication http://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors

What type of load is connected to the problem switch. it's possible that once the load is on it's causing interference on the powerline.

Do you have any newer dual band Insteon modules such a an on/off module, or a dual band lamplinc module that you could move around in an attempt to improve the Insteon signal?

If the Thermostat is showing firmware v.00 in the ISY then it's possible that the ISY and the thermostat aren't properly coupled. Try doing a diagnostics / compare link table on the thermostat. You can also try a restore device on the thermostat

The power line is divided into two legs. The PLM signal need to have access to both legs in order for devices on the leg opposite from the PLM to work. You may have to add two range extenders, one on each side of the leg, in order to bridge the Insteon signals. It's also possible that there is signal interference on the leg the PLM is currently plugged into. How many dual band devices do you have? Are you currently using any range extenders or dual band plug in devices such as on/off modules?

What is the ISY firmware version, is the admin console the same version as your ISY firmware?

When you do a replace device it has to be like for like. You'll need to delete the device, do a factory reset on the device, then reinstall it

Thank you. The big problem is that Smarlabs is constantly updating their firmware and doesn't provide release notes. What makes sense today may not be the case tomorrow. Maybe the new owners will be a little more sympatric to our frustrations.

IndyMike, Thanks for the follow up. The developers guide I have is dated 2009 and doesn't include IC2S commands and shows the EA link as reserved. Michel, If you agree with this assessment could the EA link records be configured to not show in the diagnostics? Techman

the conundrum just got a bit smaller, but hasn't gone away I found this post from 2015 http://forum.universal-devices.com/topic/15336-device-links-table-corrupteds/ I just found an old version of the Developers guide. At the time the guide was printed the EA link wasn't being used. Seems it was reserved for I2CS. Anyone have a current version of the guide?

What is an "EA" link record. They frequently show up during a link record diagnostic / compare. My recollection is that they can be ignored, but I still don't know what they represent or what creates them.

if you delete a device from the ISY it also gets removed from programs, however the program will contain a null where the device name was so the program won't function properly and might cause issues.

It's possible if the problems only show up when the light is on. You'll have to go through the process off elimination in this order 1. Factory reset / restore device 2. Try a different bulb. 3. Replace the device My guess is that's it's probably a failing component in the device.

Being that both your bulbs are high output they probably generate some heat. Over time the heat can degrade the driver circuit.

JSP0511, Most LED bulbs contain driver circuits. It's possible for their components to fail after being in service for years. If your problems persist after the factory reset / restore then I would suggest swapping out the bulbs. Do the bulbs have adequate air flow around them?.

JSP0511, I've had similar problems with KPLs. Usually a factory reset followed by a restore device clears up the problem A power fail or power surge also seems to wreak havoc with KPLs Another possibility is that the load is creating noise on the powerline. What type of bulbs are you controlling?

Take a look at the ISY error log. Any SMTP errors should show up.

Most likely What's the version and date code on the PLM?