brians

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 -

So to confirm: Removing and updating the zooz does not lose any info in isy? Can the zooz usb be replaced with another in case of failure etc - is all the info stored on isy? in my experience using the single on pc I got impression that the dongle stores all the associations and the isy just interfaces with it therefore resetting or replacing will break zwave network.

This works much better than the version I tried a couple years ago!

I figured out... I have to make my program like this...

I installed this and have it setup with pushover, but I see not messages nodes appear in IoP I can press send in ISY and I get a blank pushover notification on my iPhone, but I see no way to access these custom messages.

@tired_runner My Yale assure lock requires a code to exclude/include. There is no factory reset button. Entroll: PIN followed by # Press 7 # Press 1 # Unenroll: PIN followed by # Press 7 # Press 3 # When I added my lock back in after upgrading to Polisy it took several tries. Then afterwards, communication was flakey for a while but eventually is more stable now as Z-Wave network seemed to learn/heal on its own - I would say 99%. I have 20+ Z-Wave devices. Here is information on mine... strange the last route was the node 4 family room bird lamp which is just about the furthest away Z-Wave device from it LOL, but not sure it uses it because it looks like it is also talking direct to ISY. Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] ---------------------------------------------- Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] Front Door Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] ZW007_1 uid=7 security=S0 type=4.64.3 mid=297 tid=32770 pid=1536 model=5 Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] Association Group ID 1 Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x5E V2 ZWAVEPLUS_INFO Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x72 V2 MANUFACTURER_SPECIFIC Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x98 V1 SECURITY Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x5A V1 DEVICE_RESET_LOCALLY Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x73 V1 POWERLEVEL Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x86 V2 VERSION Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - Secure Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x80 V1 BATTERY Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x62 V2 DOOR_LOCK Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x85 V2 ASSOCIATION Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x59 V1 ASSOCIATION_GROUP_INFO Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x71 V4 NOTIFICATION Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x70 V1 CONFIGURATION Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x63 V1 USER_CODE Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x8A V2 TIME Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x8B V1 TIME_PARAMETERS Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x4C V1 DOOR_LOCK_LOGGING Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x4E V3 SCHEDULE_ENTRY_LOCK Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - x7A V3 FIRMWARE_UPDATE_MD Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - xEF V0 MARK Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] Last working route from ISY to Node 7 - Front Door Mon 03/14/2022 11:57:27 AM : [ZWAVE-TX ] [01040092076E] REQ ZW_GET_LAST_WORKING_ROUTE Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] - Node 4 - Family Room Bird Lamp Mon 03/14/2022 11:57:27 AM : [ZW-SHOW ] Mon 03/14/2022 11:57:27 AM : [ZWAVE-TX ] [01070080070000FD82] REQ ZW_GET_ROUTING_INFO Mon 03/14/2022 11:57:27 AM : [ZWAVE-TX ] [01070080070100FE80] REQ ZW_GET_ROUTING_INFO Mon 03/14/2022 11:57:28 AM : [ZWAVE-TX ] [01070080070001FF81] REQ ZW_GET_ROUTING_INFO Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] Node 7 - Front Door has the following neighbors Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 1 - [This ISY] Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 2 - Living Room Outlet Front Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 3 - WaterCop Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 4 - Family Room Bird Lamp Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 8 - Dining Room Salt Lamp Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 14 - ZW 014 Binary Switch Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 15 - Downstairs Hallway Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 16 - Family Room Xmas Tree Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 17 - Master Bedroom Lamp Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 18 - Living Room Xmas Tree Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 19 - Rec Room N Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 21 - Dining Room Lamp Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 22 - Main Bathroom Light Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] - Repeater - Node 27 - Outside Xmas Mon 03/14/2022 11:57:28 AM : [ZW-SHOW ] Mon 03/14/2022 11:57:28 AM : [ZWAVE-TE ] [85/05] Assoc Groupings Get ACK,AUTO,EXPLORE To=0x07 Mon 03/14/2022 11:57:28 AM : [ZWAVE-TX ZW007_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x07 Mon 03/14/2022 11:57:29 AM : [ZWAVE-RX ZW007_1] [98/80] Security Nonce Report - nonce=[53A7FE92E4ACA80B] ACK,AUTO,EXPLORE From=0x07 Mon 03/14/2022 11:57:30 AM : [ZWAVE-RX ZW007_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x07 Mon 03/14/2022 11:57:30 AM : [ZWAVE-TX-NONCE ] ... Mon 03/14/2022 11:57:30 AM : [ZWAVE-RD ] [010A001307038506012500AB] REQ ZW_SEND_DATA Mon 03/14/2022 11:57:30 AM : [ZW-SHOW ] Node 7 - Front Door has 1 association group Mon 03/14/2022 11:57:30 AM : [ZWAVE-TE ] [85/02] Assoc Get grp=0x01 ACK,AUTO,EXPLORE To=0x07 Mon 03/14/2022 11:57:30 AM : [ZWAVE-TX ZW007_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x07 Mon 03/14/2022 11:57:30 AM : [ZWAVE-RX ZW007_1] [98/80] Security Nonce Report - nonce=[0BE4471BCE14DCC1] ACK,AUTO,EXPLORE From=0x07 Mon 03/14/2022 11:57:31 AM : [ZWAVE-RX ZW007_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x07 Mon 03/14/2022 11:57:31 AM : [ZWAVE-TX-NONCE ] ... Mon 03/14/2022 11:57:31 AM : [ZWAVE-RD ] [010D001307068503010100012500B0] REQ ZW_SEND_DATA Mon 03/14/2022 11:57:31 AM : [ZW-SHOW ] Associations for group 001 of ZW007_1 Front Door Mon 03/14/2022 11:57:31 AM : [ZW-SHOW ] Max Associations = 1 Mon 03/14/2022 11:57:31 AM : [ZW-SHOW ] - Node 1 - [This ISY] Mon 03/14/2022 11:57:31 AM : [ZW-SHOW ] Mon 03/14/2022 11:57:31 AM : [ZW-SHOW ] ----------------------------------------------

