Geddy

I think this is a known issue and being worked on and hopefully corrected in the next release. I've seen @DennisC comment about this being known. 
I believe the other is also part of the same issue. 
I had the issue once and it hasn't returned (thankfully). I'm not sure if others that got this error still get it often. 
(@DennisC do you still get the alert?)
You can check the subscriptions by using this URL: http://eisy.ip.address.here:8080/rest/subscriptions (replace the crossed out text with your actual eisy IP). It will ask for your user/pass this should be for local login to admin console. 
The result is an XML file showing the subscriptions to the isy process. 
<Subscriptions> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="36" sock="7" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="no" isPortal="yes" sid="0" sock="28" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="39" sock="9" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> </Subscriptions>  
I would suggest you shutdown the eisy (6 button presses...wait for red light), pull the power, wait ~20 seconds, power it back up, wait ~60-90 seconds, and log into Admin Console.
 
 

@CandC, @FloridaGary and @glarsen see if fixed this morning. Appears that a server might have lost a connection. It was fixed this morning from another post. Wondered if it impacted what you were seeing for favorites not showing status. 
 

From the wiki: 
[NOTE: The ISY994i takes a MicroSD card. The max size is 32GB. Please look for a card with the newer A1 rating (A2 also works, but will fallback to A1 because the ISY994 does not provide hardware support required for A2). All other process steps below remain the same.]
 
The wiki also outlines the process for proper replacement and reinstalling firmware. 
 

Perhaps the easiest way would be to enter a support ticket to get help getting to where the logs are and delete bloated logs and hopefully get you running again.
https://www.universal-devices.com/my-tickets
Additionally they would confirm that it was your log issue that was causing problems. 
 

@Wes Westhaver If you log into your account at Universal Devices website you can manage modules for your devices there. It might allow you to buy through the site that way.
Otherwise, try sales@universal-devices.com
Or you could open a support ticket via: https://www.universal-devices.com/my-tickets
Be sure to include your UUID for the ISY994 you want to add the module to.
Honestly though, ISY Portal is a steal for what it offers you. $23 for the first 2 years, then $20 for 2 year renewals. You get the Network Module as well as UR Mobile (for 5.x+), Alexa, Google Voice, Remote Access (no need to open ports on home network), and other options. All for less than $1/month!
https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Portal:_Integration_with_Amazon_Echo/Google_Home/IFTTT
(FYI @Techman the support email might not reach anybody (I haven't tried it lately), but it's not the suggested rout for support tickets now. Something went "wonky" sometime in the last few months.)
 

Make sure you search for "pin out" information. This is one that I book marked a while back from @Brian H to help describe what connects where:
There are a lot of posts. Perhaps the easiest way to find them/others is using Google Site Search since some might be archived and not showing up in the forums search function.
 

@richtimpa 3.1.18 is only for Polisy. 
If you're on eisy you should be on 3.1.22 (as of current release posts). 
If you're on eisy make sure you can log into IoX Admin Console. Then use that same user/pass to log into PG3x on eisy. 
 
If you're still having issues please power cycle the eisy by removing the power plug, waiting ~20 seconds, plug it back in, allow ~5 minutes for full boot. Then log into IoX before attempting to log into PG3x. 
More than likely if you ran an update and didn't allow enough time before trying to access the system it could create a conflict and UDX did not start correctly. From other posts it seems to correct itself after a power cycle and allowing it to completely boot up before attempting to log in.
 
PS: Nice auto correct on "eisy" to "Etsy"!

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: