Geddy

@DreamerI90 please let us know your current IoX version and PG3 version. When you are local to your device open this in your browser (note if you get a security/privacy warning it is okay to continue to the site as it is just a local page offered up on the eisy): https://eisy.local:8443/WEB/sysconfig.txt Please post what you see for IoX(ISY) and PG3x versions. Do you have the eisy device connected to a UPS device to try to keep power to it? That would be an option. If the power outage is too long for the UPS then the device should still load correctly and things shouldn’t be an issue, but unexpected boots do happen. Most of the plugins should attempt restarts, but if there is an internet issue when they try to restart and connect to their service it might cause this issue (however odd that Notifications doesn’t restart because I don’t think that requires network to startup…I don’t use that one so not totally sure). Once we know the versions you’re on there might be more things to try. Otherwise, might need to open a support ticket to get the logs reviewed to see what causes the failure to connect on reboot.

@JimTurner more than likely your best bet is to open a support ticket with UD and get help directly from them. https://www.universal-devices.com/my-tickets You've done the usual troubleshooting of power cycle. However, how did you perform this power cycle? If you accidently triggered an update run and then pulled the power it's possible that the update was corrupted and the eisy is not coming back up as expected. But, if you're able to access the admin control portion it might be working as expected for that portion. When you're local to the device try these two URLs: (if you get a privacy warning it's fine to proceed...click advanced and proceed to site) https://eisy.local:8443/WEB/pkg.upgrade.htm - Just wanting to see if this loads. It might say no updates needed, but if it says updates are pending/needed then certainly open a support ticket. https://eisy.local:8443/WEB/sysconfig.txt - What is the IoX version and when was it installed? Also, what's the PG3x version and when was it installed? Rather than attempting random SSH commands UD has asked anybody with issues similar to this or related to the update process to open support tickets for direct help. They don't want other issues from random commands being run that would make it more difficult to diagnose and resolve. Please post back how this is resolved. Good luck.

Got it. I was trying to find the link too and couldn't so went the web archive route. Once I saw that it was in the old PG2 area it made since why you were getting the error (I was too). Info might still apply. I don't use that plugin so can't offer help/tips. Maybe @sjenkins can give some advise until @TriLife is back to try to help.

Looks like the help file is linking to an old forum that's been taken offline or archived and no longer available. I found it by looking through the internet archives. Take a look here: https://web.archive.org/web/20240716121024/https://forum.universal-devices.com/topic/24538-sonoff/ It appears this was in the old PG2 area. Since PG2 is no longer supported those old forum topics have been archived. I'm not sure if the old post applies to the new version or not, but the link above should help you some with information from the old plugin (node server) setup.

Honestly, no. It will run simple stuff enough. Once you get it working for your lifestyle you might be ready to update systems to the latest device (eisy). But get things working….as they say crawl before you walk. Sounds like you’re well on your way. Strong community here to help you along. The main reason I don’t suggest upgrading is because there were big changes from 4.x to 5.x and right now it’s best to get the system working with the current firmware. If you start replacing switches just don’t get the new i3 line as the do not work 100% with the ISY994. But all the legacy Insteon products still being sold should work just fine with 4.9. Key thing….make BACKUPS after every few changes! Never know when something might goof up and it would be easier to restore a backup than figure out what (you) changed.

@Mwid excellent! Glad you were able to get in with the default information. Happy learning the system! Lots of resources found on the forums and the UD Wiki - https://wiki.universal-devices.com/Main_Page In the wiki you'll find a link to an "old" ISY Cookbook. A lot of that information still applies so it would be the starting point for anything you might want to try for programming. While you're in the admin console look at the "Help" -> "About" and let us know what firmware you're on. For now don't worry about updating the system. Just want to know what you're on. Once you get to the point that you might want/need to update the device I would caution you if you're on 4.x currently the most you'd want to update to first would be 4.9. If the firmware happens to be a 5.x version then you'll need to know if you have a z-wave card or not and that will determine which version you might go to in the 5.x branch. But for now...don't worry about updating. Just tinker and see if there are programs that you need to adjust to fit your lifestyle. Welcome to the UD family of home automation!

@Mwid welcome to the UD Forums! Good luck getting into the ISY994! In addition to what others above have given for accessing the device keep in mind that the user/password could be anything the prior owner setup. The user name should be "admin" (without quotes). Then try the default password of "admin" (again, without quotes). If that doesn't work you might be at the point of needing to reset the device and that gets very complicated. The good thing is you don't get locked out of the device if you try too many passwords. Maybe the prior owner might recall a random password they set and you can try those. To expand on what @paulbates gave you...once you have Java installed on your computer you'll need to get the IoX Launcher that should find your device on the network. You can download that from the UD site: https://isy.universal-devices.com/start.jnlp Running start.jnlp once should put an icon on your desktop called "IoX Launcher". Then you'll launch that and it will open a window called "IoX Finder". After a short moment it should find your ISY994 and will show a name, uuid, url, type, and version. Click anywhere on that line and then select "Admin Console (local)" and it should open the admin console for the ISY then after a few more seconds prompt for user and pass. Good luck! Please post how things go. And if you run into issue share a screenshot of what you're seeing.

@LarryCRetired nice to see you back around here! Hadn't seen you post in a while. Hope things are well! As @Guy Lavoie points out you won't technically migrate from both devices into the eisy. You'll probably want to focus on the migration path from ISY994 to eisy. I'm not sure what to suggest about the Polisy plugins (formerly node servers) moving to the eisy. It wouldn't be common, but do you happen to have an active portal subscription for the Polisy? The best is to read the migration steps in the wiki before you attempt the process. It's a little tricky and might not be exactly as stated in the wiki, but it should be fairly close. https://wiki.universal-devices.com/Eisy:User_Guide#Migration The one tip I try to be sure to mention is to save a text copy of your current programs from the isy994. Right click on the root folder and select "copy folder to clipboard" then paste that into a TEXT editor (like notepad on Windows computers - DO NOT use a word processing app/program). Then save those programs for future reference if needed. Also make note of any network resources you've setup and any notifications you have (specifically any long/complicated notifications). Since PG2 is no longer supported (and was removed from Polisy if/when it updates to a later version) you probably won't be able to migrate any other plugins you have been running on the Polisy. So you'll be looking at setting those up new in the eisy (this is where that copy of programs might come in handy if you have programs relying on those plugins they will be broken and will need to be edited). If you have paid plugins running on the Polisy you might be able to open a support ticket with UD to see if there is a way to apply the license to the eisy, but more than likely the easier process would be to buy them again in the new device. One thing is depending on how old the eisy is you'll want to get it up to date before you migrate. You might run into issues so it might be good to try updating the eisy first. If you just got the device it might be fairly current, but if you bought it when released there are a lot of updates that need to run. You might have problems and will need UD to help support that process. You can open a support ticket with UD: https://www.universal-devices.com/my-tickets Good luck with the process! It is possible, but being slow and methodical about it helps a lot. Again, welcome back! Hope things are going good.

Seems like you’re trying to run current plugin on an outdated system. I don’t think PG3x allows or is setup to have an external ISY (ISY994). The current PG3 version is 3.3.18 (at leased based on my system currently). I suspect you haven’t updated the Polisy. I suspect your setup is blocking some advanced settings and you are seeing that with unexpected results in information being shared back to an old ISY994.

@diggler did you follow the directions from the eisy migration process? Linked to the portal migration process: https://wiki.universal-devices.com/ISY_Portal_Migrate_configurations_to_a_new_ISY What's the error that you're getting? Ultimately, if you've followed the migration path and it still isn't happening opening a support ticket as @paulbates suggests is the best method to complete the process. But it should work fairly easily.

