Jump to content

Migrate from ISY944i to Polisy Pro


ThisIsTheWay

Recommended Posts

Posted

For some strange reason I cannot find the guide for how to move (and then deprecate) my ISY944i over to my Polisy Pro.

Will it matter that my ISY944i is on version 5.3.4? IoX in Finder shows as version 5.5.3

Capture.JPG

Posted
20 hours ago, Techman said:

Your firmware versions are correct for migration.

Do you have Z-wave or are you just migrating Insteon? 

I removed all Z-Wave and have those paired with my Home Assistant Box.

Speaking of Home Assistant.  Anyone have tips/advice for the transition form ISY to IOP for HA?

Posted (edited)

Uploaded the ISY backup to my Polisy.  First log in no devices were present but the programs were there.

Trying a second time and now IoX finder refuses to find the device.  When I add it, in IoX finder, it says "Not found"

The polyglot dashboard at "https://192.168.1.7:3000/dashboard" is visible.

Should I just wait longer, its been 10 min?

EDIT: could not wait.  pulled plug. seems ok now....should I be worried?

Edited by uffy
Posted

I thought I would share a few highlights from my experience migration from ISY to Polisy.  I have not had the smoothest experience lately with making updates to my system, and have been very hesitant to make this migration, but decided it was time to take the risk.  I attempted to follow the instructions from the wiki, but found a few instances where the instructions could not be followed to the letter due to them directing to choose options from the admin console that did not exist in mine.  Regardless, I believe I followed the intent of the instructions.  My migration was using the existing PLM, from the ISY.

Highlights from the process:

- "most" of the Insteon devices came over.  A few are missing (so far, I am missing a lamplinc and fanlinc, but am still sorting this out and may find more).  Scenes that formerly contained the missing devices are no longer working from the admin console.  Some controller devices within those scenes might still trigger the missing Insteon devices.  Some don't.  I assume that the links between Insteon devices remain, but the ISY link records no longer match.

- zwave devices all came over but required the individual "sync and interview" process to work.  Perhaps, if I had waited a day or three, this might have happed automatically, but I chose to force it on each individual device.  All wired devices came through this, but sometimes with missing nodes or missing functionality (a z-wave switch that I could formerly use as a scene controller no longer worked as such...the ISY did not recognize a status change when the switch was manually toggled).  I was unable to transfer any battery-operated z-wave device, with two exceptions: a door lock, and an alarm.  No motion sensors.  No door sensors.  I was unable to force the door and motion sensors to respond to the interview request.  I could exclude, then include them but, like the previously-mentioned switch, the ISY would not react to a status change when a door is opened or the motion señsor saw activity.  This rendered those devices of no use.

- Portal migration worked well.  Alexa spokens, as best I can tell, all transitioned.

- PG3 did not migrate properly.  In this case, however, I am willing to assume this was a self-inflicted wound.  Prior to the migration, I had PG3 working with the ISY, as well as with an unmigrated IoP.  I cannot say (don't recall) that I had all node servers in the same slots, however.  After I made the transition, the former nodes (I use Hue, Roku, Sonos, Harmony, and a few others) appeared in the admin console as before, but none worked.  After attempting a few things, I ended up clearing PG3, clearing the node servers from the admin console, and re-adding to PG3.  This also meant re-populating a few scenes and programs with the "new" nodes, but this is mostly working at this point.

- most interesting to me: I have at least one case where I have an ISY scene connected to Alexa.  This scene originally included several keypad buttons and two fanlincs.  The scene is, I assume, typical for fan control.  Button A = off.  B = Low, C = medium, D = High.  It has worked flawlessly since creation.  Sometime between the time I last used it and now (I assume as the result of the migration), the fan scene ceased working.  I can no longer control the fan from the KPL, nor can I control it from the admin console.  Not only is one of the two fanlincs missing from the scene definition, it is completely missing from the device list.  Despite all this, both fanlincs still respond to Alexa commands.  I cannot even come up with a theory about how this is possible.

- I thought I had successfully updated to 5.5.5 on IoP, prior to migration.  After migration, however, the admin console for IoP shows 5.5.4.  Did I imagine things?  I guess I will never know for sure.

 

Posted (edited)

With my replacement ZMatter board, things when significantly better. After manually running several interviews, and removing a couple of old devices that I could not find, IoX on Polisy is mostly working now.

The only thing I still have not gotten to work are my garage door openers. They are GoControl ZWave Plus controllers and they show up are barriers in the admin console, but the status never shows anything, even after querying them. Yhr open and close commend work, but the status never reflects the state.

My Schlage and Kwikset wave door locks open, close and report their state fine, so I know barriers work, just not the GoControls's for some reason.

I did remove and re-add one of them, but that made no difference.

Has anyone else gotten GoControl garage door opened controllers fully working with Zmatter/IoX?
 

Edited by stevesreed
Posted (edited)

one other issue that has come up as I've been fixing up programs for a few devices I removed and re-added.

Loading the program page int he admin console is super slow, like a couple of minutes slow. But more importantly, I can only change and save a couple of programs before it fails to save and I have to reboot the ISY, if I want to edit/save anymore programs.

I get these after a few saves:

Screenshot 2023-01-29 at 3.51.48 PM.png

Edited by stevesreed
Posted
52 minutes ago, stevesreed said:

one other issue that has come up as I've been fixing up programs for a few devices I removed and re-added.

Loading the program page int he admin console is super slow, like a couple of minutes slow. But more importantly, I can only change and save a couple of programs before it fails to save and I have to reboot the ISY, if I want to edit/save anymore programs.

I get these after a few saves:

Screenshot 2023-01-29 at 3.51.48 PM.png

Perhaps you should open a ticket.

Posted
1 hour ago, Techman said:

@stevesreed

take a  look at this thread

thanks. I looked, but my PLM status just says connected. The issue seems to be only when editing and saving programs. I managed to get all the changes in after a dozen or so reboots, so I'm at least working for now. I still want to fingureout what wrong though, incase its a sign of large upcoming failure.

I did notice on the System Status page, it shows a lot of "Bad" memory. I'll open a ticket.

Screenshot 2023-01-29 at 1.09.00 PM.png

Guest
This topic is now closed to further replies.

×
×
  • Create New...