bob123

I recently migrated from isy with ELK to polisy and ELK node server. Was pretty painless. I had copied out my programs to notepad prior to starting. After I had restored to the polisy, I installed the ElK nodeserver. Each program that referenced an ELK item has those references commented out; I just updated the program with the appropriate device/ item from the ELK nodeserver. I used the notepad program text as an aid when I wasn’t sure what the placeholder was. It has been working well for a few weeks now.

Great news (except for the zwave rebuild). I did the full rebuild which was pretty straightforward. I had only door locks and repeaters- had to exclude each one and then include. Had to uninstall the door locks to bring them close to the zooz stick so that process would work. I then had to edit each program fixing the zwave device name - some were commented out and some were incorrect. pretty painless except removing the physical locks from the doors.

See my thread from a few weeks ago. My issue was very similar - I was going from isy to polisy. The last response in the thread is the solution I used that worked perfectly. Not sure if eisy supports the zooz stick or only zmatter, but worth a shot. Polisy supports both.

Here is the solution from the great support staff (Chris) - it worked great. Basically resets the configuration/system tab on the admin manager and restores ability to have a zooz 700 zwave stick instead of a zmatter. One additional step I found was to re-enable insteon and zwave on the configuration/system tab. Do not do migrate to zmatter. 1) ssh to Polisy 2) run command: sudo rm /var/isy/FILES/CONF/0.UCF 3) close ssh (unless you want to keep it open for something) 4) Restart IoX 5) Go to Configuration Tab in Admin Console, you should see a button "Migrate to ZMatter Z-Wave", this indicates that you are now currently using original Z-Wave. (Don't press the button obviously) 6) Update the values in the Configuration Tab to what they were before 7) Under the Z-Wave top level menu you should see all the options (like add, remove, etc.)

I received a response from support. When migrating a backup from ISY-994 to eisy or Polisy, it automatically sets it to use ZMatter Z-Wave. So, any restore of an isy backup to polisy will configure it to zmatter only. They will be sending me instructions how to configure the Polisy use the original Z-Wave implementation (using the Zooz dongle). Thanks everyone for the assistance.

I did not do a separate zwave backup on the isy. I just did a normal full backup. How would doing the zwave backup have affected the restore to the polisy? If the older 300 series zwave file was 'restored' to the polisy, how do I rebuild the polisy zwave from scratch. The polisy does not even recognize the device. Unfortunately, I did not backup the polisy when it was running correctly with zwave dongle, so can't restore that way. Is there a way to reset iox/zwave on the polisy to initialized state? If I were to do that, how would I prevent the 300 series zwave from my isy from restoring again? Thanks

Thanks landolfi - I tried the suggestions in the link to override the usb port for the zwave stick. Unfortunately did not help.

Tried unplugging all the zwave devices in the network - was only 2 plug in aeotec doorbell/range extenders and a lock. Rebooted. No change. The polisy still says zmatter zwave not responding. I tried the usb extender to ensure the zooz stick was firmly plugged in. No help either. I've submitted a support ticket. Very frustrating since I went through all the effort to ensure that zwave with the zooz stick worked properly on the polisy prior to moving my insteon to it from the 994. Now I have a non-functioning isy994 because I upgraded to 5.3.4 which does not support my 300 series zwave and a polisy that I can't use.

Thanks- will unplug my zwave devices and reboot. Strange part is it was working great prior to the restore from backup. I also ordered up a usb plug extender. Found some posts that plugging in the plm usb could possibly cause interference to the zwave stick usb connection as it’s a tight fit.

Yes. It was still checked after I restored the backup from the isy. I then unchecked it, saved and rebooted, then checked it, saved and rebooted. Still not working. I then tried removing the PLM and rebooted- still no help.

I decided to finally take the plunge and upgrade my isy to my polisy. I got the polisy up and running prior to the upgrade. All running great. Also had some PG3 node servers running great. My isy was on 300 series zwave. I upgraded it to 5.0.16 and all went well. I then installed a zooz 700 stick on the polisy, unrolled some of my zwave devices from the isy and enrolled them on the polisy. Worked great. Next step was to upgrade the isy to 5.3.4 so that I could back it up and restore my insteon stuff to the polisy. I knew that zwave would not migrate (series 300) and that I would manually have to rework it on them on the polisy. Did not do the 'migrate zwave' backup - just normal backup. Restored the fresh backup from the isy to the polisy. Problem - the zwave does not work anymore on the polisy. Clicking the zwave menu says - zmatter zwave not responding. I am completely stuck. Why would the polisy support the zooz stick perfectly prior to restoring the backup from the isy? Now is seems like it does not recognize the device and is looking for the zmatter board. I have checked and unchecked the zwave support under configuration and rebooted several times. Any help is appreciated.

The timeout was not the issue. It was my own late night testing. I started from scratch with new entries and it worked. I had a typo in the actual isy test command. Entered /rest/get/vars/1/1. It should be /rest/vars/get/1/1. I tested different timeouts from 800-3000 and all worked. thanks everyone for the assistance

I spoke too soon on success. Using the http Get works great from the polisy to the isy. I cannot get a similar call working from the isy to the polisy to set a variable. The error I get is TCP client request failed. [Net Module Rule: 30:404]. I have tried both the secure and insecure port (8443 and 8080). I know it’s reaching the polisy because an incorrect login password gives a different error message. Works fine from Chrome. Any ideas? thanks

That’s very close to my plan. Modify existing isy programs to work on triggering from sets of state variables so that I can transfer functionality gradually over to polisy with little modification. As you said, it’s getting time to fade away from my trusted isy.

Goose66 - thanks so much. Changing to an Http get did the trick. Thought I had tried that previously but guess not. Knew it was something simple. Much appreciated.

I'm starting to plan my migration from isy to my polisy. Both are up and running, but given that the isy is 4.9 and series 300 zwave, I've decided to take it slowly. Breaking the migration into 2 parts- first, move zwave and ELK to the polisy and ensure I'm happy with behavior, then upgrade the isy to latest 5.x.x fixing all issues and then move insteon over. I will hand update the existing ELK and zwave programs after everything is on the polisy. To accomplish this, I want to utilize variables and the network module to control programs/state between the zwave/ELK on the polisy and the programs on the isy using insteon. I've tried to use the network module from both sides to set/get variables from the other side and cannot get it to work. I can go into Chrome and 192.168.1.206//rest/get/vars/1/1 works perfectly. This works to both the isy and the polisy. From the network module on the polisy, I try the same and get a 'TCP client request failed [Net Module Rule 1:715]'. I have it setup as follows I'm sure I have a setting incorrect, but have tried just about every one. If I put in an incorrect password for the authorization I get a different error with a 401 Error, so I know its talking to the isy. I have also tried different rest commands. These all work from Chrome. I have tried this also from the isy to the polisy. I used https and 8443 for the port - got the same type of errors. Any suggestions are welcome. Thanks

Thanks everyone for the assistance. Haven’t taken the leap to migrate to the polisy yet as my 994 is on series 3 zwave which complicates the move.

I understand that developers can charge for their work, but previously I installed PG3 node servers on the polisy with no portal account linked to the polisy.

I do not have have an active portal account linked to the polisy. My account is linked to my isy994. The polisy is linked to my ud account. But, I have been able to purchase/install PG3 node servers in the past and have a few installed Did this change so that I now have to purchase an additional portal account just to test the polisy and see if I am comfortable migrating to it? I set the log to debug and saw no activity at all when trying to install a node server. I tried installing Holiday and Google Holiday.

The upgrade process worked for both the polisy and pg3. ISY 5.5.9, PG3 3.1.18. But, I still have my original issue. I cannot install any new PG3 node servers. I hit the install button, it shows depressed and nothing happens. Tried 2 different browsers thinking it might a browser issue - no help. Any ideas or just submit support ticket?

Thanks Dennis, Ran the pkg install and rebooted. The tail -f log is now showing many, many upgrades happening. Will let you know the outcome

I have continuous scrolling of The most recent versions of packages are already installed Updating FreeBSD repository catalogue... FreeBSD repository is up to date. 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. New version of pkg detected; it needs to be installed first. Checking integrity... done (0 conflicting) The most recent versions of packages are already installed Updating FreeBSD repository catalogue... FreeBSD repository is up to date. 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. New version of pkg detected; it needs to be installed first. Checking integrity... done (0 conflicting) The most recent versions of packages are already installed

uname -a FreeBSD polisy 13.1-RELEASE-p5 FreeBSD 13.1-RELEASE-p5 releng/13.1-n250174-753d65a19a55 POLISY amd64

I'm a long time, very happy 994 user with a rock solid large insteon, some zwave installation. Every few months, I think about migrating onto my polisy (purchased as early adapter), and every time I am frustrated by issues that leave me feeling that the polisy is not fully production ready. Today I tried to install a PG3 node server. Finder would not find it - did power cycle. I go to the store, choose a free node server (example, google holidays) hit install and nothing happens. The button pushes in and nothing. Tried restarts. Figure maybe PG3 is out of date. I am at 3.1.16, it suggests 3.1.18. Go to admin console and do upgrade packages. Disconnects me, wait awhile, finder can't find it. Add it back manually (IP). Still at 3.1.16. So upgrade is failing. My polisy is at 5.4.5. Figure that is out of date, but upgrade packages does not update it either. What am I doing wrong? Can't install new node servers, can't upgrade packages or versions.

Similar issue for me tonight. Cannot connect from Mobillinc through the portal