DennisC

Is enabling the Vacation folder's date/time setting a manual operation? This could be automated using a button press or even UD Mobile - just something to consider. Also, your date and time is done by adding a folder condition to enable the folder for a certain period. Just be aware, that folder conditions can sometimes be unreliable. Therefore, if your program fails to run or runs when it shouldn't, check your folder conditions. Also, since the If portion of your Vacation folder doesn't contain an If statement, there is nothing to actually trigger your program to run. The folder condition just says ok, you are allowed to run, but you need an If statement to trigger run then or else. I hope that makes sense. If you only have one program, the date/time could be in the If portion of the program and eliminate the folder condition. There are several ways of doing this. Since you can enable/disable a program from a program (a disabled program will not run from the If statement, but can be run manually) my suggestion would be as follows. I would suggest eliminating the folder condition. Use your Hot Water Sink program and then add another program as follows: If: From 6:27:00AM on 2023/02/26 To 9:30:00PM on 2023/03/19 Then: Disable program Hot Water Sink Set 'Hot Water Sink / Hot Water Sink' Off Else: Enable program Hot Water Sink You can add a turn on to your else statement, or just let your 1st program turn on by itself after being enabled.

Yes, the best one is created by UD and it is called UD Mobile. https://wiki.universal-devices.com/index.php?title=UD_Mobile

Yes,that dongle is still supported, you just won't have ZMatter support once completely implemented. Glad you are up and running.

I believe a post at the bottom of this thread by bpwwer provides the best possible explanation: I'm not sure what that link does. My assumption is that it sets a variable telling the Polisy that it should install PG3x instead of PG3 when doing updates. It should also remove PG3 and install PG3x. and then restart everthing. When PG3x first starts, it will check to see if it needs to migrate the database/node servers from PG3 to PG3x and will then proceed to do that. Depending on how many node servers are installed, this can take some time. It should send notices to the PG3x UI for each node server it migrates. Expect at least 30 seconds to 1 minute for each node server. If you interrupt this process you'll probably end up with some node servers migrated and some not so don't be in a rush, take your time. It also logs the migration progress in the PG3x log file so if something does go wrong, downloading the PG3x log and attaching that to any support request (ticket or forum/PM). I believe it does not try to start the node servers after it migrates them so they should all be in the disconnected state and you have to manually start each one. The migration should not effect any configuration or existing nodes. My testing involved migrating 30+ node servers multiple times (so yes, it takes quite a while to run) and I didn't see any issues, but I can't account for all the different environments and combinations of node servers. There's no easy way to go back to PG3. In theory, the variable can be cleared, PG3 can be re-installed and restored from a PG3 backup and it should work. There's probably some other stuff that PG3x did that will need to be cleaned up, but it should work. This hasn't been tested so for now, best to consider it a one-way migration. If you try https://polisy.local:8443/rest/pg3x.enable and it doesn't work, please submit a support ticket.

I am using Schlage door lock with no issues using UD's new Zwave ZMatter dongle found here: https://www.universal-devices.com/product/zmatter-usb-enclosure/ You need to follow best practices for adding ZWave devices (for example excluding before adding) and then it works fine.

Sounds like this step was missed from the instructions: Restore from PG3 backup on eisy using the "Migrate from PG3 Backup" option.

Short answer is yes, you could do this by testing for running programs or by using a variable. However, for specific assistance, I think it would be best if you pasted your existing programs here. To do this, right click on each program name and at the bottom of the pop up list select copy to clipboard. Then paste here in a reply. After posting your programs tell us what you would like to have done.

Tell us more about your system, what ZWave dongle are you using? Firmware version 5.4.5 had a bug that caused the upgrade packages function to get stuck in a loop. If you know how to ssh in to Polisy you can verify this is what is happening. If you don't know, you best wait for UD support. To verify, ssh in to Polisy and type: sudo uname -a Post the output here, this will provide the package information. Next, type: sudo tail -f /var/udx/logs/log Then press the multifunction button one time and watch the ssh log you previously started. Check the output to see if the same entries keep repeating.

