Geddy

@RCJ welcome to the forums. I’m not sure if UD Mobile can access remotely as you describe. Based on the wiki other methods are supported. https://wiki.universal-devices.com/UD_Mobile#Remote_Connections Did you have the ISY994 connected to the UD Portal before they stopped selling the add-on in 2023? If you have an active portal subscription you can use the portal connection. It’s safer than opening ports on a home router (as long as your password is secure).

@EddieRock you're probably best off getting help directly from UD on this issue. Please open a support ticket with them: https://www.universal-devices.com/my-tickets Try what @Techman points out, but don't do anything deeper than that unless instructed to by UD. It's almost like something is corrupt and they would be best to work with to troubleshoot the issue and correctly resolve if it's more involved than simply reloading the IoX Launcher process or rebooting the eisy.

@jsilver561 split your post out to the ZMatter forum since it more seems to be asking about connecting via Matter option. I've not tried this device, but I would assume since Matter support is very limited (currently) that you're probably seeing the best you can get through the IoX+Matter integration. I believe it's still just supporting bulbs and switches (I actually haven't been keeping up as I don't have any Matter devices). Meaning that I doubt the Matter support is fully developed to cover properties like color changing. Since you are able to get the device to connected through the plugin and can control more features I would suggest that's probably the best course of action at the present time (for your situation).

Not directly attached to the device, but I added a (small) USB fan (from Amazon for ~$10 at the time) to circulate air through the cabinet that houses my electronics. It just helps circulate the air in a piece of furnature not really built for electronics, but there were vent holes in it so this seems to move enough air that things don't "cook". With the ZMatter dongle on the eisy it's difficult to stand verticle without props (IMO). There were rack mounts in the box, but never attempted to add them or make something that might elevate it. I've had the eisy running in the same spot since its release and don't think (expect) heat has been an issue. The mini computers are designed to specifically pull the heat to the surface. They will feel warmer on the surface, but should be well within operating temp internally just from their design.

@CoolToys have you performed a full power cycle on the eisy? Rather than just the reboot following the update it might need a full power cycle just to "catch up" or at least trigger things correctly. I would shut it down (6 button presses or press and hold), actually pull the power cord, wait 10 seconds (random amount of time), plug it back in, and power it up (i forget if it turns on automatically or not). Your programs are executing exactly at "x" time. Do you have many other things triggered at the same time? Even though it has "worked for years" (famous phrase among many of us), it's possible that there could be a lot of communicating at the same time and something is missed. Shifting something just a few seconds might help.

@CoolToys said "at least 20 watts total" The issue is the LED aren't pulling enough power for the Insteon switches to properly dim. I too had issues with some Home Depot ecosmart brand. I found that Philips bulbs (the warm glow on dim) work really well, but they seem to be discontinued (or very difficult to find). Lately I've found the Cree also worked really well, but again no longer being made. I haven't tried Feit bulbs yet, but they were on my list to get next time I was in need. I've heard they worked well with dimmers similar to the Insteon switches. Bummer if what you bought isn't working well though. I recently purchased some 60w equivalent Philips bulbs that are used in a ceiling fan kit that dim well (down to ~10%). WOW! Looking at the HD site it does look like the Philips warm glow are available (they were packaged differently a few years ago when I made the LED swap that I don't think I recognized the packaging as "warm glow" when I was there last). PS: I'm not electrician (and have no such skills - HA!) so comments above about pulling power are what I've heard referenced previously. Above is also personal experience with limited bulbs and only (older) Insteon dimmer switches. I do not have any "NEW" models of Insteon dimmers or switches.

@haroldunger looks like you’re talking about this old topic:

@skydvrz you should contact UD directly via their site: https://www.universal-devices.com/contact-us/ While UD does sometimes monitor the forums questions like this are best asked directly by contacting them using the information found on their site. Good luck recovering from the hit! Hope there wasn't further damage to your property.

