Techman

When you clear your java cache you need to check all 3 boxes. When the cache clears it will delete the IoX Launcher from your desktop Then download the IoX launhcher from this link: https://isy.universal-devices.com/start.jnlp If you click on help about, what is are your firmware and UI versions Some of the early Polisys require a bios uipdate, you may need to open a support ticket if you're still hsaving issues.

I just took a look at my programs that are scheduled to run at sunset. The next schedued run time is correct based on the actual sunset time. So it appears that the admin console is displaying the incorrect time and the programs themselves are actually running based on the correct (sunrise) / sunset time. Note: I had rebooted prior to viewing my runtimes, so I'm not sure if the reboot had any effect.

EISY time of day is correct, but I also noticed Sunrise and Sunset times were off by an hour this morning. I Rebooted the EISY but it didn't correct the Sunrise/Sunset times. The GMT offset for my location is showing -8 and it should be -7 for daylight savings time in California. I tried to change it manually but it reverts back to -8

Post a copy of one of your programs that's not running

@fanpatsdec What are your EISY firmware and UI versions?

You definately need to put filters between the UPS and the powerline. You should see insteon signal improvements after they're installed.

@GSpitale01 If the random on is only affecting one device then it is usually the device itself, or a program/scene that contains the device. v.45 is current and has no issues that I know of. What are the details of the load connected to the 2477D? If you're seeing a lot of EA links in various devices then you could have general communication issues cause by either noise on the powerline or poor communications between the two powerline legs.

@GSpitale01 The mismatch of EA links is not an issue and can be ignored. Take a look at this old post Device Links Table Corrupteds - INSTEON Communications Issues - Universal Devices Forum (universal-devices.com)

You definitely need a noise filter between the UPS and your powerline Powerline Noise Filter – Insteon

If the KPL buttons are part of a scene then the button will light when the scene, or load, is turned on. There's no workaround to accomplish what you're trying to do.

@Merlin Take a look at these troubleshooting suggestions INSTEON: Troubleshooting Communications Errors - Universal Devices, Inc. Wiki (universal-devices.com)

Make sure you have a current backup. Any 1011 errors mean that there are pending writes to that device. I don't think the PLM is the core of your problems. However if wouldn't hurt to install the USB PLM as the newer PLM's have updated hardware and firmware. You should really focus on what's causing the communication issues. It could be a defective device that's creating powerline noise. Try pulling out the set buttons on all the non-battery devices that are showing pending writes and/or a red exclamation point then check your log to see if the X10 data stops. Being that you bought the house with the Insteon devices it highly possible that one or more of the devices is causing an issue. You can also try factory resetting the devices, then doing a restore device to see if that clears up things. Do one device at a time then check your log to see if the X10 data goes away.

Replacing the PLM is just an academic exercise. Instructions are attached. Replace Modem (eisy_polisy).pdf

There's no risk in doing a restore devices, it just rewrites the link tables stored in your controller back to the devices Were any of your devices, or PLM, purchased used, if so they might contain an X10 address. Also take a look at your error log to see if there's any indication of an issue.

@Merlin Under the admin console file menu do a "restore devices". This will rewrite the link tables stored in ther EISY to all your devices. If you have any battery operated devices then first disable write to battery devices. If you still have issues after the restore devices, then I would focus on the PLM and possible communication issues such as noise being generated by other electronic devices on the same circuit as the PLM including X10 devices

@Jack D Make sure that only one battery operated device is in the linking mode at a time otherwise their link tables could get cross linked. If you think that may have happened then do a factory reset on the device, then a restore device.

The node status of battery operated devices won't update in the admin console until the device sends a signal for that node, i.e. a open, close or heartbeat signal. All battery operated devices must first be put into the linking mode before they can be added to the Eisy. When battery operated devices are not in the linking mode they go to sleep in order to preserve battery life and therefore can't respond to a query

I guess I should have been clearer in my explanation. Agreed that devices on the same leg will blink red but in order to properly couple the powerline legs you also need devices that blink green. I was also taking into consideration that some of the older Insteon PLMs and older Insteon devices were single band which wouldn't provide the RF coupling.

@IndyMike The range extender is just an example. Any newer dual band device will suffice. The incoming powerline to a home is divided into two 120v legs. To insure that the insteon mesh signal is able to reach both legs, the legs should be bridged using dual (RF) band devices. A 4 tap test is able to verify that the legs are bridged via the green flashing leds..

If the device is flashing red then the powerline is not properly bridged. Take a look at the attached file 4 Tap test.pdf

Based on their firmware not all devices respond to the 4 tap test. Try the test from other, and newer, dual band devices.

Are you able to open the admin console? If so, post a screenshot Do you have windows firewall software running?

@GSpitale01 Take a look at your event log. Do you see a command to open the door, if so look at the commands above it to see if there's a device that triggered just before the door opened. If you don't see a command to open the door when the door was opened then it's most likely a spurious command coming from the PLM not the controller. In that case it could be noise on the powerline that's triggering the PLM. It could also be the garage door motor/controller. I have mine plugged into a filterlinc.

@GSpitale01 The PLM firmware cannot be updated. Take a look at this link: INSTEON Random All On Events - Universal Devices, Inc. Wiki (universal-devices.com)

Here's the guidlines for replacing the PLM. It was written for the ISY994 but is basically the same for the Polisy and EISY Replace PLM.pdf