TriLife

I was able to log on, and transfer my PG2 data to PG3, or almost. Please look at the screenshot below. The three node servers that I transferred have "no data available", are "unmanaged". No way to manage them or otherwise modify them. I I tried to reinstall them, but they are would be going to a different slot. and I haven't found a way to delete them either, so I can reinstall them... Thanks for your help.

That was the ticket! Thanks @Techman

Greetings; Just updated my OI to 13 on my Polisy Pro. Did a first upgrade packages, which seemt to have worked fine. Now, when I launch IoX (5.4.5), I get an error stating that IoP is on 5.5.0, but admin console is lower version... Where can I find the new admin console, please? Thanks!

Ditto!

Thanks Geddy, Most helpful insights again. Yes, I'm using Upgrade packages now, trying to get PG3 to upgrade to 3.1.16... Since the house is mostly up and running now, I think it behooves me to wait a few days until the ZMatter dongle Firmware issue is resolved and then I'll migrate Z-Wave and retire the ISY994... Thanks again for your help!

mostly SOLVED! These are the steps I took to fix MOST of the problem: 1- From within PG3, I picked the second option of restoring PG2 into PG3 2- From withing IoP, I restored ISY994i 3- Rebooted PG3 and Admin Console and everything came on line 4- Added ELK, Sonos, WeatherLink and WOL, which all came on line once I exited and reentered Admin Console. I now have the ISY994 running on PG2, with only the programs that include Z-Wave sensors enabled. IoP is running on Polisy. QUESTION: Can I add the ISY994i to PG3 instead, or better to just wait for Zmatter dongle? Remaining issues: 1- I cannot seem to be able to upgrade PG3 to 6.1.16. It's stuck at 6.0.63 2- Google Home turns individual Tasmota MQTT switches on or off without a hitch. If, however I ask it to turn on a room with several switches (like Kitchen or Office), it executes (seemingly slower) and then tells me that it cannot reach Universal Devices... 3- It still refuses to open the Wine Cellar for my wife Heather!!! ( I think that once the the ZMatter dongle firmware is available and installed, I'll disconnect UD from Google Home, reset my Google Home account, reconnect and set it up again and readd my wife to it. This is a simple but tedious job and I don't want to repeat it needlessly. Thanks again for everyone's help. BTW, UD did reach out to me via suppor@...

Thanks @Geddy, that explains the odd behaviour. Correct. My bad I've been running Polisy nicely for about 2 years, with PG2. It was sitting in the closet from purchase until the house was ready until then. I ran quite well except for one major crash, which required @Michel Kohanim remote intervention (something about mongo db crashing) and vanishing passwords. I have the Z-wave 500 board and am running on 5.3.0 (one of you told me that I would not need to upgrade to 5.3.4 as suggested in the migration document you refer to above , since it only fixes a unit conversion bug). There was chatter about not being able to use the upgrade button with the pre-order units in some of the chats. I must have confused them. Finally, I just checked, in the Admin Console of the ISY, that Upgrade button obviously isn't available. Hence SSH... This is the pdf, I was following: I understand. I meant to say that once I had PG3 up and running, ISY994 wasn't responding anymore... before going to bed last night and stopping the trouble shooting, I had to disable PG3 via SSH and powrup 994 in order to control my lights again (UD Mobile works, but Google Voice controls are sketchy: individual lights work, programs don't). Started to follow this manual, with the hopes that it will straighten out the problem. However, already in step 3: 3. Backup your 994's Z-Wave dongle (Admin Console | Z-Wave | Utilities | Backup | Full) there is a discrepancy. I only get the choice of (Admin Console| Z-Wave|Backup). Additionally, after the backup it says "Backup successfully completed", but it doesn't tell me where. It is not in Downloads. The File|Backup ISY command does ask me where I want to back it up... Strange. I'm currently at 3.0.63, Tried to follow the steps in the link, it stays at 3.0.63... Good idea. I will resend and add my current findings. Thanks again for all the insight, Geddy. Seems like I'm stuck for now, until UD gets back to me.

Is stopped PG3 via SSH, turned the power to the ISY994i back on and everything is working again for now. When UD comes back on line and I can get a ticket issued and responded, we'll continue this saga. Very disappointing, I must say. I'm sure there's a good explanation to this. Thanks for all of your efforts to get this resolved. I'm going to bed!

This was the first time I went into SSH, following the Wiki pdf. I have one of the original pre-ordered Polisys. Unfortunately, I have no way of getting a hold of UD at this point. Their portal is down and when I write to support@... although they answer, I don't get their mail. I would see it in my ticket queue, but, I can't log on. Hopefully @Michel Kohanim will see this post and either fix the portal or send me a response from outside the ticket management system. Cheers;