@Ross not seeing this on my side. Meaning I DO have status options to select from. If you reinstalled the plugin have you closed and relaunched admin console? Even though you see the nodes in the main portion sometimes reloading admin console might bring everything current again. Random would be to clear java cache and get a new start.jnlp from UD and load IoX Launcher fresh on the system. What IoX version are you running? Browse to this site when local to your device: https://eisy.local:8443/WEB/sysconfig.txt (if you have polisy replace eisy with polisy or use your device internal IP address) Look for IoX/ISY version: (Recent version showing)

Open a support ticket with UD and let them know the plugin and the situation and see if they can refund that way. https://www.universal-devices.com/my-tickets

You can copy all your programs by right clicking on the root folder (usually "my programs") and selecting the last option "Copy folder to Clipboard". Then open a text editor (not a word processing program, but just a plain text editor like Notepad on Windows machines) Paste what you copied to the text file. That will give you everything you have for programs. You can also do this on individual programs, but copying the root folder allows you to view everything you have. You can also use the "find" option in the text editor to look for devices. The only thing is there's no way to import a program into IoX so any changes will need to be made to the specific program in Admin Console then SAVE the programs. If you find yourself working on multiple programs be sure to save after a few changes and make backups along the way (in case you mess up and want to restore to a prior save point).

My suggestion wasn't a wired to wireless adaptor. It's the same as @paulbates suggests that it would pickup the wifi signal AND enable the ethernet ports so they could connect to the ISY994. More than likely the facility IT staff is looking for rogue SSID (kind of like at my kid's university). They don't want conflicting wireless signals/networks to degrade their own setup. There needs to be some way for them to allow a wired connection, but if they're charging more for it then that might be the best option to go and just pay the additional amount to keep the ISY994 and ISY Portal "happy".

@matthewjocko you posted the same thing in three places….getting help from others and then you’ve opened a support ticket…consolidated all replies into this thread (in case replies seem out of sorts) so the help you get from others can be streamlined. Since you’ve opened a support ticket please post here what happens to resolve your issue so that it might help others down the line.

@bfish I’ve never tried this device directly, but either saw it mentioned here before or elsewhere for travel reasons and think it might work….please research before buying. https://www.amazon.com/GL-iNet-GL-SFT1200-Secure-Travel-Router/dp/B09N72FMH5/ This seems to be able to be used as a repeater, but I believe will allow the LAN ports to work. The issue becomes how the community handle IP assignment. You might not be able to get IPs assigned internally. Might find more info on the GL iNet site.

@bcdavis75 I'm not entirely sure how to remove them from the PG3 dashboard, but in Admin Console I think you can remove them from there and they might go away in the web dashboard. It's been too long since I tinkered with PG2/PG3 to remember the process. In Admin console: Plugins -> Configure -> Pick the range -> Select the plugin -> bottom of window "Delete" Did you re-install each one individually or did you use the system menu option to "Reinstall all Plugins"?

@bcdavis75 It might be something that you need to open a support ticket with UD to see if there was a release put out that might have messed something up. You've performed the usual step of power cycling to see if they would load automatically, but something might be causing an issue. You also have several that are unmanaged. Did you have some PG2 plugins that you haven't removed since updating to PG3x on the Polisy? https://www.universal-devices.com/my-tickets I would suggest that you try one of the disconnected plugins and set the log level to "debug" then restart the plugin and allow it to run and settle (a few minutes might be needed). Then download that plugin log and see if there are any errors following the plugin restart command. It might give some hint as to what is causing the error. Either to you or to UD support.

That's marketed to be the ultimate goal of the Matter "standard", but this is the initial release from UD for Matter support. Only bulbs and plugin modules were mentioned in the release. Might not be fully covering all brands of these items. Seems to be like with z-wave that any and every "smart" product maker tried to slap a matter label on their item and hope it ends up working with hubs sooner or later. And yes...now I realize it was in the title, but it was lower case and I just assumed some sort of typo or autocorrect situation. Since I don't keep up with matter products your title didn't make sense as a product name.

@proj964 you've never said what device you're trying to add. Please share what brand/model you're trying to add. It's possible that this initial release of matter support doesn't support what you're trying to add. I don't have any matter devices so haven't attempted to link anything. Probably not worth a support ticket at UD at this point, but might be something to at least confirm that it's not a supported item. I might just suggest waiting until more items are supported or at least until a later release of Matter support is put out by UD.

Yes, that's the "current" or most recent, but there have been minor updates since the release announcement was posted. Please go to this URL when you are local to your eisy: https://eisy.local:8443/WEB/sysconfig.txt (if you get a privacy warning please proceed to the page/site. If you get an error please replace "eisy.local" with the IP of your eisy.) Look for IoX Version - a more recent version would be: I haven't randomly tried to update in about a month so not sure if _18 is the "latest" or not. Some users will randomly update and notice a different build. Sometimes this has caused issues.

Probably best to open a support ticket on this one. If it came up after the power outage and showed was online when you checked the portal, but couldn't access it locally is probably a local network issue. Then you said you power cycled it and now UD Mobile said it was updating, but is/seems dead. Not sure how an update got triggered, but if you did pull the power during the update it could have corrupted the update. UD will need to try to see if you can get it started and working again. Open a support ticket here: https://www.universal-devices.com/my-tickets Please try to keep up with what is done to get this resolved and try to post back what gets you back up and running. Hopefully it's a "simple" issue.

Here's a good comment from @MrBill that I keep handy to suggest noise troubleshooting options: https://forum.universal-devices.com/topic/35216-programs-not-working/#comment-330289 Later in that thread he posts these wiki links: https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors https://wiki.universal-devices.com/index.php?title=INSTEON_Signal_/_Noise_Troubleshooting https://wiki.universal-devices.com/index.php?title=INSTEON_No_Status_Feedback_From_Devices The key to noise is it can be anything new OR old...can even be something that's randomly running (or not running) at the times you're testing (if it's inconsistent).

