Techman

The firmware version shows up in the device window in the admin console. the current firmware version is v.47 Current hardware version is v1.6 . Your sensors were manufactured in 2014 and 2015. The versions now shipping were made in 2019.

I noticed that when I turn a device, that's a controller in a scene, on or off not all of the devices in that scene respond accordingly. If I turn the device on or off from the admin console all the devices in the scene properly respond.

If you bought them off Ebay there's a very good chance they're used, so it's best to factory reset them. After the reset do a restore device which will rewrite the link tables stored in your controller to the device(s). What is the 4 diget date code, hardware and firmware verson of the sensor(s) The factory reset instructions are attached Factory reset.pdf

@gweempose I also get at least 6 months, usually longer. Check your sensor options to make sure the sensor isn't reporting heartbeat or orther data more than it should. You may want to try factory resetting the sensor(s) Did you buy them direct from Insteon?

With the 6 button KPL, If you want the ON/OFF buttons led to turn off when the the load is off then set the on/off button to "Non toggle Off"

The Insteon firmware doesn't have an option to set the led brightness on the individual KPL buttons. @maxnorth When you set the backlight level be sure to click on the "Blacklight" button after setting your levels. Make sure you Keypad button option is set to "toggle. If you set the levels to 1/0 the KPL leds should turn off when the button is off

The eisy should automatically connect to the router after the router reboots. Are you using a reserved address for the eisy, it's possible that you have an address conflict in the router. Why are you rebooting your router so often?

Yes, that's what I was referring to. Have you tried excluding and then including the sensor. When including it keep it in close proximity to your controller. What controller, Zwave dongle and firmware are you running?

Correct, the solution is in this thread, posted on January 26th.

@EJones01 The solution is in this thread Help with Aeotec Trisensor Setup - ZMatter - Universal Devices Forum (universal-devices.com)

If you have, or want to add, zwave then take a look at these: ZOOZ ZEN17 UNIVERSAL RELAY – ZOOZ (getzooz.com) Zooz ZEN16 MultiRelay – ZOOZ (getzooz.com)

Check your ethernet cables and connections between the router and the eisy. If they're OK then you should probably open a support ticket.

Yours is an isolated case. Have you tried rebooting your router. Are you usinng a reserved address for ther eisy in your router?

During your previous install some of the links may not have been written. Glad you're back in business.

One last thing to try, put the MS into the linking mode then from the tools menu run a Device link table diagnostic. After the links poipulate click on compare to see if you have any mismatched links

All dual band devices act as repeaters. When you installed the MS II did you link it using the "Sensors" "Motion Sensor II" option in the linking menu What PLM are you using? The insteon signal emits from the PLM not the EISY. Are both sides of your power line bridged, you can verify that using the 4 tap test (see attached) 4 Tap test.pdf

Being that the MS is working when close to the controller, the problem is not with the MS. You need a dual band plug-in device closer to the MS to act as a repeater. between the MS and the EISY.

@twired You didn't previously mention that you swapped out you PLM. Did you follow the replace modem instructions (see attached). This was written for the ISY994 but also applies to the newer controllers. You propably don't have to delete your devices, you can probably just do a replace PLM procedure. Replace Modem.pdf

Try doing a factory reset on the MS, then a restore device. Keep the MS fairly close to the Eisy during the restore

You can run a Scene Diagnostic (Tools | Diagnostic | Scene test) This may pinpoint any issues with the scene. Post a screenshot of the results. It's also possible that there was a glitch durning migration which corrupted the link tables. Another option is to run a link table diagnostic on a device that is not supposed to be triggered by the scene (Tools | Diagnostic | Show device link Table) After the table populates, click on Compare which will show if there are any mismatched links between the Eisy and the Device.

You can reloicate the Zmatter dongle using a standare USB cable You can find info and pictures here: UD Store - Universal Devices (universal-devices.com)

What EISY firmware version are you running Are you using the MS1 or MS II Have you tried replacing the battery. If you move the MS closer to the EISY does it then correctly show the status?

It sounds like some of the link tables in your devices may have been corrupted prior to the migration Do a restrore device for the devices in the scenes(s) your're having a problem with. What was your ISY994 firmware version? Was your firmware backup current prior to the migration? Did you uddate the EISY firmware prior to migration?

With the EISY it's either LAN or onboard WiFi, it doesn't support both protocols at the same time.

@Brian H Does the PLM's firmware reside on the main board or the daughter board? In theory, could you swap a serial daughter board with a USB daughter board?