brians

Working now thanks.

@TJF1960 I was thinking of that but the program triggers between ready and not ready if I open/close the front door. What I ended up doing is making a variable named something like Alarm_Armed When my program detects armed stay or away, it sets the variable to 1 Then another program that detects disarm, it checks if partition state is ready and Alarm_Armed=1 then is true, and the then sets Alarm_Armed=0, and also inits in case ISY was rebooted. Alarm Disarmed - [ID 006C][Parent 0061] If 'Alarm Panel / Partition 1' Partition State is Ready And $Alarm_Armed is 1 Then Set 'Notification Controller / Service Pushover Brian' Priority Normal Set 'Notification Controller' Message Alarm - Disarmed Set 'Notification Controller / Service Pushover Brian' Send $Alarm_Armed = 0 $Alarm_Armed Init To 0 Else - No Actions - (To add one, press 'Action') Alarm Armed Stay - [ID 006A][Parent 0061] If 'Alarm Panel / Partition 1' Partition State is Armed Stay Then $Alarm_Armed = 1 $Alarm_Armed Init To 1 Set 'Notification Controller / Service Pushover Brian' Priority Normal Set 'Notification Controller' Message Alarm - Armed Stay Set 'Notification Controller / Service Pushover Brian' Send Else - No Actions - (To add one, press 'Action')

Yes I have 3.0.47 also.

I can’t seem to find a way to trigger a program based disarm. I can do for arm stay and away and alarming etc but no way to trigger a program when the alarm has been disarmed.

If you currently have Insteon and plan on going to Z-Wave then I would go for the Polisy. If you do not have your serial cable for the PLM it is easy to make one. Since you are running only Insteon, the transition will be easy. For your roomiermote it should work but since Polisy uses port 8080 for its web interface, you would probably have to add a :8080 to the end of your IP address in the REST commands. The ISY994i only supports Z-Wave 500 series. The newest Z-Wave standard is 700 series which the Polisy supports via S2 dongle. Looking back at history, people with older 300 series boards on ISY could not upgrade to newer versions of firmware because support was dropped and their Z-Wave stop working. I can see the same thing happening with ISY994i and 500 series boards being left behind. I do believe that all future Z-Wave development at UD is going to be with Polisy only, and we will see no new features on the older ISY994i with 500 series boards. With Polisy, the Z-Wave is theoretically upgradable in the future so if a new Z-Wave series comes out (eg. 900?!?) you could just insert a new dongle. If you decide to leave Insteon and Polisy for something else in the future, you still have a useable dongle for something else like Home Assistant. Regarding polyglot node servers, with PG2 being deprecated, future Polyglots will need PG3 which only runs on a Polisy (you cannot install PG3 yourself on your own hardware like you could before with PG2). Right now PG2 are still working but the focus is on PG3. Note that Polisy currently runs both PG2 (for legacy) and PG3 servers so you would have access to everything.

See this starting from Advanced | Factory Reset Z-Wave dongle https://wiki.universal-devices.com/index.php?title=ISY_Users:V5:ZWave:Advanced_User_Guide:TopMenu This is for ISY994 however iI think the same principles apply to Polisy except it uses an external usb stick. Since Polisy does not have similar function to backup stick yet I think we should backup separate on pc and restore if replacing the dongle in a working system. I believe that if I has just placed my brand new stick in without restoring then all my z wave devices would have been orphaned and I would have had to exclude include one by one. Someone here with a test Polisy can confirm by backing up nvram, resetting their stick and plug back in Polisy and note if all wave devices are orphaned, then restore nvram to same stick and plug back in again to see if zwave works. Of course shut down polisy in between removing adding stick. UDs goal I imagine is to create an automated tool that converts the isy994i backup file to one compatible with an s2 stick, in the future for those updating from isy.

@JimboAutomatesI noticed the log package contains pg3-current.log which has logins and passwords for all my PG3 nodes. debug.log looks ok, I will send you that for now until I look over other log to make sure.

You said earlier yours was a new install and stick, I misunderstood and thought you meant you had no previous z-wave on there and when you said new install meant a new IoP install/setup with no previous Z-Wave devices. So please confirm that your old z-wave dongle was being used in IoP and had Z-Wave devices, and then replacing it with a brand new z-wave dongle you still had everything in Z-Wave show up and useable in IoP? If this is the case then there is no reason to do a NVM backup and restore when changing dongles and IoP must reprogram the dongle.

Ok good news is I restored my Z-Wave configuration to a new Zooz stick. The steps are: I shut down Polisy. I removed the old Zooz stick and backed up the NVRAM using PC. It saves as a zip file. I plugged in new stick in PC, then upgraded firmware on my replacement stick I restored saved NVRAM to new stick on my PC. I plugged in Polisy and turned on let it boot up and all my Z-Wave works as before. I recommend whenever doing any significant changes to backup the Zooz stick on PC, in case need of restore... until UD implements a backup/restore like they did in the ISY994i (I presume that is what it did?!?). Now I still do not know what would happen if I just placed in the new stick in Polisy without restoring the saved NVRAM from old stick. I did not want to try because I thought what I did was the proper way based on my research what other hubs and HA people do.

I get this error... api_key is not defined, must be running local version or there was an error retreiving it from PG3? Must fix or add custom param for local I was getting this error, and a couple others stating that was expired and must re-key. I deleted the app in my ecobee account, tried uninstalling and re-installing the Node server and all I get is this error now.

