tlightne

Just FYI I have my Alexa's that are close to each other with different wake names..

Aeotec and Zooz both have zwave motion sensors that also measure light either would work if you have zwave support in your Eisy..

Do you have other Node servers and are they connected???

@bpwwer Is it possible to get the daily lightning count added to the Ambient Weather node server? It has last distance but that is all for lightning. Thank you...

If you are not having any issues I would wait. I am not doing any upgrades until 3.1.34 shows up.

@bmercier OK so the only way to restart PG3x is to reboot Polisy??

I was able to upgrade my Polisy to 3.1.32 today by using the My Notifications Bata feature on UD Mobile. The only issue I had was all my custom contend notifications I had setup reverted to the customized content #1. It did not delete anything so I was able to back through my notifications and reassign the proper content to the proper notification. @bpwwer Is there no longer a button to restart PG3x on the web UI ? I thought it used to be in the dropdown list of System.

@tazman Thank you for the reply. I tried to complete that upgrade earlier today and I had the same result as you will try again tomorrow.

@tazman Which upgrade?? From PG3 to PG3x or PG3x 3.1.29 to 3.1.32??

It is the same as the HTTP address except the port is 8443 instead of port 8080. You are on a local network so it really is not necessary to have the HTTPS url...

From the Polisy users guide.. Upgrading to PG3x 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. NOTE: This process will remove PG2 and PG3. Furthermore, there is no "undo" for this process, so be certain that you are ready to update to PG3x before proceeding. Specifically, please make sure you take good backups.

@JaviWill this run on Polisy if we are already migrated to PG3x??? Thank you

@JMcKain Just be advised there is no going back to PG3 after doing this upgrade.

Did you try logging into PG3x and restarting the node servers?? If they still do not restart PG3x may need to be restarted.

I entered the token and ip address of my bridge and all it discovered the new nodes with out issue. Thank for the quick response and the great explanation on the Zeroconf module. The only other node server I can think of the is using anything of mt network would be the ShellyRGBW2 it is driving LED strip lights I have around the eves of my house. Thank you again.....

Yes I restarted the node server after I saw the first error but did not help. Do you have to make the bond Bridge discoverable again? I assumed the Node server already knows about it from the original ceiling fan installation. I am running the Ring NS, Holiday NS, Open Weather Map NS, ShelleyRGBW2 NS, Ambient Weather NS, Notification NS, Bond NS. I have no idea what Avahi/Zeroconf listener is, I have nothing else installed beyond the Node servers listed.

@Goose66I do not think I pressed it more that once but I just tried it again still seeing errors here is the latest log. Thanks Bond_6-15-2023_33900-PM.zip

@JTsao I log out of AC after hearing the 5 beeps which before the latest upgrades you were forced out. Clear Java cache (Same as old process) then log back into AC and get only one reboot notice which I follow.

@Goose66I have added a second ceiling fan to my Bond Bridge but Discover in node is creating errors and the node server does not see the new fan. The original fan (Front Porch Ceiling Fan) is working with out issues. The Bond app sees the new fan and can control it with out issues. I have included a current log. Hardware is Polisy 5.6.2 PG3x 3.1.29 Bond Bridge is Firmware 3.13.6 Thank you Bond_6-15-2023_121405-PM.zip

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.

If you are not running PG3X there will not be an update path for Polisy to 3.1.29. PG3 3.1.21 is the latest version.

@theitprofessor I initially did the migration but one did not install all the nodes. I had to exclude it and include it with S2 before it would install all the nodes. Looking at them in AC they show S0 so I would say they are not using S2.

It comes with (1) external Zwave antenna and (1) Zigbee external antenna. The antennas are tuned for the proper frequencies...I believe it is a standard SMA connection..

Did you close the Admin Console and re login since you installed the Node server??

Upgraded without issue on Polisy from 5.6.0. Cleared Java cache, restarted Admin Console and logged in to AC. I did receive the popup telling me I needed to reboot. All is good...