Ed Sybesma

Interestingly, for me, with a 2024 PLM (same revision I think), switching on and off did not work on any of the devices, but clicking on query worked for all of them to generate a 1011 icon to allow write updates to device and connect.

Even after resetting my new PLM to factory settings and starting over, the Restore PLM command and the Replace Modem PLM instructions did not do the trick for me, but I did find a very convenient workaround: Querying the modules triggered the green 1011 “waiting for updates to be written” flag and then using the “Write updates to device” option got my devices linked. But thanks to hart2hart and Techman for their input which might have saved me that extra effort if I had started with it the first time.

No, I didn't use replace PLM. Where will I find that. Does it Show up under tools | diagnostics with a new modem is attached? Right now, I can't find it anywhere. Or is that "restore PLM"?

I just attempted to switch PLMs. I went from a 2413S to a 2413U. I am using EISY and everything is up-to-date. Although the administrative console recognized my Insteon devices, it would not communicate with them until I individually relinked them. Unfortunately, I have a few micro switches which are very labor-intensive to access in order to be able to relink them. From previous posts, it appears that in making this transition the Insteon devices should be automatically reconnected. Are there any special steps to take to be able to accomplish that?

In addition to instructions, you need image files which are in excess of 8 GB in size. I think the instructions may already be in the wiki for EISY, though I have forgotten I also got instructions from AI, I think Gemini, which were also helpful. Here they are: The process involves two major stages: Preparation & Backup, and then Re-flashing & Restoration. 1. 📝 Preparation: Crucial Backup Steps DO NOT start the re-flash process without a complete, current backup file saved externally to your computer. Step Action Notes 1. Z-Wave Backup In the Admin Console, go to **Z-Wave Backup**. 2. IoX System Backup In the Admin Console, go to **File Backup IoX**. 3. External Storage Verify the .zip file is fully downloaded and saved to a safe location on your computer or cloud storage. You will need this file after the re-flash to restore your settings. 4. Locate Hardware Find your Eisy Reflash USB Stick (or an HDMI monitor and USB keyboard for the manual boot process). The USB stick is the simplest method if you have it. 2. ⚡ Re-Flashing the EISY (Wiping the System) The simplest, recommended method for re-flashing involves using the official Eisy Reflash USB Stick (if available): Step Action Notes 1. Power Down Press and hold the multifunction button (power button) until the light turns Red (to shut down the system). Disconnect all network/interface devices like your PLM/Z-Wave dongles. 2. Insert USB Plug the Eisy Reflash USB Stick into one of the USB ports on the side. 3. Connect Peripherals Plug in an HDMI monitor and a USB keyboard (if not using the Reflash USB Stick, or for troubleshooting). This allows you to interact with the BIOS/boot menu. 4. Power On & Boot Plug the power cable back in. Quickly and repeatedly tap the F7 key on the keyboard until you see boot options on the screen. If using the USB stick, select the USB device (e.g., "Orico") from the boot menu. The re-flash process will start and run automatically. 5. Wait for Completion The system will install the latest OS and software and then automatically turn off. This process can take several minutes. 6. Remove USB & Reboot Unplug the USB stick. Click the power button to restart the EISY (light turns Blue). Allow the system 2–3 minutes to fully boot and stabilize. 7. Verify Access the Admin Console (it will be in its default/factory state). Go to the Configuration tab and click Upgrade Packages just to ensure the absolute latest packages are applied. 3. ✅ Restoration: Applying Prior Settings After the re-flash, your EISY is factory new. You now need to restore your settings from the backup file you saved earlier. Step Action Notes 1. Connect Devices Plug in your Insteon PLM and/or Z-Wave/Z-Matter dongle/board. Ensure they are fully connected to the EISY and recognized. 2. Restore IoX In the Admin Console, go to **File Restore IoX**. 3. Wait for Reboot The EISY will apply the settings from the file and reboot. This step may take several minutes. Once rebooted, log in using your old (pre-backup) username and password. 4. Restore PLM (Insteon Only) If you use Insteon and have the same PLM, go to **Insteon Restore PLM**. 5. Final Z-Wave Check Go to **Z-Wave Synchronize Nodes** or simply verify your Z-Wave devices are online and working.

