Jump to content

Migration from ISY994i to EISY


jlloyd_UD
Go to solution Solved by Geddy,

Recommended Posts

Posted

I just initiated a migration from my old (but still functioning) ISY994i.  I did the backup of my configuration before disconnecting the ISY 994i. I initiated the migration using the instructions and using the mobile UD (UD mobile). All seemed to perform properly. I was able to open the new console for the IOX, but my Insteon devices and programs are not listed.  I tried to restore the PLM (which is active) and restore the devices, but nothing happens.  The Portal for Amazon Alexa appears to have migrated successfully; however, it will not work without devices. I performed a system reboot. The network tree on the main tab shows two branches: 1 IOX and 2. Auto ADR.  My migration seems to be short of 100%. How do I proceed to recover my devices and programs?  Until recovery, I have to use my physical switching devices! 🙃 Thank you.

Posted

I have taken all steps as you have prescribed.  The IOX initialized as it did the first time I installed it, but the devices and programs are still absent.  The network again only lists IOX and Auto ADR

Posted

 is the insteon box checked?  Under the System box "Insteon support" box is checked.

What is the firmware version of your ISY994?  version 4.9.0

Is your eisy connected via wifi or ethernet cable?  ethernet cable

  • Solution
Posted
1 hour ago, jlloyd_UD said:

I was able to open the new console for the IOX, but my Insteon devices and programs are not listed. 

Did you restore the backup file you made? That's what pulls in the devices and programs. 

Quote

If you are not migrating your Z-Wave network
Use (Admin Console | File | Restore IoX) to restore either your Eisy / Polisy backup or your ISY-994 backup

(Source:  https://wiki.universal-devices.com/Eisy:User_Guide#Migrating - Step 5)

What you're describing seems that you missed the step to restore the backup and went to a process of restoring the PLM, but that's not going to bring the devices in. 

Once you restore the backup you should review your programs. If you have any network resources you'll need to open each one and save them. (Also from the wiki - "during migration": "Network Resources
All Network Resources will be migrated seamlessly, however, you will need to open and save each one individually."

 

Posted

I made some assumptions that the Mobile UD would prompt me to do this.  I also thought I had selected to restore the IOX, but maybe I did not, since I really was unsure what it would do.  As you advised, I have now performed step 5; I did not have a Z-wave.  The devices and programs have been restored after selecting the backup file I made before starting the migration.  Thank you.  I have tried my Amazon Echo device, and it is not responding.  I opened the portal and looked at connectivity for the Amazon Echo, and the "spokens" have not been mapped. My Amazon device indicates that it has lost connectivity to the "hub." I might have to access my Amazon app on my phone to proceed with connecting the hub or should I reboot the "hub."  I am investigating further, but I think the main problem is now resolved.  I appreciate the assistance.

  • Like 1
Posted
2 hours ago, jlloyd_UD said:

The Portal for Amazon Alexa appears to have migrated successfully

Since you migrated the portal before there were any devices it's more than likely everything previously sent to Alexa is gone. Check on the Alexa app to see if devices are still showing there. If they are, but they aren't on the UD Portal then you should probably delete them in the Alexa app and re-map them in the Alexa portal. As you do it the Alexa will discover them and add them back to the app.

There's no way to go from the Alexa app to the UD Portal. And it's possible that if you map new devices the Alexa app will find them and treat them as duplicates. So that's why I suggest you delete them on the app first before mapping. 

To test maybe map one and see if you have any issues with Alexa saying there are multiple devices. If not then keep going, but it's tricky. 

Glad the other restore helped out. I'm not sure about using UD Mobile for migration since that's a new wrinkle that's been possible since the first migration steps were written in the wiki. UD Mobile is not doing anything with the IoX backups made in Admin Console so there's no way for it to restore it to Admin Console in the migration process. I'm "old school" and don't use mobile apps for "automation" so just handle everything in Admin Console and knew the instructions were written for that in the wiki.

Good luck sorting Alexa out!

Posted

I believe the Portal was migrated as part of the mobile UD app automated migration process.  I looked at the Alexa mapping in the portal, and no/zero devices are shown.  My Alexa simply says it is not connected to the "hub" which I assume is the new EISY device.  I am still fumbling around to see if there is a simpler solution other than mapping everything again in the portal.  Since there are no devices showing in the portal, adding a device should not cause Alexa to report a duplicate device.  Would rebooting the EISY resolve this possibly?

 

Posted

The Potal tab indicates the portal is online and registered and displays my name as registered. Clicking on "more information" identifies my account as a "corporate" account type.  I chose not to click on the "revoke" button as I fear it will make matters worse

Posted
42 minutes ago, jlloyd_UD said:

I believe the Portal was migrated as part of the mobile UD app automated migration process.

Again, since the portal migration might have happened when you didn't have any devices in the eisy it more than likely wiped out anything that was previously there. When you log into my.isy.io go to "Connectivity" -> Amazon Echo. If the list is blank then you can try hitting the "refresh" symbol now that you have devices in your system, but I don't think that will do anything. 

At this point you might need to open a ticket to see if UD has any "tricks" or tips to get the mappings back, but I think it's not possible. 

45 minutes ago, jlloyd_UD said:

Since there are no devices showing in the portal, adding a device should not cause Alexa to report a duplicate device.

Know that Echo and UD Portal are different systems. Just because you don't have items showing in the portal (I'm assuming you mean my.isy.io) don't assume they don't exist on Alexa/Echo. Confirm in the Alexa app that you don't have any devices through the UD Skill. In the Alexa app (on iOS) click the light bulb in the bottom of the app and it should take you to all the devices it knows. Look for anything you think should be a device from the ISY. Click on the gear icon on the top right. That should take you to "Settings". In there is an "About" and a "Connected Via". For UD Portal it will just show "UDI". If you find any devices connected that way, but in the UD Portal (again, my.isy.io) you should delete them from the Alexa app. 

 

