Geddy

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).

When you log in this way use your portal credentials. Needs the port like @slimypizza suggests. If you're downloading the admin.jnlp from the device itself then you've got the IP right. Are you not using the IoX Launcher? That's start.jnlp and is available from the UD website (clicking "My ISY" on the top right) or linked in the Wiki.

@KenUD2 if you cannot connect locally, but the portal says the eisy is connected then it's still something locally blocking local network traffic. Are you running different vlans? Do you have a firewall device or different SSID that is blocking cross communication? But you're able to get something working after a reboot? If you cannot connect with IoX Launcher what computer system are you using (Windows 10/11, MacOS, other)? Can you connect with IoX Launcher after you power cycle the device? It might be best to open a support ticket with UD and see if there's something happening in the logs. Go here to open a support ticket: https://www.universal-devices.com/my-tickets Please post back with answers to the above questions as well as if you get help via the ticket what happens to resolve the issue so we can learn and it might help if others have a similar issue down the road.

Did you create at least one notification with UD Mobile? According to the post by @Javi in the thread at least as of last year UD Mobile would create a template and increase the number if there was already one created. It's possible something has changed as both systems developed over the last year. Might also need to run a sync on UD Mobile (while Admin Console was CLOSED) then re-launch admin console.

@KenUD2 this sounds like a possible internal network issue blocking communications. Have you setup UD Mobile with local access and can you still control devices while local with UD Mobile this way? Have you checked the Portal to see if the eisy is connected (https://my.isy.io/)? This might be something you need to open a support ticket (https://www.universal-devices.com/my-tickets) with UD to get the logs checked. There was a portal maintenance scheduled about a month ago. Did it happen then and since? Have you performed a full power cycle of the eisy? Lastly, what firmware are you currently running (please give actual version number)? Please be sure you're up to the most recent release (5.9.1) - be sure if you're not current to read the release announcement to be sure you don't run into issues. Don't blindly click the upgrade process without reading and preparing for the update.

@matapan the link that @Techman posted includes some information about having to enable the .jnlp to run (and if you've got -8 means you must have a lot of start.jnlp downloads (at least from a Windows user any -# or (#) means you have multiple copies of the same file. Delete all old "start.jnlp" or "start-#.jnlp" files. Also, the part about Apple not letting it run because it's from an unknown developer is covered in the wiki: https://wiki.universal-devices.com/Main_Page#Unidentified_Developer_Blocked Seems that Apple is fighting the Java world more than Windows is sometimes.

@slimypizza glad things are returning to normal. I wonder if you might have had a surge from some of the storms we had push through ATL recently. Not sure what side of town you're on, but we did have some recently that carried a lot of lightening. So random, but glad that resetting them and restoring them in the eisy seems to be bringing things back to normal. @Guy Lavoie agreed - this is one for the memory bank for future troubleshooting and hopeful tips for good outcome.

@matapan what version of macOS are you running? More than likely it’s a macOS issue with the certificate and not something you need to do with/for the ISY994. If you’re on an older version of macOS there are some possible support stems in the wiki you should try. Otherwise, there have been others that have posted help for getting IoX Launcher and admin console working on macOS. Maybe try a Google Site Search to find those posts. Be sure you review this recent post about getting things to load:

I've never attempted such a restore process. Might be time for a support ticket with UDI to see if there is any troubleshooting they can see. Very strange that the switches work with other controllers since they all go through the eisy/PLM to operate the switch. When a physical switch doesn't operate when manually controlled it usually means the switch is bad or wiring to the switch is bad. If you were to remove the eisy all switches should still at least function when manually operated. I would test a few switches by factory resetting them, removing them from the wall and setting up a local test loop to see if they do function correctly on their own. Agreed that it would be unlikely so many switches fail at once, but further unusual that if they were controlled by the PLM/eisy then you have them exposed to Echo via the UD Portal and HA via the ISY integration that those 3rd party controllers are operating the switch when they basically pass code back through the eisy to PLM to switch. If you've setup some direct connections to HomeAssistant then that makes sense why the eisy isn't controlling them, but no sense why they wouldn't operate manually.