When I try to install the latest Java JRE I keep getting an error 1603 "Java install did not complete", and nothing more. I have spent over 3 hours today trying everything I can find to resolve this - YT videos, Java help articles, Googling, user suggestions, running as Admin, messing with folder permissions, rebooting, you name it. Java simply will not install no matter what. I've even observed it populating its target folder with some files and folders during the install process, but then it deletes them and throws up the 1603. I've even logged on with an Administer account but that didn't make a difference.

Has anybody heard of anything like this or have any suggestions? I'm at my wits end, and cannot get Admin Console working any more. I've been using it for many years on this computer. Now Java is messing up.

Thanks.

Any one any idea:

a. What it is doing

b. how to stop it?

Thanks!

Anyone else seeing this?

Trying to add some new devices. I tried finding my eisy with IoX launcher and my eisy isn't there. Cleared the Java cache (all three boxes) and reinstalling Java. Nope. Tried adding the IP address in. Nope. I can see it in the portal but need to do admin console level stuff (at least that is how I normally do it).

Any ideas further?

I am using this version of IoX launcher:

Am I using the wrong version of the launcher? Is a new one coming out? Am I misinterpreting the message?

If

Program 'Kitchen.counter.passthrough' is True

$sTheme.kitchen < $cMODE.FULL.ON <----- AND missing

Then

// delay time must be longer than Kitchen.counter.passthrough delay

Wait 3 minutes and 15 seconds

Repeat While $Kitchen.theme.saved is not 0

$Kitchen.theme.saved = $sTheme.kitchen

$sTheme.kitchen = $cMODE.RESET

$sTheme.kitchen = $cMODE.FULL.ON

Repeat 1 times

Else

Wait 15 seconds

$sTheme.kitchen = $Kitchen.theme.saved

$Kitchen.theme.saved = $cMODE.OFF

I've tried clearing the Java cache, updating Java to the latest version (Version 8 Update 491), and rebooting EISY, all to no avail. I can launch the Web Browser admin console just fine but this doesn't have the required functionality.

As a side note, I have a 2nd EISY system on the same network (different home on a different VLAN) and when I launch the Admin console on it everything works just fine using the same computer with the same .jnlp file.

Has anyone else seen this behavior? Any additional debug steps I can take?

Mike

AI results suggested (keep your commentary about AI to yourself, please) that I power cycle the PLM, which I did with the admin console cleanly closed.

I returned to the console and attempted again, this kicked off the normal linking progress bar which takes a few minutes to complete, but then it reset to zero and started again. My console has been in this cycle for over 12 hours and there are no additional indicators whether this will ever finish. I've got probably over 50 devices in my Insteon network and nearly as many scenes. Am I just seeing a complete scan of every device and scene relinking? At this point I'm just going to let this run the rest of the weekend and cross my fingers that it finishes without error.

My concerns are two-fold: one that none of my scenes or programs are runnable due to all the link activity currently running, and two that I'm going to come back to my PC to find that something is irreversibly broken requiring significant rework.

If you have any solid advice or experience to share on this, I would be appreciative.

CAN ANY ONE that has a fool proof set up share. I read so many in the isy forum only to get confused to with one work and not. Some say creat more the one scene. Other say about ungrooping button. I never have tdone that and dont understand that all.

Not all of us live and breath Eisy. We just use it. Now I'm out searching these forums on how to update the console.

Please help those of us that are not power users. Updates should not be painful in 2026.

How the heck do I update the console? The program says not compatible, then I click OK and it closes. So now I can't open the console. UGH!

I thought I saw a message many months ago that this was going to be simplified.

https://wiki.universal-devices.com/ISY_Users:V5:ZWave:Advanced_User_Guide:Scenes#:~:text=as%20a%20Responder-,Removing%20a%20Controller%20or%20Responder%20from%20a%20Scene,Native%20(Controller%E2%86%92Responder)

Without the tree view how do we removed devices from scenes?

Firmware loX v.6.0.4 ( 2025-12-18-18:51:58 )

UI IoX v.6.0.4 ( 2025-12-18-18:51:58)

Product eisy (5226)

• OpenADR (21010)

• Networking Module (21040)

• Portal Integration - UDI (21075)

• Z-Wave Module (21100)

• A10/X10 Module (21060)

Thanks!

Patrick

Since I already have a couple of old alarm PIR's to a Shelly i4 Zwave module, which has been rock solid in basic functionality (PIR triggers Shelly on hardwired connection, Shelly sends basic open close to programs), thought I would replace the MS II with another PIR / Shelly combo.

As I have NO PROGRAMMING background, its been a slow learning process by coping examples found in the Wiki / this forum / trial & error, but in the end always found some function missing or something not working 100% of the time as expected. And as complexity grows and programs accumulated, diagnosing problems turned into deeper problem for me to work through. My whole deployment is lighting only, so no fancy addon's just basic lighting automation.