@jstjohnz what was your previous router? It's possible that the new Unifi router is blocking the traffic for the ISY994 causing the portal to not stay connected. Is the ISY994 directly connected to this router or another switch/hub? I would suggest trying a different network cable as first step to fix. Does your old router still work? I would go back to that router to see if the connection still has issues (maybe test it just for a few hours or maybe a day at most - if possible). Since you have some success then I would say the portal license is valid, but just to be sure login to the portal and confirm your license has not expired. What firmware are you running on the ISY994? Since you're using UD Mobile it's in the 5.x branch, but are you on the last update for your situation? If you don't have z-Wave or are not using it then please be sure you are running 5.3.4 (you can find that information in the "Current Release" area of the forums. The current suggested method for IP control is only through router DHCP reservation for the device. Setting up a static IP on the ISY994 can sometimes cause issues (especially when replacing routers). Please leave the ISY994 setting to auto for DHCP. Are you running any VLANs or advanced firewall rules on the new router? Do you have a "guest" or "IoT" network setup that might have time limits or on/off times? If you're able to connect to the admin locally while the device is "offline" in the portal that means there is internet traffic issue. The next time you get an alert that it is offline try to connect to admin console from a computer that is local to the ISY994. If it connects without issue your router/internet would probably be the issue to next troubleshoot.

I think a few posts back (maybe a page back) there was something from @sjenkins about connecting a device to the local hub. I don't have this so haven't been testing, but I would think with the YoLink setup is dependent on how the devices are added. @Panda88 commented that at the time additional hubs are to extend the network. If those are cloud hubs then they probably wouldn't communicate, but I don't exactly know how hubs talk to each other. I would expect if a device was added/linked with only the local hub active then another hub was placed for range it's possible it would still report. Would need to test for personal use case unless others already have and can comment. I only need one hub with the amazing range of YoLink and only having items inside the house I don't need to get to other buildings or outside areas. I do like the idea of a local hub though, but this is why the current YoLink hub is on my "IoT UPS" so it is online if the power goes out. I don't run anything critical enough to worry if there's an internet outage, but do want to keep up with the temp in fridge/freezer if the power goes out for too long.

@srjacob the hangup will be the Elk "module" as @paulbates said. Proior to when UD ended support for the ISY994 they stopped the option of buying modules for the ISY994. When support ended I believe they also said they would no longer transfer modules to other devices. You might want to go see some of the old news posts on the UD site for when the ISY994 ended support. Otherwise, for the Insteon side it's not overly complicated to mirror between two devices. Make sure they both have the same firmware. Just make a backup of the current/old ISY994 then restore it on the other/new device.Your only problem with the Insteon side is the PLM could cause a communication issue, but it might be simple (I've just never actually tried it). I know after getting the ISY and Insteon running on Polisy then eisy I ran the ISY994 for a while to help people here. I had to install the non-inseton firmware so it wouldn't always start in "safe mode" because I didn't have the PLM connected to it. Ultimately, the question is...why do you want to do this? Just to have a spare? I would rather suggest that you keep good backups of the working system. Then if/when something happens and you have to change to the other ISY994 it's an easier process of just restoring the most recent backup. Knowing that the ISY994 is no longer supported by UD and many here have updated to the Polisy and eisy the user support is also waining for those devices. There are a few that still use them that are very active here, but many (UD included) will probably suggest your time, effort, and money is better put toward updating to a new eisy.

Probbaly some of the plugin developers can diagnose an issue. However, the developer of the "current" production plugin for Govee is no longer supporting it. The plugin hasn't been updated in a while (since 2021). That's why I wonder if the Pro is a new line and it's not supported with the old programming. I know it was converted from PG2 to PG3 by UD at the time PG3 was introduced, but I think that's all that has been done to this plugin in several years. There appears to be a Govee plugin in the non-production store, but not sure if it has any better/different function since it hasn't been updated in a few months. I have not tried that one. Done. Thanks for suggesting.

It's quite possible the "old" plugin doesn't support this product. I know it's kind of old, but doubt Govee has really changed all that much with their API over the years. I know I have an older Govee "lamp" that is wifi/bluetooth that I was able to connect to the plugin. @dbuss what product are you using that works with this plugin? I wonder if anybody has experience with this same "Pro" model.

This is why I run my eisy on a battery backup (UPS). Specifically I have this one: https://www.amazon.com/dp/B01FWAZEIU (just the eisy...NOT the PLM!) That battery supply only runs the eisy, cable modem, primary wifi router, and yolink hub. I figure with that little power pull on the battery it should last a while before it dies and if I'm home/awake when the power goes out I can power things down. But for storms when the power flickers I don't want the eisy to reboot. Now, to this program running...very strange, and you said it's not set to run at startup. But as @hart2hart points out do you have the entire system set to catch up when turned on? (that's on the configuration tab) Your program is odd to begin with. It's set to run at exactly two time occurrences and if onvacation = 0. The issue is with the "wait" in the THEN. When it's not EXACTLY that time the program would be false. When a program is in wait and the condition of the program changes it will evaluate again. In that regard this program should turn the fan on, but never turn off. Usually people would suggest you run this as 2 programs so the wait doesn't mess you up. 1st program would trigger at those times and if onvacation = 0. your THEN would trigger the 2nd program (that should always be disabled and NOT have an IF statement). The 2nd program would then turn on the blower, set the wait, and then turn off the blower. In your log it looks like just a status update of the BSMT Blower being off. Then apparently another power outage happened and it was then status on. Didn't see anything that specifically turned it on. Is it possible you have another program controlling BSMT Blower? You can use "Find/Replace" on the programs tab and look for text or a node to see what programs reference BSMT Blower. (Right click any program and it should show up in the menu). Catch up in the wiki: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Program_Summary_Tab Find/Replace in the wiki: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Tree_View

