DennisC

Thought you said it was connected to your ISY 994? If it was connected to any system, it needs to be excluded before adding to new system. There are times when even new devices right out of the box need to be excluded before they are included. Hence the best practice recommendation to exclude devices before including them

Try right clicking each none working device and select restore device.

The reason I asked you to tell us the procedure you used is because I suspected you were not following best practices. @tlightneis correct, it is best practices to exclude or remove a Zwave device before attempting to add it to a network. Zwave devices can only be part of one network. The procedure is the same when adding Zwave devices regardless if you are on 994, Polisy, or eisy. From UD's Zwave directions: 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.

It's not clear to me the procedure you followed to get where you are. How about telling us the steps you followed to get here? Possibly, reboot eisy, open event viewer to level 3, and try adding g your Zwave device again. If you are adding a battery device, be sure to wake it up first.

I would suggest you fully flow the UD instructions from here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

First, did you upgrade packages? That should have been the first thing you did. What firmware andUI version are you currently on? The latest is v5.5.5. I believe v5.4.3 had an issue recognizing the ZMatter dongle. Are you upgrading an existing system or starting from new?

Is this your data you are trying to add? To use the API, you need to have the access token for the data. Weatherflow has a page on their site for you to register for the token. If it is not your data, you can see publicly shared data via a web page, but not from the API.

For me, the IoX finder finds my eisy on my network automatically using https on port 8443.

The 300 series will have an LED protruding out of the rear of ISY and may have an antenna mount as well. From the Admin Console select the Z-Wave™ menu at the top of the screen. Select Z-Wave™ Version. If the version is 4.55.00 the ISY has a 300 Series Z-Wave™ dongle. If the version is 6.81.00 the ISY has a 500 Series Z-Wave™ dongle.

I would suggest putting this question to UD via a help desk request. Not sure what the impact will be on migration of assorted licenses or if the license can be migrated again. I believe there is a note in the wiki (?) about licensing migration being a one time affair?

Don't forget to do an "upgrade packages" before beginning. Good luck.

There shouldn't be an issue as long as you meet the requirements from the wiki: Requirements If you are migrating Insteon you must have a compatible PLM Eisy / Polisy supports these PLMs: 2412S, 2413S, 2413U, and 2448A7 If you have a 2413S (serial), you will need our Serial PLM Kit If you are migrating your Z-Wave Network, you must have our ZMatter Z-Wave USB Dongle If you are using Polisy, you can alternatively use our ZMatter Z-Wave Board for Polisy After restoring your backup, you will need to follow the directions from the wiki below to restore the PLM. 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

UD has stated this will be implemented in a future firmware upgrade, along with a few other promised upgrades. No ETA was given.

Given these two statements in the wiki migration document, I suspect you have an issue with something: Our Original Z-Wave implementation is the certified version of Z-Wave on the ISY-994. This code was ported to Eisy / Polisy, but is being deprecated in favor of our new more functional implementation called ZMatter Z-Wave. The original implementation on Eisy / Polisy can use generic Z-Wave controllers such as the Zooz stick, or, it can use the ZMatter Z-Wave controller (either board or USB dongle). The ZMatter Z-Wave implementation can only use the ZMatter Z-Wave controller (either board or USB dongle). 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.

Providing you did not select ZMatter Migration at anytime and since you restored a previous backup and you no longer have the ZMatter migration button, have you confirmed your firmware and UI versions are both still v5.5.5?

I had to rebuild my Query all program after the upgrade also. I matched what was originally in Polisy. Query All - [ID 0002][Parent 0001] If Time is 3:00:00AM Then Set 'ISY' Query Else - No Actions - (To add one, press 'Action') Factory Query Program

Are you using a VPN or antivirus software? Have you followed these directions from the wiki: Can't Find eisy First and foremost, all VPN software block discovery of eisy on your network. As such, if you have a VPN software running, please turn it off. If you have a modern router, eisy advertises itself as eisy.local on your network. As such, and in most cases, you should be able to find eisy at https://eisy.local:8443/desc. What you need to do is: In IoX Launcher, click on the Add button Enter https://eisy.local:8443/desc into the dialog Click on the OK button If you are still having a hard time finding your eisy, it's best to check your router's DHCP client list and look for a device that has the same MAC address as the one the label at the bottom of your eisy. eisy's MAC address starts with 00:21:b9. Once you find the IP address for eisy, in this example, 192.168.1.122, then In IoX Launcher, click on the Add button Enter https://192.168.1.122:8443/desc into the dialog. Note 192.168.1.122 is an example. You should use the IP address for your eisy. Click on the OK button

According to the wiki: 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.

You might have something else going on, I haven't experienced any unknown cause rebooting on eisy. Maybe check the plugs, sockets, and maybe even swap power supplies. It might benefit you to rule out some of these eisy things.

Got it, thanks very much.

@bpwwer, I'm trying to improve my ability to read error logs. Hope you don't mind my asking: Is this the error you're seeing when WeatherFlow attempts to start: [pg3] info: Starting log stream for pg3frontend_yZlDB :: /var/polyglot/pg3/ns/0021b90261f0_1/logs/debug.log 2/5/2023, 12:12:46 [pg3] debug: MQTT Results: [frontend/ns/dcrupi] :: {"startLogging":{"success":true}} 2/5/2023, 12:12:46 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:02:61:f0_5] {"shortPoll":{}} 2/5/2023, 12:12:51 [pg3] debug: Sending logfile to frontend :: /var/polyglot/pg3/logs/pg3-current.log 2/5/2023, 12:12:51 [pg3] warn: stopLogging: unwatch failed, TypeError: Cannot read properties of undefined (reading 'pg3frontend_yZlDB')

No rush, let me know if you need anything else.

I was able to resolve the issue of not receiving notifications from the node server. It turns out, after all was working on Friday and early Saturday morning, some how the host IP addresses in the network resources reset to the old Polisy IP. Once they were updated to the IP for eisy, notifications resumed. I have no idea how this happened, as all was working on Friday.

@Jimbo.Automates, I migrated on Friday to eisy and I am running the Elk Node Server v3.5.8. I am having some issues with PG3x and I am not sure if this is related or not. On the main Area 1 node page, the field Zones Violated is not updating. When a zone is violated, the node for that zone shows the Logical Status as violated. Back on the Area 1 node, Arm Up State changes to Not Ready to Arm, the Last Violated Zone updates to indicate the violated zone, but the Zones Violated remains at "0". I have attached 2 screenshots. Thanks, dc

No worries, we are all in this together.