Techman

@Brian H I sent a message to Insteon support re: the new PLM's, here's the answer I received: "The newer PLMs are still under development. I don't have an ETA to share at this time."

In the admin console you can use HTTPS://eisy.local:8443/desc which will use your original user name amd password

Here;s the latest update from Insteon Passcode Required - Zoom Passcode: 78&YPnWK

Have you tried a Synchronize in UD Mobile. In the home screen, click on the 3 dots in the upper right.

@someguy Do you have any Insteon motion sensors installed? Do the lights all come on at the same time? If you look at your EISY log do you see any activity just before the light(s) come on Do you have any older, non dual band insteon devices, in your system? Do you have any power supplies plugged into your a/c outlets Did you look at your program summany page to see if any programs ran at the time your light(s) came on?

if you still need a range extender any plug-in dual band device will work. If you have numerous dual band devices in your Insteon network then there's probably no need for a range extender as all dual band devices also act as insteon repeaters.

Once your favorites are restored it's time to make a UDM backup

@MTellevik You may want to check your netural and ground connections on the KPL. Being that the issue only happens when the load is increased points to a possible bad connection

What type of load is conected to the switch? Is the switch a dimmer or on/off model?

If you have Zwave something like this might work http://www.empers.com.tw/ZC120_485.html

The Insteon LED Bulb automatically enters linking mode every time it is powered on, it's possible to accidentally link a device to the LED Bulb in the brief period of time that the Bulb is in linking mode. Because the LED Bulb lacks a set button, there is no manual way to factory reset the LED Bulb. You can try removing the bulb from the socket, replacing it and then doing a restore device It's also possible that the electronics in the bulb have failed

Creating a Topology report will give you all device addresses and lots of useful additional info TOOLS | GENERATE TOPOLOGY

You'll need a a tile that represents a scene, as you mentioned scenes are not yet supported.

Try HTTP://eisy.local/

Are you using HTTP or are you using HTTPS to access eisy-ui

This is what you need for the UPS, originally it was called a FilterLinc Powerline Noise Filter – Insteon It's also possible that the SwitchLinc is defective and creating the noise, do you have another one you could replace it with? FilterLinc.pdf

It could be a combination of the off signal from the switch and noise from another device. Some things to check/try Put your UPS on a Filterlinc as they are notorious for creating powerline noise issues Check the batteries in your motion sensors, a low battery can cause insteon issues If you have any battery/phone chargers plugged in, unplug them.

@tibbar Alkso take a look at these links Mystery X10 codes - help to find source - ISY994 - Universal Devices Forum X10 log events, no X10 devices - ISY994 - Universal Devices Forum

Take a look at this link. Being that you don't have any X10 devices and the fact that you have comm issues I would think that you have some type of noise on your powerline. Do you have a UPS or other electronics installed near your PLM? Do you have any battery powered motion sensors installed? ISY flooded with X10 status requests - ISY994 - Universal Devices Forum

It's possible the link tables in the switch got corrupted. Try doing a factory reset on the switch, then a restore device Being that you have comm issues, they could be caused by noise on the powerline, a poor insteon mesh network, or a defective device. Do you have X10 devices currently installed How many Insteon devices do you have installed In HELP | ABOUT, what is your firmware and UI versions

None of my programs that are triggered by time of day ran after the DST reverted to standard time. My eisy clock showed the correct time and sunrise and sunset were also correct. I rebooted the eisy which I think corrected the problem as all my lights were off this morning as they should be.

The eisy uses an USB port to interface with the PLM, you'll need an USB to serial convertor cable such as this one: Serial PLM Kit - Universal Devices or you can use a 2413U USB PLM

Being that your Polisy firmware is 6.0.0 the 5.x.x data file wouldn't be compatible. A socket timeout error occurs when a network operation, such as connecting to a server or receiving data, does not complete within a specified time limit. This means the client or server waited for a response or a connection to be established, but the expected event did not happen within the allotted time. It's possible that the 6.0.0 data file you were trying to restore is corrupted, After you rebooted are your programs and devices all working normally, if so It's best not to try restoring a backup. If all is good then do another backup. You should also clear your java cache, be sure to check all 3 boxes, then download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp

What was the reason you tried to originally do a restore? Reboot your Polisy. After the reboot when you click on HELP | ABOUT what does it currently show for your firmware and UI versions If your current firmware is 6.0.0 then don't try to restore a 5.x.x file

Are you able to do a backup? When you do a restore the zip file must remain in the zip format. What is the firmware version of the backup file you're trying to restore