I have a few X10 devices that are controlled through my Insteon integration. They have been working fine but then stopped.
I believe the latest update might have affected them. I have attempted to delete and re-add them through the Insteon integrations card in Configuration but have had no luck getting them working again.
The devices are successfully added but if you try to activate them nothing happens. The toggle can be moved to the “on” position but after a few seconds HA moves the toggle back to “off”.
I have attempted rebooting and deleting and re-adding the devices. No luck in either case.
There are no notifications relating to any problem with X10 or the Insteon integration.
The Insteon devices are all functioning normally. This is only affecting X10.
Almost exactly the same issue with my X10 via Insteon integration. My control toggle is greyed out and I can’t even move it. Definitely something broke.
My observation is the same. Here is a temporary workaround.
Steps
1. Edit "config/.storage/core.config_entries" which is in JSON format.
2. Locate the "insteon" domain attribute
3. Locate the "x10_devices" array under the "insteon" entry
4. In my observation, only 1 out of 12 physical X-10 devices is specified in the array.
5. Specify any missing X-10 devices and add them to the array. The order of the array element does not matter.
6. The value of the "platform" attribute should be either "switch" or "light".
7. Save the changes and restart Home Assistant.
8. X-10 devices will become available after the restart.
Problem Description
The Insteon HA module incorrectly thinks that there is only 1 available X-10 device.
Here is the line of code where X-10 devices are registered during the initialization. You may set log-level to debug to verify whether you X-10 devices are registered or not. The objective of this workaround is to force the Insteon initialization to register all X-10 devices.
There are several ways to resolve the issue but I am new to Home Assistant. It is unclear to me if there is a bug in the frontend wherein the Insteon entry of the parent device (e.g. PLM 2413U) configuration should be persisted with all child devices (i.e. X-10) or not.
Since I posted this, X10 started working again after subsequent upgrades. That is until 2020.12.0 when X10 was broken again.
I tried your suggestion and ended up crashing HA. I probably screwed up the syntax or something but once I got it running again I just went back to 0.118.5 where X10 was working.
I can confirm that this resolves the problem. I couldn’t understand why my Insteon X10 devices didn’t respond and the switches snapped back (just implemented HASS with my Insteon a few days ago) and just tried this method and it does work. Just make sure you properly format the JSON as each element MUST have a comma after it like such:
I started having trouble with my X10 again so I thought I would circle back around to this offered solution and give it another try. Unfortunately, this does not appear to be the same problem. I checked my core.config_entries file and both of my X10 devices are listed.
Edited to add OT:
Teharris1, if you see this are there any instructions for adding the Insteon USB RF adapter to HA? HA doesn’t seem to see it but I am wondering if the driver for it is not in the boot image for the Raspberry PI edition.
Oh, never mind. You mean an Insteon modem type 2448A7 or 2448A7H that only works with RF, not PowerLine. I use that same modem on an RPi so I know it works but I forget how I set it up. Looking at my setup, when I go to Supervisor -> System -> Host -> Hardware I see the following:
Should I go through the Insteon integration gui and add it as a device override? If that is the case, what might the values be for device category and device subcategory?
Tried adding the USB RF adapter through the add device override option in the Insteon integration gui… It did not work. Don’t know if it should matter but this adapter is being added to an existing Insteon integration.
I think I figured it out. Looks like you can oln have one PLM at a time. I am testing on a clone of my primary HA which has the serial Insteam PLM on it. I deleted the entire existing Insteon integration on my testing platform and then added a fresh Insteon integration in and it found the Insteon USB RF adapter right away.