Thanks Techman. Since I already have the serial adapter cable, that's pretty much a wash for me. Are there any other pros or cons?

It is time to replace my old 2413S. I have a new, unused 2413U. For use with EISY, are there any pros or cons as between the two?

I submitted a support ticket in order to get access to files and instructions for "re-flashing" the EISY.

Yes, the reflash did take care of the problem.

Yes, that's how I know the upgrade didn't work: Firmware loX v.5.8.4 (2024-06-27-11:35:44) Ul loX v.5.8.4 (2024-06-27-11:35:44) FYI, I submitted a ticket and Michael is having me reflash my EISY. I just hope that goes smoothly!

That link gives me The error message: This site can’t be reached Check if there is a typo in eisy.local. If spelling is correct, try running Windows Network Diagnostics. DNS_PROBE_FINISHED_NXDOMAIN

Hi Techman, after the upgrade attempt, Java required me to upgrade Java in order to log into administrative console again, and I did so. I had not previously downloaded and updated version of the IoX launcher, but have done so now. Unfortunately, that didn't change anything.

The recovery instructions seem to apply to the situation where “your eisy does not come back online after 2 hours”. My system is up and running just fine, but simply hasn’t upgraded. I will submit a support ticket before going through that procedure, but was just hoping someone had a quick answer.

Guy, thanks. It logged me out of administrative console and told me to log back in. It never told me specifically to reboot but I assumed it rebooted itself since it logged me out. In any event, I did reboot just now and still no upgrade. I should add that in UD Mobile I received notifications telling me that the upgrade was in progress and later that “Upgrade complete!”

I have now tried upgrading my EISY both from administrative console and from UD Mobile. In both cases, dialogues and notifications tell me that an upgrade is in progress and eventually the system reboots, but when I log back in I am still on loX v.5.8.4. Any suggestions?

Yes, that's definitely a better option than UD mobile. The reason a word processing alternative would be useful Is that I have a few moderately large programs which I occasionally wish to copy and modify many lines. I was just hoping, but it's not a common or significant issue.

Is there any method for editing programs outside of administrative console,, e.g., in a text editor or Word, and then import them into EISY?

FYI: restoring the backup did the trick so that at least EISY is working again.

Yes And since I disconnected my EISY this time (as opposed to other times in the past), it's UUID changed. Now nothing is working on the EISY. Do I have to re-recognize all of my devices (or perhaps just restore my backup)?

Thank you for your suggestion. It led to new information which is in itself baffling. My router does not recognize the Polisy at all, even though the LED lights on the back of the Polisy indicate that there is network communication going on. (The EISY is not connected.) Is it possible that my Polisy died a quiet death during the time it was not in use? I have rebooted everything twice now, my router, Polisy, my computer.

In answer to your question, I switched from Polisy to EISY somewhere around December 20. At that time they were running the same firmware and the same data file. I don't think there has been a change in the firmware in the meantime, but I'm not sure. The data file in the EISY has changed and the Polisy has not been used since then. If I rephrase your suggestion as follows: "If so, remove power from the PLM and the eisy, wait about 15 seconds then connect the PLM to the Polisy, power up the PLM, wait 15 seconds then power up the Polisy", that is exactly what I tried and it did not work. Again, my ISY/IoX finder would not recognize the Polisy.

How can I temporarily revert back to Polisy from EISY? I am using the same Power Linc Modem, model 2413S, for both Polisy and EISY, with the appropriate adapter for EISY. I attempted to switch back by disconnecting the EISY, connecting the Polisy to the PLM, and then starting up the Polisy, but my ISY/IoX finder would not recognize the Polisy. (EISY is now reconnected and is properly recognized.)

Incidentally, one reason I care about the path for beginners is the desire to ensure that UD is sufficiently successful that it sticks around for a long time to come, and continues to make the kind of advances we have seen to date. (Of course, one might not want it to be so successful that it gets bought out by some giant corporation or goes public. Sorry, Michael.)

I definitely would not want a dumbed down version in terms of capabilities. I don't think there has to be a trade-off between that and easing the path for beginners.

I totally agree, and apparently, hopefully, that is what UD is in the process of doing.