Geddy

@buckeyebez welcome to the forums! This could be a couple of issues. Let’s check the UI and Firmware version in the “Help” -> “About” screen. Please make sure they match. The current IoX Firmware for the eisy is 5.7.1. Next, check this section of the Wiki to set a higher memory cap for Java. https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_is_very_slow_or_hangs Depending on your system you could probably go up to 1024 or even higher if you have a very high memory based system, but most don’t need much more than 1024. It is strange that you seem to imply that the programs are there, but then disappear after loading a few Z-Wave devices. I know there were some high traffic devices identified earlier this year (I don’t know which ones). Perhaps the devices you are using are very high traffic and could be bogging down the system display. I’m not 100% sure that’s even possible, but a SWAG if the above two things aren’t a fix. Have you attempted a Java cache clearing (remove temporary files) be sure to check all 3 boxes in that process? Download a new start.jnlp (from UDI’s site and clicking on “My ISY” on the top right), Running that to get a fresh IoX Launcher. Are you running any firewall or anti-virus programs? What computer OS are you using?

I had already moved it. No worries.

@phawtrey not entirely sure why you hid this in the Brultech Energy Meters area. Moved to eisy since it didn't seem to have anything to do with where you posted it. No, this is not possible. Insteon devices can only have one controller. With the Polisy or eisy you have 1 PLM to communicate to the devices. So only one controller can/should be used at a time. It's entirely possible to have a PLM for each system, but you could only link devices to one PLM at a time. So some devices could be linked to the Polisy and the others to eisy. Kind of awkward, but if you're up for a lot of work keeping things straight go for it. You run a risk of having 2 PLMs sending out power line signals getting crossed and missed since sometimes Insteon signals can become corrupt with a small amount of noise.

@bmercier it was my understanding a past update made the log change back to "info" so it wouldn't load up the log when users leave it in debug mode or other overly active mode. The problem at the time was that logs were filling up and causing issues by being so large and then being swapped out and losing 24 hour period of logging. Only going from memory as to why it was changed previously. I think @bpwwer made that change so might have the reason behind that choice.

Are you sure you're adding devices correctly to the Alexa connection? To have Alexa find them (and learn the spoken names) they have to be added via the UD Portal site: https://my.isy.io/index.htm Click on Tools -> Connectivity -> Amazon Echo Then in that screen you have to add devices or other items. Then Alexa will find them the next time you command: "*wake-word* discover devices". You keep saying you put a spoken in the notes on admin console and somehow it shows up in Alexa. I've never attempted that, but I have a lot of devices connected through the portal and never have issues with it finding or controlling. You should review the wiki for setting up Echo and Portal. https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3 Make sure when you're on the Portal and adding devices to the Echo "device list" your UUID should match the device you're using. If you have multiple devices you need to select the primary device in the profile setting in UD Portal.

Here is what UDI has published for power supplies for ISY994: https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights

@david-4 sounds like it's stuck and a power cycle would reset everything. Try the multi-function button to shutdown the device. If it doesn't properly shut down within 60 seconds of pushing the button then pull the power supply. Look for the User Guide for your device in the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Online_Documentation It should NOT take longer than a few minutes to reboot and shouldn't get stuck in a loop like that. When you said the Z-Wave menu shows not connected that means the IoX service didn't restart properly and it's stuck. If you still have issues after a power cycle please open a support ticket with UDI for them to review the situation. Good luck! Post back an update once resolved.

@david-4 what IoX firmware are you running? Should be able to tell from the IoX Finder window (don't need to be all the way in admin console if it's locking up). Is all you did was enable Zigbee checkbox and it's in this loop?