In the meantime, onto the ELK NS. It shows connected in PG3 and I can see the different areas and sensors within NODES. However the ELK NS doesn't show up in the Admin Console 2022-12-10 20:38:47,137 Thread-63 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:39:18,591 Thread-64 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:39:48,838 Thread-65 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:40:17,232 Thread-66 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:40:19,526 Thread-67 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:40:50,707 Thread-68 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:41:22,802 Thread-69 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:41:53,271 Thread-70 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:42:06,650 Thread-71 udi_interface ERROR Controller:discover: ELK Controller: discover currently does nothing 2022-12-10 20:42:23,961 Thread-72 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:42:55,019 Thread-73 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:43:26,503 Thread-74 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:43:57,636 Thread-75 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:44:20,246 Thread-76 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:44:31,042 Thread-77 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:45:00,125 Thread-78 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2022-12-10 20:45:30,726 Thread-79 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete Here's the log file for ELK

is @Michel Kohanim aware of the log-on page being down?

Thanks for that important piece of information. In the meantime, I was able to get UD Mobile to connect to PG3. Progress. However, neither Mobile nor the Admin Console are giving me the status of my MQTT/Tasmota switches anymore... At least I can turn off the lights now (no mechanical switches in this house)

Thanks, some progress: Google still says that it cannot reach Universal Devices, but after 30 secs or so lights sequentially respond... The Home App still says it cant talk to UD though.

Hmmm... do I understand you correctly that in order for Google Home to communicate with my Polisy, the UD infrastructure needs to be up and running? Was I mistakenly thinking that Google would communicate directly with my Polisy?

I did a complete SSH upgrade following the Wiki document just a few hours ago. BTW, PG2 has a Polisy Update Button, but that option doesn't exist in PG3 anymore...

In the meantime, I tried to "reconnect to Universal Devices" From within the Google Home App. I get a "Could not reach Universal Devices". Definitely up a creek. And PG2 doesn't seem to be working together with PG3. In order to undo this mess, I think I have to completely delete or at least stop PG3, restart PG2 and turn on ISY994. Not really a smooth migration, is it? Especially when UD is unreachable...

yup. real bummer

I did... No answer. But that sometimes happens. They do answer, but it doesn't get to my email. It only shows in the ticket managments system. But since I can't log onto the ticket management system, I'm kinda up a creek...

Yup, when I do that, it tells me that I already migrated 93 commands. Yet Google Assistant tells me that it cannot connect to Universal devices. And, I lied, its not 5-8 seconds to log onto Polyglot, its more like 90-150 seconds.

Greetings; So, I was following the Wiki 994i to Polisy.pdf nicely. The ISY was showing up, I started configuring the three NS I have. Then, all of a sudden things came to a screeching halt, or to a crawl. Say I click on details of the MQTT NS, it shows up after about 5-8 secs of only the Polisy SW versions. I click configure. nothing for 5-8 secs. Then some fields show up. Then 5-8 later the config help shows up... I go back to the Dashboard and click the ELK NS. for about 8-10 secs it goes backt to MQTT NS. Then slowly things appear. When I go to the admin console, turning things on or off also takes 5-8 seconds. Oh, then, when I reboot Polyglot 3, it flashes to the my.isy.io screen, asking me to sign in. Same happens after the reboot. I go to my-IP:3000 and after a long while I get the user/password screen. when I enter the combo, I get flashed to my.isy.io again and back to the my-IP:3000. After a lot of thinking, it says it cannot find the ISY.... I tried soft resets and power cycles. No dice. Polisy is on 5.4.4. FIGURED THIS ONE OUT: Oh, and in my.isy.io i get the attached information, "pending approval by owner"... Even if I purchased the full year's license on top of the 30 day trial as suggested in the above Wiki... And to boot, UD's ticket system seems down, doesn't let me sign in. the buttons are missing. Please HEEEELP!

Trying to open a support ticket. Seems like their server is overloaded. Not letting me sign in (log in buttons don't show up. Neither on PC nor on phone)

Duh! I was so eager to get IoP up and running, that I mistakenly bought the wrong Node Server. Paid $10 for DavisWeather (no free trial), but I really wanted WeatherLink (yes, I didn't read the warning!), with 3day trial... Is there a way to transfer the $10 from one to the other? I think Bob Paauwe @bpwwer? is the author of both. Cheers!

And I'm guessing that sometime in the foreseeable future, UD will stop supporting the ISY994. When something goes wrong after that point your planned/routine migration will turn into an emergency... I have a ton of Sonoff/Tasmota devices and about 20 Z-Wave sensors. Haven't yet migrated from the ISY994, as I'm waiting for the ZMatter dongle, which should be waiting at home by the time I get back from my holiday in Mendoza Argentina... I'll begin the migration, just as soon as the migraine from all the Malbec clears🤪

And mine

"the eisy before the end of the year." I just looked in the UD Store. Don't see the eisy available for order... Am i missing something? I did the preorder the Z-Wave dongle when I got the email for it. Cheers.