@smorgasbord glad you got it sorted out. It is an odd error though and one that has shown up before, but not commented on recently. If it happens again (soon) try running the upgrade packages again and reboot then power cycle. Are you using UD Mobile? Is it up to date? If it happens again start a ticket before doing too much self troubleshooting or “repair” (other than update process or power cycles). As it would be beneficial to UD to see what is happening so if it’s a bug they can repair for the rest of us.

Cool….yeah, at least you’re already on 5.9 so you should be good with a standard backup before pressing the “upgrade packages” button. I would probably still make a text copy of programs (it’s just something I do now and then to have in case something fouls up). Allow a good bit of time to pass and watch the admin console screen for when a reboot is needed. Just also wanted to ask if you’ve reserved an IP address in your router. This way the eisy will come back to the same internal IP. When done with the reboot I would perform another power cycle to fully reset everything. Make sure you allow the device to fully restart from the first reboot. If you have access to the eisy check the wiki for the button presses for a shutdown or just press and hold the power button until it changes color. (I think the on is blue and off is red) Clear your Java cache (check all 3 boxes), and possibly download a new start.jnlp file (not required, but good practice). Run start.jnlp to return the shortcut to your desktop. I have run an update in a month or so and think my system is at 5.9.1_19. Check the sysconfig link again to confirm update. Good luck!

Since you haven't done anything in over a year your best shot is to check the wiki for the update process. Although, there was an update to 5.9 that required an updated operating system in the eisy. I'm not sure if that's been overcome and installed at the same time. It might be best to open a support ticket if your device is out of date for updates to be sure that it will update "easily". You can open a support ticket here: https://www.universal-devices.com/my-tickets What I would suggest first is try to go to this page in your browser: https://eisy.local:8443/WEB/sysconfig.txt See what ISY version you're running as well FreeBSD Maybe looking for FreeBSD: FreeBSD eisy 14.1-RELEASE-p6 (should be the top line of the output of the sysconfig.txt page) A little ways down you should see: ************ IoX ************ isy-5.#.# Name : isy Version : 5.#.#_## Installed on : Date & Time You can look at the past (or current) release notes in the release area of the forums to see when the OS updated to FreeBSD 14. If you don't have that then you'll need help getting that installed before you can update to 5.9.x. Be sure you read the release for 5.9.1. Pay special attention to item #3: Lastly, be sure you backup your IoX (if you have z-wave back that up first then back up IoX). Then also run a backup of PG3x (just to be safe). I would also suggest you make a text copy of all your programs. Right click the root program folder and select "COPY folder to Clipboard". Then paste that in a text editor (not a word processor!). That way if your system does not come back correctly and you have to rebuild or start over and you have problems with your programs you have a "hard copy" to reference and not having to go from memory of what items were in what programs. Good luck if you proceed. It is a good idea to keep the system updated as releases are announced as they incrementally improve the system and take care of bugs along the way.

@tracknut, even though you probably didn't initiate an update it's possible that by pulling power it caused a corrupt process that isn't allowing the eisy to fully boot and initialize the ISY side. I would suggest you open a support ticket with UD to have them help troubleshoot with steps they know and know what results they're looking for. This has happened a few other times with various issues causing it and support has been able to get them running quickly. Hopefully your issue is easy to resolve as well. Going into the weekend though you might have limited help until Monday. But rest assured UD will be the best bet of how to resolve. https://www.universal-devices.com/my-tickets

@MJsan your last question about the PLM going bad...it very well could be. You have what appears to be one from October 2016. If you've been using it since then it's quite possible it could be failing. Again, let's wait and see what UD says. It could be (or have been) a noise issue suddenly started. Doubtful, but with remotes and then keypads not working it very well could be. I'm just worried that the restore PLM might have corrupted something.

Honestly, the best support you'll get is through the support ticket. At this point you've already tried a lot of troubleshooting and steps that could ultimately change other issues in the system. I think it's best to wait for support to reply to the ticket and troubleshoot with them in a methodical way. They have tips/tricks/solutions that most of us on the forums wouldn't know about and might point you in the wrong direction. Especially with some of the potential errors you're having with files not being available it's not something I would want to suggest resolving and would leave it up to the master(s) through UD Support. But please...do post back with how they go about getting things sorted out. It could just help us and others should this become an issue for others. Good luck!

Did you type in the Insteon address? More than likely one of the "B"s is actually an 8 (eight). I'm not sure if the battery leak sensors can link without typing in the address, but try an alternate putting ".8F" then try ".89.BF" Edit: I see @larryllix commented on another post that 8 could also be 0 (zero).

