Geddy

If still having issues you should open a support ticket and let UD help directly with this. https://www.universal-devices.com/my-tickets/ Have you performed a full power cycle recently? https://wiki.universal-devices.com/Eisy:User_Guide#Multi_Function_Button Also, what IoX and PG3 versions are you currently running? (Please reply with actual version numbers and not just saying "current versions")

@rg65 does your Polisy have a Z-Matter or other Z-wave controller attached? Have you enabled Z-Wave in the settings?

Depends on your computer system. There's not a firm answer for it. Since Admin Console isn't open for very long (typically...remember it's not meant to be left open 24/7) there shouldn't be much impact on the system for other processes running. If you have a lot of memory you can run up to 1024. Somewhere it was also suggested to set the max and min to the same amount, but I've not seen that impact performance (for my system) any differently. Search the forums for Runtime Parameter to see the discussion over the years use Google Site Search. What @lilyoyo1 posted is from the UD Wiki: https://wiki.universal-devices.com/Main_Page#Admin_Console_is_very_slow_or_hangs

https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Troubleshooting_Flowchart Not specifically for the PLM. Note, if you check link count make sure there is NO activity on the system. Take multiple counts if you see discrepancies as any activity will cause the counts to be inaccurate. Also review this: https://wiki.universal-devices.com/INSTEON_No_Status_Feedback_From_Devices Lastly, you can also check the event viewer (set to level 3) and control the devices and see what the event viewer shows. Others are better at reviewing what that exposes so if you see "strange" results in the Event Viewer post the text and maybe others can chime in. Or you can search the forums for discussions about similar results.

@jamesm007 Seems the fix is released:

Seems the "fix" is out. See if updating helps your issue.

If you're going to try to continue to use the current ISY994 then Serial is all you can use for that. If you're just going to order the eisy and a new PLM then get the USB so you don't have to worry about a converter cable. If you're getting the serial PLM then you need the Serial PLM Kit. Or there were a lot of posts of other cables you could buy and build your own if you have different places to source the cables in Canada. Use Google Site search for looking up the cable posts as they were about a year old.

Make sure you check this out for the lights blinking: https://wiki.universal-devices.com/Main_Page#Front_Panel_LEDs/Lights But glad you got it back up and running for now. See if you've got a spare power supply that would work to test on the ISY994. (From the wiki page linked above: You can try any power supply that outputs anywhere between 5 volt and 30 volts, center positive, 2mm barrel connector) Keep checking for noise on other circuits. Good luck! Make sure if you turn the power off to the ISY994 and PLM that the PLM is powered on first and allow some time for it to "stabilize" (maybe 60-90 seconds?) then plug in the ISY994 and watch the lights on bootup.

Yes, available again. https://shop.insteon.com/collections/interfaces Not sure. Does Insteon ship to Canada?

@zsima you could use the "Repeat" function in the program. I don't typically use repeat; therefore, I don't have much experience with it. Know that any change in the "IF" statement will cause the program to re-evaluate might stop the wait and/or repeat portion. You can read more about programming in the ISY Cookbook found in the UD wiki. While it was written in the ISY994 days (and some even before) much is still applicable today. It can get even more advanced by using deactivated programs that are called by other programs. Options are limitless. Just have to "play" and learn what works for what you're trying to achieve. Note: To test the program disable the program (so the "if" isn't evaluated), right click the program and select "RUN THEN". That should run the lights and waits that you setup. If I do this I'll reset all the waits to something like 10-20 seconds so the lights cycle quicker than waiting hours.

