Geddy

I know just enough to get into trouble sometimes. I don't really know the answer to that questions, but suspect others will. Offhand I would say that NO, any friendly name is not the same as how the device is broadcasting itself on your network. I don't force computers to use external DNS lookup, but leave them default to the router for DNS lookup for local access. Is that what you mean by all clients use 8.8.8.8 for DNS lookup? The router should be handling that (IMO). The eisy appears to be broadcasting as eisy.local. When IoX Launcher runs it opens a IoX Finder window. It should find the eisy and display as: Sometimes mine will jus find it by underlying IP, but most times I get it populating this way. If you window ends up with "Not Found" then hit "Refresh" and what happens? Now, since you've added it to your host file it might find it because of that, and since your on macOS other things can come into play. But on my several Win10 devices eisy comes up just fine 99-100% of the time. I suspect if you allowed the devices to rely on the router to handle DNS it would work more often for you. But, again, I'm not a network guru. Ultimately, you've got it working. For you. I don't think it would be a widely used method of resolution.

@hchain While @Techman does have a point about the "All On" issue I thought that was a thing of the past. There haven't been many (maybe ANY) issues/reports of a real "All On" (bug) reported here. Especially with the eisy. I think Insteon fixed the issue either in a PLM firmware update or device update somewhere a long time ago. Unless your devices are really old I don't think you're having a true "All On" bug issue. You should check for random programs running the next time this happens. And as info the PLM should NOT be on a UPS. Many surge protectors and UPS may interfere with the Insteon line signal and block it from correctly getting to the devices, or the return to the PLM. What does "not locked" mean? Do you have other times where you have to reboot something to make it work? If so, that's not normal and you need to troubleshoot that potential issue further. (Perhaps in a support ticket if you're having to reboot the device often.)

@ricke If you want to disable the folder then set up a folder condition that is ALWAYS false. When a folder is FALSE any programs in that folder do not trigger (consider as though they do not exist). You would not be able to run the "THEN" or "ELSE" of any program in a False folder (either by calling on them from another program or right clicking on the program and running it). Folder Conditions are tricky and can cause unintended issues. So use wisely. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Scope,_Precedence_and_Execution_Order#Folder_Conditions

Interesting fix. Glad it works. Since you're on macOS there's been some that get it to work right away and others that need a different approach. The biggest issue I've seen (from a non-macOS side) is that many home routers have issues with the local naming and many have to use the IP address to connect. It's very hit and miss though. The best thing is to set an IP reservation in the router so the eisy is always at the same IP and you either remember it or have it in a saved file that can be easily loaded.

True...those that use the system regularly don't seem to have problems. Only a small few seem to have issues; those are the vocal ones about it.

If you upgraded from 4.x to 5.3.4 the upgrade probably set all programs to enabled again. It was a long time ago and lots of tips around that update phase made notes of that happening. Glad the summary helped sort it out. Many have taken to putting disabled programs in a folder or having a character in the name to signify if it’s disabled. Doubt it would happen again, but a step toward watching out for that happening in any future migration stages.

@TRI0N yeah, don't think it was actually fixed in 5.5.9 as some have posted it still came up following the update. Sit tight. Don't worry about updates until there are release posts.

@TRI0N what pop up are you talking about? There is/was an alert in Admin Console that updates are available. That's been a known bug and can be ignored. I thought it was fixed in 5.5.9 as I didn't have the issue after rebooting, but guess it's still an issue. I know it's been reported and is said to be fixed in an upcoming release.

This is your current issue. The PLM must plug into a USB port. The PLM is not a network device. It might have the Network type cable connected to it, but it is a serial setup. (and @tlightne answered while I was typing) You need this kit from UDI: https://www.universal-devices.com/product/serial-plm-kit/

Quickest place to find current releases is in the "Current Release Announcement" area of the forums. While not a clean list like you've got above it is only the "current" versions for UDI Releases. The good thing about that area of the forums now is it is truly only an "Announcement" type post. Not 100 replies of help. Those are the "Support Thread" for each release.

It seems that your Polisy is out of date (i.e. you haven't been updating it along the way). Since you do not have IoP running the preferred/suggested method of the "Upgrade Packages" in admin console is not an option. Your best bet would be to open a support ticket and get the proper steps to bring the Polisy up to current release for everything related to the Polisy. https://www.universal-devices.com/my-tickets/ Then, as @Ross suggests if you're using Z-wave and only have a 300 series controller then you would not be able to perform a migration from ISY to Polisy. Those steps require ISY994 on 5.3.4. I don't think 300 series Z-wave will migrate to ZMatter. Do you even use the Z-Wave portion of your ISY994? If not then you could remove the board, upgrade to 5.3.4 then the migration steps would apply. Directions to install the Z-wave board are in the wiki. Just follow in reverse to remove the board. Support can assist with that information for the time being as well. Please review the Polisy User Guide on the UD wiki for assistance with the migration - https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide

I doubt it will help your linking issue, but you should have upgraded to 5.3.4 when it came out in 2021. Being on an older build is not helpful and very few would probably remember any tips/tricks for that version. Read the update steps to get up to 5.3.4 found in the release post. Once updated clear java cache (be sure to select/check all three boxes in the process) then download a new start.jnlp file from UDI's site. Run that to put the IoX Launcher icon back on your desktop. Some have said there were issues with Win11 and Java, but the process should work just like it always has. I don't run Win11 yet so can't say first hand if you need to watch out for anything. Before logging into admin console for the first time if your system has a lot of available memory then set the min/max Java setting as mentioned in the release post to at least 1024 for both. (-Xms indicates the minimum and -Xmx the maximum) Good luck. Looks as though most your problems went away after a full power cycle of the ISY994.

@TRI0N moved your answer into this thread. Figured this was probably the most current asking about the length. This question has been asked/answered before.

"Halt & Catch Fire"! Great show on AMC for a while. That's the thing though... @Greg P. said he just used the (-h) shutdown command rather than going down to the basement to pull the power. So if -h doesn't reboot it then he (or somebody) would have to go turn the device back on....right? Best yet...."Alexa, Reboot eisy" routine upcoming! Glad @Greg P. has it sorted out though. I was just uncertain about the command difference. I've seen the -r mentioned here so many times that the -h was "new to me". Thanks for the lesson!

@oh2bnMaine how are you accessing the admin console? Are you using IoX Launcher icon from the desktop? (used to be called ISY Launcher) The screen shot appears to be from Admin Console, but I've seen other people mention this error and are accessing it somehow through the old dashboard method. It's possible you're accessing it oddly and having network issues. What OS computer are you using to access Admin Console? Make sure you're using the ISY/IoX Launcher method mention in the Current Release area of the forums and suggested in the Wiki.

@roberthleeii excellent to hear you're getting support from @Michel Kohanim. Having gone through all the above it sounds like you might have had an older Polisy system and it was stuck in the an update loop that was impacting systems many months ago. Hopefully Michel has you all patched and caught up to speed now. If you still need help let us know. Also, make note of what you had to do to get it resolved and post here to possibly help others that might stumble into this issue. Most importantly is if you remember what IoX version you were running before you hit the "Upgrade Packages" button. My guess would be something in the early 5.5.x range. I think there was an issue that didn't complete the auto upgrade process around 5.5.3 or 5.5.4.

Thanks. Not a *nix user/fan. I'd think you would always want to reboot the device. Otherwise how do you get it to come back from a "shutdown"? Maybe -h also allows it to come back on? @Greg P. some have gone outside the ISY world and use a wifi enabled outlet to be able to perform a "remote" power cycle for the device. It's an option...maybe not the cleanest reset option, but also saves you a trip to the basement.

Are they turning on/off at the same time every day or randomly? If they're at the same time then just before you think they're to turn on open Admin Console and open event viewer and set to level 3. That will show traffic that happens during that time. Prior to that you can review the "Summary" tab of the programs tab and see if any programs have triggered around the time those lights change. You can sort the summary tab based on "Last Run Time" and see what might have run about the time these lights randomly turned on. If no program triggered then it's a scene triggering the lights. Next thing is on the lights in admin console see if they are part of any random scenes. You say they're in scenes that are getting turned on/off with a program. Is there another controller of that scene that is causing these lights to come on? Click on the device on admin console and on the right it should say "Membership". See if it is responder to any different scenes. If it is then go to that scene, right click on the device and select "remove from scene". Lastly, the best method to resolve this is to factory reset the devices and then set them up again. If they're easy to reach then it should be a simple task. It's possible the lights got manually linked somehow and the ISY994 doesn't know about the manual links. (If none of the above troubleshooting steps help) Some devices have different reset options so best to google search for a user manual for the type of device you're resetting to get the proper method. FYI I just Googled for 2477S Dual Band SwitchLinc and found it :

@Greg P. There's also a "Reboot" button/option in Admin Console -> Configuration tab While it's almost fool proof it doesn't always actually work, but should get you there in a pinch. However, seems like you connect via SSH more often than admin console so the shutdown command may be acceptable. I've seen UDI suggest using: sudo shutdown -r now Rather than your "-h" command. Not sure the difference.

@johnnyt perhaps that's best addressed by contacting UDI directly rather than random forum post. https://www.universal-devices.com/contact-us/ sales@universal-devices.com I think this topic has wondered fairly far off topic. OP hasn't returned since Thursday to update status. @someguy your method for updating can be found in this post: If you still have issues after updating to 5.5.9 please submit a support ticket for review and assistance. Many bugs have been fixed in recent updates and it's easier to support on current versions.

@bpwwer I agree with @MrBill about not forcing/pushing updates. His thoughts about possible updates being pushed while away are huge. And we've seen a lot of users on here that have systems in two houses and one might be their seasonal home so long distances between properties. While I see that the desire is for PG3x to be accessible remotely, much like IoX, that's a plus, but sometimes when traveling the last thing I'd want to do is be stuck on questionable wifi in a hotel (or somewhere else) and trying to troubleshoot/fix/band-aid a system back home. This makes perfect sense! Usually that's what the forums replies have been if somebody came in and was running an "outdated" system. Especially since eisy and PG3x release. But also during the ISY994 v5.x transition. This brings me back to a comment on the forums a few months ago about perhaps UDI has a new page/area on their website showing what the "Current Supported" versions are. Yes, it is another place to keep up with something, but would be a simple place for those that are more active on the forums to point others to for an "official" listing of what versions are tested and supported "at the moment". If users aren't willing/able to update to the latest versions then the forums remain the place to get the user-to-user help. But from the official support it should be limited to only the most recent builds. As you say...new builds should be fixing the bugs that many might experience on older machines. However, the big "BUT" to all this...there has long been those that just setup the ISY994 and never touched it again. I think what IoX (and Polyglot) has evolved the system into can no longer be considered a "set it and forget it" type of system. There are just too many moving parts if you have any node servers integrated into your system. So the issue becomes how involved will users be in maintaining their systems? That's where it gets dicey and could leave the door open to having options of how/when to update/upgrade. Good luck! No "easy" way to make everybody happy, but at least the question is being asked. So thank you for that!

As @tmorse305 suggests a routine would be the way to make a simple phrase trigger an action. Be careful using just “good night” though. At some point in the past Amazon thought it would help by having Echo reply to a “Good Night” with some smart-ass quip. So I changed my “good night” trigger to, “Alexa, tell Amazon you’re programmers are f*ing tools”. The first time I wrote that out for a house guest staying the night they thought I was joking…until I uttered the phrase and everything turned off - in order. Now, I will also caution this…perhaps a program would be better suited for this process as you can control what order lights go out. Mine start at one side of the house and move to the other (as if I’m heading to bed). We don’t have a big house, but being able to time the lights from the kitchen to the master closet really helps keep enough light up during the walk to bed. The program can be disabled and not have an “IF” statement so it’s only triggered by Alexa/voice or a routine (or other methods). “Alexa, turn “program X” on”, runs the “THEN”, and “Alexa, turn “program X” off”, runs the “ELSE”.

Like me, my eisy doesn’t like to jump the gun on updates! That or it slept in on a Friday. Thanks for the explanation @bmercier!

@smileyw @brians Sadly this has been a long standing UI issue that many have brought up through the years and nothing has been changed. It ranks up there with font size and colors. I (personally) doubt this is high on the list of correcting at this point with the focus on continued development of eisy/Polisy, PG3x, and ZMatter. Certainly the only way to get more attention to the issue(s) is to submit support tickets, but based on how long comments of UI "bugs" have been in the forums I wouldn't expect any large changes anytime soon. (Try a Google Site Search for font size or color hard to read) https://www.universal-devices.com/my-tickets/

I don't have Google Home so can't help directly, but I think the same thing happens on an Alexa/Echo Show. It's more than likely just an anomaly with the UI on the cloud systems. Something might not be reporting back the actual status. It never bothers me because I don't usually stare at the screen of my Echo long enough to care. If the light acts correctly following my voice command I'm happy. I don't care what the "smart" device is displaying that I told to do something. If it (the "smart" assistant) did its job what does it matter what a temporary screen shows?