Geddy

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?

@bmercier understood. Worth the shot.

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 would it be possible to request a change in the backup name created in eisy-ui? I'd like to suggest if it is possible to put date first and no hyphens. yyyymmdd-eisy-backup It's just a personal preference. I've long used dates in my file management and put dates first (yyyymmdd-xyz) then what it is so it all sorts by date created. It's always been bugging me when I'd make lots of IoX backups and it would be "IoX-Backup.v#.#.#_day yyyy.mm.dd hr.min.sec am/pm". If it's just going to "eisy-backup" then the date it would be good (for me) to put date first. I'm sure everybody might be different, but it's a heck of a lot easier to find most recent when it sorts by name and the date is first. At least you've left the day out! (That's appreciated!) Interesting to note the files inside the .zip are all showing time created in GMT. I made a backup 4:34pm Eastern and the files inside the .zip show modified time of 9:34pm.

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

That's interesting. Guess they still have a few display issues happening. Are you running on a Polisy or eisy?

What browser are you using? It's possible a browser is blocking the redirect to Ring. When I click on the authenticate button it directly goes to the site for oauth.ring. I'm using Chrome with no blocking on the browser or router. I would attempt with a different browser first to see if that had a different result. If you're sending logs it would be best only for the ring plugin log (NOT the PG3 log). I would suggest you open a support ticket and possibly reference this thread and include a plugin log file. Before pulling the log try this: Switch the log status to debug then press "restart" for the plugin. Allow a few minutes for it to completely start then click on Authenticate. After about 5-10 minutes download the log package for the plugin and attach it to your ticket Start a support ticket here: https://www.universal-devices.com/my-tickets

Typically it's only one per device found automatically if local. There was a period of time that two popped up and that messed a lot of people up, but that's been a few years. For the more current time I only recall having 1 come up per device. You can add a second and it will remain until a period of time (usually with a Java update or a temp file dump). Since the IoX Finder window information is kept in the UD*.state file in the temp folder it's not always a "fixed"/saved list. That's why many will suggest saving the finder list for the time(s) it does go away and you had a specific system added to your finder list. It is easier to load a saved list than trying to remember what address(es) you had saved previously. I think with the introduction of eisy_ui and requiring the UD Portal credentials has become the default found when IoX Launcher is first run. I have two entries as one uses the UD Portal creds and the other is the local (unit specific) creds. Thankfully it now shows which one to enter when selected on IoX Finder.

@raymondjiii This is similar to an issue that was in another post over a month ago. Make sure you've updated recently. Since UD isn't posting release announcements I'm not sure if they've updated again, but the last time I updated it installed 6.0.4_1 You can find what you're running on a web browser: https://eisy.local:8443/WEB/sysconfig.txt (click advanced and continue if you get a security/connection warning). Also, you can apparently see on eisy_ui if there are updates available (I'm not sure as I haven't used that ui much). However, the fix in the past post was simply a power cycle of the eisy. https://forum.universal-devices.com/topic/45990-trouble-with-new-device/#comment-399971

If you haven't removed and reset yet this part gets a little tricky. It might, but might not have any impact on programs. I would suggest the following two steps if you haven't removed them yet: Make a text copy of ALL programs On the programs tab right click on the root "my programs" folder. Select the last item of "Copy Folder to Clipboard" Paste all programs into a text editor (i.e. Notepad on Windows) https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Tree_View On the Programs tab you can (again) right click on the root folder and use the "Find/Replace" option. You can then search by device and make note of each program that device is referenced. https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Tree_View#Find/Replace Sometimes when you remove items and add them back exactly as you have them they might not mess up programs. Just don't do anything in IoX while you're doing this process. Don't close Admin Console, don't click on a different tab, just remove the device from Admin Console, Factory Reset it (at the switch), Link in Admin Console. Use the exact same name for the device. It could be that it will re-populate in the programs, but having the text copy and knowing what programs it is referenced in will help a TON by being able to go back and repair any broken programs. There is no way to backup the programs then re-import them so having a text copy of ALL programs is key to try to fix if stuff does go into a broken state of missing device in programs.

@raymondjiii usually the "name" is what is the root or actually one under the root when in admin console. You can change the folder name and then clear java cache and run start.jnlp again and it should change the name. I'm not sure why you have different entries for the same device, but it explains why on a newly installed (computer) they would all show the root. Perhaps you changed the name at some point and the cache or .state files that UD use still have the old name. I have my root as "eisy" then the folder just under that has a personalized name. When I open the IoX Finder window it shows just the second folder name (the personalized folder name). I only have one system though.

@DennisC thanks for the info. Maybe it's progressed far enough to be reliable. Too many moving parts to keep up when things are moving this quickly. I know it's the ultimate goal to have eisy.ui replace the Java admin console. I've just experienced enough issues with the web ui to not find it reliable for my comfort level. Maybe someday...but I've not had issues running admin console and updates from there so works for me. Currently every time I log into eisy.ui I have to refresh the browser (Chrome) because it just goes to a blank page. It's a minor annoyance, but that's the unreliability that is just enough not to want to use such an interface. I guess more have issues with Java and admin console so UD is finally (after many, many years) going to a web ui, but the growing pains (for me) with that system outweigh the reliability I've had with the Java interface. By a long shot! I'm with you! There was debate several years ago about allowing automatic updates when the device reboots. I was told then, and numerous times since that UD would not implement "automatic updates". However then @bmercier indicated there was indeed an automatic update after 6.0.x came out due to an underlying issue that required an update of an apparent "minor" part. I would hazard a guess that something in 6.0 triggered the auto update to the current 6.0.4_1. The issue remains that an unexpected update could crash somebody's system. If they were away from home it could be days/weeks/months before they returned to get the system working again. That's the underlying concern that UD addressed in the past by not having an automated update process. Sadly, I think the error that was caused recently was an unavoidable situation that forced an automated update somewhere, but even then that's seeming causing issues for some users. I would suggest opening a support ticket to let them know of the issues you faced. Even though you've fixed it on your own for now maybe there was something they could review with you to see what happened to cause a failure. This is the time that when issues are experienced during an update that tickets are best for both UD and the users as a whole to potentially fix what could break everybody's systems.

@mullercentral not sure if you were still having issues when you posted this as you had several posts about this time that seemed to indicate you had a successful update. I just ran the 6.0.4_1 update (coming from 6.0.3_3). The last few times I have updated I just pay attention to the alerts on UD Mobile. It will tell you that the system has been updated and should be rebooted. I run 100% of the update process through Admin Console (the trusted Java access process). In the past there would also be an alert on the admin console, but I think that's gone away as of late...at least I haven't seen it. But once the UD Mobile app sends a notification to the phone (iPhone) I probably wait another 5 minutes then press the reboot button in admin console. Then after a bit of time UD Mobile will say PG3 is stopping and system rebooting then I get some alerts that it's come back up. I wait another few minutes then clear java cache, download a fresh start.jnlp and run that to access admin console. All seems well. Every now and then another reboot might be needed, but it's not been a common occurrence. I think somebody posted recently that the updates can sometimes take a while, but certainly not hours. This seemed to be a very minor update from 6.0.3_3. While I didn't time it seemed to be less than 5 minutes. I was busy doing other things while it ran. Since eisy.ui is still being developed I have been cautious to try to update from that side. I rely more on the tried (and true) admin console process to update the device. Until UD publishes something that says different that's the way I'll continue to update. One thing I wouldn't suggest is just pulling power. Either attempt a reboot in admin console or press and hold the power button to force a shutdown of the device.