Techman

I've never noticed the (reset?) hole in the back of the eisy. It's not mentioned in any manuals. I have no idea what it does. Maybe one of the forum developers knows. The device in your circuit breaker panel appears to be a surge arrestor, not a powerline bridge. I can't read the model number, so I'm not sure what it is. It's possible that it may be attenuating the Insteon signals.

Not sure what the "notification controller" is. It must be something you installed. if you expand it what are its nodes? Did you previously install any node servers? What type of bridge do you have across your power line legs? Having dual band devices on opposite legs of the power line will act as a bridge.

It sounds like you may have some older single band Insteon devices, the 2472 is single band, the 2472D2 is dual band. You may want to replace older single band devices with the newer dual band devices which will improve the reliability of the Insteon mesh system. If devices can be controlled via the admin console but not programs, then the issue is most likely within your programs.

The Aeotec range extender will do the job. I have one in my system. The only Zwave module that's compatible with the eisy is this one: ZMatter USB: Z-Wave+ & Matter Module for eisy (Beta) - Universal Devices (universal-devices.com) Before you venture into zwave You should get all your Insteon devices and programs debugged. In an earlier post you mentioned putting a paperclip into a hole to reset your eisy. That's the reset method for the Polisy, the EISY uses a button on the front panel for resets. Are you sure you have an EISY?

Have you tried bringing the MS next to the PLM which will eliminate a communication range issue. Also when next to the PLM, put the sensor into the linking mode and do a restore device. Let me know the results. I have several of the sensors linked to the eisy without any issues.

Regarding Zwave - You may need a zwave repeater between your EISY and your door locks unless you have other Zwave line powered devices in your zwave network. Z-Wave: Configuring Range Extenders and Door Locks - Universal Devices, Inc. Wiki (universal-devices.com) I've also attached a PDF file on Zwave installations. Here's the Insteon troubleshooting instructions: INSTEON: Troubleshooting Communications Errors - Universal Devices, Inc. Wiki (universal-devices.com) zw.pdf

The older Togglelinc is a single band device. If you're having problems communicating with it then you either have noise on your powerline which is interfering with the Insteon signal, or the switch is on the opposite leg of your powerline. In either case a dual band device installed close to the Togglelinc should rectify the problem. "Can't determine Insteon Engine" and "Cannot determine Device Link Table Address" means that the PLM is not communicating with the device. If you're manually entering the device address when attempting to link the device, then either the address you entered is incorrect or you have the issue explained above.

The eisy should show motion status once motion has been detected. After motion is detected, and the sensor times out, the node should show OFF. If the sensor is in night only mode you won't get any motion status updates during the day.

It worked for me, I'm on an Eisy

@dbwarner5 @landolfi Remove power from the eisy/polisy for 15 seconds. After it boots up Zwave should be working. Seems that there might be a bug in 5.6.3 that disables Zwave.

@johnnyt The issues I had appear to be a one time event. Everything is currently running smoothly. I don't have any zigbee devices, only Insteon and Zwave.

Yes, you can uncheck the Insteon box, click on save at the bottom of the window. then reboot your system Did you also delete the Insteon devices from the Polisy device tree? Are you running any Zwave devices? Do you plan on using a PLM and Insteon going forward?

The 5th jumper when enabled will put the sensor in night only mode, so you most likely want it disabled. The device status on the admin console will only update when the sensor status changes. You can query it only if it's in the linking mode You may have to wait for the sensor to time out, then be activated before its status will appear in the admin console.

You're correct, the ISY to PLM is a Cat 5 ethernet cable.

@axmill8 To factory reset the PLM you need to unplug it, hold down the set button and continue to hold it down while you plug it in. The PLM will beep, wait until the PLM stops beeping before you let go of the set button Remove power from the PLM and the ISY, then power up PLM first then the ISY. Click on Help | Diagnostics | PLM info. Does it show the PLM as connected?

I had a Zwave issue on my eisy after updating to 5.6.3. Removing power cleared it up. UD is aware and looking into it

What are your firmware and UI versions? I'm not sure what's causing the errors. If you can't get them cleared up then it's best to submit a support ticket.

@AKAPADIA Try removing power from your Polisy for about 15 seconds. That may resolve your issue.

I had a random EISY re-boot two days after updating to 5.6.3. Not sure if this is related to the update. This is the first time this has happened. UPDATE: I just noticed that Zwave on my Zmatter board was unresponsive. I tried a re-boot which had no effect. I removed power from the EISY which corrected the problem. Note: I had previously activated Zigbee (checked the box and saved the configuration), and had then de-activated it prior to the random re-boot and Zwave failure Ticket submitted.

Reboot your eisy. If that doesn't resolve your issue then do a factory reset on one of the devices you're having issues with and then do a restore device. If that works then apply that to your other devices that won't update. It's also possible that you have noise on the powerline which is creating a communication issue between the PLM and your devices.

There's always the possibility that over time the hardware could be upgraded or modified based on part availability, manufacturing, technology advancements, the economy, etc. The smart home technology is an evolving work in progress. I started with X10 about 45 years ago, and now I have the eisy. I'm a happy camper.

@saclarkdoc You mentioned that you loaded an old backup onto your ISY. Prior to migration did you update the ISY to 5.3.4, which is a migration requirement. Preparing for Migration from ISY-994 On your ISY-994 Make sure the ISY-994 is upgraded to 5.3.4, If you are migrating your Z-Wave network You must be using a 500 Series Board in the ISY-994 Make a backup of your Z-Wave network (Admin Console | Z-Wave | Backup) Make a backup of your ISY-994 (Admin Console | File | Backup ISY) Power down your ISY-994 (very important). ISY-994 needs to be powered off because when you migrate, both your ISY-994 and Eisy / Polisy will think they are controlling the Z-Wave network. If you are not migrating your Z-Wave network Make a backup of your ISY-994 (Admin Console | File | Backup ISY)

The short answer is "yes" The firmware is still in development. There are numerous features that have yet to be implemented. Not sure if certification is a factor.

@MarcusD Delete the shortcut and then download the IoX Launcher from the link below. This will place the IoX Launcher on your desktop. https://isy.universal-devices.com/start.jnlp The devices that have the Green 1011 means that there are pending writes to that device. Right click on the device then click on Write Updates

Any chance of posting a list of devices that were successfully updated, without being bricked, along with a huge warning. Is OTA still being refined?