Geddy

Are you leaving admin console open 24/7? Don't! It's not meant to be open all the time. Open only when you need to adjust something then close it. The Red "!" means communication is lost to the device. Could indicate PLM issues. Be sure if you're trying to add it back that you have the correct address or use the auto linking process. Sometimes B/8 D/0 and S/5 can look alike. Try operating the device in UD Mobile or even in Admin Console (and/or even in eisy_UI). More than likely you're having some noise issues if this just randomly started happening if the PLM is new.

no. I have programs that set on levels that work just fine. Are you doing this in a program? If so, please post the program (Right click on the program and select the last menu option of "COPY to Clipboard" then paste the text in your reply - Be sure you're using the "COPY to clipboard" option- Not "export"!). What kind of device are you setting this to? Is it battery or wired device?

No. This is not correct. "Control" is only if a device is PHYSICALLY operated. If a program might say at 2:30pm turn off a device and another program says if the device is "controlled"/switched "OFF" then do another step. If the program turns off that device the other step is not performed. Just tested this with devices in my office. If I manually turned off the device then the next program would run. What you're looking for there is to either put another line in the "THEN" to call on the "then" of the 2nd program or change the second program to a "Status" so if the status of "device x" changes to "OFF" then the second program would run. The second program would have two "IF" statements of "if switched (controlled) off" or "if status IS off". As @hart2hart points out the device can be in the state already and physically controlled to that state it will trigger the program. If the lights are off and you press the switch to off again the program would trigger. Lastly, for your multiple posts about questions it will help if you can give a program you're working on by including in your post rather than lengthy descriptions. Try a program. If it doesn't work as you expect then posting the program here gives us an idea of what you're attempting and might lead to suggestions of what to alter. Just be sure you post the program as text and NOT a screenshot! Text programs are many times easier to alter/edit to help you along the path. Right click on the program and select the last menu option of "COPY to Clipboard" then paste as text in your thread.

@SMonk this could become an issue with a looping program. I'd suggest something like @dbwarner5 has or even a status check. "device" Status is not "Off" Then you could also have a: "device" Status is not "On" The loop comes into play for your other program. What are you trying to do when this device status changes? You might be creating more problems than it's worth. Remember that "Control" = "Switched" = physical operation of the device (i.e. not a program or controller operating the device). If you're going for something for only when the device is physically adjusted then you would need to use the control option and you would potentially need to account for each control option. Otherwise, you would be able to use status and could use the "ON" or "Off" status and then the "Not" "on"/"off" or even < > options. Just depends on what you're ultimately trying to accomplish with the other side of this program. What have you attempted so far (that might not be working)? Please share the programs - RIGHT CLICK on the program and select "COPY to Clipboard" (last menu option - be sure you select "COPY to clipboard" - NOT export!) then paste as text into your reply.

@Guy Lavoie odd. Again, didn't try it. I only used it for a very limited time in a program. Never tried it on touch/operation. Glad it seems to have gone away with a reset and adding new. Never restore that switch!

@Guy Lavoie there used to be a beep function. It wasn't very loud and I'm not sure how many used it. Did they take it away? No, I just looked in my eisy (6.0.5) and it's still there. Like the "Backlight" and "Ramp Rate" setting you have to press the label next to the setting to write it to the device. I didn't test it (don't want to goof up my working device(s). It's an annoying little beep/chirp if I recall. I used it for a while on one program and my kid made fun of how wimpy it sounded that you had to be right next to it if there was any other sound in the room to hear it. So I turned it off.

Clear the Java Cache (check all 3 boxes!) Download new start.jnlp from UD site (https://www.universal-devices.com/ - click on "My ISY") Run start.jnlp Remember to use the local user/pass you'll probably need to add the local connection in IoX Finder window. Add "https://eisy.local:8433/desc" (without the quotes). It will prompt you for the "device" user/pass. Otherwise, it will ask for portal user/pass. Personal preference. I'd think not since you're using the eisy already. It's more or less that the eisy r2 was a different configuration that UD went with for availability. They've even come out with the "eisy | lite" that is a cheaper unit due to the rising costs of memory and storage. Since the standard eisy sits between the two I'd think it would be safe to say it should carry the workload most need and will be updated by UD as long as "eisy" is their primary line of products.

Have you restarted the plugin then pushed the button on the hue hub within a little while (few seconds) of the plugin starting? It's as though it's not making that connection. You might want to put the log status for the plugin into "debug" mode and restart and let it settle. Then check the log for lines around when you restart the plugin to make sure it's connecting to the hue hub. Otherwise, there might be errors suggesting it cannot find it at a certain IP address. Make sure you do all this with the java admin console CLOSED. I'm not 100% sure, but if you delete and reinstall and it does connect and you keep admin console closed then it could bring back the bulbs in the same nodes and might not dissrupt your programs. Although, I would strongly suggest you make a backup of your programs: in the Java Admin Console right click on the "My Programs" folder (or whatever you might have named the "ROOT" folder in the program detail tab) select "COPY folder to Clipboard" (be sure you use "COPY" - should be last item in the menu) PASTE that text into a text editor (not a word processing app - for Windows I suggest Notepad) Save that text file - you now have a text represnentation of ALL your programs. You'll be able to search for names and repair the programs easier if they are broken from removing and reinstalling the plugin. I've not had experiance having to remove and reinstall the plugin (at least not recently). It coudl work. Mostly the issue is the plugin is not properly reconnecting with the hub. You probably need the IP address and then perform the pairing again for it to properly connect. It's odd that you said the node listing went away when you tried this before and came back when you removed it. You might be best off trying a support ticket with UD at this time. I know @xKing is shown as the developer for this plugin so maybe there are some other tricks to try, but I'd say we've pretty much exhausted the typical fixes that we've known from helping others here and experienced ourselves. I'm sure in the end it will be something simple and probably related to your network setup.

Sounds like @Guy Lavoie might have it right. If you see the nodes in the dashboard side then restarting admin console should pull them into that view. Honestly, I don't really use/rely on the Hue plugin or IoX to control the hue other than a timer to turn them on off so not sure how well it works or doesn't work otherwise. What version Hue Hub do you have? I honestly don't know all the versions they have, but know if it's the pro or a more recent hub that might not work with the older plugin and might need to get the newer one. I just run 0.1.11 since that worked when I first setup the eisy and my hue hub. I haven't tried with the newer version.

@PeterP you'll probably need to tell the plugin where to find the Hue hub. In the configuration area add a custom parameter: bridges Then the IP should be in this format: ["10.0.1.1","10.0.2.1"] Be sure you include the brackets [ ] and the quotes around the IP addresses of the bridges! From the plugin setup information: Since the plugin isn't looking for the hub to move you've got to tell it where to look and perhaps re-link it. To re-link just restart the plugin then press the top button on the Hue Hub within a few moments of pressing restart (if you have the old style hue hub it should only one button - I think. I don't have new hubs and haven't looked at them to see if they're different).

This is correct and has been this way since day one for Polisy and eisy devices. UD made the change post 5.x firmware on ISY994 to not allow to set a static IP address on the device due to the number of issues it created and support tickets that were created when people had static IPs set and replaced network equipment. What do you see if you're logged into eisy_ui and click the three bars on the top left? Go to settings then what do you see? Should see similar to this: If not, then I might agree about an update issue and you should have UD focus on that issue. Strange that @someguy is having IPv6 issues. Hopefully support is able to get those sorted out and make sure others don't suddenly have the same issue. I know UD made a comment when eisy_ui was in the early days that it did take over portal authorizations so you cannot confirm those in admin console anymore. Did either of you have the device only connected via wifi before the update? I wonder if you connected with a wire if that would resolve any issues.

@johnstonf for the issue about time to respond (even though 10 seconds isn't that long) you would want to look to see if you have anything set in the memory usage for the java process. Take a look here: https://wiki.universal-devices.com/Main_Page#Admin_Console_is_very_slow_or_hangs (note this was written a long time ago so the number can be increased depending on how much system memory you have. Java is not a friendly memory user and usually uses just enough it thinks to run. If you set a minimum level it could help your response time, but not guaranteed. For the "out of memory" usually this would indicate two possible issues. 1) Firmware and UI mismatch. Go to Help -> About and make sure Firmware and UI match versions. (Since you didn't mention what version are you running? With z-wave also need to know what version z-wave controller you have 2) Have you deleted devices recently or are some devices not connected/communicating with the ISY994? The program will have a broken line and just needs to have the device reselected then SAVE the program(s). You can right click on one of the lines that says "Out of Memory" and then "Edit" to go directly to that program. Check that all devices show up in the program. You might have some "//" comment lines if the device is missing. If you're not able to select the device then you have bigger issues and need to re-add the device. Then you can come back and fix the program. Since you haven't been updating the eisy once you have the errors fixed in the ISY994 you should (must) open a support ticket with UD (https://www.universal-devices.com/my-tickets) to get help bringing the system up to current status. There have been a lot of updates and several have bricked older devices that have not been updated along the way. Let's focus on fixing the ISY994 issues here. Then you can work with UD to bring the eisy up to date then work on the migration.

@oamber you'll need to find the .sate files for UD. Depending on your computer OS. Referenced in the wiki. Look for these and delete them all (make sure admin console and finder are closed before you delete these files). https://wiki.universal-devices.com/Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored (In macOS it looks like they might be in /var/folders (try typing open $TMPDIR in Terminal) - I don't know macOS, but Google told me that) Then if you're on Windows to right click on IoX Launcher shortcut and make sure the "Run:" option is "Normal Window"

The tab is a little stronger than you think. I've only had to perform an air gap reset on a few devices and surprised at how it really takes a little effort to pull the thing out. Of course as @hart2hart says a tiny screw driver really helps. What bugs me is having to hold it in until the beeping stops. That's the hard part. On the IoX side of things in theory when you link a device to IoX it has the option to "remove existing links". While that's not a true factory reset of the device it should overwrite any device links, but many have commented it can still leave ghost links so the air gap method is the best way to reset it. Too far down the development road to expect Insteon to make a new/different way to reset a switch. But a great suggestion to maybe take to their tech support!

This is a longstanding "bug" (UI difference) that started in IoX 5.x many years ago. After you set the percent you need to hit the button NEXT to that value. This goes for most the options like on level, ramp rate, and backlight. Write changes is not doing what you think it should (I think it's mostly for battery devices). I don't ever click "write changes". There's also a UI issue that sometimes might not always show what the level you have set will be. That usually is for the backlight setting though (if I recall correctly). Also, please update your system. It will help keep things current and fix any unexpected issues otherwise. See the information in the current release area: https://forum.universal-devices.com/topic/46475-updated-software-available/

@JohnC I've given up trying to make this work with Apple. It was hopeful and I think I got it to work for a bit, but the plugin keeps expiring and it's not something I use enough to try to make it work right. Out of 40+ Insteon nodes I have maybe 10 worked as expected and those were just on/off switches. I couldn't get fans, dual or dimmer outlets to work. Having to set this up multiple times and knowing that so many didn't work I'd end up having to skip programming them and it was too time consuming to try to get things setup or not setup to mess with it. So the last time the plugin quit working (maybe a month ago) I just haven't done anything about trying to get it reset. Thankfully my Alexa setup still works as expected so I really don't need the Apple connection. Though it was nice to have the watch turn stuff on/off rather than having to "yell" at Alexa.

I would suggest a program to set the on level for the different times of day. From "x" time to "y" time be "w%" on value. I think I had something like this before, but not with a motion sensor. Just having lights to turn on less bright at times in the middle of the night so not to blind or wake people. Night-MWC - If From 11:30:00PM To Sunrise + 1 hour (next day) Then Set 'MWC' On Level 30% Else Set 'MWC' On Level 100% This is only for overnight and it will be 100% the rest of the time. You would want a different program for each on % you wanted to use during the day.

https://wiki.universal-devices.com/UD_Mobile#Show_Favorites_at_launch This used to be available. I'm not sure if Android is different now or not. I guess Apple doesn't work like it once did, but I just checked and the part that is crossed out saying deprecated did work (iOS 26.4.2 / UD Mobile 1.4.23) and would launch me to favorites. I haven't tried the shortcut method mentioned in the wiki. I 100% wish this was possible. And to have them setup their own favorite screen so things would just be a big remote and just have tiles to press to turn things on/off.

I would suggest opening a ticket with UD - https://www.universal-devices.com/my-tickets Since OP posted in ISY994 area I thought it more likely to be a license issue. I've tried Alexa to turn things on/off and it works fine. Might be localized, but nothing on Amazon's AWS status page to indicate issues in the US. Maybe UD can dig into it from their side to see if they have issues with AWS or see something device specific. @LVaden01 I wouldn't mention Mobilinc in the ticket since it is not "supported" with the eisy. But I use it and it still connected and could sync and control devices while remote. Agreed. This is odd if both are indeed not working. I'd open a ticket as well.

@lgilsenberg thanks. Yeah, just happened to look at that up. Apparently went to a paid part of Echo+Ring "Alexa Emergency Assist". Just what I'd want is to PAY to have Amazon listening for issues inside my house.

@SHM I noticed that sync got "slower" a while back, but it's never failed for me. I've probably got 40-45 nodes and 20 programs. iOS 26.4.2 UD Mobile 1.4.23 Sync took about 42 seconds running on the same network. Sync took about 1 minute 10 seconds on cell network at the same location. (I'll admit I live in a data challenged area) It seemed to stick on Nodeserver (running 8) and Matter (no devices). I don't see/know of any logs for the sync so I'd suggest opening a support ticket with UD (https://www.universal-devices.com/my-tickets) if it happens more often than not that you get errors.

Oh my goodness. Thanks for catching this and sharing. Yet another thing that Echo developers seem to think people would want/need to automatically have in their "smart" home. Sometimes it baffles me what the mega corporations change without any thought to the impact. Or if they had given thought to the impact they just don't care and do it anyway. Is there not a way to disable guard?

@Yoda since you say you can log into the portal you'll want to check that your license is still active. Log into the portal then under "Tools" check "Information" then "USY Portal Access License". Make sure it is current. If not there should be a button to renew. After you confirm the license is active make sure you're using the proper Alexa Skill (https://wiki.universal-devices.com/ISY_Portal_Amazon_Echo_Integration_V3). You might need to re-link the skill in the Alexa app. For a support are you using: https://www.universal-devices.com/my-tickets/ ? It requires Portal Login. Be sure you turn off any VPN or popup blockers for the browser. Use a different browser (perhaps a different browser on a different device - like phone or tablet). Try in private/incognito mode.

@SHM split this post out from a 3 month old thread that seemed to have been resolved. Plus, the old thread was for status updates. Your post seems to indicate sync issues (different issue than the thread you posted in). Are you local or remote to the system(s) when trying to sync? How large are the systems you are syncing with? (roughly how many nodes, programs, scenes?) What phone OS are you running? (is it updated?)

@aLf I don’t think MyQ works with eisy any more. There used to be a plugin, but MyQ closed their system to 3rd party API access. Many have moved to other options. You might find some suggestions in the “old” MyQ area: https://forum.universal-devices.com/forum/328-myq/ PS: edited subject to be more with what you posted so you might get more help.