@zsima Lots of ways to do this, but the best is to start with the "IF" for being from Sunset to Sunrise (next day), You can also make a folder with folder conditions that would only allow the folder to be "true" from Sunset to Sunrise (next day) and then programs inside there to turn lights on and off at set times. Random-On-Example If From Sunset To Sunrise (next day) Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') What you can then do is add waits and turn lights on then more waits and turn off. I do this some with programs to run when out of town to randomly turn lights on and off. I add a fixed wait time then a random wait time to at least get some difference for the starting time and/or the time between when lights are turned off. Note, since random really is just that I add the fixed time to be sure the lights are on for at least 2 hours. You could alter/adjust to fit what you're trying to do. Like this: Random-On-Example2 If From Sunset To Sunrise (next day) Then Wait 2 hours Wait 21 minutes (Random) Set 'Backdoor' On Set 'Front Door' On Set 'Table' On Wait 2 hours Wait 1 hour and 21 minutes (Random) Set 'Backdoor' Off Wait 1 hour and 21 minutes (Random) Set 'Front Door' Off Wait 1 hour and 21 minutes (Random) Set 'Table' Off Else - No Actions - (To add one, press 'Action') Folder conditions setting: (Note, folder conditions are special and should not be set on the root folder ("My Programs"). Any folder condition controls all programs within THAT folder. If the Folder is "False" nothing in that folder will trigger.) Tests - Folder Conditions for 'Tests' If From Sunset To Sunrise (next day) Then Allow the programs in this folder to run.

It seems you might have a sudden line noise issue. Kind of difficult to find, but follow the troubleshooting tips in the wiki and you'll be on your way to figuring out if this is the issue. https://wiki.universal-devices.com/INSTEON_Signal_/_Noise_Troubleshooting Things to check for are new devices added, old appliances that might be running on same circuit of either the switch or the PLM, as simple as phone charger left plugged in could be going bad. @MrBill had a good post that I remember helped others in the past. Check this process out for assistance. If you mean "work as regular" meaning turning the load connected to the switch on/off that's expected...just means the switch is working normally. Just the "smarts" of it might not be working. If it's in a scene it should still be working the scene because the ISY writes the links to the switch. (I think this is expected...I don't have many scenes to directly compare/test with). Now that you have another device not working it's either the noise or sadly a PLM could be dying. I'd troubleshoot the noise first.

@SHM split out from where you or originally posted since it's really a different issue (and specific to your issue). This way it allows YOU to get the help for YOUR issue. Since the other thread had a solution (that didn't apply to your issue) it's better to have started a new topic to get help and find a solution that works for you. Would you post the program that's setting the variable? Do you have just one program that is set to adjust the variable on motion and again when it times out? What is your program that is setting the variable back to 0? What are you attempting to do with the variables?

Glad you got it sorted out. Seems like you might have had an old "version" of the start.jnlp file. There was an issue several months ago (October 2023) about that happening when something changed in the background (best I can explain). I was going to ask when you were getting the "not found" error. If it was a pop up what you just did (using a fresh downloaded start.jnlp file fixed). Previous posts about the "not found" issue: https://forum.universal-devices.com/topic/42008-iox-finder-error-not-found-warning/ https://forum.universal-devices.com/topic/42159-iox-finder-not-found-error-message/ https://forum.universal-devices.com/topic/42176-not-found-message-when-starting-iox-launcher/ If you're saying you're getting it in the IoX Finder title bar that's something different. But, sounds like you got it resolved. As to where stored addresses are kept they're probably in the .state files Here's some wiki info related to other issues, but I think one of them might keep the info of manually entered IP information. https://wiki.universal-devices.com/Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored Usually though manually entered IP addresses can be removed without issue.

