tlightne

EISY is out of stock but from an email I received yesterday they should be back in stock by the end of the month.. For education on the EISY read through the WIKIs and and search these forums. If you only have insteon then EISY is your only choice to replace.. The 994 is usually rock solid and dies when either the power supply or SD card go bad. I would try replacing the power supply first.

@mmb Yes when EISY was introduced UDI offered a $75.00 you needed to purchase your Polisy in 2019 or 2020 to qualify but I never saw EOL announced. If Michel responds we will have our answer. From UDI https://www.universal-devices.com/product/eisy-home/ Discounts? Yes, in the form of trade-in and the offer expires on 01/31/2023: ISY994 purchased in 2019 or later: $36.00 Polisy2019 | 2020: $452021: $602022: $75 Polisy PRO2019 | 2020: $602021: $752022: $90

@Michel Kohanim Can you set the record straight once and for all on the life of Polisy??? I have asked @mmbwhere this was documented but as of today he has not produced that documentation. If us Polisy owners only have 3 years before EOL then I would like to start planning now to move to Eisy...

@bpwwer Thank you for the updates. This is perfect...

@bpwwer Backup and running again.. Thank you..

When you query them make sure they are still awake. They are battery so they sleep quickly..

@Techman He is on the 994 and if memory servers correct that uses the Ethernet cable..

@bpwwer I upgraded Ambient to the 2.0.9 in PG3x 3.1.36. Station online status in lox is false. I restarted the node server in PG3x and still see the same status. PG3 x shows it as running and UD mobile notifications say it is online. All the new nodes show up in PG3x dashboard. I have attached an error log. Getting parsing errors name ' raw' not defined. It also took the name from my Ambient weather station and added a new node in the proper slot to loc with all the new nodes. Can I just delete the old Node in lox? AmbientWeather_7-17-2023_63318-PM.zip

Since everything is so new with Zigbee I would open a ticket with UD support.. https://www.universal-devices.com/contact-us/

If you did not do a Zwave backup before doing your lox backup you will not have any zwave data in the lox backup. If you did a Zwave backup did you try a zwave restore after doing the lox restore??

@mmb You say you have <3yrs to move to Eisy according to UD. Can you tell me where this is documented? I must have missed it.

The Polisy is not EOL... Supply chain problems made it impossible to manufacture so UDI switched to Eisy for their customers..

The PG3x restart button has been removed. Unplug power and reboot polisy or easiy or sudo service pg3 onerestart

Yes as @Geddystates do not uninstall. When I upgraded the notification node server I went to the NS store clicked on the install button the next screen should give you the option to reinstall and make sure it is in the same slot.

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.