Geddy

@smokegrub there you are! Looking like yourself again! 🙂 I can't help much on the macOS other than what's in the wiki. I think @Javi or @bmercier posted something recently about how to work with the macOS security issue to get IoX Launcher installed. I know @Bumbershoot posted something a few years ago about how to make it work, but I'm sure a later update changed those processes too. Maybe check this post: https://forum.universal-devices.com/topic/44943-admin-console-not-working-on-mac/ If you already have that machine then I would be using that if that's what you plan to be using in the future. There's nothing really to "move" for IoX stuff, but if you're using multiple computers and one will be the future use machine then I would suggest using that now (again, if you have it). And not worry with the "older" machine. I'm not sure what macOS you mention is so not sure if it's old/current/future. Being old has nothing to do with it. Apple hasn't liked playing with Java for a long time and makes it difficult. I wish it would just work, but you've got to do funky things to make it work. Just glad you've got the grasp of some technology. I'm sure many your age might not have as much experience as you've got. Good luck getting it sorted out.

@smokegrub - Another way to get the start.jnlp file is from UD's website and clicking on "My ISY" on the top right. What computer OS are you using? What browser are you using? Some browsers will not automatically save *.jnlp files and will ask if you want to "Keep" the file before it downloads/saves to your local drive. Then, if you're on MacOS you've got to do some extra steps to make it work correctly. I'm not sure what those are, but there have been posts about it in the fourms and in the wiki https://wiki.universal-devices.com/Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop

@MBrzeski that I do not know. I don't use this but just tried to help with the steps to add the custom keys. Maybe somebody else uses this plugin or Flair support can help further.

As with the OP I would suggest you open a support ticket to get direct help from UD. While they do monitor the forums some they have not had the time recently to directly answer issues posted here. https://www.universal-devices.com/my-tickets Since OP has not posted an update it would be best for you to also open a ticket.

The “adapter” is just a USB flash drive. (I had to ask the same in the past)

No, it's just probably not a UD Matter supported device yet. There hasn't been an updated announcement as to if UD has added more devices under the Matter ability. Since Matter support was announced by UD back in Feb there hasn't been any comment of additional items being added. In that announcement they said, "Support for additional Matter clusters are brewing as we speak." I'm guessing it's been a challenge to get more devices added. You could open a support ticket with UD to see if there is support for this device. https://www.universal-devices.com/my-tickets Also, this doesn't help. Sure you added "as of tonight", but honestly version numbers are always better than just saying "latest" versions. Just FYI and consideration in the future.

It might be good to open a support ticket with this issue. It could be a bug that needs further testing. As @hart2hart suggests it's a "known" issue, but what you're experiencing might be different and would need to be diagnosed if it's seemingly working, but later making a duplicate. https://www.universal-devices.com/my-tickets

@Brian680 what is the top two lines result when you go to this page: https://eisy.local:8443/WEB/sysconfig.txt Since OP hasn't posted back following their support ticket you would probably best be served by opening your own support ticket. https://www.universal-devices.com/my-tickets

@Riggins44 Simple answer might be to open a support ticket with UD to see if they can trace the issue if your portal account isn't staying active. https://www.universal-devices.com/my-tickets Since this happened following an update make sure that you've fully rebooted the system. Perhaps even a power cycle (press and hold the power button until it turns red, wait 10 seconds +/-, press the button and allow the system to fully boot before attempting to log in (I would suggest using java admin console). Is your device (I assume eisy) hard wired to your network or are you using wifi to connect? If wifi, is it possible to get a wired connection to where your device is in relation to your network equipment? Lastly, make sure your portal subscription is active. (UD Portal -> Select Tool... -> Information -> ISY Portal Access License)

@FloridaGary I am not sure how much programming has advanced on UD Mobile, but it didn't used to be all that easy. Simple solution would be to use admin console to make a program. Maybe post your screen shots that you see. Have you attempted to add/make a new program? Look at the "My Programs" under Automations then click the "+" on top right. Should give you the option for "New Program". It takes a while to spin and then comes up with the program appearance. Add you conditions (Time shows "error" until you make a selection). The "THEN" action will be "Command". Here you select your device and what you want it to do. After you complete it be sure to "Save" (top right). Then go back to main screen and sync (just to be sure it's written to the Polisy IoX). I think "My Schedules" would work the same, but I went down the "My Programs" side just now.