@peterathansI have three Zen71 switches but haven't installed any of them other than one in a test box. I did make an ISY scene with another device. I posted this earlier, but will say again here briefly that the Zen71 report their status back almost instantly to the ISY whereas a Jasco equivalent seem to have some firmware issue which takes 2-3 seconds (it is uncertain if we ever got associations to work on these devices if this would become faster or still 2-3 seconds). Regardless, for now I think you could make a scene with a couple Zen71 by adding them both as controller and just using the "Default" in an ISY scene. The speed of all this round-trip to the ISY and back to the other switch is fairly fast - not as fast as Insteon, but still is very fast with a Zen71. Realize that if you do this method, it requires the ISY to handle the scene, but ISY is reliable - at least my ISY994i I can confirm it runs without errors. My IoP I cannot claim this due to lack of experience/history with it and the stage it is at now there are lots of updates/messing around now but should stabilize - when I leave it alone, it doesn't ever seem to crash for no apparent reason

So far here the only devices that are reported in this thread which add the z-wave options in a scene are motion sensors. From reading here, looks as if other hubs like hubitat can do... https://support.inovelli.com/portal/en/kb/articles/how-to-use-the-z-wave-association-tool-hubitat This is a support from inovelli on hubitat, but I get the impression that hubitat can work with any brand of switch that supports associations. An acknowledgement from UD regarding this support in IoP would be nice... whether or not they plan to support this.

Based on what gviliunas did, I thought maybe it works with motion sensors... I tried with only motion sensor device and realized that it depends on what node you add for the device and what the device is. In my case, I am testing a Jasco in-wall motion switch and another Jasco regular switch and I attempt to control the other switch based on an event (hopefully motion) from the controller switch. I used the Notify Sensor node from the motion switch, which then enabled an additional option in the scene other than the Command, Default, and Ignore. I cannot remember exactly what it was called but was named Z-Wave something and ended with MC... the reason I cannot remember is then everything suddenly went sideways... It started writing updates to the Z-Wave device... then I would get communication errors on the other device. Then my entire Z-Wave network became unresponsive. I was able to remove both devices however no other Z-Wave would work and would give communication error. Rebooting IoP did not resolve, rebooting entire Polisy did resolve fortunately. I then added back the two switches and strange enough they retained the same Node ID numbers as before - not sure why this is, maybe they were not removed correctly before from the dongle and it recovered them somehow. Anyways I spent about 45 min fixing this so I am hesitant on testing any other Z-Wave stuff right now on Polisy LOL. I have my ISY994i that I will use to test.

I already did that to confirm, was meaning that I believe it was already installed from time of purchase. Prior to 5.4.1 we could determine if had UEFI by whether or not the TPM option was enabled and mine was. If new people are reading this looking at Polisy but are a bit hesitant because of some of the issues, then they shouldn't have to if UD is in fact shipping them out brand with with UEFI.