I retired recently and setup a lab in my office to start extended testing of modifications to or for new lighting solutions ... therefore before replacing the MS II, I wanted to fix some of the broken / missing functionality of what exists to today, e.g. motion override (disable the timer via switch paddle and auto delay timer reset when human traffic exists longer than the normal / default timed event.

I have success, but it took 5 programs to make it work as wanted ... so question to the forum : is this efficient ? is there a better way to write this ? do I just deploy and not worry, the EISY has lots of CPU Attached are my programs, there are notes for each program ... I would appreciate feedback if anyone would like to critique

Motion1.rtf

Please include:

• Manufacturer Name
• Model #
• Link to sales/availability site(s)
• Key/desired function support

This is only to begin targeting expansion for supported devices. This is not expected to be a long-term request thread, but certainly to target expansion and support for what the Universal Devices community has in service. In order to get an idea of what devices should be supported as this rolls out.

Please like (press the heart reaction) a suggestion/request rather than duplicating an already suggested device.

anyone know what this might mean, we had a power glitch and I cant get back on.

A PDF posted on the forum says:

Replace Modem (PLM)

This operation is most useful when you need to replace a defective PLM and the EISY/POLISY is rebooted with a new PLM. When the communication links were established via the Link Management Menu, the PLM and INSTEON devices adds each device addresses it is linked to, in its own link table.

The EISY/POLISY also reads and stores the PLM’s address at boot up. The EISY/POLISY stores all the configurations settings in the device tree. If you are replacing a PLM the EISY/POLISY will have the old PLM address link stored in it.

Warning: Never replace your PLM while the EISY/POLISY is running because it will assume it is still connected with the old PLM. The EISY/POLISY will appear to work, but it will be writing the address of the old PLM into the device links, thus you will not see devices updates etc. If this menu option is selected, the EISY/POLISY goes through all INSTEON devices looking for old and new PLM address links. If an old PLM address link is found, it replaces them with the address of the new PLM and adds the corresponding device link to the new PLM.

Here is what I did, after taking out the old PLM and ordering a brand new one from insteon.com:

To update corrupted tables in a PLM (modified from posts on the wiki):

- Take the power plug out of the EISY to do a power-off cold reboot

- Disconnect the data cable between the PLM and EISY (NOT necessary to unplug the RJ-45 ethernet cable if you use one to connect your EISY to the internet or local network

- Take PLM out of the AC power outlet (this does NOT by itself reboot the PLM AKA reset the PLM tables)

- New reboot the PLM, AKA factory reset:

- [hold the set button in on the PLM while plugging it in and continue to hold until the PLM stops buzzing, then all links are cleared. (Steve Lee, Insteon Support) Nope, this didn't work for me]

- Reset the PLM:

"To reset PowerLinc Modem to its original factory settings, unplug from wall outlet and wait 10 seconds. Press and hold Set button; while continuing to press and hold, plug back in. A long beep will sound; continue holding Set button until beep stops, then release. After several seconds, status LED will turn on to indicate reset is complete]

- Connect the PLM to the EISY/POLISY with the data cable

- Plug the power cord back into the EISY

- Go to Admin Console and wait for system initialization to complete

- [ignored probably irrelevant information about waiting for battery powered units and looking for a battery icon in IoX; I don't see a battery icon, nor is there any buttcon with a hover state indicating battery; these buttcons – buttons with icons – need a mouse hover state that explains what they are) Click on the Battery icon at the top. This will prevent EISY/POLISY from trying to update programming on your RF devices which are probably in sleep mode]

- File > Restore Modem (PLM) menu

- Wait until the "System Busy" at the bottom left goes away, and the green 1011 icons quit appearing

- In case EISY/POLISY cannot communicate (or decides not to if it’s an RF device during the process, you will have a series of nodes with green 1011 icons in the device tree. For each one of those nodes:

- If an RF device, ensure that the device is in Programming mode (awake)

- Right mouse click > Write Updates to Device.

If the above procedure fails on many of your devices, it's highly recommended that you follow the instructions for Restore Devices.

Looked in https://wiki.universal-devices.com/Eisy:User_Guide and searched the forum for Restore Devices, and found nothing useful.

See the picture for the number of devices IoX can't communicate with.

I tried rebooting both the EISY and my PC, after which IoX showed no errors! But then I went through the list and tried to turn each of the Insteon units on and off and you can see how many failed. I started at the bottom and tried "Write updates to device" and "Restore Device" both without doing anything to the Insteon unit and after putting the Insteon unit. Both failed for the bottom two units with a big red exclamation point at which time I gave up and created this post. I would hate to have to replace this many Insteon units without knowing that it would solve the problem. I thought, "maybe I need phase a signal bridge" and then "no, with so many dual wireless/powerline Insteon units, I have no need for a physical phase signal bridge."

This is very rare event occurring once every 4 weeks ... The motion sensor is top of basement stairs and controls basement light scenes ...

Post event, looking through LOG (Tools) the motion sensor, the garage door (IOLinc) or the LampLinc do NOT appear when this event log and when I look at the LampLinc status, it shows off state, and If I look at a scene containing the LampLinc, it shows OFF status, but a mini remote button (4 Scene) shows ON associated with the LampLinc

I have run Tools / Diagnostics / Event Viewer for weeks hoping to catch what triggers this event ... no luck ...

Looking for direction on how to capture / diagnose this random event

Cheers

Can anyone help me understand what is going on?

Issue- When the device was properly added to the scene as a responder, instead of working with the settings in the scene, the device simply goes to 100% every time a scene button is pressed at any of my devices with that scene. However, when the app it used, the device goes to the level set in the scene.

What I have tried-
-restoring the device
-resetting the device entirely using the button on the front and restoring
-restoring the PLM
-changing the scene settings in various ways to hopefully get it to reprogram

Any suggestions on a cause for this behavior or on what to try next to get the device to properly respond to scene button presses?

Eisy

Cell: Mint Mobile (T-Mobile)

Gmail Account

Help Needed; I’m unable to send TEXT notification via eisy,

What I’ve confirmed:

Eisy email notifications work ######@gmail.com, “when SMTP Settings is Use Default”

Manual email sent from a PC to ##########@tmomail.net works.

What I’ve tried;

SMTP configuration Use Default

SMTP manual configuration tested (Gmail):

Server: smtp.gmail.com

Port: 587 (also tested 465)

Security: TLS checked and unchecked

Username: full Gmail address

Password: Gmail App Password

From address set

TEST Button Result is always an immediate “Mail server failure.

Questions:

Is there anything I’m missing? Has anyone been able to get TEXT notifications to work with a Mint Mobile phone?

Any help would be greatly appreciated