Geddy

UD has been updating the wiki here and there with eisy ui information: https://wiki.universal-devices.com/Eisy:User_Guide#eisy-ui It's very much a work in progress. I have a few folders and find the main list very lack luster and difficult to migrate. It had a period of time that folders would automatically expand and they don't seem to keep their memory from one use to another. Because it's not very useful (to me) I haven't used it very much up to this point.

@j.rieff glad you found it. For future reference: Go to Universal Devices site (https://www.universal-devices.com/) and it's available via the "My ISY" near the top right of the site. Or you can direct link to it here: https://isy.universal-devices.com/start.jnlp

@matapan I'm assuming by "per documentation available" you were following the instructions found in the wiki: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card It says if it was a new SD card you wouldn't need to format it. I'm not sure if formatting it has any impact on the NEW card or not, but perhaps some artifacts from macOS formatting it might happen (not familiar with macOS to know if even doing FAT32 doesn't add some "mac cooties" to the sd card. According to these directions there should be a "Goodbye" message after the formatting in the telnet session and then the ISY should reboot. I think at that point you have a very basic way to access the ISY994 via the admin console and that's why/where you would then need to update firmware to the latest for that specific device. NOTE: do you have a PLM connected to this "backup" ISY994? If not, you should only download/install the non-Insteon firmware. Otherwise, without a PLM connected you will always launch into admin console in "safe mode". I wonder if you could disk copy the working SD card to the new SD card and try that to see if it would boot up. I've never attempted it, so just a swag suggestion. Otherwise, try the telnet formatting again. Is there a way you can wipe the new card of any information and put it in an unformatted state?

Try these directions: https://wiki.universal-devices.com/ISY_Portal_MobiLinc_Configuration Remember, I don't think you can add the ISY Portal to ISY994 any more, but certainly works if/when you get the eisy on the portal. I just checked it out and my setup is exactly as described in the wiki. Online line I think it left out was "Connect Method" and I have it to Auto Detect and it shows as "Auto (HTTPS)". I also have it set to auto sync over wifi and cellular. Oddly enough it does show my plugin folder and the YoLink plugin does show temps of all my temperature devices (that's nice). Other plugins are there and report some info, but I don't typically refer to them in the app and don't use many plugins in automation settings. A couple of my Zigbee smart plugs/outlets do work. I don't have any z-wave currently connected so not sure if they respond or not. They do show up in the list of items, but they are not currently in use (come to think of it I don't even know where they're being "stored").

Did Michel get things cleared up for you through the support ticket?

Mobilinc HD still works just fine with Insteon devices and the eisy. I use it (rarely). I have it on the iphone and know exactly what you mean by being able to sort by name or on/off status. I've set mine up to use through the portal access just as I always had it with the ISY994. The only things I miss by using Moblinc are devices added by plugins. To me Moblinc HD/Pro has/had much better UI for layout. However, UD Mobile has been good the newer things being added with z-wave, zigbee, and plugins. I just don't have much use for those so haven't spend the time learning/transfreing to UD Mobile like others have. I'm using Mobilinc v4.17 on iphone iOS26.2 without issue. The "old" Moblinc Connect option is what broke when UD came out with the Polisy/eisy lines.

If you clear your java cache or look in the windows (I assume you're on Windows) temp folder for UD*.state files and clear one that might say finder or list or something (I forget the actual name and not local to my device currently) it might change the name the next time IoX Launcher is run. I think the name of the device is a cached value. If it didn't change on the following launch. Best to use the ticket option. My guess is something didn't update correctly and UD will look through the logs and probably give you a few commands to run. Since you ran the update packages again in admin console that would be the first suggestion to try an update process again. Odd that the web didn't give you anything on the sysconfig page. That could be a web issue. I would suggest trying a different browser. Also, you mentioned you use the Unifi edgerouterX. Do you run vlans? Are you running any antivirus, firewall clients, or VPNs on your computer? If so make sure you are on the SAME vlan as the eisy. Turn off antivirus, firewalls, and VPN clients.

@dbwarner5 I got the same email. Waiting until things don't work. At least you can get out of the "early access" easily. Just have to say: "Alexa, end Early Access," or "Alexa, exit Alexa+". But if what @TJF1960 and @apostolakisl are saying is that things work (now). That's hopefully a positive sign. If not for Echo for all the UD integration parts. 🤞

This would be simple if you had an on/off outlet for the modem. I might wait a little longer than 60 seconds for the modem to be fully offline and the cable provider to "know" the device was offline. Make sure the program isn't set to run at startup in case you have a power outage and it shuts things down just as things are trying to boot up. I would probably go the route that @Ross did and get an inexpensive "smart plug" and just have an automation within that app to turn the plug off for 3-5 minutes (maybe middle of the night). It's tricky though do those power back on if the network is down when the scheduled time to turn back on happens? I don't use them so can't test (haven't tested). But ultimately, it comes down to what are you really fixing? You might still have underlying internet issues somewhere that would be better fixed with the provider. You're just making a work around situation rather than getting them to fix their problems (or finding out that it's something on your side that needs fixing). It's kind of like when router manufacturers added the ability to self reboot on a schedule. Why did they do this? Because they wrote bad code that would cause the router to lock up over time and people felt it was easier to make a reboot schedule than to buy a better quality router. You're just rebooting a problem rather than having the cable provider "fix" or at the very least troubleshoot if they have potential issues.

@stillwater Since the IoX finder window seems to indicate the device is updated to 6.0.4 it's possible you need to perform another reboot/power cycle to the device to bring things up again. Are you able to get information if you browse to this page: https://eisy.local:8443/WEB/sysconfig.txt (If you get a security message click advanced and click continue to site - it's local so it's fine to access) If after a power cycle you're still unable to get eisy UI to come up at https://eisy.local/ then I would suggest opening a support ticket before you go any further. Certainly don't get into SSH and run any random commands. During this time of development it helps UD more if users file support tickets before random attempts of repair that might make things worse. It helps them learn what happened to a system, but is also easier for them to correct what has happened to this point. Open a support ticket here: https://www.universal-devices.com/my-tickets Where will it show as "ISY"? On mine the "Name" is my personalized name given to the top item in the node tree and "Type" shows as "eisy". What's the result when you got to https://eisy.local/?

@matapan the underlying question is simply, why? Why do you need to try to capture an extended event log? Perhaps you could explain any issues you are having or are trying to find and get help with those rather than just a random time of event viewer? Also, as @IndyMike points out I don't recall there being any timeouts on the admin console. Certainly not on the ISY994 (that's where you posted this question so I assume you're using the ISY994). What firmware are you currently running? I know it's not advised to leave admin console open, but it's been known that many do. It's more likely a computer issue is killing the Java connection after a period of time. If you're going to leave it open for an extended period of time I might suggest you do so on a computer that can be hard wired to the network rather than a laptop or other device that is relying on wifi network access. Even with sleep and hibernate turned off sometimes a small blip of the wireless network signal can cause issues (perhaps causing the admin console to disconnect/reset).

@bwbeisne not that it would be the entire answer to your issue since it's "worked" this long, but you're on an outdated firmware. It's a small update from 5.3.3 to 5.3.4. I would suggest you make a backup of your system and update to 5.3.4 to see if there are any fixes in that update that might resovle other underlying issues. The release information for 5.3.4 and the download links can be found here: https://forum.universal-devices.com/topic/33287-534-isy994-last-release-for-isy994/ The errors of "System -170001 [UDSockets] PSub:41 error:6" are infomrational in sorts for the ISY. According to Michel in another post (from 2019) this indicates that a socket isn't closing properly. Do you leave admin console open for long periods of time? And you also mentioned something about the web ui (is this through the portal?). Neither options are designed to be left open/connected for long periods of time. I woudl suggest you log out of everything if changes are not actively being made. See here: https://forum.universal-devices.com/topic/28034-help-with-repetitive-errors/ Other items that would tend to slowdown admin console: Memory usage of Java on your system. Look up how to set min/max memory settings in the Java console (configure java). Looping programs - make sure in the program / summary tab that no programs are looping. Usually this would make admin console unusable, but just watch for any out of control programs. Look in the summary tab for any programs that are set to run at boot. Turn those off or disable the programs for now and reboot the system again. Lastly, are you using any 3rd party apps to access the ISY994? I would make sure those are closed and/or disconnected from the ISY994 then power cycle the ISY994. This could be a drastic last step that I would suggest. If you do this make sure you have a current backup and perhaps even a backup from before these issues began. If the PLM is failing (again) making a backup now could include issues from the failing PLM. This is why you would want to be sure you have a (recent) backup from before the issue was noticed. According to the PLM quick start guide - to factory reset the PLM - What's strange is after the reboot you're having something logging into the device that's failing (-10104). Then you have some files that are failing to open (-110022) (you can see more about the error codes in the wiki). It might be a problem with the SD card and that gets a lot more involved with fixing. Look in the wiki for replacing the SD card. Again, try running a backup now and see if you have any recent backups that you could try to restore depending on your next steps.

@theitprofessor I learned recently that there's been a few "bugs" under the surface that UD is suggesting you only access PG3 through the eisy_ui connection rather than the "old" port 3000 method. Now that you're on 6.0.4 make sure you get in the habit of connecting to PG3 through eisy.local (web ui) moving forward and not through the "old" method of directly accessing PG3. The bugs seem to cause some connection issues with plugins when using local or eisy.local credentials. I'm not sure what plugins were/are impacted, but just out of precaution use the eisy_ui method moving forward. (Thanks @DennisC for pointing this out to me!)

Maybe describe some of your issues you're having and people here can help identify if this is an Insteon issue or an ISY994 issue. As @apostolakisl mentioned above there's a new "eisy_ui" in the works that is browser based. So far it's still being worked on and developed. For the time being the tried and true java admin console access remains available and works just like it has for the ISY994. However, I might expect that "replace device" might be a late addition to the web interface. There's no ability there currently, but I too hope that it would become available before completely shelving the Java access. This one ability alone has helped so many through the years as old Insteon devices fail and are replaced. Sadly, if you are replacing old devices with "new" i3 devices from Insteon the only way to fully support those would be with the current eisy r2 (and eisy or Polisy, but these devices are not currently being offered and Polisy has changed to end of life - basically - with no further os updates). This is in the eyes of the beholder. Many others have relied on the Java interface for ages (many more that don't post here because they don't have issues and thus don't need to post here). My only hope is the new web ui has the same abilities as the tried and true java admin console. It's certainly been growing pains while it's being developed.

@HTTRC I never recall trying to add/change user names. As far as I recall from comments on the forums I don't think the ISY994 ever implemented the multi-user ability. I think it was limited to one account that acted as admin. It's been so long since I used the ISY994 and not a feature I needed so just going off long time ago memory of random comments on the forums.

If the password didn't reset then it's possible you didn't hold the button long enough. Sadly, on the ISY994 if you hold the button too long you can end up factory resetting the device. The instructions you linked to indicate that it will be about 4 seconds for the lights to blink in unison then hold an additional 7 seconds. It's an awkward process and timing is everything, but if you went an additional 10 seconds after the lights started blinking it might be enough to trigger the password reset. If you're able to log in why not just change the admin password back to the default? What are you attempting? Typically the password reset function is to use when you cannot get logged in and need to reset the user/pass to default rather than fully resetting the device. Since you are able to log in then I would just reset the admin user account and possibly the User 1 account (if that's what you're saying you're using to log in). https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:File_Menu#Set_Userid.2FPassword It's been quite a while since I used the ISY994 and remember having to reset the password once or twice and didn't have issue with the button process. I'm not sure what firmware you're using, but don't think that process ever changed since the wiki is written for the older ISY26/99 devices, but continued to work for the ISY994 (and even Polisy and eisy) device(s) using the Java Admin Console access method. PS: @DennisC this is in the ISY994 area so I assumed they're using ISY994 device.

@DennisC thanks for the info. Crazy times!

@Kentinada when your system comes back up you might need to associate your portal account with the PG3 access. I think somebody else went through this the other day with something else. Try accessing PG3 via web browser by this address: http://eisy.local:3000/ (If this doesn't work replace "eisy.local" with the IP of your eisy). Then on the top menu click on "System" then click on "Switch Portal Profile". Log into the portal with the account you've always had (the one you purchased this, and hopefully other, plugins). It's likely that you somehow logged in with a different account or PG3 had forgotten your portal account. It just needs to be re-synched.

A disabled program will run if specifically called. In your situation if the program above is disabled and your geofence is set to run the IF (as @oberkc suggests) then it will only evaluate this program when the geofence (entrance) is triggered. This is typical suggestion for programs that you don't want to run on their own. However, another program calls on the "IF" of the program above it would evaluate the disabled program and run true (THEN) or false (ELSE). Having the program disabled means it won't run on it's own from sunset to sunrise (next day). But when your geofence triggers the entry area it will run the "IF" line and the result would be to turn the lights on from sunset to sunrise (next day). If it's before sunset then the lights will "turn off" (based on your "ELSE"), but they shouldn't be on so really the else is useless (in this case). If the program is false it just won't turn anything on. If it's the middle of the day though and the lights are on as you have it now the else would turn them off. I would probably suggest removing the ELSE lines from your program. As @oberkc suggest you need to have the command after the wait to turn the lights off. I would suggest this as your program: Geofence Entry Lights - [ID 0007][Parent 0006][Not Enabled] If From Sunset To Sunrise (next day) Then Set 'Gate Lights' On Set 'Garage Door Lights' On Wait 10 minutes Set 'Gate Lights' Off Set 'Garage Door Lights' Off Else - No Actions - (To add one, press 'Action')Make sure 10 minutes is long enough from when you enter the geofence area though. And sometimes I've been known to have to unload the car and take my time that 10 minutes isn't enough so I'd have to turn the lights on again (manually - oh the humanity!). Lastly, the program will have the little red circle with a line through it to indicate it's disabled. Due to some issues (in the past) of IoX updates enabling all programs I have added "-d" to the end of my disabled programs. If you wanted to go a step further you could put them in a folder called "Always Disabled Programs" (or just "Always Disabled"). Don't set folder conditions, but just put all your disabled programs in there. That way if there's another update that suddenly enables all programs you know where and what programs should be disabled and can change them quickly. This is just a point of organizing for me and learning from history.

This is odd. Are you sure this action is disabling it or do you leave the program disabled? Enable the program in Admin Console then trigger the "enter" again with admin console open to see if it is disabling the program. Could you post a screen shot of how the geofence is setup? The only way the geofence would disable the program is if you have that as an action on the app. Otherwise, something else in IoX is disabling that program. It's been a while since I used a program on the geofence setting. @oberkc brings up a good question as to what is being called by the program. The way you have it written (and it being disabled) depending on when you trigger the program only after sunset would it turn the lights off. Maybe change the geofence to trigger the "THEN" just to be sure that program works to turn those lights on. Otherwise, if you trigger it and it's before sunset then the lights would stay off (because of your ELSE). Also, I would remove the "wait" line. There's nothing after it (at least not showing in what you pasted). I haven't setup tracking by more than one phone (we just don't need it for our automation), but nothing you have above would be dependent on which phone crosses. If it's setup the same on both phones to call the same program then if either phone crosses into the geofence they would both call on this program. You might want/need a variable if you're trying to track by phone, but that gets more complicated and involved.

@UD2)17rrh What phone OS are you running? Be sure location permissions are allowed. On the geofence do you have it calling on the program or is the program setup for location change? Please post a copy of the program for reference. Be sure you RIGHT click on the program and select "Copy to Clipboard" then paste as text in here. Be sure you use the "COPY" option - should be last option in the menu! (NOT export!) Be sure the geofence is setup as outlined in the wiki: https://wiki.universal-devices.com/UD_Mobile#Geofencing Once you have the geofence setup and commands in there you should be able to run the "trigger enter command" to see if it would work. Where do you see this? I run Geofence options on UD Mobile, but do not have anything related to them in Devices and Scenes in UD Mobile. It must be something associated with Occupancy 2.0. I do not have that in use (It's not needed any longer - according to the wiki).

I've still got some of the old 5.3.4 backups from about the time I migrated to eisy. They're the same as what you notice. They are ~76k, but could just be difference in items and programs. I have older ones (by a few months) that are ~48k. They're also as you see just zip file with a zip inside that appears empty. I haven't ever actually expanded the files, but just windows 11 file explorer viewing the files. Approximately how many devices do you have? Also, how many programs and Network Resources (if any)? Just be sure you follow the migration steps and you should be fine. How are you observing "a lot of console activity"?

Click on a selection that you added to IoX Finder window. Maybe post screen shots of what you're seeing. I'll assume you mean "start.jnlp". There shouldn't be a .win file. This was meant to be used on a browser. That launches the eisy-ui interface. Attempting to add this in the Java IoX Finder window will NOT work. Still possible. Just need to add your device locally. Sounds like you're having issues due to being scattered and trying too much all at once. Pick IoX Launcher and focus on loading that. If you're reading the wiki then it walks you through the process of adding the eisy manually if it isn't found. Are you running VLANs (on your network), anti-virus, or VPNs on your computer?

Go here: https://www.universal-devices.com/my-tickets Log in with portal credentials.

Is this something that worked and recently broke? If you click on the scene in the admin console and turn it on does it do what you expected it to do? If so then it should be setup correctly. But there have been issues with scenes being corrupted coming from 4.x to 5.x firmware. Since you mentioned ISY994 in the original post I figured you might be on the older device. Being that you're on eisy and running 6.0.0 (ps that's now outdated and you should update to 6.0.4 for minor fixes by UD) your scenes had probably already been modified. Thanks for posting, but you didn't use "COPY" you used export. The last option when you right click on the program will be "Copy to Clipboard". That gives a much cleaner and user friendly paste for the program. Since it's a simple program the above screenshot will work for now. It's not a program issue, it's likely a scene issue. I do not use many scenes so cannot try to describe what you should look for in the scene settings or in the program itself. Perhaps others that are scene gurus can chime in to help.