JTsao

Well, 5 months later and attempting to migrate again and ended up back here - all node servers unmanaged - I have tried to restore the pre-migration eISY PG3x backup (which has no node servers) and when I do, for a while there are no node servers, then the unmanaged 11 node servers come back - is there another way to wipe PG3x clean and re-start from scratch?

I am trying to migrate from a Polisy with the latest 5.6.3/3.1.36 to an eISY with 5.6.3/3.1.36 so I'm going from PG3x to PG3x - do I just do a restore? or do I need to do a Migrate from PG3 Backup? EDIT: well things have gone downhill fast and I am completely locked out of PG3x (can't log in - 503 Service Unavailable) - opened a ticket

I appreciate the reply but I have thoroughly read all of the Wiki pages - I guess not a good post on my part - well I decided to try the full migration from Polisy/Zooz/2448A7 to eISY/ZMatter/USB wired PLM in progress now...

I would recommend just doing it because you're going to have to eventually - I've done it on a Polisy and I don't recall it being too bad...

OK, big picture, I am concerned about going from the Polisy/Zooz to the eISY/ZMatter (I have both) as it didn't work so well when I attempted this 2X in the past - my idea is to attempt this in steps by updating the Zooz dongle to ZMatter first, then later updating the Polisy to the eISY - that way, I don't get overwhelmed with having to fix, re-enroll devices or transfer licenses for Z-wave, UDMobile/Portal and Node Servers all at once, but the Wiki doesn't seem to explicitly cover doing this in 2 steps, so I am wondering if this has been attempted and if it is possible (before I try) - can anyone comment on this??

Per the Wiki, in order to migrate from Polisy/Zooz to the same Polisy/ZMatter, I would perform a z-wave migration backup, then power down, unplug the zooz dongle, plug in the ZMatter dongle, power up and do a restore - does this sound right? has anyone done this?

A few months ago, I attempted to migrate my Polisy/Zooz USB stick to the eISY/ZMatter - I may try again in the near future, but was wondering if I should factory reset the ZMatter prior to attempting again, because it contains links to my Z-Wave network from a few months ago - alternatively, would it be better to do one step at a time? 1-migrate Polisy/Zooz to eISY/Zooz, then 2-migrate Zooz to ZMatter? Or perhaps 1-migrate Polisy/Zooz to Polisy/ZMatter, then migrate Polisy to eISY?

I was able to upgrade my Polisy from 3.1.29 to 3.1.32

I went for several days with no errors, but just had another reboot - will open a ticket later today...

Anyone else seeing this? I have been updating IoX and PG3x fairly regularly now that things seem more stable with the releases. Most recently, I upgraded to PG3x 3.1.29 - after this, I have seen a number of Polisy reboots that I did not initiate - nothing really changed except keeping the software updated - just had 2 reboots today alone, one around 12:15AM and another at 8:30PM The only clue that I have found is that in the IoX log file, there are entries a device "0" and control "null" around the time of the IoX reboots.

This is kind of a minor issue, but for the past 2 upgrades, my eisy A/C tells me to reboot via a pop up window - possibly after I exited the IoX A/C and got back in, but prior to any reboot attempts - my Polisy A/C doesn't tell me to reboot when the update is complete (I hear 5 beeps) but after waiting a bit, I reboot anyways, then when I start the IoX A/C, then it tells me that I need to reboot - so then I have to reboot again - so there is some kind of minor difference between IoX A/C behavior on the eisy vs Polisy (unless the Polisy requires a much longer waiting period for the pop-up message) - in any event both recent updates have gone without any observable errors

To be clear, I did see a reboot message in orange at the top of the PG3x web page on both devices (both were PG3x 3.1.27 prior to the update), if that is what is meant by the popup - what I meant was the message box in IoX admin console indicating that a reboot is necessary - I only saw that on the eISY for some reason - maybe I didn't wait long enough on the Polisy, but I did hear 5 beeps

Upgraded both a Polisy and eISY to IoX 3.6.2 with no issues observed so far - only saw a popup on the eISY, not the Polisy (but heard 5 beeps)

Updated to 3.1.27 from 3.1.26 on my Polisy - no major issues - one minor issue - the IoX admin panel did not list any of my programs, although they were clearly running - I did a shut down, unplugged and powered back up and everything looks good...

In my case, it was changing from PG3/v3.1.20 to PG3X/v3.1.25 that caused the issue - in this case some files or folders had incorrect ownership - I ended up opening a ticket and UDI remoted in to my PC to correct - I think there is a fix for this now in v3.1.26 but in your case, you are only at v3.1.20 - I don’t recall that update being a problem - you may have to open a ticket