@SteveT1 Welcome to the Universal Devices forums. Sounds like a pickle and hopefully this helps some... This is an image of an Insteon hub: What Universal Devices supplies works with Insteon switches and a wide range of other products. They are not related to Insteon. Universal has several hub options. ISY994 (now discontinued and out of (free) support window) Polisy/Polisy Pro eisy Those are the hubs you might find if the prior owner left a hub. From the description you're giving it doesn't sound like they did. When an Insteon device cannot communicate to a hub or other devices it will flash red. Insteon switches without a hub present are just like "dumb" switches however, if the prior owner made direct links in them a single switch could control other devices. The best option would be to take the faceplate off the switches and see if you see an Insteon sticker. Most of the time it's been on the silver tab at the top of the switch. Should like similar to this: From there it has the model number on it. You might be able to find the user manual for the model(s) you have in a Google Search. Look for a factory reset method. The typical reset might be: Pull the set button found at the bottom of the switch sometimes you might need a small flat blade screwdriver to pull away from the wall Wait about 10 seconds Push in and HOLD the set button until the long beep stops again, might need to press it in with the screwdriver to keep it pressed in Release the set button Device should beep (and/or double beep) This removes any programming in the switch. The light might still blink red, but I don't think it would. It's been a while since I reset a device and tried to operate it without a controller. It's very easy to remove. It's just a switch. The "smart" portion of it would be controlled by an Insteon Hub or by another controller (like the Universal Devices options). The issue would be removing a switch that doesn't have a load just putting a dumb switch in wouldn't do anything either. At that point you would need an electrician or electrical tools to figure out where the wires went and what lights, plugs, or other things they controlled. You have 2 options...after resetting every switch keep them as "dumb" switches where they are or replace with other "dumb" switches. Since you said it's an older system some old Insteon switches were just on/off switches, but had a light rail along the side. They wouldn't act as dimmers and if you press too long think they go into pairing mode. That might be why some might not work now if held too long. Maybe after a factory reset they would operate whatever is connected to their load (if anything). Since Insteon switches could be a smart controlled system they were easy to put somewhere that typical wiring wasn't available and could be linked to control something anywhere in the house. Sadly, without the hub to tell it what to turn on it's not working as the original owner programmed it to. Finally, if you're interested in learning how to make them smart then take a look at the following sites: https://www.insteon.com/ - This is the company that manufactures the switches/outlets/hubs https://www.universal-devices.com/ - The company related to these forums that makes and sells the current hub called the "eisy" that runs Insteon and has an adaptor for handling Z-Wave and Zigbee (with future support for Matter) as well as a whole list of plugins for other home automation programming under one roof. http://wiki.universal-devices.com/index.php?title=Main_Page - the Wiki for the Universal Devices offering Lastly: since these are old devices as you said they appear to be "Smartlab" devices. That's the old parent company for Insteon. They went out of business a last year. However, the Insteon name (and company) was revived by new owners (some former employees) and is back in business supplying some of the same devices, but also a new line of options. Hope this helps! Feel free to post if you have more questions or issues getting devices reset. As far as help directly from Insteon you could contact them through their website (linked above).

Yeah, seems either bad PLM or maybe a bad cable since still didn’t connect after power cycling. Only other suggestion would be to try to factory reset the PLM and see if it would connect. Do you still have the ISY994? I might suggest connecting to that to see if it sees it with a standard network cable. If so that would point to bad cable. If not then points back to bad PLM. How old is the PLM? There should be a date code on the sticker on the back. Good luck

@TMcCarthy I’m only on a mobile device so can’t download/view your attachment. Sounds like could be PLM issue. First, please backup the current IoX system to have a current backup. How recently have you made a backup otherwise? What do you get when you click on Tools / Diagnostics / PLM Status Info? if that shows connected look up PLM Link Tables (note, this isn’t just counting them as that number can change with any activity during the count). Mainly you want to see that it’s not empty. An empty link table could suggest the PLM is bad. When you can perform a power cycle of the eisy also power cycle the PLM. Be sure to plug the PLM in first and allow it a few seconds to initialize. Then plug in the eisy and allow it time to fully boot. Make sure the PLM isn’t on a UPS or power strip. If you have other “noise” producing devices plugged in nearby remove them. Maybe try the PLM on a different circuit in the house. Lastly, how is the PLM connected to the eisy? Only USB connections are available for the PLM. What wires are being used to connect the PLM? If a USB type PLM all good. if Serial what adapters are you using to connect to USB? Next I would suggest opening a support ticket with UDI if there is other troubleshooting they can suggest.

@TMcCarthy Open the Event Viewer (Tools -> Diagnostics -> Event Viewer) In Event Viewer window press "Clear" on the bottom left. Then set "Level" to "3. Device Communications events" Drag that window to the side a little bit. Click on a device and control it from admin console (turning it on or off - depending on it's current state). You should see something similar come through the Event Viewer: Fri 11/10/2023 03:07:06 PM : [INST-TX-I1 ] 02 62 46 0D F9 0F 11 FF Fri 11/10/2023 03:07:06 PM : [INST-ACK ] 02 62 46.0D.F9 0F 11 FF 06 LTONRR (FF) Fri 11/10/2023 03:07:06 PM : [INST-SRX ] 02 50 46.0D.F9 44.D1.80 2F 11 FF LTONRR (FF) Fri 11/10/2023 03:07:06 PM : [Std-Direct Ack] 46.0D.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 11/10/2023 03:07:06 PM : [D2D EVENT ] Event [46 D F9 1] [ST] [255] uom=100 prec=0 Fri 11/10/2023 03:07:06 PM : [46 D F9 1 ] ST 255 (uom=100 prec=0) You're looking for the "ACK" and "SRX" lines to know if the PLM is communicating. Would you please post what Firmware you're on for IoX? Also, go to link below when local to your eisy and post the ISY- version info. https://eisy.local:8443/WEB/sysconfig.txt (If you get a security warning that's fine, click advanced and proceed) Look for: isy-5.7.0_5 Name : isy Version : 5.7.0_5 If you're on 5.7.0 and not "_5" please be sure to run the "Upgrade Packages" process and perform a full power cycle of the device. Allow the device to fully update - leave any alert windows open in the process. You should receive a "update complete please reboot" type of message. Rather than pressing reboot on admin console please perform a full power shutdown: Press the power button 6 times Blue light should turn red after about 30-60 seconds Unplug device Wait 20-30 seconds Plugin device Wait 2-5 minutes for the device to fully boot and be functional. Now try to access the admin console and try controlling devices again. If still unable to control devices please open a support ticket with UDI for them to help further. https://www.universal-devices.com/my-tickets

