asbril

THANKS

I asked some questions in the "linked" post.

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 ?

So to use the Zooz on eisy, you first did a restore of a Polisy Zooz backup and thereafter you put the Zooz on the eisy ? All your devices, programs and variables are working on eisy ? Any importance on moving the Zooz to eisy before or after the restore ?

Hi @brians I must admit that I don't fully understand your instructions. In my eisy with ZMatter board and 5.5.2 I added a motion sensor and a lamp switch to a scene, but I don't see the Basic Association node. Not having Insteon I am not fully familiar with how scenes work. A lot of what you mention in your instructions, I do not recognize/find in my Administrative Console. Can you give me some hints ?

@bpwwer I believe that I found the cause. It appears that I needed to re-approve the eisy in my Portal account. I realized this when I saw that eisy appeared greyed out in the Portal account. I deleted and re-added eisy in Portal and (re-) approved in the Portal tab in the AC. I am sure that I had not changed any settings so not sure what happened.

Thanks. It is really weird. I just went to another of my computers and initially I was able to get in but I noticed that the one Node Server that I have on my (for the time being) test eisy remained shown as disconnected. After I clicked on restart PG3 in System, now also on this computer I can not even get in the eisy PG3 on its own URL. As mentioned before, I can get in the eisy PG3 when I add it to the Polisy URL which is 3.1.16 version. However there that Node Server shows as unmanaged. As you suggest I will PM to @bpwwer.

Thanks but no success

Thiis is weird...... Earlier today I deleted my eisy's ISY from the Polisy's PG3 (as an additional ISY) and opened a separate PG3 URL for the eisy. That was successful. Just now that eisy PG3 shows no ISY and when I try to add the eisy's ISY, it does not let me. The Node Server that I had added earlier today to the eisy PG3 DOES show up successfully in the eisy's Administrative Console. Furthermore when I succesfully added the eisy's ISY (temporarily) to the Polisy's PG3. I am not aware having changed any settings on either the PG3 or the eisy itself. I power cycled the eisy, rebooted, restarted.... but none of this made a difference. pg3_1-4-2023_114621-PM.zip

5.5.2

Matter/Thread will be a future feature of the new ZMatter board. Not activated yet.

try power cycle the Polisy. That sometimes resolves issues.

https://www.universal-devices.com/my-tickets/

Thanks. The solution was actually to power cycle the eisy. I also now have eisy on a separate PG3 web page and it does indeed show 3.1.17

while before I was able to get to the login page, now I don't get anything with eisy url:3000. I am going to wait till I move my stuff to eisy.

I clicked Upgrade packages in Configuration of the eisy AC, then restarted PG3, and refreshed my browser. I actually did that 3 times, but PG3 remains on 3.1.16 Just to make sure..... I have one URL YYY.YYY.YY.YY:3000 for PG3. That is the url of my Polisy but it gives me the choice of ISY's, Polisy or eisy. I tried using the eisy with its own url XXX.XXX.XX.XX:3000. That gives me login page, but when I enter admin/admin I get an authentication error.

For all, Let's wait and all be patient (starting with me). We can be sure that Michel and Chris are well aware of the issues and they must be working almost day & night to give us the best possible migration. As far as I am concerned, I have a well working setup on Polisy and as much as I have the itch to move everything to eisy and explore new features, it does not really matter whether that happens tomorrow or in a month. In July I ordered another tech product that I was supposed to get in October and now the eta is for the end of January. Some of us like the enjoyment of new gadgets, but I rather have a delayed well working product than something flawed because it was rushed. From experience we know that Michel and Chris are perfectionists, so as of now patience & respect is my attitude.

You mean my questions ?

Good idea. I have those, so will try later this week and let you know.

Yes I am itching but at the same time I don't want to put more pressure on Michel and Chris. They are great people. Somehow it is their fault for giving me that itch. One thing that I am eager to explore is the use of Scenes in Zwave. While most likely not as thorough as with Insteon, apparently a lot better with the ZMatter board than before.

As always @lilyoyo1you are the best and thanks for helping me understand this better. Now it makes a lot more sense. I know that a lot has been posted, but some were confusing. Thanks again & Happy New Year. Having to wait for the Zooz-to-eisy migration.

I have been looking at the Wiki instructions on the migration to eisy and I have several questions, which I highlighted in red. I will also send this to UD as a ticket. THIS IS NOT URGENT AS I CAN PATIENTLY WAIT FOR UD TO DEAL WITH ANY URGENCY THAT THEY MAY HAVE, BUT MAYBE SOME QUESTIONS CAN BE ANSWERED BY OTHERS, OR OTHERS MAY HAVE THEIR OWN QUESTIONS. Migrating from 994/Polisy to eisy Note Z-Wave nodes are not automatically migrated: Note Z-Wave migration can only be done from 994/500 Series board This means that (currently) migration can not be done from Zooz Dongle ? Make sure the ISY994 is already upgraded to 5.3.4, I guess that 5.5.2 is ok The eisy OS should be at level 13.1 or greater. Just in case - Note the IP address of the ISY994 and the eisy. Where can I check that eisy OS is at 13.1 or greater ? Backup your 994's Z-Wave dongle (Admin Console | Z-Wave | Utilities | Backup | Full) There is no Z-Wave / Utilities / Backup in the AC of my Polisy but I see that option in the eisy AC. see picture Zwave Polisy Backup your 994 (Admin Console | File| Backup ISY). Note where you placed the backup of the ISY994 it will be needed in step 7. Plugin the PLM to your eisy Restore the backup of the ISY994 on the eisy (Admin Console | Help | Restore ISY) from the location saved in step 2 Log back in to IoX and make sure INSTEON Support is enabled (default username/pwd = admin/admin) If this is a new PLM, Restore the PLM If you have Z-Wave Make sure Z-Wave Support is enabled Reconfigure any software utilizing the ISY994 to point to the IoP (From Step 4), restart the other software, if necessary. What software do you refer to (examples) ? If you have ISY Portal on your 994, follow these instructions to migrate your account, license, and Alexa/Google Home settings This will also migrate all node server licenses from your Polisy to eisy If you have Network Resources, please make sure you open and save each and every one individually Make a backup of your newly configured IoX. Migrating Node Servers to PG3 Backup PG3 on Polisy Restore from PG3 backup on eisy Currently the backup/restore process assumes the IoX isn't changing so it restores everything pointing to the original IoX (i.e. back to the Polisy or 994). As such: In PG3 Dashboard, click on ISY | Edit Current and make sure the host is localhost (or 127.0.0.1), port is 8080, and HTTPS is not checked I don’t see host, but I see Name , IP, Port, Username and Password. The IP is set as the IP of my eisy. Must this be changed to localhost ? In IoX Admin Console, for each Node Server Node Servers | Configure | Slot | <Name> - make sure host is localhost or 127.0.0.1, port is 8443, SSL is checked Same question as above, it is ok to have the IP set as the IP of my eisy or should it be localhost ? See picture eisy Node Server slot This image is the slot of a Node Server that I added to the eisy directly, without migration Untitled 1.pdf

Where do you have a system busy window ? I have not done the migration as I want to have more clarity on the process. I did "activate" my eisy with the ZMatter USB, added 1 Zwave device and also added 1 Node Server. When I activated my eisy, it was quite straight forward. Upgrading my Polisy to 5.5.2 took a long while and the system was busy for long minutes.

@DennisCis correct but be aware that the device may already have been "excluded" and as such it may not react to the exclusion. I have made a "portable" switch box that I use to exclude/include switches near the ISY/Polisy/eisi before mounting them in the desired location.

Unless you have many of these battery devices, exclude / include may be the way.