Techman

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.

@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

Hi everyone, Wow, it feels like I blinked, and it is already the two-year anniversary of Richard and I launching Insteon! With the passion and loyalty of all of you fueling us, we are even more excited for what the next two years will bring! Let’s celebrate this milestone together! Free Shipping All orders of $50 or more placed before the end of September are eligible for free shipping*! Thanks, Ken CEO, Insteon Technologies

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