Geddy

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

Not sure, but I think from some comments it was eisy targeted. It could have impacted some Polisy if they have converted to PG3x. I think it was more targeted to PG3x and IoX 5.5.9 based on reading this thread and maintenance thread(s).

@KConover Feel free to let UDI know - https://www.universal-devices.com/contact-us/

Well that explains my reboot about 10:25 eastern today. Thanks.

Google Home turns the display off? Isn't that normal? Or do you mean something else?

HAHAHA! Yet some around here "swap out" their PLM like changing socks. It's shocking sometimes that people just "swap the PLM" as a troubleshooting tip. Personally that's probably very, very last ditch effort in any line of troubleshooting I would consider. And only then would it be after a support ticket (with UDI and possibly even Insteon) and then at their suggestion to swap a PLM. But I digress. Hopefully people that really NEED a PLM are able to pre-order one and get one to get their system running again. If all ISY/Polisy/eisy users order one just to have as a spare it's possible somebody that really needs one for a non-functioning system would miss out when needed. Hopefully Insteon has a good supply rolling in and more beyond an initial shipment. 🤞

HA! "Getty" @ctviggen1 no worries. Glad to give the info. I'm not sure what's the big hope to use a newer version if your current PLM is working just fine. I'd rather use the current device until it wasn't reliable rather than use a new device and then have a "used" device as the fall back. That's why I'm keeping my spare PLM as "NIB" (new, in box) status until it's absolutely necessary. Which I hope is no time soon, but at least there is hope that PLM will be available regularly in the future. And even better that my next spare might be a much improved product. I'm not willing to unplug my working PLM to check the version/date on that one, but thankfully it's been running since 2017 so I'm not going to risk issues at this point. I'm not a person with any retail manufacturing experience, but just my theory would assume there probably wasn't anything actually changed in "versions" for the old Insteon. It's probably just a way for them to track production batches and/or years that some components were used. Somebody that might have more firsthand knowledge/experience of the insides to describe the different versions. Or could confirm if there was indeed any difference from 2.4 to 2.6. I think @Brian H (and maybe others) may have documented changes from very early versions to later versions, but not sure if specifics have been made for such a "small" version change.

Probably get more accurate information asking Insteon directly. If they've received the recent shipment they can at least tell you what version they're calling the current production runs. But @lilyoyo1 is right (and basically confirmed by @Techman in edited OP), that using the same part numbers basically implies that it's the same build as before. But just for reference: Serial PLM (2413s) received in January 2021 is Revision 2.6 and date code was 4520. I think others got some around that same time and might have been the last time they were available from prior Insteon.

@HHarris Welcome to the forums. We split your post out to a new post as you had it posted in a Win11 issue, but say you're on Win10. What has changed that your ISY994 is not found on the network? Did you replace your router or did you update the ISY994 firmware? What firmware are you running? If you changed your router please review this section of the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Changed_ISP/Router_-_Can_no_longer_access_ISY Also, please review this section and observe the lights on the front of the ISY994 and report what you see: https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights

Nothing known here beyond the email everybody received. To guess would just be speculation until somebody confirmed directly with Insteon. Probably best to email/contact Insteon directly: https://www.insteon.com/contact-us

Check if you have another power supply available to test on the Echo if you move it back and they return again. It could be that the brick of the power supply for the Echo is flaky and where you're using it is causing the noise. I recall there being other posts that cell wall warts started causing noise randomly. So it might not be the Echo itself, but it's power supply. Depending on how old the Echo is you might get Amazon to replace the cord, but they don't usually offer that kind of option. I've seen elsewhere that some have been able to get Amazon to issue a credit for the amount of a new cord, but it's also difficult to get. Good luck.

Correct. If you get the serial version. Since the USB is also available for pre-order just go with the USB version and not have to worry about additional cables. That is if you're going to use it with the Polisy or eisy. As @nowandthen stated they got the serial version to use with the existing ISY994. The extra cable just adds unnecessary clutter to the cable management system (or lack there of for some) and another possible component failure to have to troubleshoot should there be an issue. (IMO)

@asbril Since UD Mobile can call on the program directly it is possible that you just make the geofence trigger the "THEN" of your program. Since a Geofence can have multiple commands just add another command, select "My Programs" -> "Run Then" Otherwise, you could still use the variables and have it set a variable and then trigger any number of programs off that variable. I still wonder where your "Occupied is true" portion came from.