DennisC

Correct, with Sunday currently at 0, Monday at 1, Tuesday at 2. The issue being looked at is why Sunday is 0 instead of 1. I didn't understand why you wanted Sunday to be 7?

These both work for me: ${sys.program.#.name} ${sys.node.#.name} If I recall correctly, it only works when called by the program logic. I don't think it works correctly when selecting "Run Then".

Try Synchronize with Interview.

I would suggest starting with Synchronize with interview. If that doesn't work, you can always try exclude then include to manually add the device back in. I suspect if you were adding them manually it would start with 1, but the migration will carry over the address, except going from ZW to ZY. You would need to factory reset the ZWave dongle, exclude each device and then add in by include. Afterwards you would need to update all programs and notifications.

Out of curiosity why 7, Sunday is typically the start of the week and labeled 1?

Yes, it is still accessed using the admin console via IoX Launcher. The alternative is to use UD Mobile app which can handle a lot but not all of the functionality of the admin console. UD Mobile is actively being developed by UD and the developer is very responsive to issues and requests. It is a much better choice then Mobilinc, which still doesn't fully support plugins (node servers). Also, it takes some extra steps to get the Mobilinc portal working with UD's newer setup, so consider adding UD's portal along with UD Mobile.

Here is the UD Mobile user guide: https://wiki.universal-devices.com/index.php?title=UD_Mobile Spend some time getting familiar with the many features. You can set up a Favorite's page, add different folders with different devices and/or programs in the folder. You can display different status' and change color based on the status.

I would suggest power cycling Polisy. Mine was fine this morning. Also, verify you are on the latest build, v5.7.0_5. You can run: https://xxx.xxx.x.xxx:8443/WEB/sysconfig.txt Substitute your IP address for "x". You may need to click through some warnings. You can use Ctrl + F to search for ISY to locate your version.

Try power cycling your unit. IF that doesn't work, try restoring a backup.

If that doesn't work try using the Interview command. I am not in front of computer, but I think it is sync with interview.

Is the node server / plugin running without errors? Maybe reboot your ISY followed by an UD Mobile sync?

Have you added the ISY uuid to your portal account? That is the prerequisite of approving it in your ISY. If you haven't seen them, the full instructions are here: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions BTW, be aware that the ISY994 is at end of life and no further development will be done. In addition, free support from UD is also over. You should consider upgrading to eisy.

Have you tried the factory default of admin/admin? I would suggest once you get back in to your system and before doing anything else, you read and understand the migration document here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide

One more thing to try, if you can ssh in, run sudo tail -f /var/udx/logs/logand try the update again. if no activity gets log, the update will then need to be forced and UD support can explain how to do that.

Since Polyglot doesn't need wifi to connect to Polisy, I suspect it was removed from this location. Most of the devices I have connected to wifi, create a pop up when sign in is required. It is possible, that would happen with Polisy. Just like trying to issue a rest call via a browser, you receive a pop up asking you to sign in. However, unless Bob responds, I suspect the only way to be sure is via a UD help ticket. Also, since your Polisy is already connected to wifi, I'm thinking the credentials are already saved and you wouldn't need to re-enter them. But it is best to ask to be sure, via a support ticket.

That's one of the reasons I suggested the Notification plugin using Pushover. The notifications come up the same way, you can read and dismiss most of them, without opening Pushover. I also use Verizon and got very tired of the delays and periods of just not working. This way is convenient and just works.

Try using Notification plugin. You can also add a service like Pushover, or use UD Mobile for delivery. Both a very responsive.

Yes, I'm writing on a mobile device and it looks like it has a mind of it's own. Going to edit my post to correct.

I have a Yolink door contact installed in a metal mail box located about 100 feet away and thru a concrete wall from the hub. They advertise up to 1/4 mile with no obstacles. So far it has been working. I intergraded it in to eisy with the node server. The reaction has been almost immediate. So far, it is working with no problems. If I didn't hard wire GDO in to my Elk, I wouldn't hesitate to try Yolink solution for it.

The only reference to wifi for Polisy is in this section or the instructions: Installation Installation is quite easy Make sure your network has DHCP auto enabled Connect one end of the included Cat5e cable to Polisy’s Network Port and the other to your network. You must use the port that’s closest to the right most edge of Polisy when the front of Polisy is facing you (closest to the db-9 serial port). Note: the network must initially be DHCP auto enabled If you have the PRO version, attach the included antennas to the back of the unit. Connect the power supply Make sure the bootup sequence is as described below. I take that to mean if you have DHCP enabled, which is required, and do not plug anything in to Ethernet port, Polisy should auto configure for wifi. In PG3 or PG3x, all that is then needed is the IP address and the port number, if Polyglot can not auto configure.

Yes, the process is simpler without Zwave. Here are sections you need to follow from the migration document. What to Expect During Migration Insteon The Insteon network on ISY-994 will be seamlessly transferred to Eisy / Polisy. Your nodes, programs, and scenes using Insteon will remain unchanged. Network Settings Starting with Polisy, and due to massive support requests, we have disabled static IP configuration. Please use DHCP reservation in your router instead. The advantage of DHCP reservation is that, in case you change your router, you can still find your eisy/Polisy. Preparing for Migration from ISY-994 On your ISY-994 Make sure the ISY-994 is upgraded to 5.3.4, If you are not migrating your Z-Wave network Make a backup of your ISY-994 (Admin Console | File | Backup ISY) On the Eisy / Polisy your are migrating from Make sure Eisy / Polisy is up to date Go to Admin Console configuration page and select Upgrade Packages If you are not migrating your Z-Wave network Use (Admin Console | File | Backup ISY) Migrating On the Eisy / Polisy you are migrating to Do the appropriate preparation step (see above) Make sure Eisy / Polisy is up to date Go to Admin Console configuration page and select update packages If you don't have a current backup, make a backup of your Eisy / Polisy (Admin Console | File | Backup ISY) If you are using Insteon, plug in the PLM If you are not migrating your Z-Wave network Use (Admin Console | File | Restore ISY) to restore either your Eisy / Polisy backup or your ISY-994 backup. If you are using Insteon Go to the Admin Console configuration tab and make sure INSTEON Support is enabled (default username/pwd = admin/admin) If you are using a new PLM, Restore the PLM Reconfigure any software utilizing to point to this Eisy / Polisy, restart the other software, if necessary. If you have ISY Portal on your 994 Follow these instructions to migrate your account, license, and Alexa/Google Home settings This will also migrate all node server licenses from your Polisy to Eisy / Polisy. Have you completed all of the above? Were there any errors? Did you move the PLM or start with a new one? Did you check the Insteon support box on Configuration tab and restart? Does the PLM on eisy show connected?

Restore is not the way to migrate from ISY994 to eisy. You need to follow the migration instructions linked by @lilyoyo1 Before migrating be sure to read and understand all of the instructions. Ask questions about what you don't understand before starting. Also, be aware, you either require a USB PLM or if you want to use your existing serial PLM an adapter cable available in the UD store.

Are you sure about that? Zwave devices with the prior Zwave board and Zooz stick were named ZW. If you migrate to ZMatter, the name is upgraded to ZY. Although I see it has been removed from the migration wiki, this use to be specifically called out in the migration instructions. I believe it still holds true.

Try going to the log tab, setting it to information or higher, and then restart the node server. Check the log for problems. Keep the admin console closed while doing this.

I would suggest running restore PLM again. Keep the event viewer open set at level 3 while doing this. Monitor for any errors.