Guy Lavoie

How about a simple test for the PLM: try manually linking a spare switch or module to the PLM, just using the link buttons on each device. Just to see if they can talk to each other, without the isy being involved.

He's logged in on the console (physical keyboard and hdmi monitor) so no network access is needed to log in and see this.

We love happy endings 😀 Good to know. So no automatic updates, but there were some unintended update errors caused by this.

Look at the file: /var/isy/FILES/WEB/sysconfig.txt Scroll down to the *****IoX******* heading and you'll see the version on the following line.

Since you can access it on the console, what happens if you try to reinitiate the acquisition of a ip address? Something like this: sudo dhclient -r re0 What error message do you get, if any?

What version of IoX were you running up until now? 5.9.1 or older? If older, any hints that an update might have happened? Tried just unplugging and reconnecting the network cable, or a different cable? Everything else in your local network is working as before?

Well, if the distance is too great for the technology desired (Insteon or zwave for example) but you have wifi or wired ethernet, you could set up a separate controller (like a ISY994i) and have your master controller, like a eisy, send commands to it using REST commands. That might be a useable solution if the number of devices to be controlled is small. Tracking status would be more difficult however.

If you can detect the double tap as an event in a program, then you could have two programs, something like this: If switch double-tap on event Then set motion detector parameter 1 to <enable> If switch double-tap off event Then set motion detector parameter 1 to <disable> I don't know these devices, so I can't tell you what is settable or not by program statements.

Which Insteon device has no link button?

The mystery here is that Insteon is working but not X10, and (seemingly) only X10 transmission with the eisy. It's as if the PLM was unable to transmit X10. Yet another PLM was tried with the same results. The hardware connections like the PLM cable seem ok since Insteon works. The next thing I'd try is moving the PLM to an outlet on a different circuit, and maybe on the alternate phase. It sounds like there is a X10 signal issue, at least in some area of the house. Alternately, try a X10 transmitting device (like a transceiver) in the same outlet as the PLM. Is that device now having trouble transmitting? Has anything been added that might be a "signal sucker"? We add and move so many electronic items nowadays that this might be hard to really be aware of.

Have you tested to see if your eisy can receive X10 signals? Do you have programs triggered, or variables set by received X10?

If I'm not mistaken, after a while it will also disappear on it's own.

It's in nostalgia mode. Have you tried highlighting the line and clicking on "delete"?

Yes, the X10 module was mostly a convenience, allowing you to add X10 devices to your device list. It would still be handy to a user who is looking to replace a defective unit and recover from a backup, without needing to edit all the programs.

If it doesn't already have the X10 module, you can't add it anymore. If you want to stick to a ISY994i, you'll need to find a used one that already has any modules you want.