49 minutes ago, jlloyd_UD said:

Would rebooting the EISY resolve this possibly?

No, rebooting the eisy does nothing to the portal mapping. If restoring the devices and trying to refresh through the portal page mentioned earlier (in this reply) doesn't re-map the devices then you'll either have to manually redo them or open a ticket to see if there's a magic way UD can help restore them. My bet would be you'll just need to manually enter them again.

46 minutes ago, jlloyd_UD said:

I chose not to click on the "revoke" button as I fear it will make matters worse

Yeah, that wouldn't be advisable. 

 

48 minutes ago, jlloyd_UD said:

Clicking on "more information" identifies my account as a "corporate" account type.

That's "standard". Not many ever click "more info" (I assume). Nothing to worry about there.

 

Posted

Thanks again for your advice.  I am beginning to believe the portal was wiped clean, but I am trying other approaches.  My Echo device is not linking to the EISY, so I am trying to figure out what that means and how to resolve it.  It has happened before with the ISY994i when I have had power outages, and I thought a reboot resolved the problem. I will continue to restore the spokens but I will likely have to reinstate them.  Most are easy.  The fanlincs are a little more troublesome.  Thanks again.

Posted

Just for the record.  These are what I found after trying each step.  I have an Android.

Again, since the portal migration might have happened when you didn't have any devices in the eisy it more than likely wiped out anything that was previously there. When you log into my.isy.io go to "Connectivity" -> Amazon Echo. If the list is blank then you can try hitting the "refresh" symbol now that you have devices in your system, but I don't think that will do anything.    '

It did nothing.

At this point you might need to open a ticket to see if UD has any "tricks" or tips to get the mappings back, but I think it's not possible.   I opened a ticket for this problem

Know that Echo and UD Portal are different systems. Just because you don't have items showing in the portal (I'm assuming you mean my.isy.io) don't assume they don't exist on Alexa/Echo. Confirm in the Alexa app that you don't have any devices through the UD Skill. In the Alexa app (on iOS) click the light bulb in the bottom of the app and it should take you to all the devices it knows. Look for anything you think should be a device from the ISY.  It has all my devices from the ISY on my Android Alex app.

 