There is a migration process (UD links to it in their email release). Although you can also review the UD Wiki for the eisy user guide that has the migration process included. https://wiki.universal-devices.com/Eisy:User_Guide In typical migrations from ISY994 to eisy most Insteon is simply moved to the new device. Everything should look and act exactly the same. There are some issues that have been posted about here (probably a while back now), but I think the process is fairly straight forward and seems to work (the posts here about it not working might be rare cases because most won't come to the forums to post "it worked as described"). And the option of what to upgrade to is simple...only the eisy is available from UD at this time. The Polisy is no longer available. That's why this topic is asking about upgrading from the Polisy to eisy.

From recollection when the eisy was released there is marginal differences on the surface level as far as IoX and Plugins are considered. I think all the underlying programming that UD handles is the same (or at least very close to identical). The reason for the eisy introduction when it was released was lack of ability to source the hardware for the Polisy (one of those issues that can be blamed on covid and the supply chain issues that followed). As stated above if you've got a working Polisy at this time just keep it updated. UD pledged to support the Polisy for several years after the eisy was released. That timeframe I do not recall for certain, but think it was several years. We are a couple of years since the eisy was released so expect the Polisy to continue to be supported for a few more years as long as UD can keep the code for the two devices similar. I moved from Polisy to eisy when the eisy was released. I do not experience any difference in my use. I have a mid-size Insteon install (~70 nodes +/-), 6 z-wave devices, 4 zigbee devices, and maybe 5 plugins. I don't get crazy with programming or variables. Since the underlying IoX code is identical there's no "speed" difference. I'm sure the device processing power might be different/better, but at the end of things IoX computes the change and sends signals out via the PLM so there's not any speed difference, at least probably not that a we could tell in the real world use (as @larryllix points out).