Geddy

Read his earlier reply. Perhaps some changes have finally broken the last ISY994 firmware settings. I recall that there was a time that 4.x and early 5.x wouldn't work with the default due to the changes.

@GreyFox because this program is set to "run at startup" if you reboot your eisy then log into admin console this program will probably usually show the red line. Here is the reference in the wiki just as information: https://wiki.universal-devices.com/index.php?title=ISY_Programs:Icon_Colors The only time your icon would be fully green is while it was running the "THEN" portion. After the 15 minuets it should show half green. If you're rebooting your system and looking at admin console before the program triggers at 10:30:00pm then it will be partially red. That doesn't mean it isn't running. It's just the last time the program triggered it was false (and since you have something in the else section it would have run that portion). So that it doesn't catch your attention you might want to disable the "Run at startup" by right clicking on the program in the summary tab and select "Disable Run at Startup". You should look at the other programs that show half red in the summary tab to see if the "Run At Startup" column shows "ON" or a dash (-). If you want to see if the program works then right click the program and select "Run Then". It should turn on your light. But because the "IF" wasn't run it won't turn off in 15 minutes. If you're still worried that your programs are not running in the Summary tab look at the "Last Run Time" column and see if it's recent. If you just rebooted the device and all your programs are set to run at startup then most all of them should have a recent time run. I should also caution you that if you have a lot of programs set to run at startup you could run a big risk of too much Insteon traffic and create issues for your system. I would suggest limiting only major necessary programs to run at startup and others just allow to run at their regularly scheduled time. You could set the catch up grace period to a longer time if you have a lot of power issues. As @hart2hart suggests you should review the "Query All" program. Since in the ISY994 that might have been referencing the ISY994 or the name of the ISY994 you had. The Query All program is no longer default on Polisy or eisy systems. You will probably need to update that to point to your new device. The object will be in the "Your Devices" list. Sometimes it is near the bottom as a scene and will have an icon like a computer monitor. Then be sure you save the programs once you make the edit.

Try to reboot your device. Then also only access dashboard through eisy_ui and see if the versions are updated. Also, try the sysconfig.txt link above to see if the versions are updated. Lastly, relaunch the browser and refresh the page. Could be a browser cache display issue.

@hart2hart https://forum.universal-devices.com/topic/46475-updated-software-available/ I too seemed to be able to update without issue...maybe. Took less than 5 minutes. I think about 7 minutes including the reboot based on notifications from UD Mobile. Two issues I experienced: eisy_ui had issues logging in giving this error: "Timeout waiting for PG3 UI Session" (using Chrome) Plugin dashboard did not load (just showed blank page) (using Chrome) Just closing chrome and re-opening it seemed resolve the problems. The unit seemed to be okay to login so not sure why the errors were being given, but seemed to load fine on Firefox so restarted Chrome and things worked as expected. I confirmed with https://eisy.local:8443/WEB/sysconfig.txt that all systems updated to versions that @Michel Kohanim posted in link above. Nice work UD! PS: If you are using the java admin console and using the device credentials (i.e. https://eisy.local:8443/desc w/ local user/pass) you will need to clear java cache if using IoX Launcher/Finder (be sure you check all three boxes!). If you use the admin.jnlp direct download from the unit you'll also need to clear the java cache and download a fresh admin.jnlp so that UI and Firmware match.

@aLf too many uncertainties to say. I'd say no on an initial simple answer. Only because the ISY994 is no longer supported by UD and it's been so long for many of us on the forums since the update to 5.x to try to help resolve any issues that might happen in the update. If you need to spend a lot of time fixing things now then making the mover to eisy you might become frustrated and have issues that carry into the eisy system. One thing to look for in your current system is any programs that use "adjust scene". I recall that those will probably 100% break in the update from 4.x to 5.x. You'll need to recreate the program and possibly the scene. So if you have a lot of complicated scenes and even more complicated programs then I wouldn't spend the time to go to 5.x on the ISY994. It's just personal preference at this point and knowing that you won't have support from UD for the changes and have limited user help here because of time it's been since many updated to 5.x can't remember the little tips/tricks that fixed things along the development of 5.x.

