asbril

As my objective is to migrate to eisy, I wonder whether there is any advantage to migrate on my Polisy from Zooz to ZMatter board. If the upcoming migration tool will lt let me use a Polisy-Zooz Backup for a Restore on eisy, then I'd rather avoid changing anything on Polisy right now. I do wonder however about the right steps to migrate the node servers if I Restore a Polisy Zooz 700 Backup to eisy. I saw that I can move the node servers licences to eisy in UD Portal, but do I add my node servers to eisy before the Restore or after ?

I suggest that you open a ticket. My bet is that there is a solution.

For time being I am staying with Polisy and Zooz 700 dongle. The eisy is in "test" mode till migration tool is ready.

I have the ZMatter board on my eisy and successfully included several Zwave devices. What is not ready yet is the migration (backup/restore) from Polisy-Zooz Dongle to eisy, but starting a fresh Zwave network on eisy is not a problem. You may want to check whether the board has been properly fitted in the enclosure.

The primary purpose of the backup is a restore on the same system if & when there is a breakdown. Each UD product has differences in infrastructure and that makes each new generation better than the previous. UD is working on using the ISY / Polisy / Zwave 300 / 500 / 700 backups in the migration but that is apparently a big job, especially to make it work on eisy with the Zmatter board.

That seems to work

Or change browser, but that should not be needed. If several of us have this issue, then most likely something is wrong. I understand but why do we have this issue with the eisy PG3 and not with the Polisy PG3 ?

Unfortunately my suspicion is that the error is fundamental and may occur again, though of course I hope that it will not................. and just after I wrote these words it DID happen again here with an error message something like UD Portal token expired. On same computer I changed from Chrome to Edge and that worked. Something is wrong.

yes, a different browser seems to be the solution, but it should not be.

@bigDvette I followed each of these steps and more..... The only resolution (for me at least) seems to have been using a different computer and restart PG3. Note that this is most likely not a problem of the computer itself as the incident has happened on computers A and B, with resolution on B for A, and A for B.

Something is definitely wrong somewhere and I hope that @bpwwer can find out. On the computer that works, try to restart PG3.

I just had exactly the same issue. From one moment to the other the eisy PG3 3.1.18 did not open and I got the same error message. I tried reboot and power cycle, but this time no luck until I went to another computer and connected to PG3 without a problem. And then on the first computer I was also able to connect. This has never happened with my Polisy PG3, so I wonder whether there is a bug in 3.1.17 and 3.1.18. If @bpwwer wants I can send him another log as yesterday my log did not show him the issue.

Sorry, I missed that. It was just what came to my mind. I can feel your frustration. I have had these moments and I understand you.

I suggest that you do not publish your UUID as could allows others to access your system.

Have you considered a factory default ?

A real saga. The double evolution of eisy and the ZMatter board, plus the PG3 update, comes with a lot of challenges and I am sure that the UD team is on top of it all. The issues that we are going through, or at least some of these, will help the UD team to identify and resolve problems. At times it can frustrate us but we need to be patient (like you) and I'm sure that it will all be resolved soon.

I like your optimism 😁

Funny thing just happened..... I clicked on the upgrade packages and I was no longer able to access the PG3. I first deleted thei from my Portal and added it again, and when I wanted to Approve, I got the same bad error message as you. I power cycled my eisy and then the Approve worked. Now I am on 3.1.18

I have no other suggestion than what you, to open a ticket. I believe that the guys at UD are very busy this week with the migration etc, so you may have to be a bit patient.

Did you follow these steps ?

ZWAve Plus Ecoline. I changed the setting to test which supposedly makes it stay ON for a few seconds only. I will try again when I have some time.

correct.

When a ISY is added to your ISY Portal, a message comes up telling you to 'approve' the connection in the Administrative Console - Confirguration - Portal Tab.

I tried with a spare sensor that I had and it did indeed switch the lamp ON, but whatever reason the sensor remained on ON and I was not able to fully test. I will have to wait till the migration when I will have more sensors on eisy and ZMatter. I removed and re-added the sensor aeveral times (which puts it in factory default) but same ON all the time.

It is all working again but I have no idea why the eisy was disconnected from ISY Portal.