Techman

Have you tried unplugging the Zmatter/zwave dongle from the eisy then plugging it back in while the eisy is powered up. It's possible that the usb port is not seeing the dongle.

@wmcneil Where did you find the ZSE70 800LR, it's not listed on the Zooz site.

Select HTML as the message format For a carriage return add "<BR>" to the end of the line

Being that you moved the switches from the ISY 300 Zwave you may have some of the previous links stored in the devices. Try doing a EXCLUDE DEVICE, then factory reset the device, and include it. If it then displays properly in the admin console you'll have to do that that with the rest of your devices. Let me know the results.

Add the switches to the scene as controllers, which will also allow them to act as responders. I'm not sure about adding them with S2. If they're not related to a security system/device You could probably add them as S0. I would assume that they would both need to have the same security configuration.

It could be a range issue with marginal communications. It could be an interferance issue, it's difficult to say. Set your event viewer to level 3 and then send a command on a device you're having issues with and post the event viewer results.

If your zwave devices are 10 years old then they're most likely use the 300 series chipset. Do you have a model number of the GE switch? By having 300 series devices in your network i believe that the network would revert to 300 rather than taking advantage of the Zmatter's 700 chipset and features. The 300 chipset has a slower speed and less range than the 500, 700 and 800 series. You might want to pickup a 700 series repeater, and rebuild your network by first installing the repeater and then adding the other devices.

When you rebuild a Zwave network you should add the non-battery powered device that's closest to the eisy first, then add the other a/c powered devices. The battery operated devices should be added last. This ensures that the Zwave mesh network is properly built. It's possible that your Zwave network has some communication issues. Here's info on repairing your zwave network. Is your eisy zwave module away from obstructions? Are your zwave devices 300, 500 or 700 series? ISY Users:V5:ZWave:Advanced User Guide:NodeMenu - Universal Devices, Inc. Wiki (universal-devices.com) Zwave network repair.pdf

When you migrated to the EISY the names of your Z-wave devices may have changed. You need to check each program that contains a Z-wave device. It's possible that some of your Z-wave devices didn't migrate properly. Prior to migration did you do a zwave backup? What was your z-wave controlller on the device you migrated from?

If you think you're still covered under warranty you can try submitting a support ticket: https://www.universal-devices.com/my-tickets

@peterathans Take a look at this Z-wave article from the UDI Wiki. ISY Users:V5:ZWave:Advanced User Guide:Scenes - Universal Devices, Inc. Wiki (universal-devices.com)

Is the ISY using the router's guest network? You might try selecting DHCP on the ISY, assumming that the router is also supporting DHCP UDI discontinued support for the ISY994 effective last month. The ISY has since been replaced with the EISY, a more powerful platform. See the attached link. Final Goodbye to ISY994 Series - Universal Devices - News (universal-devices.com)

I've not used the MS2, but a long ramp up/down time might be draining the battery. Try setting the ramp time to default to see if that makes a differance.

At this point you could either try another converter cable or a new USB PLM. I doubt that the issue is with the eisy.

Under the Configuration tab on the eisy, do you have the box for Insteon support checked? What is your eisy firmware and UI? Have you tried removing power from the PLM and removing and resetting the USB cable at the PLM?

It's possible that the serial to USB cable is defective

Have you changed any of the parameters in the 2nd sensor? What is the 2nd sensor controlling? You could try a factory reset, restore device on the 2nd sensor. The batteries should last as long as the 1st sensor unless something is constantly triggering the sensor.

@guyhamelin Is the green led on the PLM lit? How old is the PLM?

It's under SETTINGS | FIRMWARE Scroll down towards the bottom of the window

@MrEstateManager Your PLM link count of 65 is too low for the number of devices you have.. Most likely when you switched PLMs your link table didn't fully populate Is your USB plm connected to the eisy with a standard USB cable? What is the result when you right click on a device with red explanation marks, then do a restore device? Your firmware and UI are outdated. Before you do any more tweaking, update both as the current firmware contains numerous bug fixes. Be sure to clear your java cache (check all 3 boxes), after the firmware update, then download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp

Being that you've tweaked a lot of things it's difficult to assess exactly what the problem is. How are you interfacing the Serial PLM with the eisy? What PLM is currently attached to the eisy? When you click on HELP | ABOUT what is your firmware and UI versions When you click on TOOLS | DIAGNOSTICS | PLM Info, what does it show? When you click on TOOLS | DIAGNOSTICS | SHOW PLM LINKS TABLE, what is the link table count?

When you cleared your java cache did you check all 3 boxes? Did you download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp When you changed PLMs did you follow the "replace plm procedure", see attached Replace PLM.pdf

Did you folllow the replace PLM procedure (see attached) when you switched over to the USB PLM? What PLM is currently attached to the eisy? Have you tried "RESTORE DEVICE" on the device(s) that are not communicating? Replace PLM.pdf

You may have a corrupt config file. Clear your windows temporary files, you want to delete the temporary files in the attached screenshot. If that doesn't fix your issue then it's best to submit a support ticket https://www.universal-devices.com/my-tickets

After you upgraded to 5.8.4 did you clear your java cache and download the IoX Launcher? Also make sure there are no unusual characters in your scene name