Click on the gear icon on the top right. That should take you to "Settings". In there is an "About" and a "Connected Via". For UD Portal it will just show "UDI". If you find any devices connected that way, but in the UD Portal (again, my.isy.io) you should delete them from the Alexa app.   I could not find a "connected via" anywhere.  I tried to connect a "hub" in the Alexa app and UD ISY is not a listed hub.  I tried other and it could not find it on WiFi.  I enabled WiFi on the eisy but it reported a problem (could not verify a WiFi connection) even as eisy  said it was connected to a network after updating the network credentials I reconnected the ethernet cord.

 

No, rebooting the eisy does nothing to the portal mapping. If restoring the devices and trying to refresh through the portal page mentioned earlier (in this reply) doesn't re-map the devices then you'll either have to manually redo them or open a ticket to see if there's a magic way UD can help restore them. My bet would be you'll just need to manually enter them again. 

I have initiated  ticket to look for a magic bullet. I have set up some devices but most will not work becasue the UD is not connected, I suspect.  There has to be a way to connect the UD.  I have it on the local network.  Not sure it is accessible via WiFi.

Posted
13 hours ago, jlloyd_UD said:

I have initiated  ticket to look for a magic bullet. I have set up some devices but most will not work becasue the UD is not connected, I suspect.  There has to be a way to connect the UD.  I have it on the local network.  Not sure it is accessible via WiFi.

Do you have the UD Skill enabled on Alexa? Make sure you're using the v3 skill (released many years ago). Some people setup the Echo connection/skill in the v2 time period and recently received notices (from Amazon) that v2 is no longer supported (or will end soon). You'll need to enable and link the v3 UD skill in the Alexa app. It's possible it became unlinked and just needs to be relinked.

This might help: https://wiki.universal-devices.com/ISY_Portal_Amazon_Echo_Integration_V3

Hopefully support can give other tips. I'd be interested to learn if it's possible to restore the spoken/setup you had previously.

 

Posted

Geddy,

I submitted the ticket and was also steered to ISY Portal Migrate configurations to a new ISY - Universal Devices, Inc. Wiki.  With a few clarifications, the migration was done successfully, and my spokens from the previous ISY are now successfully transferred to the new portal UUID.  The problem I had was assuming that the UD mobile app did everything, needing only to follow its step-by-step migration.  The final migration of the portal configuration was done using the instructions in the established link above.  I am now finished with the total migration.  I approached it with a little fear and intimidation but with all the help I received I was able to complete the migration.  Thanks.  Jim

  • Like 1
Posted
6 minutes ago, jlloyd_UD said:

The problem I had was assuming that the UD mobile app did everything, needing only to follow its step-by-step migration.

Great to hear! Yeah, I didn't link to that since you said you had already migrated the portal. Seems that you hadn't. The migration process was written when eisy was just released. I don't think much has really changed and seems to still be a viable tool. I am not sure if there's anything in the ordering or setup instructions that might direct users to the wiki for the best/easiest migration process to follow. As far as I know UD Mobile really just lets you setup the device and get it updated to the current version. Moving years of hard work in setup, programs, and voice commands is a daunting process. Thankfully the migration steps are available in the wiki and work. Just knowing about them and being directed to them could probably be better. UD has often said they're programmers...not so much documentation writers. Thankfully there's a good (active) group of forum users to lend a hand, and of course UD Support is top notch!

Have fun learning the rest of the eisy. If you've got other issues that crop up please be sure to start a new thread. 

Posted
1 hour ago, Geddy said:

Do you have the UD Skill enabled on Alexa? Make sure you're using the v3 skill (released many years ago). Some people setup the Echo connection/skill in the v2 time period and recently received notices (from Amazon) that v2 is no longer supported (or will end soon). You'll need to enable and link the v3 UD skill in the Alexa app. It's possible it became unlinked and just needs to be relinked.

I had no UD skills in Alexa. I am unsure if I have ever had one.  I searched for a UD skill that might be available, and none are listed among the dozens of home control skills listed in the Alexa search.

Posted
2 minutes ago, jlloyd_UD said:

I had no UD skills in Alexa.

You've got to. It's the only way Echo gets the information from UD.  But you said it's working now. At least all the items/devices showed up on the UD Portal site. So hopefully Echo is working and controlling devices again.

Otherwise, make sure you follow the setup in the link provided above. You're looking for:  "ISY Optimized for Smart Home V3". 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...