tlightne

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

I have three Kwikset 916 running Zwave connected to my Polisy and Zmatter board. They work with out issues. Polisy is 5.6.0.

@Sparks For what is is worth I have been using the Bond Node server for around a year running ceiling fans and I have not had any issues with the Node server.

@landolfi Are your ZSE40s reporting battery level?? Thanks

Add a device = Include Remove a device = exclude

Not a global Zwave lock issue. My Kwikset 916 Zwave locks all work with out issue...

@Jimbo.AutomatesGot it thanks...

How does one obtain a Portal API key??

Does ISY Portal show it online or offline??

@JSylvia007 You should not have any problems with Aeotec. I use Aeotec motion sensors and off brand open/close sensors with out any issues..

You should always do an exclude on any Zwave device before including. Even if it is new. Zwave devices can only include into one network and you never what occurred with your device before you opened the box..

There is a Keep Awake node where you can adjust the keep awake time...