matapan

Here is a screenshot:

Has anyone encountered this behavior with adding a new ZWave device? Recently, I purchased a ZWave On/Off Module with Energy Monitoring capabilities. I enrolled the device as I have done with other, older ZWave modules. The process went without a hitch. After a few minutes, I noticed that the device entries all had the green <Writing> status next to each entry. For Insteon devices, there is an explicit command for finish writing updates to a device. What are you supposed to do for ZWave devices? I have tried leaving the device alone and waiting for the <Writing> status to go away. When it didn't go away, I tried putting the plugin device into pairing mode. No change. Does anyone know what's supposed to happen here? Or is this device just something to return for another device from a different company? Thanks.

There is a very comprehensive post by danu1964 on this forum describing the repair of a 2413PLM that is very helpful. I have a 2413S v.1.0 PLM which is a little different from the later PLM versions. At position C7, there are two 10uF 63V capacitors connected in series and there appears to be no position C13. Has anyone here recapped one of these PLMs? Should I recap it the way it is with new parts?

How are ZWave parameters exposed on the ISY? Especially in a script. Thanks!

I'm using the Synchronics to change the state of devices linked to the Synchronic in a scene. How does one perform the same task with the Zooz smart plug? I read the manual for the plug and to me it didn't seem there was an equivalent function in the smart plug.

The Zooz Smart Plug is a ZWave 800 device. Will this device work with the ISY994i ZWave 500 board?

Out of curiosity, is there anyone offering a service for repairing failed Insteon modules? Insteon initially had a wide range of module offerings, some of the modules were very useful, but maybe a little esoteric for the general audience. The new Insteon company has understandably pared down their module offerings. The Synchrolinc is one of the modules I like because of its load sensing capabilities. It would be great to keep some of these older modules going and not have to use a device with a different protocol like Z-Wave or Zigbee to use the same functionality. At least this is my initial preference.

Thanks Brian, I will try this out shortly.

Hi there, Are there any instructions on how to install this I/O controller on an ISY994i? I have one of these but no SmartenIt brand PLM. Just an Insteon 2413S. I checked the wiki but didn't find any special notes on the installation process for this device. When you add a 2413S PLM, the ISY registers it as an "Unsupported Device". I read the lengthy post on a user's issue restoring his setup with one of these devices already.

I think MS2 is 2844-222. At least this is what shows online.

Sorry, I meant a 2420M and 2842-222.

Does anyone know if there are any differences between these two motion sensor models? Is this merely a model number change, or is it more than this? Thanks!

Thanks to all that have responded to my post. What does a device failure look like? Versus a line noise induced issue? If a scene test has a device which consistently fails, even after device restore and it doesn't appear to be a line noise related issue, does this point to a device failure? When a scene test has members which all fail, what does that mean? I have scenes which appears to work fine under normal use conditions whose members fail the scene test. How does one interpret this result?

Thanks Techman. What does it mean when phases are not correctly bridged? in my setup, I have a main panel with two auxillary panels connected to the main. I had the electrician install a phase bridging device on the main panel. I assumed after doing this there would be no issues with devices connected to different phases. I have two dual band Switchlincs in a two gang box, one flashing green and the other flashing red. Even if they are on separate phases I expected both devices to be flashing green. can you help me understand how to interpret this?

So I experienced a blackout recently. The Insteon modules are all probably from the 2015-2017 era. They are all dual band devices. The scenes work as they should. Are you suggesting the modules have somehow failed?

The serial PLM's are available once again on Insteon.com, while the USB PLM's are out of stock. I'm planning on acquiring several PLM's as backups for my system. I'd like recommendations on whether it is better to purchase a new PLM or to refurbish old ones (dual band of course). There is an eBay seller who purportedly refurbishes PLM's to be much more reliable by using tighter spec components. The refurbish service costs more than buying a new PLM. But if the PLM is going to be rock solid for say, 7 years - maybe it's worth it. What do people on this forum think?

