DennisC

If you wrote you are down, they typically reply within a few hours, sometimes even on weekends.

Try one more thing from the ssh screen: sudo service udx restart

Can you try another cable? I am out of suggests, you should open a support ticket: https://www.universal-devices.com/my-tickets/

First, check this: Check error light on front to see if they match my post above. Make sure you have connected the network cable to the right jack on the back of the unit (the right most when Polisy is facing you) Make sure your router is initially DHCP enabled Possibly a bad cable?

Did you try all the steps from both wiki's? If you can not find your Polisy by adding the IP address to the Launcher manually and you are not running a VPN or antivirus software, it is possible your IP address changed. Check your router and confirm you have the correct IP address. Also, confirm you used https and the port :8443, and that you did not change the port at sometime. Did you check the error lights on front of Polisy? If ISY Launcher cannot find your ISY: Most importantly, you need to reinstall the ISY Launcher VPN software is running on your computer or you're on a VPN network Unit is not on the same network as your compute. Perhaps you changed routers? If so: follow these instructions If not #1, please open your router page and see whether or not you see ISY994-EMS (for ISY) or polisy (for Polisy) in the list of LAN clients. If you find the IP address, then, in ISY Finder, click on the Add button and enter ISY994: http://1.2.3.4/desc (replace 1.2.3.4 with the actual IP of ISY in the router) Polisy: https://1.2.3.4:8443/desc (replace 1.2.3.4 with the actual IP of Polisy in the router) If not #2, then perhaps the unit is not powering on: ISY994: Please make sure the pattern is as outlined here Polisy: Reboot the unit, all 3 LEDs should get lit and then only the left most is lit. Wait for 30 seconds. You should hear a beep If not #3, the issue is that you might have firewall/VPN software (especially VPN). Please do #2 Maybe try removing power one more time?

First step is to do a graceful reboot. Since you can log in via ssh, enter sudo shutdown -r now. That should reboot Polisy. You mentioned clearing Java cache, which is good, did you then download a new start.jnlp? If not, clear it again, including deleting all 3 check boxes, and then download it from here: https://isy.universal-devices.com/start.jnlp Click on the downloaded file and it should add the ISY Launcher to your desktop. Make sure you wait at least 15 - 20 minutes before trying to access the admin console. Still can't find Polisy, click add button in Launcher and add: https://xxx.xxx.x.xxx:8443/desc and click Ok. Note: Replace xxx.xxx.x.xxx with your IP address. If that doesn't work, check instructions here: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Can't_Find_Polisy and here: https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Not_Found

I would suggest that there might not be a need to do a factory reset. However, if you wish, the multi function button is your friend. Per the eisy user manual here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Multi_Function_Button, 10 presses of the multi function button does a factory reset. The reason for using the upgrade packages button is to insure the updates are applied in the correct order. I would suggest signing in to admin console and go to Configuration tab and select upgrade packages. Note that the admin console should close after a short delay and you should wait about 15 - 30 minutes before logging in again. You might also need to do a reboot after upgrading. I would suggest trying this and if all is good afterwards, a factory reset isn't required, but future upgrades should follow the directions. As for the PG3 login issue, you should be using the same login credentials for PG3 on eisy that you use for your eisy. If you still can not login, I have found shutting down eisy and removing power for a few minutes corrects that issue. It is something that is being investigated. If you still have an issue, post full details and a screenshot of errors. As for the notice about upgrades being available, that is a known bug that will be corrected with the next release.

Try deleting device and do a factory reset. After that, re-link it.

Here are some troubleshooting steps for Mac's. https://wiki.universal-devices.com/index.php?title=Troubleshooting_Help Are you using DHCP reservation in your router? If not, could the IP address have changed? Have you tried rebooting ISY? Have there been any network changes? Try turning off antivirus programs?

@Techman This is a known issue and should be corrected in the next release.

I've also seen this error several times. When it happened, I had no problem logging into admin console and rebooting eisy. This would not solve the issue. The only thing that worked for me was to shutdown and remove power. Once eisy restarted after removing power, I would have no problem logging into PG3x.

You need completely follow the directions here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