Make sure you put an IP reservation in the modem (or whatever is handling DHCP) so it doesn't move if/when the modem reboots.

@trevorst The IP has to be added to the plugin in a strange (unexpected) format with square bracket and quotes. KEY = bridges Value = ["#.#.#.#"] (MUST include the square bracket AND the quotes!) "Failed to read bridges variable" means it didn't connect properly. Now I forget if I had to pres the hub button or not, but I'm fairly certain it might still be needed. Make sure you press "restart" on the plugin then within a few moments can press the button on the hue hub. Once you get success make sure you restart the node server and also restart Admin Console (if you have it open - please note it's always best practice not to have both Admin Console AND PG3x web interface open at the same time. Admin Console only receives changes/update when reloaded. If you're making changes in PG3x always re-launch admin console (if you had it open) for the changes to show up on the IoX side. I always suggest people not have both open so you don't forget that step!) If you're unable to get it configured please open a support ticket with UDI to see what other tricks/tips they might have for getting this resolved. https://www.universal-devices.com/my-tickets Just looking at my Hue setup realized that I don't have the IP address coded in the PG3x version. I ran Hue under PG2 on a Polisy, but when I changed to the eisy think it setup correctly and I've got a reserved IP for the Hue bridge. I wonder if you could delete the plugin and reinstall if it might connect without forcing the IP as a custom parameter. I know in the old PG2 there was an issue with the plugin storing the IP somewhere and it always looked at the old IP for it even though I did have it move (like you I replaced a router with a different DHCP table).

@Bob Amott This means you're running an old version of the IoX Launcher. To fix: Close admin console Clear your java cache (temporary internet files) Delete all old start.jnlp files from your system Download a NEW start.jnlp file from the UDI website (clicking "My ISY" on the top right) Run start.jnlp to add the IoX Launcher back to your desktop Several months ago a bug was introduced into the start.jnlp code, but was fixed almost immediately. The 2 addresses are fine, and not an issue. UDI even confirmed this is "normal" and expected, but it has caused some to be concerned. It randomly happens. Because both addresses are "found" they cannot be deleted. Either can be used interchangeably to connect to your device as they are the same device. Also, if you haven't run an 'update packages" lately please do so to be sure you are at the current versions for PG3x and IoX. There were bugs in early IoX 5.7.0 that have been fixed, but no "official" post/announcement was made (it was posted in the support thread). Browse to this page: https://eisy.local:8443/WEB/sysconfig.txt (if you get an alert for it not being secure click on advanced and proceed to page) Search the page for "isy-5.7.0" and see what you have after the .0. Looking for _5 (as of this posting). Should see it showing as: isy-5.7.0_5 Name : isy Version : 5.7.0_5

This still sounds like your file association is not correct (as I stated before) Also, please stop posting screen shots as PDFs. You can paste images directly into the post. When viewing the site on a mobile device there's no way to download then view the PDF so posting the image directly in the body of your post is 1000x more helpful. First, lets make sure Java is setup to run "Web Start" applications. Open the Java control panel and click on "Security" tab. Make sure the top checkbox is checked. Once confirmed that is enabled, check this that start.jnlp is associated with Java Web Launcher. Wherever you downloaded the start.jnlp make sure it appear like this in the explorer window: If it doesn't then it's probably not assigned to be opened with Java Web Launcher. Right click and open properties. This is how it should look on the general tab. If not click on "Change". Usually (if Java was installed correctly) you should see a Java option available when you click on "Change" as a selection in this window: If not you need to click "More Apps", scroll down to the bottom of the list and select "Look for another app on this PC". Then then look for javaws.exe in the Java\jre-1.8\bin directory of your programs file (if running 32bit Java it will be in the Program Files x86 folder. Now, if that association doesn't fix your problem, and you've cleared java cache by clicking all three boxes... Then, as @larryllix suggested, you might need to forcefully remove IoX Launcher from the Java Cache. To do that, open the Java Control Panel and click View (on the General tab). It will open this window: If you've gone through these steps and all the steps posted above and it still doesn't work...please open a support ticket and see if UDI can help you get this corrected. https://www.universal-devices.com/my-tickets PS: Changing the router has ZERO impact on Java not working/opening start.jnlp file to put the IoX Launcher icon on the desktop. It would 100% impact your ability to find the device if it was an old ISY994 that you set to a static IP in your old router DHCP table, but it sounds like the device is able to get on the network since you can control it with mobile apps. What does this mean? If you can't get the IoX Launcher/IoX Finder to run how is everything working fine with Portal? Do you mean that you can just log into my.isy.io and it appears that your device is online?

@trevorst I see you posted here too! More than likely the hub is at a different IP address. If you have the same DHCP range try to make a reservation for the hub where it was before. If you cannot, then code the bridge IP and restart the node server then press the button on the hub. It “should” discover again that way. In Hue screen in the plugin store there should be a “more info” button to see how to code the hub IP address in the settings of the plugin.

When is the “unable to launch application” happening? If you’ve successfully installed Java then it sounds like an association might have been broken. What computer OS are you using? (If Windows what version?) What version Java have you installed? The IoX Launcher is designed to work with the standard version downloaded from Java.com (currently Version 8 Update 391). If on Windows you might need to go to default programs (in Windows settings) or once you download a new “start.jnlp” right click on it then properties and see what it has for “open with”. If you’re on macOS there are some settings to adjust that the system should prompt you for. I don’t use macOS so can’t fully help, but know others have posted this fix on the forums.

Like this: https://forum.universal-devices.com/forum/432-tasmota/

@KHouse for future reference it's easier to post a program to the forums as text. To do so: Right click on the program Select "Copy to Clipboard" Paste as text. This does 2 things. 1) makes the program searchable in case it's a program that others are attempting in the future. 2) allows anybody helping you make the modification(s) to help explain how to fix the program. In addition to what @Techman suggested is the switch you're checking for "on" a dimmer? If that's the case maybe make it "Status NOT off". That way if it's at 50% the status would be "not off" and at 9pm would turn it off. This is a test program I just made and confirm it worked and looks like what you're attempting: Office_test If Time is 8:43:00PM And 'Office' Status is not Off Then Set 'Office' Off Else - No Actions - (To add one, press 'Action')