@zGuy981 be sure the router is reserving the IP for the Hue bridge. More than likely it wasn't and it's changed IP. Even with your bridge addition it might have changed again. I would check the IP address of the hue hub. Make sure it's being reserved at the router side. Then power cycle everything. power down/unplug eisy unplug hue hub plug in hue hub wait for it to be online/stabilize plug in eisy wait for it to come up and stabilize It looks like you're using the proper "bridge" and ["##.##.##.##"] setting. Not sure why it wouldn't be catching it. You might need to restart the plugin and put the button on the hue hub (within a few seconds) to make the connection again.

Since you're the only one here reporting such an issue I highly doubt it's a "IoX issue". It seems more system related to your situation. Typically posts on the forums are more of the issues being faced as people that don't have issues typically have no reason to stop in and say, "my system runs perfect I'm so happy". But I understand that having an issue seems to be easy to point the finger at the system. This doesn't help at all. Imagine reading this months from now and the version is a completely different number than now and somebody thinking whatever ends up resolving your issue would work for them since they'd be on the "latest firmware". Thanks for including a screenshot though showing you're on 5.9.1. For IoX Launcher "LAN" and "Cloud" mean different things. From the wiki: It doesn't mean that you're accessing Admin Console "through" the cloud. It's (quickly) downloading the UI to work with your firmware. It was designed that way when the ISY994 was going from 4.x to 5.x firmware so people wouldn't need to clear the java cache with each update in 5.x line. The "Cloud" option always keeps the UI and Firmware in match. I would suggest that you express this in the tickets you work. So many people that do use the support tickets to resolve issues sing the praise of UD support for taking care of issues quickly and thoroughly. Maybe a time difference from when you're able to work on the system and when they're working means a delay, and the volume of other items being dealt with can delay support replies at time. If you rebooted the eisy and the computer connected without the issue, but then you suddenly had the issue then more likely than not the issue is locally caused by either the OS or Java versions you're running. What computer OS are you using? Many Win10/Win11 will run just fine. Sometimes macOS users have issues because of security macOS involves running Java .jnlp apps. If you're on Windows 10 or 11 will you look up one thing? In the Java settings see if you've got a memory setting fixed in there. Open the Windows menu and type "Configure Java" (or just Java and select "configure java"). Look on the Java tab then "view" and see if there's something in the "Runtime Parameter" cell. This is referenced in the wiki for issues with slow/hanging Admin Console. If nothing is there add "-Xmx1024m" (without the quotes) - as long as your system has fair amount of ram you can use 1024 (or more). The wiki suggests 512, but current day systems usually have a lot more ram and can handle blocking 1gb for this application use. Sometimes I set mine like this: (s = start (min) / x = max) This is just an option if you have a large system with lots of nodes, programs, scenes that take a long time to run though. Lastly, if you're able to exit the cycle again open your programs tab and look at the summary tab and make sure you don't have programs stuck in a loop (programs that ran recently or continue to show last run time of the current time). Click the "last run time" column to sort it by the last run time. It's possible something from your migration has caused a loop that is eating up a lot of memory and not allowing IoX to settle when admin console loads.

@Chevelle Sadly this does seem to be the case. I just tried changing the color (RGB or White temp) in the Hue app and each change made the light come on. I also tried setting a color in UD Mobile and admin console and each color change made the light turn on. Remember in admin console if you're controlling from the device window you need to click the button to the left to actually set/write it to the bulb. Once I clicked that button the bulb came on (to the color I set). I think like @lilyoyo1 suggests just make it a program that when that bulb is turned on (physically?) that the color is changed and hope it's quick enough not to be noticed or shockingly observed. In my test it is daylight so I didn't notice the quick color/temp change, but also was looking at the app rather than the bulb. Also when turning on is probably a better time to change the color rather than just before it's turning off (since it's your "bedtime" routine). It might not be as noticeable in the room you're in at the time the color changes if done at "on" rather than before going off. It's also possible that through an official API (and if the plugin was updated to use it) that it might be possible in the IoX world, but the plugin was created before there was an official API and hasn't been updated to use such.

@srjacob since this appears to be an IoX issue and you've got performed fairly recent migration to the eisy I would suggest you open a ticket with UD to get help on this issue. Open a support ticket here: https://www.universal-devices.com/my-tickets Be sure that you are not running any 3rd party anti-virus or firewall programs on your computer. Also, make sure the eisy has a good network connection (are you wired or using wifi?) and there are no hardware firewalls impacting the device. Please let us know what firmware version (actual number) and UI version you are using. (Help -> About in Admin Console (if it ever loads) or just the firmware showing on your IoX Finder window before you log in. Are you using "local" or "cloud" connection to open admin console (AC)? Try the other option of what you typically use. Does it happen when using the other method? Please post an update as to what support does to resolve this issue. It might help others should they face a similar issue.