DennisC

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.

Maybe you can tell me or direct me to the pros/cons of migrating to PG3x? The only reason why I'm wanting to migrate, is to try the "Notification" feature within UDI mobile and or the GEO fencing addition That's really the only reason you need, it's not going to be available on PG3. Try again by copying link below and make sure you are local. Enable PG3x: https://polisy.local:8443/rest/pg3x.enable Reboot and wait for a beep + 1. Migrating node servers from PG3 to PG3x might take up to 2 minutes per node server. So, please be patient Once all node servers show connected, reboot again.

Everyone who has migrated over to eisy using Zwave in the past 6 months. The procedure is proven and well spelled out in the instructions. If you are concerned about something, ask a specific question about the step you are concerned about and we can provide additional assistance.

That's because you only have one device, eisy. There will be a septline for each device on the network. This would be a lot easier if you could get in to your ISY and do a proper migration. What exactly is wrong with your ISY994? Have you tried a new power supply?

Which log have you checked, the event viewer or error log? If you haven't, try checking the error log.

I would also add to what has been discussed: Reboot ISY before trying again. Exclude 2 times before trying to include. If that doesn't work, try factory resetting your switch and then excluding before adding.

I would suggest doing an upgrade packages and afterwards, reboot. When that is done, power down, remove power for a few minutes and then power back up.

The ISY is much slower, have you tried increasing your time out as suggested above?

Go to and log in: https://my.isy.io/index.htm Find your device in the list and click on Select tool - Information - ISY Information Copy the full URL address listed next to: Admin Console URL: Back on your desktop, start the IoX Launcher Select Add Paste the full URL address copied above from the portal and hit OK This should list your device with the portal access URL. To access, click on the portal access URL instead of the local address. Note: When you log in via the portal, you must use your portal credentials and not your device credentials. If you want, you can click on Save in the IoX Launcher to save the file of Launcher URL's in case it is returned to default during an upgrade.

A much better way to access eisy from outside your network is through the portal, no port forwarding is required. https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Portal:_Integration_with_Amazon_Echo.2FGoogle_Home.2FIFTTT https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions

Try in creasing your time out to 5,000.

https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Change_Password

I apologize, I guess I don't understand exactly what you are looking for. Mine looks like the below screenshot.

You should be able to do this now. I do the same thing for Weatherflow. In UD Mobile go to the tile in question and before selecting it, click the pencil icon in upper right corner. Next select the tile in question and in the pop up select Edit. Under Display Node it should say Forecast # plus node name. Select Display Status and choose "Day". Select Save in upper right corner. When that is done, deselect the pencil icon in upper right corner. To further customize mine, I change the icon and color based on the forecast. See UD Mobile instructions for examples.

Did you follow Michel's instructions about upgrading after a failure in his post? If you haven't seen it, he said if you have a failed update, you need to reboot, then upgrade packages, and then a second reboot. Have you tried this?

There was a problem with updating that was corrected yesterday. You might want to try updating again.

Follow the procedure here: https://wiki.universal-devices.com/index.php?title=Main_Page#Changed_ISP.2FRouter_-_Can_no_longer_access_ISY Once you do get back in, be sure to change from a static IP address to DHCP.

Currently, there is an issue running upgrade packages that results in a permission issue and prevents the upgrade from occurring. That may or not be contributing to your problem. PG3 v3.1.23 has a reported issue that prevents the deletion of node servers. Again, this may or may not be contributing to your issue, but I don't think you will be able to complete an upgrade until the permission issue is fixed. For now, try removing power from Polisy and restarting. You may get lucky and PG3 node servers will start up. Other than that, it is probably best to open a support ticket with UD. https://www.universal-devices.com/my-tickets/

As others have indicated, you can use your backup and restore it on eisy, however, you will not be able to "migrate". As indicated in the directions documentation, the two are not the same. Migration includes moving ZWave if you meet the requirements. From the instructions: "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."

While I don't use Telegram, here are the configuration instructions, have you followed them? Telegram There is a very simple method to setup your own Telegram Bot. This is initially a semi-manual process to create your own bot. I will be researching and testing better ways to do this in the future. First create your User Bot Install Telegram on your computer or phone Will need to copy/paste a long key to PG3 Go to https://telegram.me/botfather Command: /newbot Answer questions: Bot Name: Any name you want User Name: Any username you want. botfather prints a line saying: Use this token to access the HTTP API: Copy and save that, you will need it for the configuring the nodeserver Also save a permenant record of it somewhere, along with the link in the next step You will also be given a link to your bot like t.me/{yourBotUsername}, click on it. The "Start" will be shown, click that Go to: @RawDataBot Click Start This will give your user id listed under message -> from -> id Copy that to use in Nodeserver configuration The tell the Notification Nodserver about it. PG3 UI Go to Notification Nodeserver Configuration Click "Add Telegram User Bot Service Node" Set the name Paste the HTTP API Key from above Paste your userid into the users (currently only one user is supported) Click Save Changes

That thread looks more like a PG3 and/or PG3x issue. I suggest opening a support ticket with UD so they can get to the bottom of the issue https://www.universal-devices.com/my-tickets/