Try accessing Polyglot from a different browser. If that doesn't work, I recall another user recently that had a similar problem. If I recall they did the following: login to https://eisy.local:3000 go to System | Switch Portal Profile then login (to the portal) Screen will refresh back to Polyglot click the Logout button (polyglot web access - top right) Log back in

Just made a program like this on my eisy. Test-PaulBates If Time is Sunset - 30 minutes Then Set 'Backdoor' On Else - No Actions - (To add one, press 'Action') isy-5.7.0_5 Name : isy Version : 5.7.0_5 I even closed admin console and re-launched to be sure display wasn't frozen and it still shows as expected to run 5:07:08 with sunset at 5:37:08.

@DSwallow why not just use HTTP? It won’t warn you that way. I use: http://eisy.local:3000 And never get a warning. Only if you’re using https would you. Since you’re internally accessing a device on the same network do you really need https? It’s just that browsers “default” to the https. If you would like to pose this question directly to UDI it’s best to use the “Contact Us” method on their site.

@Eric just so everybody knows what you're working with please let us know: Device Firmware While the answer normally wouldn't change all that much there appear to be a lot of long-time ISY994 users still on a 4.x firmware. There were big changes when going to 5.x. Also, nice to know if using a current model device (eisy or Polisy). Now, you might want to look at what you have setup for the controller for the scenes. Remember if you control the scene from the admin console that is a controller and it might not have the same settings as a button or switch setup as a controller. If you expand the scene compare the settings of the red devices in the scene with the settings (actions) of the root. The ISY service (i.e. admin console and possibly the Alexa) would act as the root to control the scene.

Did you do something recently to the network configuration that would make you think it would be messed up now? Otherwise, does kind of look like somebody might be running port scanning on you, but that's just a guess. I think @Techman is right the only "real" way to know is to open a support ticket and include the log (as a zip file) for them to review. https://www.universal-devices.com/my-tickets If you did make changes to the network settings please explain further. Have you added port forwarding on your router so that you can access the ISY while remote? If so, that's risky. The best way to securely access the ISY994 from a remote location would be through the UD Portal connection (make sure you have a strong password for the portal account!). Lastly, once you hear back from UDI on the support ticket please post the findings here so it might help others if they run into this issue they can learn what it was.