Try adding this to your IoX Launcher address: http://eisy.local:8080/desc That comes up with you "eisy name" userid/password option. UD has changed the "default" credentials to rely more on the portal access, but does not necessarily mean "cloud" or online connection is required. It's simply their way of bringing the eisy-ui into the web experience for users (something many have been asking to do for ages...honestly, I love the java version). I think it's also their attempt to bring things in line with single sign-on by encouraging the use of UD Portal accounts.

Mobilinc still works with eisy. Just very limited. I never used their connected version, but had the pro/HD versions and used it for a while when I first changed over to the eisy. UD Mobile is a little better as it handles more of the devices that get added via the plugins, but even then I never really used the mobile apps much so neither are a highly used app for me. I'm not sure the version you're using of Mobilinc, but if you're using the pro/HD versions they still login the way they always have (either by direct local connection or through the UD Portal). If you used the connected versions then they might not work for you. Glad you got the old files working again.

I've had this issue recently. It was noise in my system. I have one switch that's on a wall in a room not too far from the PLM, but it would randomly say unable to communicate when I launched admin console. A simple query would recover the device. Found out when two other devices were plugged in it created noise to that location. The devices were an iPad charger brick and the Somfy MyLink. When the MyLink was plugged into a different outlet and the iPad wasn't charging there wasn't an issue. Silly, but was the result to my issue. Neither device was new to the equation, but moving both resolved the random happening for me. Is your communication notice issue 100% of the time? Maybe be sure to remove it from the system before you factory restore it so IoX doesn't think it's already in the system.

@JimTurner FYI I just decided to try the update process. In all the eisy updated in about 15-20 minutes. I had a few notifications on UD Mobile to reboot the system, but I allowed a few minutes to still tick by just to be sure the system was done doing what it needed to do. I didn't get an alert on Admin Console to reboot, but after a couple of reboot notifications from the app I checked the sysconfig page on a browser and everything had been updated. (https://eisy.local:8443/WEB/sysconfig.txt) I then rebooted from the still open Admin Console window and again waited for the alert on UD Mobile to say pg3 had started and plugins reconnected. I had two plugins fail to connect (iox-matter and openweathermap). I just reinstalled these and they seemed to connect. I couldn't get them to just restart. I think with OpenWeatherMap I actually deleted and installed in the same slot and had to add the key and location parameters and things seemed happy again. When I first tried the eisy-ui web the "nodes" gave me errors. Saw somebody else post about that and had to use https and things worked fine. I'm not so hip on the web ui so didn't do anything with it yet. The java admin console worked as expected (without issue). So I'm cool with the update that far. Overall, I'd say I was up and running within 30 minutes of pressing the "update packages" button. If/when you do the update hope it goes well for you too!