Thanks to the responders to my recent posts about communication issues related to scenes and a wireless motion sensor. I've glanced through some of the documents available for troubleshooting communication issues. I have a few questions: 1. Does noise on one circuit affect communications throughout the entire house or just segments of it? I'm asking this question because some scenes pass the scene test without any issues, while others fail completely, with all devices failing. Yet, some of the scenes that fail the scene test work perfectly. I also have scenes where one device out of two or three fail in the test. What exactly does that mean? 2. If the noise affects the entire house, then I can understand the idea of turning all the breakers off in a house and turning them back on one by one and running scene tests that are in the areas where the breakers are on. What if it's mixed though? What is one device in a scene is on a circuit turned off? 3. How can you tell if there is a communication failure due to noise vs. a PLM failure? I thought dual band communication was supposed to make things like scene tests more reliable by offering a different avenue for communication between source and destination. Is this the case? 4. Are there patterns of failure visible in device communication logs that can be identified and characterized through automation? Is this type of failure analysis ripe for an AI model to simplify the process of diagnosing communication failures and fixing them? (i.e. communication failure from faulty devices, noise or a bad PLM - provide input to the model on the devices on each circuit.) My current process for addressing communication problems is to find any plugs with switching power supplies connected to it and adding a filter module, restoring devices that have failed the scene test, and observing if I've made headway into reducing communication failures. Thanks.

Does anyone have any recommendations for a 15 amp rated plug in filter? Advanced Control Technologies made one but they seemed to have closed their doors.

Hi there, I have a Filterlinc whose Filtered plug was dead. No power when the module was plugged in. I opened up the case and did a continuity test on the fuse, which was open. Do I replace the bad fuse with a 10 amp unit? The label states that the filtered circuit handles a 10 amp maximum load. Are there other things that go bad in a filter module?

How reliable is the scene test feature? I tested a scene twice and received back two completely different results. One where all devices in the scene failed, and one where all devices in the same scene succeeded. I did find that installing more Filterlincs for some other circuits helped rectify communication issues. How can one tell between a failing PLM with communication problems caused by a noisy line? Thanks!

Here are some screenshots of results:

Can anyone recommend the best way to troubleshoot link creation when one creates a scene? I have many scenes where there are multiple devices which act as as controllers for one device which acts as a responder. Once I have created the scene, I noticed that some of the controlling devices don't reflect the state of the scene. For example, if I have a Switchlinc dimmer which acts as a controller and responder in a scene, with a button on two Keypadlincs which act as controllers, I expect that when the Keypadlinc button is turned on, the button on the other Keypadlinc acting as a controller is also turned on, as well as the Switchlinc dimmer. With recently created scenes, I noticed that the state of the button or paddle which is not pressed is not updated with the current scene state. Older scenes I have created are correctly updated. Any thoughts on the best way to troubleshoot this? Thanks!

Thanks for your suggestions. I was not close to the PLM when I attempted to link the motion sensor. I tried linking the motion sensor using both methods, one described in the original post and one where I selected Start Linking and put the sensor into linking mode. The linking process in each case did not appear to initiate and the Admin Console went promptly back to a Ready state. I also tried factory resetting the motion sensor and tried to link the device. I looked at the communication events while attempting to link manually. It appears that the motion sensor was already added previously. Is this the expected behavior?

I tried adding an Insteon motion sensor model 2420 tonight and couldn't do it. From the Admin Console, I selected Link Management/Link a Sensor/Motion Sensor After accepting the next dialog with the instructions on putting the motion sensor in setup mode, I entered the device address, a device name, and the device type (2420M), then pressed OK. The console didn't do anything other than to return to a waiting state after this. No device created. Status of the controller is Ready. On a separate note, I have noticed that not all the links are created when creating scenes where I have 3 or more devices with a several controller and a responder. The observed behavior of this failure is when the device states are not synced amongst the controlling devices. I'm not sure how to troubleshoot this. Any ideas? Thanks.

Geddy: The information provided in the link was in context with the version of MacOS at the time. The Privacy and Security settings tab has been revamped in Mac OS Sequoia 15.3.2. There is a Developer Tools subtab which you can specify apps which can circumvent the security restrictions but the jnlp file cannot be selected to be added. The jnlp file is grayed out.