Techman

Yes, you can add the remote button to your existing scene. Put the remote into the linking mode then add the button to the existing scene as a controller

If your remote is the 4 scene model then you shoiuld create a scene, add the device you want to control into the scene as a controller, then add button A of the remote into the scene as a controller. You'll need to create new scenes for each of the other 3 remote buttons following the steps above.

To use a battery operated remote you need to put the remote into the linking mode and then add the remote button to the scene as a controller. Depening on the remote you're using you may have to add two remote buttons to the scene, one for on and one for off. What version of the remote are you using ?

You need to create a scene and put button A in the scene as a controller. Put the light in the scene as a controller. Button A will then be able to turn the light on or off, no need for button B. If the light is turned on manually button A will light. In the scene you'll need to set the on level for the light, and ramp rate.

Is the keypad a 6 button or an 8 button KPL? Is the light hardwired (connected to the red load wire) to the keypad? If not is anything connected to the load wire?

In your device tree there's a red explanation mark which means that the EISY is unable to communicate with the device. Try moving the device closer to the eisy then right click on the device and then click on rewrite device links. It's possible that your device is out of range from the zmatter dongle. If that's the case you may have to add a zigbee repeater such as this one: Range Extender Zi - Aeotec

Assuming you're on an eisy, try: eisy.local:3000/dashboard

In addition to @paulbates suggestion, no the link tables cannot be manually edited. If you suspect the link tables are mismatched you can run a device link table diagnostic, then a compare. That will show if the controller link tables match those stored in the PLM. If there's a mismatch, then a restore device will rewrite the PLM link tables so they match those stored in the controller.

In the admin console, is the battery voltage displayed? If so then you could use a program, see attached

Powering down the Polisy clears the memory. When there are issues it seems that powering down proves to be more beneficial that a (warm) reboot.

@ShawnW It appears that you PLM, even though it's "old", seems to be working. One other thing you can try, assuming you're on a Windows computer, is removing power from the Polisy, then deleting the Polisy temporary files which are located in the folder C:\Users\<your user name>\AppData\Local\Temp Delete the following files, then boot up the Polisy. If that doesn't fix things then open a support ticket.

@ShawnW I would first focus on your PLM. Run a PLM link count. Post the results Is the green led on your PLM lit? Run a restore device on one of your Insteon devices, does it complete without errors? How old is your PLM, and what is its hardware version?

From the config file: Release notes for: 5.8.0 - 01/01/2024 Fixed system crash (for Insteon users) Fixed subscription causing crash when bombarded Misc bug fixes Integration of sqlite database for recording events/property changes Node property history database - disabled by default

Being that's it's a brand new product it's possible that the current controller firmware isn't programmed to recognize it. You should submit a support ticket: https://www.universal-devices.com/my-tickets

What UD controller do you have? Do you currently have Zwave? An alternative might be just to buy game tickets.

The router should have nothing to do with the Zmatter dongle or Insteon devices. It's probably best to move the EISY away from the router in order to avoid RF interference. You should also not plug your PLM into an outlket that servicing other electronics as electricial devices can interfere with the PLM Insteon signals. It was most likely not necessary to factory reset you EISY as the problem appears to be some type of interference and not the eisy itself. You should also do an update packages on the EISY as there was an update to fix a few bugs. After the update your EISY firmware will still shop as 5.7.1.

Here's the cable

It should work, the MS draws very little current

It was most likely the low battery in your motion sensors that caused devices to turn on. I've had that happen..

@Steve Andrews Sometimes deleting and recreating a scene or program can fix issues

Try removing power from the Polisy for about 30 seconds then boot it up. Does it now recognize the zmatter board? Update: just saw you last post. Glad to hear it was just the cable. It's probably best to use a cable rather than connecting it directly as it puts less strain on the USB port.

Scenes have a slight delay as compared to programs, but it shouldn't take 5 seconds. Run a scene diagnostic to see if there are any issues

Did you check either the Zwave and/or the Zigbee boxes and then click on save? (see attached) The Zmatter board will work with the external enclosure plugged into a USB port or it can be mounted internally.

The PLM is the current version, it's rare for that to fail so soon. Try unplugging it for a few minutes. If that doesn't help then try a different USB port on the EISY and/or a new USB cable

Hi everyone, We recently posted the LED Flicker/Glow Eliminators on our store., we wanted to proactively let you know we have corrected some information on that product page. We had mentioned that the “Blue” version would be beneficial to use with our Dimmer (2-wire), providing adequate wattage for powering the dimmer if the load was less than the required amount. However, after further testing, we found that it doesn’t do this. Therefore, we adjusted the description on the product page accordingly. Please make sure to read through before making your purchase when these are in stock. Thank you, Insteon Support Team support@insteon.com