@JLevy02 I wouldn't worry about it for now. There are too many places/ways to log into the system at this moment (IMO) and it's not worth trying to change or make the same. I would suggest you stop/avoid using the http://eisy.local:3000 route to log into polyglot as with the release of eisy_ui this changed how plugins are managed and could cause an issue. It's been posted elsewhere that UD is suggesting this in support tickets when people find they have plugins restarting or not showing connected when they log into the Polyglot dashboard through the :3000 port process. eisy_ui is accessed at https://eisy.local and is the suggested route to get to plugins now. Due to how the plugins are managed with eisy_ui this is the "cleanest" way to currently access Polyglot (Plugins). Since the eisy_ui is not fully function with all things IoX it's more a "look here doesn't this look pretty" screen (IMO). Java Admin Console - if you just use the current quick found address and log in it will prompt you for "Portal" credentials - thankfully they've added a comment for which credentials are needed to log in. This is acceptable, but as you found has some bugs that are not going to be fixed. Java Admin Console with eisy.local:8443/desc access currently uses the local credentials - this is the "old" process of getting into the IoX admin console locally and will eventually go away once eisy_ui is fully functional. I wouldn't spend time trying to change any logins currently. If you're wanting to standardize one then just make sure you know your portal credentials. Make sure they're strong safety wise since they are an online connected service. To change the portal credentials you'll need to go to my.isy.io and change them on that site. Click on "My Profile" once logged in and you can change your password.

This is how it's designed - currently. There's nothing to change. I'm not sure I understand what you're trying to change. Since UD is moving away from the java admin console access with eisy_ui being developed to handle all the IoX and Polyglot setup you'll have a single sign on function.

@JLevy02 it might be best to address this directly with UD through their support ticket. They can check if you inadvertently purchased twice and work out a refund if you did. https://www.universal-devices.com/my-tickets If you click on the "Details" button of the plugin you should then have a configuration option. Since both the Elk and Notification show to have nodes currently something has been setup.

I'm not sure when it changed, but do you think you remember it like this: I found this image in the ISY Cookbook. My guess is that since the cookbook was written in the ISY 4.x firmware generation that it was older and perhaps even prior to ISY 4.x firmware options. I currently see this as the option: My expection is that "Your Devices" replaced the Insteon/A10 option a long time ago. If you're thinking/looking somewhere else the only other place I see "Insteon" still mentioned is in Adjust Scene in the first dropdown then "Insteon" is in the body of the options. I think what you are trying to do is adjust scene then activate the scene. It looks like you can do that in the "Adjust Scene" option. I've never attemped to do this kind of adjustment, but perhaps this is where you're looking for "Insteon" to be able to control a device brightness over time. If it's not a scene you're trying to change then it might be possible with "Your Devices" and have to set a brightness level and a ramp rate then a command to dim or brighten. Maybe some of the program gurus can chime in on that process if you're still having issues.

Nothing mentioned lately by UD. Make sure that your license hasn’t expired by logging in on the web.

There was a BIG change in how scenes were handled from 4.x to 5.x. So much so there was this portion added to the wiki: It's been a long time since I updated from 4.x to 5.x on the ISY994 and I don't use a lot of scenes so I can't really give you the details about it. But I think for the most part the scene should at least migrate over correctly, but the biggest issue was if you have programs that use "adjust scene" they would need to be re-worked. I strongly suggest you make a digital text backup of all your programs before doing anything! Right click on the root folder in the programs tab (usually called "My Programs"). Select "Copy Folder to Clipboard" - BE SURE YOU USE COPY Paste into a TEXT editor (for Windows use Notepad) - don't use a word processing app - you want to keep the formatting and text as raw text! SAVE this file somewhere you'll know where it is. Doing this will save a text copy of all your programs. After you migrate if you have any broken programs you can search the text file to find what nodes were being referenced and/or what your settings were. Easier to do this from a text file than from memory. Trust me! If you used to setup scenes with "copy" option know that process was removed in 5.x due to how z-wave certification needed to be handled. This is the biggest change many have complained about going away in the 4.x to 5.x upgrade. It's suggested if you have to create scenes now to add all the responders and setup their properties then add the controllers. I'm not familiar enough with the process to know what this achieves, but I've seen it commented on here previously.

