DennisC

Is it possible the node address is listed incorrectly on that screen? Try opening a browser and entering (replace the "x's with your local IP address): https://xxx.xxx.x.xxx:8443/rest/nodes/ Click through the warnings and enter your login information when requested. Then look for the node address.

Go to the admin console of eisy/Polisy, configuration tab, reboot. It is no longer possible to just restart PG3(x).

Did you follow these directions: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card If so, tell us exactly where what you are seeing diverts from what is written and what you were doing at the time. Your only alternative would be to open a support ticket with UD, but free support has ended for ISY994. If you have a good backup, your only other option would be upgrading to eisy.

Follow directions here: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions

In your subject line, try using .raw after CLIHUM. Also, be sure there are no spaces in the node server string, from $ to the last }. As an example: Hum ${sys.node.n001_81668.CLIHUM.raw}% For troubleshooting, I would also suggest, just using either the subject or the body for the variable, not both.

I'm not sure what "ISY portal node server" is. The only node servers that will appear in PG3x dashboard are the ones you purchase or if you are a developer self host (if still allowed). While in PG3x go to Purchase tab, those are the node servers you should have in your dashboard.

Shutdown your Polisy/eisy, remove power, and power back up after a minute.

Try setting the alarm while watching the log to see what is happening.

Try this: https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored Or this: https://wiki.universal-devices.com/index.php?title=Main_Page#admin.jnlp_does_not_start_the_Admin_Console

You are here in the instructions manual, you need to back out of it: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Individual_Status_Mappings

Use the back arrow at the top of the page to go back to the home page. You are on an edit page. As you back out, look in the upper right corner for a pencil icon that you may need to use to turn off edit. Also, if it asks to save changes, click discard (no).

From the main UD Mobile screen, connect to your controller, Devices and Scenes. Then select your device and you are able to control the devices. However, a much easier way is to set up favorites and put the devices you want all together. UD Mobile is very customizable and you can change the icons and have the color change based on on/off status. When you are ready go through the wiki instructions for "how to" information.

From memory, so don't take it as gospel, Ring node server and UD Mobile Notifications.

To convert from wireless to Ethernet, check the wiki. I believeIt is done using the multifunction button, but I don't remember how many presses.

Can't think of a reason it would not work for all programs. Try rebooting.

Everything is time based, all of these options are new. As time goes on and more people have a need to upgrade from Polisy PG3x, UD will surely address it. Currently, their resources are limited. My comment was based on the statement: If you are currently on Polisy with PG3, there is no reason not to upgrade to PG3x. There are features available now that only work on PG3x. If you are considering moving to eisy shortly, then wait to upgrade to PG3x.

Not sure why you are stating that. My move from Polisy PG3 to PG3x went off with no issues. As previously posted, there are certain features that are only available with PG3x.

No, I don't believe this is currently possible. If you use something like the Notification node server you can a text box key at the bottom of your notification. This is also possible using the builtin email notification system.

If you don't reinstall to the same spot, all links in programs, network resources, and notifications will be broken.

Were you on PG2 previously? Did you migrate your node server's according to the wiki? Do the node server's show up as purchased in PG3x under the Purchased tab? I believe unmanaged typically means PG3x doesn't know about them, but they are listed in your Polisy/eisy. You can delete them in the admin console under Node Server tab. After a short delay, the unmanaged node server's will disappear from PG3x. You would then need to reinstall them from PG3x. If your purchased node server's don't show up to reinstall, you will need to send the uuid of the before and after Universal Devices controller in a support ticket to UD and ask them to move them over to your new device.

Going to need more information, did you start out by doing a Zwave migration on your ISY? Why don't you tell us the steps you followed and what the outcome was.

In your first screenshot under groups, why does it say "removed default"? So I just looked in UD Mobile under notification settings and found this help link: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Group_Setup

This is what is in the instructions: ISY Portal The ISY Portal Servie allows sending notifications to the Portal which are handled by the UD Mobile app. Originally this service allowed sending to "devices" configured in the Portal, but as of version 3.5.2 the preference is to use groups. To send messages to just one device, create a group with that device in it. This allows you to change device names, or add a new phone to a group and remove the old phone. Users who already have programs configured which reference devices can continue to use that, but should switch to groups at some point. If you are still having issues, maybe post some screenshots so we can see what you see.

From UD Mobile wiki: Groups UD Mobile Notification Groups are used to send notifications to a single device or group of devices. A group can be used to send messages to a single devices, groups are used to assist with mobile device replacements. Groups can be created or edited from UD Mobile > Notification Tab > Settings (gear icon) > Groups. Notification Plugin (Node Server) restart is required after group creation to populate new groups. UD Mobile will also require synchronization after Node Server has restarted. If you want to send to specific devices soley using Notification node server, use the Device setting and you can select individual devices or all in the Then portion of your program.

From the user guide here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration Z-Wave The Z-Wave network managed by ISY-994 will be migrated to the ZMatter Z-Wave implementation on Eisy / Polisy. The devices in the network will remain the same, but their representation in ISY may change. Nodes Z-Wave ISY Nodes will be reused whenever possible, but new nodes may be created as well. Programs Z-Wave ISY nodes in programs will be migrated, however, node actions and conditions may no longer be valid if the node's support for them has changed. Scenes Z-Wave ISY Nodes in scenes will be migrated, but those using native links (i.e. association) may require updates. Preparing for Migration from Eisy / Polisy You can migrate locally on the same Eisy / Polisy or to another Eisy / Polisy. On the Eisy / Polisy your are migrating from Make sure Eisy / Polisy is up to date Go to Admin Console configuration page and select update packages If you are not migrating your Z-Wave network Use (Admin Console | File | Backup ISY) to make a backup of your Eisy / Polisy If you are migrating your Z-Wave network Leave your current Z-Wave board / dongle connected Go to configuration tab in Admin Console and select "Migrate to ZMatter Z-Wave" Choose the option that allows you to create a "migration" backup (first option) You will see a series of popup windows providing information and asking simple questions Once you have your "migration" backup you are ready to migrate A migration backup is different than a regular backup. When a migration backup is restored it also migrates your Z-Wave network 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.