Techman

If the Polisy is working there's really no advantage in upgarding to the eisy at this time. The current firmware and UI is 5.8.4 You probably need to first upgrade PG3x 3.2.27,, then update your polisy firmware. See the link below. Polisy:User Guide - Universal Devices, Inc. Wiki (universal-devices.com)

In Advanced Status Configuration, if I set a State Variable value as "Not Equal To" it shows as "Equal to"

@Beaker Use "copy to clipboard" then paste it in the forum

@Beaker Can you post a copy the program that's not working.

@ELA Can you post the program for one of the sensors that are active both day and night but that doesn't show up in the log. Are all the IR sensors identical, i.e. same manufacturer, same version.

@ELA Can you post a copy of a program that's not working correctly.

@MKonrad The most likey reason you had trouble adding the new keypad is that you incorrectly entered its address. It's very easy to misread B and 8. If you had intalled the new keypad and then right clicked on the old keypad and selected "replace with" and selected the new keypad, all your scenes and programs would have had the old keypad address replaced by the new keypad address. No programing would have been necessary.

Factory resetting the dongle most likely won't resolve the issue, It's best to wait for a reply on your support ticket.

So is there a way to see the history of the programs during the night like a log? The short answer is no.

The status of battery powered devices won't show up in the admin console until a specific device node updates, i.e. battery level. Email configuration won't arbitarily change to default unless the default box was checked.

The only other option I can suggest is to remove the lock, do a factory reset on the lock then re-install it. If that doesn't resolve the problem then it's best to open a support ticket as it's possible that the lock isn't fully supported by the eisy https://www.universal-devices.com/my-tickets

Is the lock a Zigbee not Zwave format?

What's the model number of the lock?

What is the ISY firmware and UI? It's possible that when you included the lock something was amiss. Move the lock close to the ISY, then exclude the lock and re-include it

It's possible that the power outage corrupted the device link tables. You should first try to do a restore device on all the hardwired insteon swiches and keypads that are common to the bathroom lights. You should also try a reboot on the controller.

What nodes are missing that you need? What device nodes display in the admin console window? It appears that you added the lock in the S0 (non-secure) mode rather than the S2 (secure) mode. The eisy uses a different zwave chipset the the ISY. It's also possible that the device firmware may be different between your 2 devices which could explain the display difference between the 2 locks. Zwave devices will quite often install numerous nodes of which some may not be applicable. This is due to the fact the different hubs support and require different nodes. You can just ignore the nodes that you're not using and/or move them into a folder, which you could call unused nodes, so you don't have to look at them.

I just tried changing themes on my eisy, mine didn't revert back. I'm running firmware and UI 5.8.4. Is your firmware and UI current?

@GHenry Take a look at this thread Support Thread: IoX v5.8.4 (June 27, 2024) - Page 2 - IoX Support - Universal Devices Forum (universal-devices.com)

Why not use CONTROL instead of STATUS in the IF field. The THEN clause would run until completion. You could keep it as one program. If motion continues to be detected the then clause would restart.

First, try doing a factory reset by Pulling out the set button, then push the set button in and hold it in. The device will start a continious beep. Continue to hold the set button in until the beeping stops. The load attached to button 'A" should turn on, then in the admin console right click on that device and click on "restore device" If that doesn't fix the problem then you'll need to install the new keyad and replace the existing one. See the attached link. Be sure to backup the ISY before and after the replace process. ISY-99i/ISY-26 INSTEON:Replacing a Device - Universal Devices, Inc. Wiki (universal-devices.com) To add the new device to the admin console enter its 6 digit address in the link window, format is "xx.xx.xx" Note periods, then click OK. Note: when replacing a device, it must be like for like, i.e. an 8 button keypad for a 8 button keypad.

Set your "C" button to "non-toggle off". The button press will then only turn the scene off when pressed.

If you're adding it with S2 authentication then it's is looking for an access code. Try adding it using S0 (no security) which also draws less battery current over the life of the battery.

Try bringing the devices closer to the the controller. On the tri sensor 8, click on write updates on your controller, then hold the set button on the sensor down for 3 seconds, the led should then blink blue once, and the writes should take place.

Not sure there's a graceful shutdown option for the Polisy. If it loses power then is powered back up it should be fine. No data should be lost unless you were in the process of writing a program or adding a device.

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.