Updated both the eISY and Polisy to 3.1.26 and both are good - thanks!

That's exactly why I haven't upgraded the Polisy - also, until I successfully migrate to the eISY/Zmatter, that platform is my test bed for testing these new upgrades first - as the eISY is not showing an available update, that was suspicious - I am still curious as to why one platform indicates an update but the other does not show it as available I have a theory regarding who that user might be...

When logging into IoX on my Polisy, I got the "updates available" message and the PG3x web page indicates that there's an upgrade available for 3.1.26 - my eISY does NOT indicate that any updates are available and the PG3x web page does NOT indicate the 3.1.26 update either - both are on versions IoX 5.6.0 and PG3x 3.1.25 - has anyone tried to update to 3.1.26 yet? Why are the two devices not consistent with indicating the available update?

@bpwwer - I think there is a remaining problem from my migration to PG3x 3.1.25 on the Polisy - I haven't been doing much with the Polisy since you fixed the ownership/permissions issue and it appeared that everything was working, but the water level in my pool was going down and I was getting notifications that it was not being auto-refilled - long story short, the Weatherbit node server does not appear to be working - I tried re-installing, re-starting PG3x and rebooting the Polisy and nothing works - it reports this in the log - any ideas on how to fix? "2023-05-06 13:14:04,135 Thread-19 udi_interface ERROR query:query_conditions: No response object in query response." EDIT: I just noticed the short and long poll times were modified to smaller than allowed values, I have increased back to match the free plan (1800/43200), but still not working yet... EDIT2: It appears to be working now (I think) - it has non-zero data - not sure what fixed it...

You can do #4 if you get a FLIRC and use the eISYIR nodeserver but then you need an IR path to the eISY - I used to use a Sewell Wireless IR repeater with the ISY994

In my experience, you can do #1 and #3 but not #2 with the Harmony Node server by itself. If you want to use the dedicated home control buttons on your Harmony remote, then you need the Hue emulator node server because the Harmony software limits those buttons to control only a small set of devices (including a Hue Hub). I use the Virtual node server to create fake switches that turn on and off in scenes accessible by the Hue emulator. This triggers programs to control fans and lighting. Maybe not the cleanest method (anyone else have a method?), but a method to get programs to trigger. If you only want scene control, then you could just use the Hue Emulator by itself.

Problem fixed, thanks to Bob (above) for remoting into my PC and fixing - it looked like some file/folder permissions/ownership needed to be changed to make everything work - I admit that I did not watch the whole time that he worked on my Polisy - I have a pretty good idea of some commands that can be typed in to fix the problem, but it's probably better for him or someone from UDI to explain

Now we are at the same point - I exchanged a couple of messages with UDI so far today on my ticket - I am thinking that we have the same problem, so I'll advise if I get it fixed

It sounds like you are in the same boat as me - I clicked that link a few weeks back and got the same error - then upon updating to 5.6.0, PG3 went from 3.1.20 to 3.1.25 (PG3x) - right now, I am one step ahead of you because I opened a ticket, but my all of my node servers have been offline (except for occupancy via ISY portal) for 3-4 days - there is still currently no solution but UDI is looking at it I can share with you the steps to get the PG3x web page back, but that's all it does - all of my node servers have been disconnected, won't re-connect and the log files are suspiciously empty since the time that I ran the 5.6.0 update - the following is what I was told to get PG3x running again due to database file permission/ownership issues: From a ssh session type [admin@polisy ~]$ tail -f /var/log/messages If you see something like: Fix globalsettings failed: SqliteError: attempt to write a readonly database and Startup error. Shutting down: SqliteError: attempt to write a readonly database In the file then you can try the next step From a ssh session do the following two commands: sudo chown polyglot /var/polyglot/pg3/pg3.db sudo chmod 644 /var/polyglot/pg3/pg3.db For me, this got PG3x back up and running, and I could log into the web page, but did not fix the overall problem because none of my local node servers will connect Please use this information at your own risk and I hope it's OK for me to share all of this...

Thanks, but I was not able to start/stop or restart node servers either - I opened a ticket and was told to do a restore from a PG3 backup - now PG3/PG3x is apparently not even starting up but at least I am in communication with the UDI team to hopefully get things working again - I am speculating that the migrate to PG3x restore option may have been a good option from where I was at (I forget what it is specifically called) - unfortunately, I guess no one has tried to get PG3x 3.1.25 running on a Polisy yet...