@Edmund Lam After you make the change you want be sure to hit "Backlight" button to the left of the setting. That should make it adjust. (This was a change made early in IoX 5.x days - back when only the ISY994 was available) Note there appears to be a longstanding UI issue that when you first open admin console the backlight setting will not display what you have it set to. Do not think this means it will revert to "On 0 / Off 0". The device is set properly, but the UI is not displaying the correct value. Not sure if this is a bug or just a function of Insteon and how IoX reads (or can't read) the value set at the device level.

@andrew77 have you made sure that your portal subscription is active? In another post @bmercier said he made some changes related to the Alexa connection this morning that might have been causing issues. The scene issues working/not working outside lights seems like it might be a local communication issue that isn't triggering the scene correctly. Remember "noise" isn't always created by NEW things added. Some have found that failing power supplies for other equipment/devices or even phone chargers randomly left plugged in can suddenly add noise or degrade powerline signals.

Are you running any anti-virus or firewall software (other than Windows default programs)? Turn those completely off and try again. Maybe after disabling you should clear the cache, delete old start.jnlp/admin.jnlp files download fresh IoX Launcher from UD site ("My ISY" on top right) run new start.jnlp and accept any java alerts What address are you using in the ISY Finder window to access the ISY994? Are you using a local IP or Portal connection? When do you get this error? When logging in or after the window has been open (a while - hours)? Admin console is not designed to be open 24/7. Have you set any "funky" settings in Java to be high security? Make sure you're running "generic" java downloaded from https://www.java.com/en/download/ (current version is Version 8 Update 401).

@glacier991 Questions to learn more to try to help: What phone system are you using? Android or Apple? Are you using UD Mobile or another app/system to trigger boundary crossing? When testing is UD Mobile active on the screen, running in the background, or stopped/forced quit? If using UD Mobile while at the location go to Geofence and hit “Trigger Enter Command”. Is the result instant or delayed? How recently have you setup the Geofence? You might need to set 2 fences with one further out for some GPS signal delays. Have you rebooted your phone lately? (Random, but just a step in troubleshooting 101)

Please be sure to update here what support finds and when/if fixed what was done to fix this so we know and it might help others if they should run into this type of issue in the future. Hopefully it's a simple fix and you're up and running again soon.

As I mentioned in my earlier reply: Of course...as you said there's also a post about it in the "Current Release" area of the forums, but there is also a link to it in the wiki. It's just 100% easier for me to suggest going to UD's main site and clicking the "My ISY" link. It's not really all that intuitive, but having suggested downloading it so many time it's simple to point to that location. Did you get things squared away? Were you running a firewall or antivirus software on the computer in question?

Make sure you relaunch admin console if it was open when you added a plugin. Nodes are only loaded to admin console on load. It’s suggested not to have admin console open when adding or editing plugins. Then all new nodes or changes are read by admin console on launch. Did you migrate from ISY994? If so you have to select and save all network resources. This is a step in the migration process.

@dpierre if you can access admin console the Polyglot uses the same credentials (as @tlightne posted) If unable to get into admin console you can reset credentials by pressing the multi-function button depending on your device. This can be found in the wiki. For the eisy: https://wiki.universal-devices.com/Eisy:User_Guide#Reset_Credentials

@ctviggen1 are you running antivirus and/or firewall software on the computer? Disable both, clear Java cache (checking all 3 boxes). Delete any old copies of start.jnlp (and/or admin.jnlp). Download a new IoX Launcher (start.jnlp) from UD site (click on “My ISY” on the top right). If doesn’t go away, but still able to find and access ISY then you can ignore it (based on old replies from @Michel Kohanim on this issue…used Google Site Search to find old posts with this issue). https://forum.universal-devices.com/topic/32124-socket-open-failed-ssdpclient/ https://forum.universal-devices.com/topic/21736-socket-open-failed-ssdp-client/

@apostolakisl Tesla recently updated their API so @Panda88 might need to update the plugin. The good news is they’re now supporting 3rd party more…hopefully it’s good for the plugin use.

Yes, I believe it should be identical. I did not use UD Mobile when on the ISY994 so don't have firsthand knowledge, but know UD Mobile works with IoX 5.x and up. Since ISY994 ran 5.x it is supported and should work the same. In the UD Mobile Wiki there are steps for migrating from ISY994 to eisy. https://wiki.universal-devices.com/UD_Mobile Sadly, no. This would be a nice addition, but not one I've seen.