Geddy

@737simguy interesting that it had another update to process. Not sure about this error. What do you see when you go to this page: https://eisy.local:8443/WEB/pkg.upgrade.htm (maybe use the eisy IP address if it doesn't resolve. If it gives you an alert/warning about it not being safe click to proceed since it's a local device it's okay to proceed.) Looking for results: "No packages need upgrading." In admin console is the Matter option "ON"? If you don't have any Matter devices leave it "OFF". Then run a sync again see if you get any errors. Be sure to fully close the app while you're working in Admin Console then reload the app. What app version are you running?

@737simguy Looks like you've already updated to 5.9.1. Make sure you've run a sync on the app. Moving this to the UD mobile area since it seems to be an issue with UD Mobile alerting you about an update.

@andrew77 I expect it just extends it. I think there's a history of the last few renewals. It's been a while since I looked at it, but I seem to recall it shows the day you renewed, but then shows that it's active following the current expiration until the next expiration. I usually renew mine a few weeks before it expires only because I have a reminder in my calendar about 14 days before the expiration date.

For specifics to what @Guy Lavoie said here's the post:

That's correct behavior. The admin.jnlp is directly from the current IoX firmware. This is acceptable, but know for certain that if/when firmware is updated in the future you will need to clear the java cache and download a new admin.jnlp version. More than likely you could start with a new start.jnlp downloaded from the UD site and things would go back to IoX Launcher/Finder method.

