Geddy

@wmcneil Since you have a ticket open you would need to reply to the existing ticket to possibly make it active again or to bring it to the queue again. It's been stated many times in the last couple of years that the forums are user-to-user support. Yes, UD might monitor the forums and answer questions that are easily answered, but for more involved support it's best to run through the support ticket process.

Do you leave admin console open 24/7? Typically the data does not refresh if Admin Console is open. If you close and relaunch admin console it might update. Are the correct percentages shown on the PG3x node levels? If so then it's working as expected. Admin Console refreshes nodes and data on launch or manual refresh (as you seem to indicate). It's not a "live" system. At least not that I've experienced. Also note that admin console is not designed to be left open 24/7. It's meant to only run when actively changing/programing IoX. Make your changes...close admin console.

It doesn't appear this plugin is supported any more. There have been other posts in this area of issues getting through discovery or updating nodes and status. I think most have either moved away from this alarm panel type or not linking it to IoX.

F5 is a browser refresh (for Windows). For the Mac use Command + R. Might even need to try a "hard refresh" - for the Mac that's Command + Shift + R.

Dang! 1000°F is insane! Good luck!

@abrayshaw (split your post out of a resolved topic that had no activity for 4 months so you might get more attention to your situation.) First off, please confirm you're running ISY994. Let us know (if you can) what Firmware and UI you are running. I realize that if you can't get into admin console (to get the UI), but if you're seeing the ISY on launcher it should say what Firmware the device is running. Did you select all three boxes in this process? The 3rd box clears the installed IoX Launcher icon from the Windows desktop. You'll need to download a new start.jnlp from the UD website to put the icon back on the desktop. Alternate method would be to download the admin.jnlp file directly from the ISY (web browser go to: http://ip.address.of.isy/admin.jnlp). Last question: What computer OS are you using? Windows, MacOS, other Make sure you've got "plain" java downloaded directly from java.com and not a special version or higher version than just downloading from java.com (showing current as of today: Version 8 Update 441).

@PapaBear just out of curiosity, what firmware are you on now (after running the "upgrade packages")? Glad they got you sorted out.

Can't help with the specific application and certainly not programming, but have you considered something like a YoLink monitor with the cable attachment? https://shop.yosmart.com/collections/smart-sensors/products/ys8004?_pos=1&_fid=4068542a8&_ss=c Not sure what your temps are reaching where you are trying to measure, but this seems to handle up to 200°F+ (the "sensor" operating range only up to 158°F, but alerts up to 221°F). Then getting the YoLink plugin to get alerts and other automation with the IoX system. I know a lot of members here (myself included) use the YoLink products (and the plugin) for other general monitoring and other product inclusion with the IoX system. Worth looking into.

As @paulbates indicated I had heard that the i3 were smaller switches making it easier to install in multi-gang locations. The switch you're talking about might be different than the single paddle/outlet design. Glad it seems you were able to get the device renamed in IoX with a restart. But that's still tricky. You might want to open a ticket with UD to get that clarified for if it's a "known" (or unknown) bug with the i3 line. I recall @Michel Kohanim commenting that the "new" Insteon was willing to work with UD and they were working with them to support the i3 line better and fully. Don't recall other issues mentioned in the past so might be a new bug or perhaps something with that device family.

Thanks for the warning. Hopefully there's a "fix" in the works for this. With your ticket are you just sending the eisy back or are they helping sort things out to get it operational and able to setup Z-wave again?

@flsenior the eisy is just like the former ISY994 (or older) devices. If you've set them up before they would work nearly identical with the eisy. Since you've been registered here since 2011 I'll assume you're coming from another ISY device. If an existing install probably very little should need setting up. However, if this is a new install then you will be starting from scratch and you'll be able to setup what works best for your situation. You can always download and review the (old) ISY Cookbook (found in the wiki: https://wiki.universal-devices.com/Main_Page#ISY_Cookbook). I'll just caution you that the cookbook was written a while back pre ISY 5.x firmware so some things have changed (scenes mostly). I'm not sure if the wiki scene portion has been updated to 5.x setup, but review the wiki and then program and adjust as best fits your needs. Personal preference. Are you controlling the devices at the same time or various times of the day? If at the same time then make a scene. Are you trying to brighten or dim devices (use programs to adjust the scene) I'm not 100% sure on this one. All my 3-way are using the same type of device. I would need to have somebody else chime in for actual use case on this. I think the question might be do you want to be able to dim the devices? If so I'd say put a dimmer on each side of this. If you're just doing on/off then maybe either would work, but again, not 100% so don't risk it. I'd just make them the same type of device. 3-way will be a scene. There is a way you could control with a program, but the suggested way would be scene. (the Cookbook might help answer some of your questions) Review the cookbook. Make both controllers so they would both show "on" when the other was flipped on. I'm not sure I understand what you mean by "main eisy scene". One difference from ISY 4.x to 5.x was the loss of "copy scene attributes" (or whatever it was called). This was due to the inclusion of Z-Wave certification. If you mean for the scene properties when you click on the scene name in the device tree you should set the device properties there, but I think it also needs to be applied at the device level. I don't use scenes much beyond 3-way handling for halls and stairs so a more experienced user with scene skills would need to chime in to help. But through reading the cookbook and setting things up I'm sure you'll get the hang of it after adding a scene or two. Just remember if you turn the scene on using admin console it might be different than physically operating a switch so test at both levels as you setup. Be sure to review the wiki for a lot of details: https://wiki.universal-devices.com/Main_Page#

@Illusion have you tried refreshing the page? Just hit F5 and see if that refreshes it to show a more accurate time. Otherwise, I'd not worry about it too much. Not that impactful (IMO).

@larryllix no, based on the comment before the quoted section… I took that as though @CoolToys was trying to set a static IP on the eisy. Good luck with your adventures and getting things sorted out. I try to keep a spreadsheet of MAC and IP reservations, but I don’t usually reserve more than a dozen items.

@hec FYI the last PDF “screenshot” shows the program tab, but those are NOT exclamation marks. That’s standard program colors. Please refer to the wiki information here: https://wiki.universal-devices.com/ISY_Programs:Icon_Colors Seems like you’re on the hunt for possible PLM issues. Have you opened a support ticket yet? I think it might be fixable with some help from UD support. At the very least they could probably confirm if it’s a PLM issue or not.

Please see my last comment. Open a support ticket. You’ve done everything us users would usually suggest so now you need to get help directly from UD. Please post back how this is resolved to help us and others.

Been that since eisy was released. UD had so many support issues with people setting static on the ISY994 that they seemed to disable it in a Polisy update and since eisy release. It’s best to reserve the IP at the router level. Has been the suggested process for many years.

Thanks for confirming they match. I haven't seen any (many) mention they're on 5.9.1. Is this a newly received eisy? I would open a support ticket with UD to get direct help with this. As @apostolakisl mentions I don't recall seeing ! on the program page. Only on the device page. Will you share a screen shot of the program tree? (Again, please only post as an image. Maybe MacOS can't do that, but try your best.) Open a support ticket here: https://www.universal-devices.com/my-tickets Please update us with the resolution from support so that we can learn and possibly help others should they run into this issue in the future.

