DennisC

For anyone still receiving the "Update Packages Available" message, I received confirmation from UD that they have found and corrected the root cause for this. It will be fixed in the next release.

This may be out in left field but.........are you using a TV or computer monitor? Are you using admin/admin for the login? Try toggling the monitor ports if on a TV. I seem to remember something I read about the user needing to be add to the video group. This shouldn't apply if still using the original admin login.

Elk support for both eisy & Polisy is now via a node server. While there is a small fee for the node server, it is well worth it. The developer is very support of and actively adds features. While it has most of the features of the Elk Module, there are a few that are missing, however, I was able to mitigate them with work arounds. When combines with the Notification node server (same developer), you can not beat the combination. Yes, you will need to update your programs, but if you add the Notification node server, you will need to update them anyway. The combination of the two is much better then anything I had on my ISY's (2 locations, both with Elk). The notifications are reliable, much quicker, and by following the examples, fewer are required.

If your Polisy used a Zooz dongle and your eisy used the new Zmatter dongle, that sounds right. Your not changing any infor on the Zooz dongle. If you move the dongle over, or change the ZWave setup after migrating, that would be different.

I migrated a Polisy system to eisy with ZMatter dongle previously and if you followed the directions, other then the false pop ups about upgrades available, it wasn't too bad. Only have 3 Zwave devices at that location, along with Insteon & numerous node servers. Yesterday, at a second location, I migrated another location from Polisy to Polisy with ZMatter. That system has Insteon, several node servers, and 7 ZWave devices. One of which is a Schlage lock. When migrating, you need to read the directions and understand the intent of the directions and follow them. If you run in to help, UD is right there for assistance. After the upgrade, my lock still functions. Polisy receives lock/unlock status and can issue the commands. Status of who unlocks/locks also work. Based on my testing, what I lost is if the lock jams, it is not being recognized as a jam, status updates to "unknown". I let UD know about it, so I am sure it will be corrected in a future update. You obviously have a lot more ZWave then I do, but how will UD know if there are issues if you don't update? UD is extremely responsive and can not test every device out there. They rely on us to upgrade and test, how do you think the ISY became so reliable? I remember when UD started to support ZWave on the ISY994. There were the same kinds of issues, they were reported and then corrected. Some support is also available here on the forum, if you have questions about specific devices, maybe some one had tried that one already and can offer input.

My opinion is if you migrated from ISY994 to eisy, and want to go back to ISY994, you would need to restore your backup on to ISY. Note, the instructions indicate using original Zwave dongle and restoring backup before migration. I believe that is a key statement. One other thing to note, if you migrated your portal license, that is a one way operation and I don't think it can be user reversed. Not sure about PG3, you might need to reinstall some node servers if you are using them, but a portal license is required. What is not working on eisy withv5.5.9 that you need to back out of the migration? Have you opened a support ticket with UD?

Here is the link to the wiki to troubleshoot this issue: https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Not_Found Don't forget the other steps I posted above (reboot router, clear Java cache, download new Launcher, ECT) Good luck.

I'm confused by your statement above, how did you have Polisy and ISY in one admin console? How does Polisy disappear from admin console? Did you mean the admin console closed - that's what it should do. Your statements have me wondering how you are accessing the admin console? Are you using the Launcher? If not, download start.jnlp from UD (link is in wiki user guide) and run that. If Polisy is not found, power cycle Polisy and start the Launcher. If it still not listed then click add and enter address manually https://xxx.xxx.x.xxx:8443. If you aren't sure of IP address, check your router. Oh, there have been some reports of a router reboot allowing Polisy to be found again by the Launcher. If that doesn't work then @Geddygave you the best advice. Also note, the wiki has a troubleshooting section for this issue at the end of the document.

First, try a safety reboot and if that doesn't work, try a safety shutdown, followed by removing power for several minutes. Here is the info from the wiki on the multi-function button. Multi Function Button There's a little multi function button behind the very small hole on the front of the unit. This button has multiple purposes outlined below. Every click on the button will cause the unit to beep. If the button does not behave as described below, please update Polisy. Update and Upgrade All the Packages Click the button once. Please consult support before updating this route. See link below for suggested update/upgrade process. Please see this important update (July 2022) Safely Reboot Click the button twice. Safely Shutdown Click the button three times.

My update to v5.5.9 on eisy went well, as far as the update goes. However, after 3 "update packages" one "reboot" and one "power cycle", I am still receiving the Update Packages messages. Just added the info to my existing support ticket about this issue.

