Techman

@gzahar I'm seeing the same options as you. What device are you trying to install and is it Zwave certified?

The Zmztter dongle is Zwave certified and supports S2 security. What device are you trying to install. Is it zwave certified and does it support S2, if not then you should select S0 security option when installing.

The Zmatter dongle is powered by the eisy, you don't need an additional power supply

Before you disconnect your zwave devices from your existing home you should EXCLUDE them from the zwave controller. After all your Zwave devices have been excluded you can then factory reset the Zmatter dongle. You then won't have to factory reset the Zwave devices.

Being that you're basically starting over you should do a factory reset on your Zwave controller and on your Polisy. Any devices that you bring wjith you should be factory reset before installing them in your new home.

You can just ignore the Binary sensor node. Sometimes extra nodes are created depending on the device and the Zwave controller. I created a folder and move unused nodes into that folder which unclutters the device table.

120 degrees is pushing the limit. Attics can exceed that temperature in the heat of the summer. The Zmatter dongle has a pretty good range. I have mine in an equipment closet with other electronics and don't have any issues.

I believe the batteries are in parallel, If that's the case, then when the battery level is low it means both batteries need to be replaced or recharged

Usually you should get a pop up that says your system is upgrading, after the upgrade is complete you should get a popup telling you to reboot Being thaat you're on 5.7.1_7 you have the current firmware. It's probably best to reboot your system.

@ShawnW Could it be that the Zmatter dongle isn't seated properly. You may want to try removing and reseating it. Worst case scenario, the dongle is defective.

The current firmware release is 5.7.1_7 What do you mean by "they keep swapping"? Are you using an external or internal Zmatter dongle?

Run this link in your browser : eisy.local:8443/WEB/sysconfig.txt and look for the attached info

Try running "upgrade packages". there was a bug in 5.7.1_7 that was corrected. After the upgrade you'll still show 5.7.1_7

Are your eisy firmware and UI the same version? Try putting the sensor into the linking mode, then do a restore device.

What firmware and UI versions do you have Do you have the zmatter dongle or the Zooz dongle?

When you installed the outlet did you use S2 security? When you try to turn the outlet on manually does the admin console show it as on even though it's still off? Set you event viewer to level 3 and then try to turn on the outlets and post the event viewer results.

Exactly what's not working? What controller are you using. What is its firmware and UI version? Being that's a battery operated device you'll need to have it within range of a dual band device, or close to your controller.

What's the make and model of the switch? What zwave controller are you using? Are you trying to control both oulets via a scene, or just one of the oultets??

Try deleting the program, then recreating it. Also verify that the time is set correctly in the admin console

All you need to do is to find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.state or ud_*.state file patterns: ud_finder.state udi_finder.state udi_frame.state udi_launcher.state udi_pgm.state udi_tree.state

@GDavis01 Are you downloading the IoX Launcher from this link? https://isy.universal-devices.com/start.jnlp

Try doing a factory reset on the switch, then a restore device. It's also possible that there's a program that has a link to the switch. Take a look at your log to see what's happening at 3:59am

Clear your java cache, be sure to check all three boxes, then download the newer IoX Launcher from here: https://isy.universal-devices.com/start.jnlp This will put an icon on your desktop for the admin console

Powercycle didn't help, ticket submitted UPDATE: Just heard back from UDI, it's a known bug. They expect a fix by the end of the week.

That would be the Trusted Platform Module 2.0. Not sure how to get that update as upgrade packages doesn't install it. It might be in the developer packages. I'll wait for comment from UD.