Geddy

In prior posts this was classified as an "information only" type error. Indicating that it is not a real error and could be ignored. I am not sure if this has changed in Polisy/eisy era, but feel that if things are working well then it continues to be information only and could be ignored.
You reference a -70001 as Vector error, but you seem to have just left out the first "1" from the actual error code. 
I also get a lot of the -170001 "errors" and don't worry about it.
And that's just a small section of the error log from this morning.

@andrew77 not sure if it would help at this point, but in the programs tab you can right click on a program and next to last option is "Find/Replace". It opens this window:

You might be able to figure out what devices was missing. It also gives the option to find "Raw Text". 
I haven't used this much in the past, but know it's an option. Might allow you to find all the places you have this "Response type 10" showing up and you can follow the bread crumbs back to what device was being referenced. 
More than likely it was a node server that either is no longer installed or not connecting correctly. If you're running node servers. 
 
Here's an old post that referenced this when upgrading to 5.x: (Found with Google Site Search)
 
 

Not sure how large your install is, but mine isn't huge and the restore took less than 5 minutes. If it was 24 hours then something went wrong.
You might be best served with a support ticket just to be certain something isn't messed up with the device and that you're up to date with firmware. 
https://www.universal-devices.com/my-tickets

@TSinclair looks like this finally got implemented into IoX with 5.5.6 release..."wider node selection boxes"
 
 
 
 

Try the default admin/admin user/password. I think it resets during the process.
First thing to check once you do get in is to confirm UI and Firmware match (help -> about). 
 

@johnnyt Since you're not using IoX then updating is fine. At this point updating the Polisy or eisy (I know you don't have the eisy, just referencing it for clarification) is done by using the "Upgrade Packages" button in IoX Admin Console for the device you're using (Note...IoX is ONLY for Polisy and eisy). 
The main thing you need to consider is what version of PG3 are you using? If it's current then you're good in that department. If it's not then that would upgrade as well.
I think we've all learned what not keeping a system updated means at this point. It's a little more time sensitive sometimes for the Polisy (and now eisy) to get those updates when you can. 
While it won't really impact your situation it would mean that your system would be operating with the current releases of ioX and PG3. If something changed dramatically in a future update and the upgrade path from an outdated system to a current release system broke then might require a lot of additional work and support.
 
no benefits to your current setup since you're using ISY994 as controller.
No, it's a free firmware update to IoX.
I believe those were more related to PG3x (eisy) and 5.5.5 in how PG3x handles node servers differently on the eisy than the current version on Polisy. But that's only from memory of reading too many posts. Make sure you review those posts to see if you can tell if they were eisy related or Polisy if you're overly concerned. 
 

