Geddy

@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.

@S. Alexei Gitter or if your router finds the eisy locally even easier to just type: https://eisy.local/ You will probably get a security alert on the browser you're using. You can click advanced and continue to get to the site. Note that I don't think eisy-ui allows direct setup for matter/thread devices. I've not tried it lately. There is a plugin that should help with that, but it's had mixed success and has very limited items for support. I don't use Matter yet so have no experience trying to add devices, but seeing the issues people have on the forums would say don't be too quick to jump on and try to add a bunch of items. As for the Admin Console (via Java) it's still available. What computer OS are you using? It's fairly straight forward (for windows). On macOS it seems to cause a lot more issues. If you're having issues with the launcher finding or keeping the listing you can always save the file locally and load it to have the last list available. Again, seems like it might be computer OS driven issues.

@TomNow2 I'm in the "if it ain't broke, don't fix it" camp. Aside from some issues (with z-wave in general) it sounds like things work as you have them setup. There's been a lot of comments through the last several years (and most recently in this thread) that z-wave (by nature) has a "popcorn effect". Meaning what you're experiencing seems to be normal for z-wave in lighting. Changing the controller wouldn't help the nature of z-wave and the inherent issues it has with lighting delays. Initially I'd say just leave it as it is. It's a vacation home and you don't seem to need to mess/fiddle with it how it currently is controlled. The other side of that would be that the investment to change the switches and other automation parts to other devices might outweigh the issues you're currently having, but living with. Sure, you could rip everything out and put in Insteon (for lighting) and have better control of on/off and dimming than what z-wave does, but you would also have a different controller that is going through ongoing development and updates that you'd need to push/update when you got to the vacation property. If the issues you're having are bothersome and you want to fix those then you'd more than likely have to remove all z-wave lighting control and go with a different option. If it's a DYI project then Insteon is probably the best option for that kind of job. Otherwise, there are still different options to consider (see referenced thread linked above). Just changing the controller for the issues you describe won't make things better. Note: I don't know the Hubitat system so can't comment on what it can/can't do. I tried Home Assistant a few years ago and was not impressed (too much learning curve at the time) so can't say if that would be beneficial to use differently.

I'm not sure I follow. But I don't often look for the isy/eisy device itself. It's always listed as whatever name is given to the in the tree with the console/monitor looking icon. It's possible that UD made it sort to the bottom of the device list, but I have my eisy name starting with a "U" so it seems to be sorted at the bottom just above the "Auto DR" scene (a default that can't be deleted). I believe the default was "my lighting", but some have changed it to eisy so it might show eisy as root and eisy as item directly under it. Some might have had it as "ISY" and it carried over in a migration. I remember when the Polisy and eisy were released that a lot of users wanted to add back the query program and we would suggest to look near the bottom and that's where people found it. But again...you've found it now. I was just worried that you seemed to have a broken query program after an update and it made me check mine to be sure it wasn't a widespread bug/issue that needed to be brought up to UD.

@mvgossman please let us know what firmware you are using on the ISY994. It could be that you updated from 4.x to 5.x and the scenes changed and are not setup correctly to be controlled by the ISY device. Also, you might want to put a 1-2 second wait between commands (maybe more) so that communication is not over loaded. Lastly, for easy of assistance the preferred way to post a program to the forums is to right click on the program and select "COPY to Clipboard" then paste as text into your post. This makes it easy if people need to help edit the program by not having to type or describe things that are in an image.

@raydoc attempt the power cycle suggested in the other topic and see if the portal reconnects. https://forum.universal-devices.com/topic/46245-eisy-offline-after-power-failure/#findComment-401708 There had been posts in the past about there being some hiccups with power loss. Depending on what firmware you were on there was a pushed update for underlying issues a while back that might have attempted and not finished correctly. If a full power cycle doesn't resolve the issue you might be best off opening a support ticket to take a deeper look into your system. https://www.universal-devices.com/my-tickets

@Techman this caught my attention...I ran to check mine and it still shows for my program and I'm on "isy-6.0.4_1" (from https://eisy.local:8443/WEB/sysconfig.txt). But I'm only looking in Java Admin Console. Haven't messed with eisy-ui or UDM in a while and never looked at Programs in those. Sounds like you found it though and can recreate the program, but you worried me that it might have gotten corrupted in an update. Last I recall a comment from UD was that it's not needed (the query program), but my concern was that it was originally there to bring battery device status in sync when the query runs. Since it's not included in Polisy or eisy by default...users have to add it back manually if they want it. I wonder if not having it causes any issues. I don't have any Insteon battery devices so not too concerned with it.

I almost mentioned that, but when I looked at it through eisy_UI that option isn't available any more. I'm guessing that is something you needed to access through the PG3x option directly. Glad you got it sorted out. Yeah, having two devices on the same portal account could be a problem when the plugins are licensed to the account and device they're installed in and you start working on another. Interesting. @bmercier is the "switch portal profile" option going to come to eisy_ui?

You might want/need to open a support ticket for this to see what's happening in the system. https://www.universal-devices.com/my-tickets I just tried on my eisy and was able to install one just fine through eisy-ui. Got the little green box that it was installing then that it installed successfully. Currently running PG3x 3.4.11 on eisy UI 0.9.0.

@bmercier What I don't understand is on the eisy-ui it has an "upgrade to" column, but it never reflects that something is available to update. If you hadn't posted that .9 was available would the system have ever told me in the web ui? After the update I get this confirmation showing a reboot is required: So I click "Reboot eisy" and about a minute later get this error: I then logout of the system and log back in and get a 404 error. I refresh the browser window (Chrome Version 143.0.7499.171) and the system comes up. During this time UD Mobile was giving notifications it typically gave about PG3 stopping then starting. I waited until the "starting" notification before trying to log in again. I would suggest that part of the "reboot eisy" process that it log you out of the web ui so errors like this might be avoided. Unless it should be able to maintain access to the ui following the reboot. It didn't appear to since no other links/sections worked until I logged out and logged back in.

Experience varies by user and systems. I find the java interface to be 100% reliable and the only thing I use. I don't use it very often because I don't need to alter my system very much. I just mostly go in to admin console when trying to help others here and I've not had an issue with it. Although, using it more than a few times a year does keep my use of the process sharp enough that I remember what to do. Thing is it's been this way for 10 years (for my time with ISY/Polisy/eisy) so am having learning curve issues when having to use the web interface that's still being worked out. Hopefully they'll get it working sooner rather than later and be as reliable as the java connected admin console. Either way I hope the web ui will be "generic user" friendly.

@KHenningsen welcome to the UD forums. Sounds like you’ve done a bit of research up to this point. Since you’re on macOS I’m not 100% sure I can fully help. However, I know some have said make sure you don’t unzip the file you download. Apparently macOS will auto unzip or decompress the files. I’m guessing you know how to stop that. You will probably want just the first link for the file in the post. Does your device have a zwave card installed? Since it is probably an older device if it does have zwave you probably have the 300 series and that is a lower firmware that supports that series. If you don’t have zwave then you can use 5.3.4. There are huge differences from 4.9 to 5.3.4 so do a lot of reading for cautions to heed before proceeding. My simple suggestion is to make a back up of the system, but also make a backup of all your programs (right click the “my programs” root and select copy folder to clipboard. Then paste that as text in a text editor (not a word processing program so it keeps text unformatted). Save that file as a back up of all your programs! There are other pitfalls that might cause issues so be sure to read through some older posts about the 5.x upgrade issues.