With eisy plugged in and turned on, check your router logs to make sure your router is not blocking eisy from receiving an IP address. It you don't find anything, try pressing the multifunction button two times, then wait awhile and check your router DHCP table for the eisy mac address. If you still find nothing at this point, pull the power plug, wait several minutes, plug power back in and check your router again after about 15 minutes.

Reboot Polisy

If you change the PLM you need to do a restore PLM. From the wiki: To replace a PLM: Unplug ISY from the power outlet Unplug the PLM from ISY and power outlet Connect ISY’s port A to the new PLM Plug the new PLM into a power outlet Plug ISY into a power outlet Go to Admin Console and wait for system initialization to complete If you have PRO Series, click on the Battery icon at the top. This will prevent ISY from trying to update programming on your RF devices which are probably in sleep mode Click on the Restore Modem (PLM) menu option In case ISY cannot communicate (or decides not to if an RF device/PRO Series) during the process, you will have a series of nodes with green 1011 icons in the device tree. For each one of those nodes: If an RF device, ensure that the device is in Programming mode Right mouse click | Write pending updates ... If the above procedure fails on many of your devices, it's highly recommended that you follow the instructions for Restore Devices. Restore Devices Selecting this menu option starts the ISY to use the current configurations settings stored within ISY, and reprograms all the INSTEON devices based on them. Upon completion, this operation reboots ISY and closes Admin Console. This operation is most useful when a PLM is replaced or if INSTEON devices and their logical representations on ISY are out of synch. This scenario might happen if INSTEON devices are manually linked without using ISY’s GUI. Please follow the instructions below: If you are replacing a PLM: Please make sure you reboot ISY with the new PLM before doing anything else Click on File | Restore ISY and restore a good backup. If you are replacing a defective PLM, choose a backup from right before the PLM died. This is a very important step Once ISY reboots, wait for the query to complete If you have PRO series, click on the Battery icon on the top right corner of the tool bar. This prevents ISY from trying to restore battery operated devices since they are sleeping and will not respond Please make sure ISY is in Ready state Click on File | Restore Devices - this will take a long while In case ISY cannot communicate (or decides not to if an RF device/PRO Series) during the process, you will have a series of nodes with green 1011 icons in the device tree. For each one of those nodes: If an RF device, ensure that the device is in Programming mode Right mouse click | Write pending updates or Write updates to device... For some newer INSTEON devices, you might have to repeat this step a couple of times since some devices may not go into linking mode If you have PRO series, click on the battery icon on the toolbar so that ISY goes back to normal mode. If you can still access admin console, I would suggest you make a back up from the File menu.

Honestly, I'm learning about the Ring node server with you. But if you want to post the log .maybe something will jump out at one of us.

Just to confirm, is the following under Control and not Status? Ring / Ring / Front Porch (Motion)' is switched Motion One other thing I think I remembered reading, are you using PG3x? Ring may not work with PG3. Is remote connection in PG3x enabled? Remote connection must be enabled Settings are in Portal under Select Tools | Maintenance | PG3 Remote connection Is there anything else in the Ring node server log besides what you already posted? Make sure ring alerts are enabled in app.

I'm not using this node server, afraid I can not offer any further assistance.

Here are some possible solutions: is the Configuration tab of node server correctly set up, with authorization for Ring?

Reboot and try again.

I think you might require Bob to look at the errors, you might want to tag him. Just to be sure, in the "value" field, you only have the number? The key field would be for Latitude and Longitude. I don't use this node server to look at the exact format.

Have you set it up on the Configuration tab of the node server? Configuration longitude and latitude are the two mandatory configuration parameters.