Are you on the latest v5.5.9 firmware? If not, click on update packages. If you are, try a gracefull shutdown of eisy by pressing the multifunction button 6 times. After it completely shutsdown, remove power for several minutes and then restart eisy. Then start the admin console (make sure your firmware & UI match, if not clear Java cache and run a new start.jnlp), go to Configuration - Portals Tab and see if the approval request is waiting for your approval. One other thought, double check that the uuid that is shown for your eisy in the portal matches what is shown in the UD Launcher.

I also don't normally like forced updates for anything. This is especially true while I am not home or even worse, traveling. As a result of yesterday's forced update, at 6:00 pm last night I finally got around to looking at my notifications from throughout the day. I receive some notifications during the day that update me certain things around the house. It was at that time I realized my ZWave thermostat notifications had no value associated with them. For some reason, and I have noticed this since I have been on IoX that some device do not update in the admin console (and notifications) until they have been queried. I had to go to both of my thermostats and query them. After that all was good. It is not a communications issue, as there has never been errors or commands not executed, and this only started with IoX. However, I also acknowledge the concern over some systems not getting critical updates and/or reporting issues that have already been corrected. Maybe as previously suggested some type of notification system (possibly email)? I would have to vote no forced updates.

Except that was added when 5.5.9 was added. I think it was just a matter of convenience.

Mine was at 8:21 am eastern time. How come yours was so late?

I reported this again when I migrated to eisy. I have been assured that it will be addressed by the addition of a scroll bar, but no time line was given. Maybe if enough people open a support ticket.........

Below is an example of using "disarmed" to turn a light on, if the time is 30 minutes after sunset until 11:00 pm. Example - [ID 002F][Parent 00B1] If ( 'Area 1' Armed Status is Disarmed ) And From Sunset + 30 minutes To 11:10:00PM (same day) Then Set 'Light xx' On Else - No Actions - (To add one, press 'Action') To turn off the light, you could set an Else action, but if you wanted the light on/off when you were home or on a different schedule, you would write a separate program to turn the light off.

Yes this is possible, I did it when using the old Elk module and I'm still doing it using the Elk node server. Which are you using? One way is to set a variable, and have it update when you arm and disarm. I use two different variables, one for armed away and one for armed vacation. The other way is to use Armed Status and/or Arm Up State. When I was on the Elk module I found the variable method more reliable. I never changed methods when I moved to the node server, but I receive a notification when arming/disarming and it includes the two states I mentioned and they have been very reliable on the node server. I actually run several different programs depending on which armed state I enter or leave.

If you are on Polisy, in the admin console go to Configuration and click on Upgrade Packages button. The admin console should close. Wait 15 - 30 minutes and log in to admin console again. Go back to Configuration and select reboot. Before opening admin console, you will need to clear your Java cache and download a new start.jnlp. Click on start.jnlp and it will download a new Launcher to your desktop.

What version firmware and UI are you on? This was an issue that was corrected in the current v5.5.9.

Sometimes it takes more than one remove to completely remove a ZWave device. Try this: Open the Event Viewer to level 3. Select ZWave - Remove a ZWave Device Put your lock in to enrollment function (be sure to follow user manual instructions) During this process, keep an eye on the Event Viewer for any errors. Reboot your UD device (you indicated you migrated from ISY994, but I don't recall if you are on eisy or Polisy) Note: You should be on v5.5.9 for either eisy or Polisy. If not go to Configuration page Upgrade Packages. If you needed to upgrade, be sure to reboot a second time. With Event Viewer open to level 3, go ahead and re-add the lock (be sure to follow user manual instructions). Keep an eye on Event Viewer window. If after this, there is still an issue, with the Event Viewer still open try: Right clicking on lock in admin console and select ZWave - Synchronize - Update with Interview. Check Event Viewer window for errors. If there is still an issue, try right clicking on lock and select ZWave - Synchronize - Update. Check Event Viewer. If none of this works, open a support ticket with UD.

What steps did you follow remove the Zwave device?

Looks like you need to ask @bpwwer. It's possible you need to add the key fields by clicking on Add Custom Parameter?

Try moving it to another outlet on a different circuit anyway. Sometimes it's a combination of items on the existing circuit and the Echo circuit.