Thanks @Panda88 for the update. I bit the bullet and updated to 6.0 (took about 15 minutes - no issues in the process - a few plugins wouldn't connect so just reinstalled and they work fine). Also got 1.6.9 updated and no sync issues with UD Mobile (iOS). Thanks @DennisC for the info of running 6.0. I hadn't been home long enough and wanting to take the time to update if I had to "fix" things following it. In all took less than 30 minutes to get things updated and a couple of plugins reconnected. Things seem to be working fine for me. Time will tell. Now I've got to read about the web ui parts and see if that's something I want to dig into. Thankfully trusty "old" java admin console works perfect!

@DennisC , @BobM99 , and @TJF1960 - what device/firmware are you guys running? I'm on eisy 5.9.1, YoLink plugin 1.6.8, and UD Mobile 1.4.1. I was getting the error still last time I tried to sync. I haven't taken the plunge into 6.0 yet and wondered if the plugins has been fixed with the updated firmware, but still off with older firmware. Fine for me as I don't use UD Mobile enough to worry about the error, but do try to keep it in sync when things update and just updated the YoLink plugin yesterday. Thanks @Panda88 for testing and trying to fix! Edit: Just saw there was an update to UD Mobile. Now running 1.4.3 and indeed still getting error.

@IndyMike sadly (?) the Polisy and eisy no longer have that program by default. It needs to be created by the user if they want it to be available again. How far are you from other Insteon devices? Maybe remove it and bring it closer to the PLM and add it again. I don't have any mini remotes so not sure how they work if they're not within a decent range of other dual band devices.

@aca2b2 as @DennisC points out it's unlikely you'd find the outdated PG2 nodeserver anywhere. Perhaps @glarsen might have it stored in a personal archive somewhere that could be available. Tagging @glarsen to try to get attention to this thread to see if they can be of any assistance. Otherwise, the options are to go without it or upgrade to the eisy and the PG3 plugins. There is indeed a discount currently available (until Nov 21) if you read about the release of the eisy r2 that was just posted a couple of days ago. Good luck.

True, but my guess is they've been focused on eisy-ui and the latest firmware/os updates. There haven't been any announcements of expanding the Matter support other than the matter plugin that helped connect to Apple Homekit.

Yeah, I removed it since you had typically the same post in another area and was already getting help there. Didn't think it was valuable to have a reply here. "reporting" an issue here is good for letting the users know, but for something that is in development it's usually better to handle support through the UD Support tickets (https://www.universal-devices.com/my-tickets) so you are sure that UD sees your issue and can accurately work directly with you to troubleshoot and resolve the issue for you (and potentially others down the road).

Did these devices work with the eisy prior to 6.0 update? Matter is still being worked on (by UD) and only a few items have been said to work. I've not added any Matter devices (don't really need them (or want) them yet), but more than likely you've jumped the gun trying to add devices that aren't supported yet. Remember the Matter announcement (from Feb 2025) https://www.universal-devices.com/2025-liftoff-2/ - I don't recall seeing any other announcements of other devices being supported.

When you're using IoX Launcher (java based admin console) are you selecting "LAN" or "Cloud"? In the past if you selected "LAN" you would need to clear the cache since the version you had previously downloaded was an older UI. IoX launcher attempted to get away from having to do this, but was only more reliable when selecting the "Cloud" option. It would usually error out before getting to the login page. If you're selecting "Cloud" option then that's (quickly) downloading the proper UI for the firmware installed and does not result in an error. Prior to 6.x it did not mean you had to use your portal credentials as it was still a local connection...it just meant it "grabbed" the UI version from the cloud before you saw the login prompt. IoX Launcher was developed during the 5.x beta version period where updates were being released rapidly and many users would forget (or complain) about clearing cache after each (little) update. UD tried to make it easier for us users at the time and it's just been the best tool since it was released (and of course the browsers ending the old java connection method). Next time you log in check the Help -> About to see if the Firmware and UI match. If they do then you're all good. If they don't you might be better off clearing the cache (selecting all 3 boxes) and getting a new start.jnlp file from the UD site (top right "My ISY") and running that to put the launcher shortcut back on the desktop (for Windows PCs). It's just always been the standard operating procedure to assure you don't have issues. Mismatched versions have been problematic for scenes and programs (and possibly other issues). It might be best to keep things in check while UD fleshes out the rest of the web based process.

@diggler glad you got it sorted out. If you really want to get crazy with the programming the wiki has some good details on this: https://wiki.universal-devices.com/ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration It was a length discussion a few years ago about the "ideal" way to program fanlinc and keypadlinc. Mini remotes are a whole other story as I don't think they'll report the status of the fanlinc if it's adjusted with another device. I don't have remotes so have never tried to program them.

My understanding of Alexa+ is that it's only going to work on new(er) devices. Perhaps they're trying to figure out how it's going to impact those of us that have 1st/2nd gen stuff (or just stuff older than they want to support with Alexa+). I have two devices that would work with Alexa+, but I am avoiding it since I don't really like/trust Alexa enough to begin with. I don't want her to keep listening for follow up inputs when all I really need are timers and to turn things on/off randomly. It's this overreaching (over listening) aspect that Amazon is trying to make Alexa smarter by forcing users to use the follow-up that many probably turned off because it wasn't very useful when they first introduced it. I might be in the minority of wanting/using the new Alexa+. It's clear (to me) if Amazon is implementing Alexa+ while not working with their partners/developers for all the skills essentially breaking the skills (that people have developed over the years) is not very good for any parties involved (Amazon/Developer/User). If what @bmercier says is true that the V3 skill will work with Alexa+, but results users are having mixed results then I blame Amazon for breaking things. Sadly, many will come here (as they apparently have) and blame UD for not working with Alexa. Let's be sure to point the finger the right direction. Amazon is making a new offering while apparently not "breaking"/changing their API that developers use to make Skills. When the skill doesn't work why is it the developer's fault? The developer is only working off what Amazon is telling them that the skill would/"should" work. Sadly, it's a never ending cycle these days. Things are trying to become smarter while not supporting things that just work now. Toss into it any little break in network/internet connection really blows stuff up quickly. Remember when we had to physically flip a switch to make a light come on? That never broke...why did anybody think it needed to be "fixed"?

probably a macOS issue. I'm on windows 10 and 11 laptops and can stay logged in without issue. I don't usually have it open more than a few minutes though (typically just enough to help others here if I need to test something out). I know Apple likes to block Java and control background running "apps" more so they can have better battery life. Good luck tracking that down.