DennisC

@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.

Multiple times, read my post above Bob's response for the fu story.

@bpwwer Not positive this is related, but I believe it is, since this started this morning, none of my Notifications have worked using the Notification Node Server. While some of the missed Notifications are for weather and the Weatherflow Node Server is not online, some were for the Elk Node Server. Both the Elk and Notification Node Servers indicate they are online. When right clicking on individual Notification programs and selecting run then, the program indicates it ran, but no notification is sent to Pushover. Other network resources appear to be working. All were working before having to reboot eisy this morning because of difficulty getting in to PG3x.

It appears in the link I provided, the migration directions from i994, Polisy, and eisy have been combined in to one document. If you follow the link and scroll down, each topic is divided in to separate sections for i994, Polisy, and eisy. There appears to be only one migration document in the wiki now. I was only able to find one section dealing with Migrating PG3x. It's what I followed yesterday and it worked without issue. Migrating Node Servers to PG3x Migration is only possible with version 3.1.17 or later of PG3x. The version of PG3x that ships with eisy is currently 3.1.16 which does not support migration. Please upgrade packages first and make sure you are running version 3.1.17 of PG3x before attempting to migrate. Backup PG3 on Polisy. Restore from PG3 backup on eisy using the "Migrate from PG3 Backup" option. Cautions: Node servers currently installed on eisy will be removed (and possibly replaced). Node servers migrated are left in the "stopped" state. You will need to manually start each one after migration. If the Polisy was configured to manage node servers on more than one IoX (say both Polisy IoP and i994) only one IoX will be migrated and you can't choose which one it will migrate. Node servers installed on the Polisy from the local node server store will likely fail to install on the eisy. Node server licenses should be migrated as part of the Portal migration step.

This is the link to latest migration directions, updated yesterday: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

Thanks, I will sit tight. If you need anything else or for me to test something, please let me know.

Have you migrated your licenses? If so, I believe you need to go to Purchases Tab and reinstall one at a time in to the same slot. Select the "Re-install" button on that tab.

Do you think additional tries to restart might help or hurt? Is it worth trying to reboot again or just restart PG3? Right now, the Elk Node Server is running and it is the one I don't want to be without.

I completed the migration yesterday on v5.5.5. While I only have a handful of Zwave devices, they were not communicating either. I had to go to each device, right click on the device and select: Zwave-Synchronize-Update with Interview. I did this with event viewer at level 3 and watched the activity. Afterwards, all Zwave devices were fine. PS: Also, make sure Zwave is still checked in Configuration Tab, just in case the upgrade turned it off.

@bpwwer I migrated yesterday from Polisy to eisy with ZMatter Zwave. I managed to get everything working fine. This morning, I had trouble getting in to Polyglot, so I rebooted eisy. Everything went down hill from there. After the start up, none of the Node Servers were running. I tried several time to start them manually with no luck. After several restart PG3's, reboots of eisy, and removal of power from eisy, I got 4 out of my 6 running. The 2 that wouldn't run were Weatherflow & Elk. After trying to stop and start these two node servers several times, I tried rebooting eisy one more time and after that I was able to manually start Elk Node Server. Weatherflow would still not start. Of interest, is the Weatherflow log would also not populate. I tried setting logging to debug and tried to start up several times more. As a last resort, I tried re-installing Weatherflow in to the same slot, like I had to do yesterday. THe Node Server apparently updated from v3.0.25 to 3.0.26 (the last time I checked for updates was just before the migration). I tried several times to stop and start the Node Server, but Weatherflow will still not run. I have pm'ed you the log files. Thanks for any help you can provide. dc

I did the migration from Polisy with Zooz dongle to eisy with Zwave Matter this morning. Other than a brief issue with migrating UD Mobile favorites, which Javi took care of right away, all went fine. Follow the wiki instructions which were just updated again. I believe I saw in the wiki that you can go back to Zooz dongle if you don't make Zwave changes.

Updated both Polisy & eisy with no issues. PG3 started fine for both.

Using USB dongle allows for easy upgrades down the road when the next hardware version is available. I utilized a USB extension cable and a wall mount that I 3D printed to hang the dongle. There is another post with examples of 3D printed mounts.

Thank you

Bob, could you elaborate on the resources available to learn how to develop a Node Server? Is there something that explains tools required and how to setup the environment?

This may be way off, but...... If you are selecting the armed/disarmed mode from the drop down field in the admin console and selecting the "set" button on the left side, do you have any other device open at the same time (Elk-RP, any other Elk app, ect)? There can only be one item connected at a time.

If you arm your Elk from the Elk Keypad, does the Node Server update to show you are armed?

It worth trying a new power supply.

You indictated no errors in the Node Server log, but is anything logged when you select armed and use the set button in the Node Server admin console?

Are you hitting the "Set Armed Status" button?

Yes, however, your post referenced the wiki instructions, not the ones Chris posted above. The instructions above are a little clearer and I wanted to make sure you remembered it was there. My link takes you right to his post containing the updated instructions.