@asbrilIf you look a few messages back I posted to a github link where they discuss performance issues on large networks. I believe the latest version is supposed to help/fix with lots of Z-Wave network traffic. I have had the first three symptoms on my network running 7.15. The latest 7.12.2 is supposed to fix.

The pinouts for 2413S PLM are in the PLM manual. It has been posted about elsewhere how to make a cable, but here is a screenshot of it here... I had thrown out my cable (probably accidentally) like most others did. When I moved to Polisy, I made my own PLM cable for 2313S out of a blue cisco console cable. I just cut off old end, crimped on a new RJ45 end with the correct wiring - only pins 1, 7, and 8 are used. If you don't have a crimper, just cut the cable in middle and re-connect the wires accordingly and test with a multi-meter.

I just received new stick and updated firmware at the office here successfully. I then restored the nvram backup I had made and looks the same - it shows all the nodes etc. like my old stick did when testing at home. I will swap sticks later when home and let know.

I see a new version is up since I got home, I installed and seems to be working fine now

I did that, I had edited my above message earlier to show but I guess I didn't save. Just notice one more update and now am at 3.0.47

When looking in polisy I see it creates the folder and are files in there... seems like the installer has a bug. [admin@polisy /var/polyglot/pg3/ns/00:0d:b9:59:40:78_2/evldsc-pg3-3.0.8]$ ls -la total 19 drwxr-xr-x 4 polyglot polyglot 12 Mar 17 15:20 . drwxr-xr-x 3 polyglot polyglot 3 Mar 17 15:20 .. -rw-r--r-- 1 polyglot polyglot 2132 Mar 17 15:20 .gitignore -rw-r--r-- 1 polyglot polyglot 1704 Mar 17 15:20 POLYGLOT_CONFIG.md -rw-r--r-- 1 polyglot polyglot 624 Mar 17 15:20 README.md drwxr-xr-x 2 polyglot polyglot 7 Mar 17 15:20 evldscns -rw-r--r-- 1 polyglot polyglot 7770 Mar 17 15:20 evldscns.py -rw-r--r-- 1 polyglot polyglot 60 Mar 17 15:20 install.sh drwxr-xr-x 5 polyglot polyglot 6 Mar 17 15:20 profile -rw-r--r-- 1 polyglot polyglot 1769 Mar 17 15:20 profile.zip -rw-r--r-- 1 polyglot polyglot 21 Mar 17 15:20 requirements.txt -rw-r--r-- 1 polyglot polyglot 1040 Mar 17 15:20 server.json [admin@polisy /var/polyglot/pg3/ns/00:0d:b9:59:40:78_2/evldsc-pg3-3.0.8]$ I am not much of a programmer/developer but if I was to guess, the reason is the archive was created with the folder name and it incorrectly gets extracted into a folder evldsc-pg3-3.0.8 where instead it should be in the root of the 00:xxxxx_2 node directory. Therefore the installer cannot locate the server.json file.

@GeddyI had already tried the ssh method and currently there are no updates. I just tried again... [admin@polisy /var/polyglot/pg3/ns]$ pkg version|grep pg3 pg3-3.0.45 ? [admin@polisy /var/polyglot/pg3/ns]$ sudo pkg update Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. [admin@polisy /var/polyglot/pg3/ns]$ sudo pkg upgrade Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [admin@polisy /var/polyglot/pg3/ns]$ pkg version|grep pg3 pg3-3.0.45 ? [admin@polisy /var/polyglot/pg3/ns]$

I installed, didn't seem to do anything, so deleted. Just had a backup and restore button in Node.

@Goose66 Hi, I just purchased and get this error.

Mine shows 3.0.45 after updates. I have reboot entire polisy also.

@kzborayThe original instructions in this thread said to use OTW (over the wire) for the stick, not OTA (over the air). Regarding NVM Backup/Restore I am going to try to do this when I receive a new stick, unless there is a different way - for all I know IoP will detect this and update the stick... @Michel Kohanim can you confirm what happens when replacing a failed Z-Wave stick in IoP with a new one? If not, is backing up the NVM and restoring to new stick the correct procedure?

What I was thinking. Anyways did you happen to restore to the new one using the backup process in the software or just started fresh with new stick ? if I get mine and updates I will attempt to restore backup I made from existing one.

@telljclThere is a pinned thread about migrating to Polisy here...

@gviliunasGood to hear that it worked. That firmware is supposed to fix issues with lots of Z-Wave traffic and large networks. I am wondering since you are just experimenting with Polisy, are you able to test NVM backup and restore feature? Eg... do an NVM backup, then reset the S2 dongle... then restore it and put back in Polisy to see if it still works. I ordered another stick off Amazon... can return if doesn't update also, have ticket request with Zooz for current one.

I have the same error when I tried tonight. I did notice that all of the nodes show up on the Windows app that were on the ISY. So how did you replace the old with new dongle in ISY? Did you have to redo Z-Wave network or did ISY reprogram it? Mine is 7.15 and I bought from Amazon in Canada. I have found this... in there is links to a newer 7.17.2 version https://github.com/zwave-js/node-zwave-js/issues/3906 I tried this one also and did not work. I also see in that link/thread they mention backing up and restoring the stick. Does anyone here know how to do that? I am thinking it is the NVM backup and restore button? I did this and seems to have created files that have XML file which corresponds to the nodes. From what I can tell, it looks as if one can just pull the stick out of Polisy, place in PC and could perform OTA updates on devices etc. then place back in Polisy -