Geddy

Take a look at this thread. If that applies to you. Since it seems Moblinc doesn't officially support the eisy there's not much that can be done, but I will say that it's still working for me on IoX 5.6.0.  
Another option (for iOS) is to run Locative + Occupancy node server (via UD Portal) to trigger geofence.

@Fredo Check the actual Geofence Location is still defined in "Location Settings" on Mobilinc. If it is then make sure the variable is still the same as you have indicated above.
I recently had a similar issue and either the location or the variable had been deleted from the app. I'm not sure if it was iOS related (I recently updated to 16.4.1) or something else, but I noticed some programs not triggering for a while. I'm running IoX on eisy, but it was clearly app related as something was missing.
I think I had to recreate the location and reset my variable. I then had to adjust my programs to reference the new variable. Since I'm on IoX I had some issues with Mobilinc making the variable through the ISY Portal connection, but I made a local connection and it worked right away. I since changed back to ISY Portal connection method and my geofence and programs trigger correctly. 
While not an issue for this situation you should consider updating the ISY994 to the last release of 5.3.4. There weren't many fixes from 5.3.3 to 5.3.4, but with support ending for the ISY994 you should at least be at the current Firmware so any forum support you get will be on the "most recent" build.
 
I echo @Javi and @DennisC comments of trying UD Mobile. You can use Geofence to call on programs to change the variable as you cross the boundary. There's a learning curve setting up the new app, but it is very customizable to fit the various needs of users. It's also being currently developed and supported by UDI, unlike Mobilinc (that hasn't been updated in several years). 
 

@johnmsch in addition to what @kzboray suggests above you might need to associate the .jnlp with Java. 
That can be done 2 ways (in Win10 and Win11).
Right click on start.jnlp and select "properties". Then in the "Opens With" look for "javaws.exe" in the Java\jre1.8.0_361\bin directory. In the properties window it should look this way:

 
Otherwise you can go to Windows Settings -> Apps -> Default Apps -> "Choose default app by file type". Then go down the list until you see .jnlp and make sure it's set to use "Java(TM) Web Launcher".

 
My bet would be that you downloaded something other than the "regular" Java that you get when you visit java.com. You might have gone looking for other versions and seen some higher number versions, but those have specific use cases and not what IoX Launcher is designed to work with. Make sure you remove any Java other version you've installed before proceeding!
 

@TRI0N what pop up are you talking about? 
There is/was an alert in Admin Console that updates are available. That's been a known bug and can be ignored. I thought it was fixed in 5.5.9 as I didn't have the issue after rebooting, but guess it's still an issue. I know it's been reported and is said to be fixed in an upcoming release. 
 

Are they turning on/off at the same time every day or randomly? If they're at the same time then just before you think they're to turn on open Admin Console and open event viewer and set to level 3. That will show traffic that happens during that time. 
Prior to that you can review the "Summary" tab of the programs tab and see if any programs have triggered around the time those lights change. You can sort the summary tab based on "Last Run Time" and see what might have run about the time these lights randomly turned on. If no program triggered then it's a scene triggering the lights.
Next thing is on the lights in admin console see if they are part of any random scenes. You say they're in scenes that are getting turned on/off with a program. Is there another controller of that scene that is causing these lights to come on? Click on the device on admin console and on the right it should say "Membership". See if it is responder to any different scenes. If it is then go to that scene, right click on the device and select "remove from scene". 
Lastly, the best method to resolve this is to factory reset the devices and then set them up again. If they're easy to reach then it should be a simple task. It's possible the lights got manually linked somehow and the ISY994 doesn't know about the manual links. (If none of the above troubleshooting steps help) Some devices have different reset options so best to google search for a user manual for the type of device you're resetting to get the proper method. 
FYI I just Googled for 2477S Dual Band SwitchLinc and found it :

@HHarris Welcome to the forums. We split your post out to a new post as you had it posted in a Win11 issue, but say you're on Win10.
What has changed that your ISY994 is not found on the network? Did you replace your router or did you update the ISY994 firmware?
What firmware are you running? 
If you changed your router please review this section of the wiki:
https://wiki.universal-devices.com/index.php?title=Main_Page#Changed_ISP/Router_-_Can_no_longer_access_ISY  
Also, please review this section and observe the lights on the front of the ISY994 and report what you see:
https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights  
 

@Jack D 
For your Sunrise program is there a "Next Scheduled Run" time shown?
I just created a test program like your Sunset program. The status matches what you're seeing.

The above "Light-test1" is for Sunset, and "light-test2" is for Sunrise.
 
Make sure that you've saved the programs. They shouldn't have a green arrow on the name like this one does:

If I run the "IF" of the Sunrise program my light turns off. It also updates the summary for "Last Run Time" so you know something in that program ran when you triggered it manually.
 
The program is:
light-test2 - 
If
        Time is Sunrise
 
Then
        Set 'Front Door' Off
 
Else
   - No Actions - (To add one, press 'Action')
 
 
 
OH!!!! I've got it (I think)! While I was typing the above I looked at your screen shot again. You've got a folder condition in the "My Programs" folder that is making the folder false. Anything in that folder won't run. (which makes it odd that your sunset program ran - maybe it ran yesterday, but didn't run tonight if you changed something today). 
Make sure your "My Programs" folder looks like this:

NO conditions!
Mine doesn't have any conditions and doesn't show up in the summary tab. I added a condition that would make that folder false and it showed up in the summary tab. Because the "My Programs" is typically the root folder none of the programs in the root would show that as the path. Only programs in subfolders would show something in the "Path".
I still don't know how your Sunset program shows "True". 

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!