bigDvette Posted January 4, 2023 Posted January 4, 2023 After an update today of the PG3 to version 3.1.17, I was able to get all my node servers configured and running. What I did was as follows. 1) I started clean with Eisy. I never got WIFI setup to work, but didn't need it. 2) I then got all my node servers setup in the same slots as the the Polisy I was migrating from. I made sure all the nodes were in the admin console and validated they had the same node_ids. The only one I couldn't get the match on was the occupancy sensor UUID to use with locative, but the ISY node was the same ID. Make note of the User ID, base URL and Host Name fields in the node server configuration in AC. They follow a format, just a bunch of pasting in step 5. This included setting up occupancy sensor in ISY portal on the slot I used it in previously. 3) After all that was working I ensured that I did not have my PLM attached (I migrated my polisy to a USB PLM before I started any of this, but I also got my serial PLM working with the adapter cables). I then unchecked the Insteon and zWave options in the AC Config tab. 4) I backed up my polisy at this point and restored it to EIsy. 5) After it came back up, I went in to each node server from menu at top and changed the User ID, Base URL and Hostname to the ones saved from step 2. 6). I rebooted IOX and made sure node servers were populating. 7). Shutdown eisy and installed existing zooz stick and started Eisy. 8 ). After it came back, I enabled zWave in AC config tab. Then did a restart IoX. 9). Validated the zwave devices were controllable. 10). Shutdown eisy and attached the PLM and started Eisy. 11). After it came back up I enabled Insteon in AC config tab. Then did a restart IoX. 12). Let it run and do its thing until devices had been updated. I have a large Insteon network but it didn't take nearly as long as the Polisy takes. 13). Did some tests, then went over to the portal. Went to my ISY I was migrating from in portal and Did the maintenance -> migrate to option and migrated all the options to my Eisy. Now I just need to have the purchased node server licenses moved and I should be good. 1
asbril Posted January 5, 2023 Posted January 5, 2023 On 1/3/2023 at 10:37 PM, bigDvette said: After an update today of the PG3 to version 3.1.17, I was able to get all my node servers configured and running. What I did was as follows. 1) I started clean with Eisy. I never got WIFI setup to work, but didn't need it. 2) I then got all my node servers setup in the same slots as the the Polisy I was migrating from. I made sure all the nodes were in the admin console and validated they had the same node_ids. The only one I couldn't get the match on was the occupancy sensor UUID to use with locative, but the ISY node was the same ID. Make note of the User ID, base URL and Host Name fields in the node server configuration in AC. They follow a format, just a bunch of pasting in step 5. This included setting up occupancy sensor in ISY portal on the slot I used it in previously. 3) After all that was working I ensured that I did not have my PLM attached (I migrated my polisy to a USB PLM before I started any of this, but I also got my serial PLM working with the adapter cables). I then unchecked the Insteon and zWave options in the AC Config tab. 4) I backed up my polisy at this point and restored it to EIsy. 5) After it came back up, I went in to each node server from menu at top and changed the User ID, Base URL and Hostname to the ones saved from step 2. 6). I rebooted IOX and made sure node servers were populating. 7). Shutdown eisy and installed existing zooz stick and started Eisy. 8 ). After it came back, I enabled zWave in AC config tab. Then did a restart IoX. 9). Validated the zwave devices were controllable. 10). Shutdown eisy and attached the PLM and started Eisy. 11). After it came back up I enabled Insteon in AC config tab. Then did a restart IoX. 12). Let it run and do its thing until devices had been updated. I have a large Insteon network but it didn't take nearly as long as the Polisy takes. 13). Did some tests, then went over to the portal. Went to my ISY I was migrating from in portal and Did the maintenance -> migrate to option and migrated all the options to my Eisy. Now I just need to have the purchased node server licenses moved and I should be good. 2) I then got all my node servers setup in the same slots as the the Polisy I was migrating from. I made sure all the nodes were in the admin console and validated they had the same node_ids. QUESTION: I would have thought to first do the migration of the Node Server licenses in ISY Portal. Am I correct ? 5) After it came back up, I went in to each node server from menu at top and changed the User ID, Base URL and Hostname to the ones saved from step 2. QUESTION: I am not sure to understand. If you “purchased” the various node servers and added them in the same slot as in Polisy, why would you need these additional steps ? Now I just need to have the purchased node server licenses moved and I should be good. QUESTION : As above, did you not migrate these licences in ISY Portal ?
bigDvette Posted January 5, 2023 Author Posted January 5, 2023 2 - Well this is what I did. At the time all the node servers would not come up until 3.1.17. So I set them up as test licenses. Now you can do a backup and restore which didn't work when I was working on this. I also wanted to keep my Polisy up until I knew everything would work. 5 - When you restore the Polisy backup, the node servers get installed in ISY AC. The IP address on them was the IP address of the Polisy. I also has the UUID in there, so I had to manually change them. I don't think purchasing doesn't anything different, but 3.1.17 gave an backup restore option and it uses the internal IP. I did, Michael moved them for me. I tried to migrate them from portal but it said I already had licenses in the slot.
asbril Posted January 5, 2023 Posted January 5, 2023 14 minutes ago, bigDvette said: 2 - Well this is what I did. At the time all the node servers would not come up until 3.1.17. So I set them up as test licenses. Now you can do a backup and restore which didn't work when I was working on this. I also wanted to keep my Polisy up until I knew everything would work. 5 - When you restore the Polisy backup, the node servers get installed in ISY AC. The IP address on them was the IP address of the Polisy. I also has the UUID in there, so I had to manually change them. I don't think purchasing doesn't anything different, but 3.1.17 gave an backup restore option and it uses the internal IP. I did, Michael moved them for me. I tried to migrate them from portal but it said I already had licenses in the slot. THANKS
JTsao Posted January 10, 2023 Posted January 10, 2023 On 1/3/2023 at 9:37 PM, bigDvette said: 9). Validated the zwave devices were controllable. I am also interested in moving from Polisy/Zooz to eISY/Zooz for now. Just to be clear, after backing up IoX and PG3 from the Polisy, I would restore IoX on the eISY, then restore PG3 on the eISY (using the migrate from PG3 Backup button), move my Zooz dongle and 2448A7 Insteon dongle to eISY and at that point all of my Z-Wave network/devices would still be intact? So, I won't have to re-enroll everything?
Recommended Posts