FYI your “screenshot” is a PDF. Better to upload as image as it’s difficult to open/view PDFs on the forums on mobile devices. Your topic mentions programs having red exclamation mark, but do you mean devices? Not familiar with programs having this appearance. The restore modem might have messed you up a little. If a program is saying it cannot communicate then make sure your Firmware and UI match exactly. What Firmware (and UI) are you running? I would suggest restoring the backup again. Then if it really is a program issue open the first program. Make an adjustment then hit SAVE for the programs. Then change it back and hit save again. If you really mean devices aren’t responding be sure that Insteon is checked on the Configuration tab.

@andrewherman please let us know what version firmware and UI is showing in admin console help -> about. Please give actual version numbers (make sure they match). Also let us know what version of PG3x you’re running. be sure that you have closed admin console and relaunched it (plugin nodes only load on launch so if you kept admin console open while manipulating in PG3x it hasn’t updated correctly. Log into the UD Portal and confirm PG3 remote connection is active. Select Tools -> PG3 -> Remote Connection Last thing….do you happen to remember what version firmware or PG3x you were running before the update? I forget when the process to reinstall plugins needed to run, but that might be something if it was “really” old version. It might be best if you open a support ticket with UD to get specific help if you don’t get this resolved by the reboots or reinstalling the plugins as you described to have done. https://www.universal-devices.com/my-tickets

When you log in next look at the Programs tab and "Summary". Do you have any programs stuck in a loop? Aside from what @paulbates suggested for allocated memory (referenced in the wiki) given that your system has 12GB ram it should be zippy. I might up the number that @paulbates suggests to "1024m". Some have found setting the min and the max (to the same number) also might help. I haven't adjusted this in a long time so think Java might be playing better with IoX Launcher/Finder, but if you have a large system it could be bogging down based on the memory being provided to Java. -Xms = selects the initial memory allocated -Xmx = selects the maximum that can be allocated.

I've got my Z-Matter dongle connected with a standard USB Extension cable of about 3 feet (similar to this one: https://www.amazon.com/Monoprice-3-Feet-Female-Extension-105432/dp/B002KKZAIU/). I've had it this way for the last couple of years just to get the device mounted on the back of my equipment cabinet to be away from the case or other metal cases in the cabinet I have network and other electronics in. I have a few Z-Wave devices and a few Zigbee devices and can't remember a time that they were unreachable or noticed the dongle to not be connected. It has happened, but not often enough for me to worry about it. Usually a reboot/power cycle of the eisy brought things right back. Honestly, for the first 6 months or so of having the eisy+Z-Matter it was directly connected to it. I only added the extender as a precaution to remove the weight off the device directly, but also to put the antenna more in the "open". I believe there were a lot of comments about running USB Extension cables a couple of years ago(maybe when Polisy came out, but again when eisy was released). Might find those posts using Google Site Search since forum search won't find archived topics.

First off...for future reference the preferred method for posting programs to the forum is to right click the program, select "copy to clipboard" (be sure you select the last item of "COPY", then paste the text into the forum post. This makes it easier for people to edit or comment on rather than a picture. Now, have you thought about removing the else? I would make a 2nd program that has a wait or is based on the micro module status to then turn the lights out. To me (not knowing what is controlling the variable) it sounds like you're opening then closing the door so the lights are coming on and going off due to the status of your variable. Removing the "ELSE" (turning lights off) will leave the lights on after the door is closed and whatever you're doing with the scene for "Path Lights" will remain on. The 2nd program would make a wait timer or even look at the trigger for the micro module to turn the scene off at a later time. Post the program(s) setting the "$sRearDoorOpen" value. Based on what you posted I expect that the program is changing to false when you're outside and causing the path lights to go out (the ELSE statement). You're then triggering them on with the motion sensor (not Insteon), but because the program above is still FALSE it's causing the ELSE to trigger again. Thus just flashing your lights. Remove the "ELSE" and test the result.

Not me. I guess my question is why is this necessary (why are you doing this)? My outlook on notifications is more for if something doesn't happen that results in an urgent situation (like a water leak or CO sensor alarm). My thought is if I get notifications all the time that I (personally) would tend to disregard the notifications and therefore potentially miss an urgent alert. I don't worry when lights turn on (or off). I just care if there is really an urgent situation that I should be notified about that would alarm me and mean I should look into the situation.

Not possible. Either you migrate the entire ISY994 system to the eisy or you start from scratch and link and build scenes in the new eisy.

@tpventure welcome to the UD forums. Sorry you're having difficulty. What computer OS are you running? IoX Admin Console is developed to best run with the standard Java version downloaded from java.com (currently Version 8 Update 441 updated January 21, 2025). If you're on Windows (or sometimes MacOS) your best bet would be to remove all versions of Java and download directly from java.com for your operating system. In Windows you will need to make sure that start.jnlp is associated with Java Web Launcher (javaws.exe), which is typically found in the Java/(version)/bin directory (for Windows anyway). The eisy/IoX Launcher is exactly the same as the ISY Launcher that you probably used with the ISY994 if you've accessed the admin console since 2018. If you continue to have problems with the start.jnlp you can attempt the direct connection method of getting the admin.jnlp (http://eisy.local:8080/admin.jnlp - if doesn't resolve .local replace "eisy.local" with your eisy IP address) from the eisy, but it seems that you're using a different java platform to access it and it's not loading properly. Resolving that should get you back up and running with Admin Console.