"The immediate physical differences between the 2 boards is that the 300 series card has a blue light in the back of the isy while the 500 does not." (Source) https://wiki.universal-devices.com/ISY_Portal_Installation_Instructions The UD Portal has long been what UD offered for remote access as well as Amazon/Google connection for 3rd party voice commands. You can learn more about it on the wiki link (above). There's also mention of it on the UD Website (look for "Cloud"). I think going to 4.9.0 would be okay. I'm not 100% sure if there is a good migration option from 4.7.3, but it might work okay. How many total devices (Insteon & Z-Wave) do you think you have? Are all your Insteon devices "easy" to access? (i.e. no devices that are in sealed off walls or very high locations that you don't feel comfortable reaching?). Do you have any/many Insteon battery devices? If the answer to total number of devices is relatively small then it might just be "easy" to setup up as a new system. If you've got a lot of programs that you can't live without then that will need to be addressed differently. The biggest issue is you're going from 4.x system to 6.x system. There were MAJOR changes in the 5.x firmware line that will still potentially impact your system/setup. Those will be around how scenes are made and controlled (too much to really go into here...go find posts about the upgrades/changes in 4.x to 5.x and possibly review scenes on the wiki). I'm not familiar with AXIS devices and doesn't appear that there's a plugin. So doubtful that you would get to add that back into the system unless you could find a developer to make a plugin for those devices (if it's even possible). "better option" is in the eye of the user. I like UD Mobile and can use it, but I have not gotten deeply entrenched with how you can set it up. Mostly because I don't use a mobile app for my home "automation". I don't need to know (monitor) when lights come on or go off and don't need to turn things on/off while I'm away (most times). For simple tasks like that I rely on Mobilinc more than I do UD Mobile because it's what I used in my ISY994 days and it just works simple enough and quick enough for a simple task of turning an Insteon device on/off.

Actually you can still use Mobilinc as long as you're using a direct connection to the eisy or through the UD Portal. I use Mobilinc Pro and it works just fine. I never did their connection method, but the app itself will connect and show anything that is showing on the ISY. The main things that DO NOT work with Mobilinc will be anything you add to the system through a plugin. You'll see them (possibly), but more than likely will not be able to control them. If you never setup Mobilinc to use the UD Portal you can follow the directions in the wiki: https://wiki.universal-devices.com/ISY_Portal_MobiLinc_Configuration. It's not required to have an active portal license/subscription to run the eisy, but it does provide you the easier (more secure) method of connecting to the device while remote. Otherwise, you have to open a port on your home router and that's a possible security vulnerability. I don't run any z-wave or zigbee devices that I need to control with an app so I'm not 100% sure if/how Mobilinc works with those on eisy. I know my Insteon devices 100% work with Mobilinc and eisy. For any plugins you end up running you'll want to get UD Mobile from UDI. That's being developed to work better with the eisy and plugins and requires UD Portal license/subscription for remote access.

@oamber a few questions to follow up - even though you seemed to have resolved from this time it could mean you've got underlying issues. How long was the power out? If it was just a brief/blink outage then it could indicate PLM issues. If it was a longer outage be sure that your eisy is updated to at least 6.0.4. There were some issues in earlier versions about not booting correctly and connecting to the PLM following a power outage. I think UD fixed that process in a recent update (there haven't been any posts about it happening lately). Were all your devices missing or only the one you showed in the screenshot? If only one device then it could be a communication issue to that device. If all devices were not showing then could be a failing PLM. Do you have any idea how old your PLM is? There should be a tag on the back (wall side) with a version and date code. If you're willing to unplug it again to check the date it might be good to know that. Although now that the system seems to be working I would just leave it alone for now. Just if it happens again make note of the version and date code on the back.

@JLevy02 be sure you’re adding that address in IoX finder. It’s not the website. Adding this address in IoX finder allows you to use the local admin credentials and should then allow you to remove customizations.