Geddy

I think the notifications are simply if the device (IoX) isn't registered with the Portal in some method. So it could have been fine locally and the wifi could have been fine, but there could have been something funky between the device and the portal. I would suggest opening a support ticket. Include your UUID and if you still have the time that those notifications came in perhaps it can be checked in some logs with UDI to see if something in fact was in error with your device. What device are you using? What IoX firmware are you running? Good point about possibly having a wait period. I'd include that suggestion in your support ticket. Start a support ticket here: https://www.universal-devices.com/my-tickets

As I said, you can find issues. It worked for countless others. I think there was another post (maybe yours) worried about a dry run and the process to "roll back" to the ISY994. Nobody really knows if they'll have issues until they just do it. You've got to figure, forum posts of issues are like complaints for products. Only those with issues will post (some much more than others!). Those that can help will reply. Many that don't have issues go unreported and just work as expected. I'm sure there were others that didn't post here and went straight to a support ticket. But, for the most part things work well. It will NEVER be 100% perfect. And don't expect that it will. You've been a member of the forums since 2010. So I'm sure you probably went from an early device to ISY994. Was that easy swimming? (maybe it was, but it was no were near as complicated as the systems are now.) You didn't go from ISY994 to Polisy, was that easy? Not really, but got much better as time went along. I'd say even now (3+ years after release) that it might not be smooth sailing to go to a Polisy. But being afraid to make the move is personal prerogative. Stop asking/thinking/begging/wishing that there be some miracle release that solves EVERY SINGLE issue. It's already better than December 31. Will it be better July 31st? Maybe. But why not migrate now and then fix what doesn't work and allow UDI the chance to squash even more bugs - if you end up with issues on products that others haven't had products to test the migration. You're approaching this from too much of a cautionary tale approach. Others dove in head-first to lead the way for the rest of us to have a more pleasant experience. It's probably not something that can be answered easily. It's not like UDI has a log of everybody that updated and how long certain steps took. They'd only know for limited test sessions, and even then it might not be representative because they're TEST SYSTEMS. The best case would be to ask others here...maybe PM some that you quote above as having issues to get their "real world" experience. Migration isn't something you can do in 10 minutes. It might take all weekend. Depends on the size of your system and what you're doing during the process. If you've got a ticket open that long then reply back to it to get their attention again. It isn't typical, but with all the issues being tracked it's sure a question that doesn't really have a clear issue could have gone unanswered simply because they can't say for certain and don't want to answer with something and you have a vastly different experience and complain that they said "x minutes" and it took you "y minutes". Enjoy & good luck!

The Geofence can trigger a program that could evaluate the time of day and fire or not fire as needed. It's not built into the app ability at this point. Not sure if it's on the future upgrade process, but easiest way is to trigger a program.

@johnnyt I think 5.5.9 has been fairly stable for many people. I know there are a few nagging issues here and there, but it's night and day different than initial release versions for eisy. I think somebody said it before or maybe in another post there are so many variables at play that there's probably no way to get "every bug" that might happen in a migration. Everybody's system is different. So while you might think they'll get most of what you have the likely hood of you having a device that somebody else hasn't migrated could be high and mean it would work for YOU. For my system, I was able to migrate fairly early on and have had a solid/stable system since mid-January. I've been able to work around some of the jitters in some updates because I had the time and ability to either live without or other reasons. By holding out now you're just asking for a potential/possible bigger issue when you finally do migrate. Thinking that it will go smooth sailing and then something breaks and you're in a bind worse than you would be if you just did it now. I'm not sure what the worry/concern is. Just take the plunge. It's great in the eisy pool! Speculation does nobody good. Kind of foolish to even think/push/hope/wish that something is "just around the corner" that might make everything wonderful. Sure, the next big update might fix something that is broken for somebody right now, but it could easily break something else for others. That's the nature of the beast at the moment. It's been that way since ISY5.x when Z-Wave became a much more important system to support. The way I see it from a user side that there are endless Z-Wave manufacturers that for some reason or another do just enough to be "Z-Wave Certified", but probably not do everything that the IoX/Z-Matter system can control and would therefore "break" something in an existing system that would need to be fixed. It's just the nature of the beast.

@GTench if you get that alert when trying to run “local” access be sure you clear the Java cache (selecting all three boxes in the process) then download a new start.jnlp from UDI site and it will match. https://isy.universal-devices.com/start.jnlp

@MWoods329 You've got 2 posts going on the same issue? Instead of posting in a thread that appeared resolved you should keep the help in one spot. Please use your new thread for further help/troubleshooting -

This question is probably best served by contacting UDI directly. https://www.universal-devices.com/contact-us/ If it's not a normal option then nobody here will know and would just speculate.

@pepethecow From the screenshots you've posted it looks normal. Your ISY is registered and the ISY Portal sees the device as online (the green circle on the portal page) Your HTTPS port doesn't matter when you're connecting through the portal so hopefully you're not trying to add that port to the URL it's using. For UD Mobile you just need your ISY Portal user/pass credentials and it should sync automatically. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Existing_Portal_Users What version of the app are you running? Make sure it's updated to a recent production or beta version. Appears you're on an Android device. Should be close to Version 1.0.33. I might delete the account in the app and then add it back in. If you still have problems the best bet is to open a support ticket and get help directly with UDI to confirm setup in the app. https://www.universal-devices.com/my-tickets And no, ISY Portal should not require you to be a network genius. It's actually there to keep things ultra simple (and a bit more secure than port forwarding).

In the admin console. Click on the "Programs" tab. Then below that is a "Summary" tab. From there you can sort the columns by clicking on the title. click "Last Run Time" twice to sort from most recent to oldest. If you see an offending program about the time that the lights/devices turned on you can select that program, right click and then "Edit" to modify what's happening. Also, you said ALL devices turned on. Are you sure every single device did or just "a lot", "most" or "some"? If you have program issues you would like to review post the entire program by selecting the program, right click, and select "Copy to Clipboard" (should be the very last option in the menu). Then you can paste the program as TEXT into your forum post. It's easier to read and assist with any modifications by not having to retype or recreate the program. Yep, I know. I'm just saying don't change that and put the PLM on the UPS thinking it might help. Your setup is fine. Ah. Okay. I thought you meant something like you leave the Admin Console running 24/7 (it's not advisable to do that!) and it was still active and not "locked up" or something funky with the IoX access.

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.