Once the ZWave dongle is backed up from the ZWave menu, everything else is done from the Admin Console | File | Restore ISY menu. The ZWave back up, once completed, becomes part of the ISY back up. Just to clearify, you are already using ZMatter on your Polisy - correct? The procedure is different if you need to migrate from ZWave to ZMatter ZWave. Here are the directions from the WIKI to get eisy up and running: 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 migrating your Z-Wave network If you aren't already using it, plug in your ZMatter Z-Wave dongle and unplug any other Z-Wave dongle you may have been using. (Polisy only) If you have a ZMatter Z-Wave board then power down Polisy, add it, then power on again. Reboot Eisy / Polisy Use (Admin Console | File | Restore ISY) to restore your "migration" backup If you are migrating from Eisy / Polisy use the migration backup (e.g. "ISY-BackupWithZWaveMigration.v5.5.4__Sat 2023.01.21 09.07.44 AM") If you are migrating from ISY-994 use your ISY-994 backup When IoX restarts, it automatically does the following: Writes you Z-Wave network into the ZMatter Z-Wave controller Interviews every Z-Wave device in the Z-Wave nework, creating/updating nodes, programs and scenes. This process can take anywhere from a few seconds to a few minutes for each device depending on the complexity of the device. The best way to monitor the progress is to open the Admin Console Event Viewer to level 3 For those who want lots of low-level details, you can also use this from the command line: tail -f /var/isy/FILES/LOG/ZWAY.LOG If you don't actually change your Z-Wave network by adding/removing Z-Wave devices after migration, you can back out the migration by connecting whatever Z-Wave dongle you were using before migration and restoring the backup you made prior to migration. 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.

I'm not clear about what you are saying, can you try and rephrase your issue? Are you saying your program is not running? If so, right click on it and select run then. Did your program run?

When you migrate a ZWave network to ZMatter, the node addresses change from ZW to ZY. However, since the node names can be customized, if they maintain ZW in their name, that change needs to be done manually.

While Zwave has its own backup button, once that is done, it becomes part of the Polisy/eisy back up. Be sure to back up Polisy after ZWave back up. Be sure to run an upgrade packages just before your migration. There are more things upgraded besides firmware and you want to make sure you are up to date. You are moving your USB PLM, but I'm not completely clear if you are moving your ZMatter Zwave dongle or are going to use a new one? Assuming you are moving the one from Polisy, plug it in when you plug your PLM in. There is no need to uncheck Insteon and ZWave support before shutting down Polisy, however, you will need to check Insteon and Polisy support after starting eisy with both the PLM and USB dongle in place. You will need to reboot after checking the support boxes. Get eisy up and running before moving licenses for portal and before migrating PG3x and node servers. Don't forget to go through programs and network resources for errors and you may need to re-save each one to get them working. If you have battery devices, turn off auto update for them and write them one at a time. Don't forget to back up eisy and PG3x when done. Be sure to follow instructions here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

Agree it is not a global Zwave lock issue, my FE469 Schlage lock works without issue.

What is your firmware version? Earlier, there were a few firmware versions that were experiencing random reboots. Firmware version 5.6.0 is good and I haven't seen any random reboots with it.

A Zwave device can only be part of one network. Best practices includes removing or excluding a device prior to including or adding the device. You can search these forums and see that advice repeatedly mentioned. The following is the Zwave instructions for adding a device from the UD Wiki, pay attention to the last line note. Select Z-Wave | Add a Z-Wave Device and wait for a popup window to appear. If the popup window does not appear, Select Z-Wave | Advanced | Stop Adding or Removing a Z-Wave Device then try again. Put the Z-Wave device you are adding into learn Mode. Refer to the user guide for your product on how to do this. In many cases this just requires you to press a button on the device. The ISY will begin adding the device (this may occur a few seconds after you put the device into learn mode). The popup window will go away and you will see your device added to the tree. Note: To add a device, it must not already be in a Z-Wave network. Therefore, if you are having trouble adding a device try removing it first.