Indeed there's kind of a blackhole for Plugin information. Each one behaves different at times (in my experience). The trick is reading the "more info" link on the plugin you are considering. And don't sweat "coding". There's generally nothing needed as deep as that. All you've got to do is setup a few things in the plugins for them to work. There's nothing to code...that's what the plugin developer does for you. Since you mentioned the Hue plugin maybe I can help you just a little bit there...It's one that I run, but I don't do a lot with it (trust me....very basic). For the Hue plugin you install it through the PG3x web interface (found at http://eisy.local:3000 - or replace "eisy.local" with the IP address for your eisy). The login for PG3x is the same as getting into admin console. Go to the plugin store, Find a plugin you want to install (in this case Hue), click "install", select a slot to install, PG3x will install and pop up an alert on the lower right that the plugin was installed Next go into the PG3x dashboard. You should now see the Hue plugin listed. It's probably showing "disconnected" or some error. Click on "details". There might be a blue bar on the screen telling you to push the button on the Hue Hub (doing this from memory because it's been a while since I set this up. Go and press the button on the top of the Hue Hub and give it a few seconds/minutes to communicate with the plugin. Once the plugin seems stable then you might need to restart the plugin. Just hit "restart" when you're looking at the details page. Once the plugin has restarted it should fill in some "Nodes" for your Hue devices. You should see some "Node Names" and below that the name for the Hue device (bulb or other). Now open Admin Console and you should see a "Hue" in the device tree. Right click that and you can "Group Devices" and that should put all the Hue devices into that tree listing in IoX. Like this: There you go! You've just installed and setup your Hue plugin. Do know that the Hue plugin hasn't really been updated recently, but it works for me (and others). Some have had difficulty setting it up (see the Hue area in the forums for that discussion). It works and is a simple free version that allows you to incorporate the automation in the ISY world rather than the "simple"/basic (but functional) automation within the Hue app. Now...what do you want to do with it? Well, I use the Ring plugin and my Hue plugin to turn lights on when the (Ring) doorbell rings. Here's my simple program: ~Door-Ring - [ID 0058][Parent 0052] If '~NodeServers / ~Ring / ~Fr_door' is switched Ding Then Set '~NodeServers / ~Hue / Couch' On Wait 5 minutes Set '~NodeServers / ~Hue / Couch' Off Else - No Actions - (To add one, press 'Action') There's unlimited possibilities for what people can do with plugins. The trick is trying to figure out what you want to do then just sorting out the best way to achieve that. I just wanted a way to visually alert anybody inside the house that the doorbell was pressed. I have different programs for if it's rung in the middle of the night and also have a trigger on a different Ring unit (flood light cam) if it's triggered in the middle of the night. I haven't used the Bluetooth plugin yet so I can't help with that one. But I know there was a lot of discussion about it somewhere...it looks like kind of limited discussion in that part of the forums though: https://forum.universal-devices.com/forum/441-bluetooth/. I recall @Techman seemed to do a good bit with that plugin. Maybe start a thread in the Bluetooth area asking about use and setup if you need/want specific help with that plugin.

In theory I think this is accurate. It seems in current IoX it would be enabled (at least evaluated) at startup, but might not rely on having that option selected (on) in the summary window. At least based on the old (trusty?) ISY cookbook it includes this information for reference: (Source: ISY Cookbook page 183 - Section 9.5.5 - bold added for attention) It seems that it's more as @Guy Lavoie points out to set a default level or a variable setting. I think some have created a program for a timer since last reboot or something that if the device restarts in the middle of the day their timer needs to be adjusted to be correct for other programs to trigger. But I see it more as a way to trigger a single time occurrence that might have happened while the device was off. I don't have any specific examples for my system as most of my "timed" events are set as "from/to" times (i.e. sunset to sunrise). If the device restarts those programs do get evaluated and run based on the IF portion.

Interesting. I thought others commented that after update it did properly update the plugin. I know @Panda88 said in another post that he's traveling so might not get a reply from him right away, but sure he or somebody will post about their update story. Perhaps try a power cycle of the device, but if you don't want to then hang on until @Panda88 can give feedback. I might suggest changing the log type to "debug" then perform an update process then maybe a plugin restart to catch any errors. Allow a few minutes for the plugin to stabilize then download the log package. PM the log info to @Panda88 in order to possibly give more data points to review. (Be sure to change the log level back to info or warning.)

@TJF1960 what device are you running and what Firmware are you currently running? There were some earlier posts that 5.8.1 and some underlying PG3x versions were having issues updating. Those seemed to have been fixed in 5.9.1 release and device OS update, but not sure what device you're running on to just suggest updating to get this to update. Also, are you sure it's 1.0.15? I think you might mean 1.4.15. That's showing the current version on the Polyglot page. My eisy is currently running 1.2.7 of the YoLink plugin. I tried an update earlier and it won't go. I haven't yet updated to 5.9.1.

More than likely something else. You say the power light is on, but is it really bright? It could be that your power supply has failed. Please review the wiki: https://wiki.universal-devices.com/Main_Page#Front_Panel_LEDs/Lights You commented on a lot of computer stuff. Sounds like you're not able to get into admin console. I'd try a new power supply and the rest should be okay. Doesn't appear that you've loaded an odd Java version and as long as you don't change the default program to open .jnlp files (should be javaws.exe - found in the "bin" directory of the current version). The address is usually stored in a "cache" (.state) file elsewhere on the computer so it might be loading that address even though the ISY994 wouldn't be connected. (Just an assumption, I've never attempted this to prove it) There are .state files (see wiki reference) that can be removed manually, but do not think this has anything to do with your current status. Just mentioned as reference to this comment you made.

There was an update to the beta a few days ago (I forget when it came out). Not sure if/when it will hit production release. I'm not sure the process to get the beta version now, but needs Testflight from Apple. There was a post elsewhere that I think had the process. I use the beta version so not keeping up when official releases are available. Reports (other posts on the forums) are that the beta version has the Matter option.

@dgwete % is "%25" in HTML. %C2%B0 = degree symbol (the % are (probably) spaces) Is there a reason you haven't updated the eisy in ages? 5.4.5 is from 2022 and didn't appear to have an official release notice (from the prior versions area). Step one in most support cases would be to upgrade to current firmware. Many "bugs" and issues are fixed along the way.

@nlaredo this was something discussed about a year ago. I know a lot of people seemed to jump on it when first "announced", but not sure how many are doing it currently. And the recent update on Polisy/eisy might have changed things so be careful how you proceed. Old post with information of how to do this midway through the topic.

@mrxmas what OS are you running on your laptop? If on Windows you just need to set what program is associated with the .jnlp file. Also, be sure you're just installing the "basic"/current version from java.com (currently showing as Version 8 Update 441 as of today). Don't get any different version a higher number is better. You want the .jnlp to open with javaws.exe (usually found in: C:\Program Files\Java\jre1.8.0_441\bin) [NOTE: the jre1.8.0_441 directory is the current installed version] I'm running Windows 10. It could be in a different spot in Win11, but doubtful. Not sure about non-windows machines.

@GHenry re-launch Admin Console and try again. I just logged into a 5.9.1. system and it did work for me. What version Java are you running? What is the exact firmware/UI on the Help -> About screen? (oddly enough for me first time I've noticed this that the time stamps for UI and Firmware don't match for the system I logged into)

@Tmc first off I'm impressed that your PLM lasted 18 years. That's amazing! I'm confused as to your question. Is that looking at the link table in the OLD PLM or the new PLM? When did you remove the 2334-232 from IoX? I wonder if it's possible for the PLM to keep old devices for a period of time. Somebody with a lot more knowledge of when and how information is written to the PLM will need to answer this. Would certainly be a risk of having a lot of orphaned links in the PLM if a lot of devices are deleted but never actually removed from the PLM links. I wonder if you have the new PLM connected and made a current backup of your IoX system then restored it would that overwrite any links in the PLM? Interesting situation you have posed. Hopefully others have information to give light on what is expected. (oh, and moved this out of Insteon area into IoX area since it's more relative to IoX level of discussion.)

@drprm1 do you already have 5.9.1? Not sure how you'd have the OS 14.1 if not part of the 5.9.1 update. I know some were reporting having 5.9 recently, but wasn't sure if it was completely released in the wild yet. So it's possible you might already have 5.9 and just need to run updates to get to 5.9.1. However, since you've got 14.1 then I'd run it to get the IoX Firmware and possibly any PG3x updates applied. Let us know how the update process goes...maybe time it too. Hopefully running on an eisy.

@BRMeeke from the wiki about the power supply: (Source: https://wiki.universal-devices.com/Main_Page#Front_Panel_LEDs/Lights)

I would suggest that anybody rushing to upgrade make sure to pay attention to the "Before You Start" section in the release notes: BEFORE YOU START 1. It's imperative that you take a backup of your IoX, Z-Wave, and PG3 settings. 2. This upgrade is upgrading your OS. As such, the unit will reboot in the process and the Admin Console will simply get disconnected (does not close). Please do not turn off the unit till you can get back to the Admin Console. 3. If you have never upgraded your unit, it's best to make sure you have release 13.1 or 13.2 of the OS (https://eisy.local:8443/WEB/sysconfig.txt). If you do not, please do not upgrade. 4. In order to get Matter supported on WiFi, we had to change WiFi settings so that it will now use 802.11a/g which is significantly slower than 802.11ac that you are used to. Although you won't see much impact for command/control, download speeds for local Admin Console will be slower. It's our top priority to get WiFi back to the ac range you are used to. -- Polisy does not support Matter when connected using WiFi. Bold and red added for attention. As of now I'm not sure how you could get to 13.1 or 13.2 of the OS before getting this upgrade.

I’d still try a different network cable. Just a random attempt.

@dex be sure that your portal license is still valid and hasn't expired. Login to the web portal then: Select Tools -> Information -> ISY Portal Access License @bwdavis7 Keep us posted on if there is any additional information on the support ticket. @inovermyhead not sure if a plugin could cause this. Doubtful, but if something is sending a lot of information to the log it could cause problems. I recall that being an issue early on, but think it's been resolved in recent updates to PG3x. It would be good to doublecheck that you don't have plugins set to debug log level. It's fine to leave them at "info" or "warning" until you're in a need to troubleshoot specific plugins. Again, there was something along the way that I thought PG3x will default a plugin log mode to "info", but can't be sure that's still the case. Just check each plugin and the log levels to be sure. The portal maintenance was 1/30. So if you started having issues 2/1 (or later) it probably isn't directly related. Though if they go back before that time it's also more than likely a different issue. Last ditch option for those that have them hard wired to the router would be to use a different network cable and a different port on the router/hub it's connected to.

@inovermyhead @Jimini @flsenior @Ross @bwdavis7 There was a portal maintenance post a few days ago. Have any of you performed a full power cycle since that maintenance? I wonder if maybe some devices didn’t reconnect correctly and are dropping randomly trying to update or properly reconnect. I would suggest making sure all devices are up to date and power cycle (either by button push to reboot or power down and completely pull the power supply doe 20-30 seconds). HOWEVER, by being “up to date” I’m not suggesting randomly pushing the update packages button. There were reports of an update out, but there have been some that had issue with that so DO NOT just push the update button. Go here: https://eisy.local:8443/WEB/sysconfig.txt (Or replace “eisy.local” with the device IP) Also check here: https://eisy.local:8443/WEB/pkg.upgrade.htm (Again, might need to replace “eisy.local” with the device IP) looking for something like: (for eisy/Polisy) udx-3.5.8 isy-5.8.4 pg3x-3.2.27 If you’re devices are current and you have performed a power cycle and still getting disconnects please open a support ticket with UD and see if they can narrow down the issue. Please post back any results from the support ticket to help others having this issue. https://www.universal-devices.com/my-tickets

Seems that you’ve isolated a concern. I wonder if there is any internal log that UD might have when devices connect. I’d go back to the support ticket and work with them some more. Might be something @bmercier would need to be monitoring at the time of connection.

@raydoc did you try migrating the portal to the new eisy? https://wiki.universal-devices.com/ISY_Portal_Migrate_configurations_to_a_new_ISY From step 9 of the migration process found here: https://wiki.universal-devices.com/Eisy:User_Guide#Migrating

@johnstonf as best as I can tell there is no direct migration path if you have the series 300 Z-Wave controller. The Wiki states for 500 series and an updated news/blog headline said earlier versions of ISY994 firmware “and don’t have any Z-Wave devices”. How many Z-Wave devices do you have? It sounds like you might have to reset everything. I will make a simple suggestion in your migration process…. Be sure to copy ALL PROGRAMS to a text file for reference. Especially since you’ll be setting up Z-Wave new. Right click on the root folder of the program tree and select “Copy Folder to Clipboard” then paste to a text editor (not a word processing program/app).