Here is a link to the complete eisy user guide: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide The recommended way of accessing the admin console is with the Launcher, not a direct down load of the admin console. Instructions are the guide from the link I posted above, but here are the directions: Accessing eisy IoX Launcher is the best method to find and access all of eisy's features Install IoX Launcher Click on the row of the discovered eisy and you will see this menu Admin Console (LAN) This menu item downloads the ISY Admin Console directly from eisy Admin Console (Cloud) This menu item downloads the ISY Admin Console from the Universal Devices cloud servers Regardless of how you get to the ISY Admin Console (Cloud vs. LAN), the results are the same: Admin Console is brought up and connected directly to your eisy. Admin Console allows you to add/remove/change Z-Wave/INSTEON devices, make programs, and make configuration changes. The best source for what you can do with the Admin Console is our ISY (994) Cookbook. Polyglot V2 (Deprecated) This is not available on eisy Polyglot V3 (PG3) This takes you to Polyglot V3 (PG3) Dashboard. Here is some info to help: Can't Find eisy First and foremost, all VPN software block discovery of eisy on your network. As such, if you have a VPN software running, please turn it off. If you have a modern router, eisy advertises itself as eisy.local on your network. As such, and in most cases, you should be able to find eisy at https://eisy.local:8443/desc. What you need to do is: In IoX Launcher, click on the Add button Enter https://eisy.local:8443/desc into the dialog Click on the OK button If you are still having a hard time finding your eisy, it's best to check your router's DHCP client list and look for a device that has the same MAC address as the one the label at the bottom of your eisy. eisy's MAC address starts with 00:21:b9. Once you find the IP address for eisy, in this example, 192.168.1.122, then In IoX Launcher, click on the Add button Enter https://192.168.1.122:8443/desc into the dialog. Note 192.168.1.122 is an example. You should use the IP address for your eisy. Click on the OK button

One other thing to check back in your router, make sure there is rule set up to block traffic for your ISY.

If functionality is in the admin console but not in UD Mobile, you should flag @Javito insure he is aware of it. That way if it is a feature he needs to add, he can. If it's a bug, he can track it and correct it.

Here is a link to all of the most current information for eisy, including the migration guide. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide

This is from the eisy guide: Using eisy In Desktop Computer Mode Yes, you can use eisy as a beautiful desktop running a lean version of XFCE on FreeBSD! Attaching HDMI Ports Click the power button 6 times and wait for eisy to shutdown Attach your monitor(s) to the HDMI port(s) Click the power button to turn on eisy When you see the login prompt, login with your credentials (default = admin/admin) Type start.win at the prompt, accept the licenses, enter your credentials again and voila! I haven't tried it either and right now I can not think of a reason to try it out.

Error 1 = Request Failed Error Does does Tools - Diagnostics - PLM Info/Status show connected? Unless someone else has a suggestion, it might be best to open a support ticket with UD at: https://www.universal-devices.com/my-tickets/ There are services that can repair PLM's and there is a post describing capacitors to replace to do it yourself. However, it would be nice to have confirmation of a failed PLM before going down that road. Did you try moving the PLM to an unfiltered outlet on a different circuit? Take note of which Insteon devices are not connected and see if anything changes. Other then troubleshooting potential communication issues, I am out of ideas.

Yes, I am aware of that, but if it was mine, I would won't to be sure before I replaced it. I don't like throwing parts at a problem. What does Tools - Diagnostics - PLM Info/Status show? With the log cleared, it doesn't look like there is anything in there that will help. It would have been helpful to see it before clearing. How about opening event viewer to level 3, and try restoring one or two devices. See what happens as far as communication is in the event viewer. After that, check the error log again.

It doesn't matter if it was working before or not. If you are sure at least one of the PLM's you have are working, then you need to troubleshoot the current problem. All things that stop working worked before, now its time to troubleshoot the existing problem. Are there any clues in the error log? Being that all Insteon stopped working, I am not totally convinced your problem is not a bad PLM. What does Tools - Diagnostics - PLM Info/Status show?

Take a look here: https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors

Yes, it sounds like your original PLM died. When you change PLM's, you need to restore the PLM. Take a look here:

FYI If you haven't, see my post about 3 or 4 post above this one.

What is your firmware and UI version? If they are not both the same then you need to correct that. If you are running an ISY994, you should be on v5.3.4 if you have a 500 series ZWave board or v5.0.16 for a 300 board. If not, you need to upgrade packages and download a new Launcher. If you still have an issue: Try removing power from PLM and ISY. Plug in PLM, wait about 30 seconds after green light comes on, and then plug in ISY. Wait about 10 minutes before logging in to admin console. If you still have an issue, clear Java cache, including program's, and download anew copy of start.jnlp, which will install a fresh version of the Launcher on your desktop.

After enabling Insteon support, did you reboot? You don't me tion it in your write up. Is it possible you missed a step when migrating? Review the latest procedure here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration If nothing else works, try upgrade packages followed by a reboot.

Try checking the PLM links and see how .any there are. I agree, it sounds like your PLM died. Is the green light on at the PLM?

Try a different browser.