DennisC

I just ran in to this issue trying to update Polisy from 5.4.4. Can you ssh in? If so, run the following and post output: sudo uname -a

The link you posted is UD's for installation of a node server. This link will take you to the node server store: https://polyglot.universal-devices.com/ If you scroll down and click on the node server name, Notification, you will be taken to a page with pricing information and a "More Info" button. That page will take you to the Github read me file: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md

Glad you got it working. I think this is the first time I heard of a range issue on eisy. Is your ZMatter dongle buried or surrounded by something that could be interfering?

Unless someone else has another suggestion, the only options I can see are: 1. I don't know if this makes a difference, but which synchronize with interview did you complete? One is reached by right clicking on the device, the other is from the top ZWave menu, Synchronize - New & Deleted with Interview. Since the wording is different, may they perform slightly different? If you try New & Deleted with Interview, I would suggest backing up ZWave settings first, then a complete backup. That way if something else is deleted you can restore. Leave event viewer open while doing this. 2. Try right clicking on device and write changes - leave event viewer open while doing this. 3. Exclude device and then include device and see if it does better - leave event viewer open while doing this. 4. Open support ticket with UD.

I would encourage you to save a copy of the log and report your test results to UD so they can investigate if it is a bug.

Not sure which question you said yes to? Did you exclude before include? You need to open Event Viewer and set on level 3 to see what is happening. Its under Tools - Diagnostics. Open Event Viewer and try again.

Sounds like a bug that needs to be reported.

Mie is greyed out also. I'm guessing here, but I would think it is programmed based on the location setting. Important thing is it is checked. How about looking in the error log and see if there is anything there? Afterwards, try rebooting again, now that the date is correct, it might realize the time needs to be updated.

I have an eisy and two Polisy running v5.5.9 and all handled daylight savings time correctly. I can see your location from your screenshot, is it correct?

Have you tried Synchronize with Interview? Did you exclude before include?

I would suggest starting with 1 press of the multi function button which will try update packages again. Wait up to 30 minutes and then clear Java cache and download new start.jnlp. If that doesn't work, try 5 button presses of the multi function button which reboots. If that doesn't work, try 3 button presses of the multi function button (resets login to admin/admin) and repeat the process.

This comes a little late to help you, but I take two back up before I migrate, over two days to try to avoid that. I did that for both locations I migrated.

Check the error log. If there is nothing there, check PLM link count. I suspect it's a bad PLM. You could try another PLM restore, but open event viewer and set to level 3 and watch messages.

Is the light on the PLM? Try power cycling eisy.

Try doing a search in the forum. I seem to remember a post where someone had an issue upgrading and when UD connected that's what they found. Just don't remember if the posted what UD did to correct. Maybe you can disable wifi until the upgrade is done?

I replied to your other post. I thought (?) the log you ran was for Zwave. I suggested another one that I thought you would be able to see the upgrade process on. Not sure if there is a difference, the one I posted was for a Polisy.

Run sudo tail -f/var/UDX/logs/log If it shows activity, I would just wait awhile longer. What version did you start with before upgrading to v5.5.9?

In admin console, under Configuration tab, have enabled Insteon PLM and then rebooted?

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.