@Davey A couple of things to check first:
What's the firmware for IoX? Have you updated it before you tried to migrate into eisy? Current release is 5.5.5. There were some issues with earlier IoX versions that caused migration issues, but they've been fairly good as of late. If you just received the eisy and didn't update it prior to migration you might be having such issues. 
You said you moved the eisy and plugged in the network cable...had you initially set it up on wifi and then changed it to hard wire when you moved it to where the old ISY994 was? That shouldn't matter, but again, if it was older IoX it could be an issue. 
Make sure that your firmware and UI match (help -> about) - They should as long as you're using IoX Launcher (start.jnlp), but always need to make sure.
Do you have a lot of battery devices that you tried to migrate? (I don't so can't help you there, but think that's been slowing some down as well) I think there's a way to turn off writing to battery devices and it might stop the update process from happening next time. Though you do need to make sure all battery devices are migrated properly. 
 

@wacvmd No. 

You can't use HTTPS in the Polisy to connect to the ISY. It needs to be HTTP.
Wiki instructions:   https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#ISYs
Step 3 = Make sure you use HTTP and not HTTPS
 
If you mean via IoX Launcher then see this section:
https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Can't_Find_Polisy
 

Did you follow step 12 of the migration process in the wiki?
https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migrating_from_994/Polisy_to_eisy
 

Follow these instructions, but remove the board.
https://wiki.universal-devices.com/index.php?title=Z-Wave:_Ordering/Assembly_Instructions#Assembly_Instructions
 
But, I think, if you aren’t using Z-Wave then 5.3.4 wouldn’t hurt with the board in. It just wouldn’t function for Z-Wave processes….but I cannot confirm 100%.  Just be careful if you do try to remove the board not to short anything out!
 

@endobiker do you have firewall between the subnet blocking traffic? It would probably be easier to use the portal process to access as though you were remote. You probably don’t have traffic configured to cross between the two. 
 
Directions: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Admin_Console
 

@ronbo take a look at this solution for similar issue. Option 2 worked for me and several others. If you’re familiar with SSH access and commands give it a try. 
 
 

@cswelin please try to update Polisy IoX firmware to 5.5.3  (just released) and attempt to add again.
Please report back if still having issues or if resolved with Firmware update. 
 

@SSamuels take a look at this solution. Step 2 helped me. If you are familiar with SSH access and commands good luck.
Otherwise, proper update methods is in Admin Console -> configuration (tab) -> update packages (button) 
 
 

Check here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Can't_Find_eisy
 
 

@SLiss and @EWhite have either of you tried this (from the Wiki)?
https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Can't_Find_eisy
You might need to add manually. 
 
If you’re pinging the device (or connecting via SSH) then you know the IP Address…..follow the process to add using the known IP.
 

That's okay. Moved it to the proper place.
 
First and foremost - make sure your User Interface (UI) and Firmware match when you do log into Admin Console. That can bungle up some GUI issues.  UI/FW must match exactly (including date/time code). 
 
Did you get a power supply that was proper voltage output? from the wiki:
"You can try any power supply that outputs anywhere between 5 volt and 30 volts,center positive, 2mm barrel connector"
(But I'm sure you checked that from your previous thread)
 
What you're experiencing now seems to indicate some issues with antivirus software. Are you running any 3rd party anti-virus or firewall programs? You need to turn those off, clear java cache (be sure to select all three boxes in this process), then run fresh download/install of IoX Launcher (previously ISY Launcher, aka start.jnlp) that you download directly from UD site or UD Wiki. 
https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop
Java Cache options:

 

The move from 4.x to 5.x was a big step so any move to 5.x to be able to use UD Mobile will require some time to get things sorted out.
There have been a lot of posts about this, but simply saying...read the 5.3.4 release thread. Skim it and look for pitfalls. 
The simple answer to your question:  Go directly to 5.3.4. Do NOT think about anything else. You don't have Z-wave so you don't need to worry about the warnings on 5.0.16C. Don't even consider installing some random version of 5.x and then thinking you will upgrade to 5.3.4 if it went better than expected. The best, and perhaps safest thing is to bite the bullet and install 5.3.4.
Now, here are some pitfalls to watch and hopefully minimize your "pain" (interaction) in the update process.
Backup current system - yes, it tells you to do this in the release thread, but do it again just to make sure you've done it.
  On the ROOT folder of the Programs tab right click and select "Copy to Clipboard" (it's the LAST option in the menu).  Paste the programs into a (plain) text editor (like NOTEPAD for Windows). DO NOT PASTE IT INTO WORD OR OTHER WORD PROCESSING PROGRAM - it could auto format text and you don't want that.  MAKE NOTE of any "Disabled" programs - on some occasions when you go to 5.x all programs become enabled so you will need to disable any permanently disabled programs you have.  If you have any "adjust scene" programs you will need to correct those once you update. 
  Be sure when you're done that you properly clear your Java cache (checking all three boxes in the process!)

  Download a fresh start.jnlp file from UD website or the wiki site. (I usually tell people before doing this to delete any OLD start.jnlp/admin.jnlp files from anywhere on the computer as sometimes OLD files will be used, and you need a fresh file that you just now download.   
This should get you there. Give yourself some time to accomplish this. Don't expect to have it done in 5 minutes, but it usually shouldn't take too long either. 
Hopefully you're currently running 4.9 (last 4.x version released). If you run into issues you can download 4.9 again from the previous release area and restore your 4.9 backup and be up and running quickly. 
Post back and let us know how it goes. 

I experienced a similar situation trying to update the Polisy. 
Take a look at this solution posted by @Michel Kohanim to help. Step #2 helped resolve my issue.
 

@elite-rob If Insteon switches it's possible they got locally linked and the ISY (994?) would not notice/recognize that link in the admin console. You can fix this several ways, but I think the easiest is to:
Factory reset the switch. Then re-link to ISY. 
I think there might be a way to make this work without removing it from the ISY tree and right click on the device and "restore device" and it should write back everything the ISY has for that switch. I've never personally tried it this way, but saw an old post referencing this method. 
 
Note - It's often suggested when installing switches to always perform a factory reset before linking to the ISY. This clears out any existing links or strange QA codes that might have been introduced to the device from the factory. 
When linking to the ISY there's always the option to "remove existing links". This way sometimes help stops this from happening, but is not always 100% accurate. That's why some will always suggest a factory reset just to completely clear any existing internal memory. 
Google search for the type of switch you have to get the proper process for factory reset.
 

Not having this issue.
Doubtful that it's the whole issue, but you need to update your Java. Current version from java.com is Version 8 Update 351.
Delete previous copies of start.jnlp or admin.jnlp (be sure to look for multiple copies of same file i.e. start (1).jnlp)
After you do that:
clear your java cache, (Be sure you check/select all 3 boxes in this process!) download a new start.jnlp file from the Universal Devices site or through the Wiki. Once you are able to log into admin console confirm your Firmware and UI match (Help -> About). They should match EXACTLY (even the date/time code).
 
Other items to check:
Is there a steady bright blue light on the front of the ISY (if not see here).
  Do you see the ISY as a connected device if you log into your Router?  Can you ping the ISY from your computer? 
  You say UD Mobile works "most" of the time. Is that accurate or assumption? If really is "most" of the time it sounds like a network issue.
  Log into my.isy.io and check the error log (Tools -> Select Tool -> Logs) to see if there are any significant errors seen. Check error codes in this wiki article  
Let us know how things look once you check/fix/update the above.
 
 
 

At this point I'd say don't worry about Polisy. Take a look at the next gen eisy.
But if you want to learn more about Polisy:
https://www.universal-devices.com/product/polisy-pro/
https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide
Polisy and Polisy Pro are out of stock.  So can't get them currently.
 

Quickest and easiest…. ISY Portal account…
https://wiki.universal-devices.com/index.php?title=ISY_Portal_Admin_Console
 
Plus, MobiLinc works with ISY Portal for remote access…
https://wiki.universal-devices.com/index.php?title=ISY_Portal_MobiLinc_Configuration
 
And to fix your default email issue you need to update to 4.9 if you’re running 4.x firmware. Otherwise setup a Google account and use that.  Directions also in the wiki.
 
Finally….read the information in current release area (on the forums) for ISY Launcher for current/best way to access ISY locally (the “old” method of a browser and Java don’t work so need to learn the new way). It’s simple if you’re as tech savvy as you say you are.   
 

@fbelg210 follow the instructions here: