Power line noise issues that do not appear to be valid

[tbonini]

I am running HS3 on a Raspberry Pi and am using a USB to serial converter to connect the Pi to a CM11a using the X10 3.0.0.50 version of the plugin. For a long time everything was running as well as could be expected from X10 equipment but a few months ago I started getting issues that seem to be getting worse. Every time HS attempts to control a X10 device, I get multiple warnings like this

X10 WARNING

Still waiting for CM11a to send data... (11.153 sec)

I thought that perhaps there was an issue with the serial converter so I ordered another one and no changes or improvement. Ok, perhaps the CM11a is going bad so I replaced it with another brand new one I had and again, no changes or improvements. There have been no changes to the Pi and it worked fine for years so I really doubt that it is the issue. I have replaced many of my X10 equipment with Z-Wave but during the holiday season, I have a lot of X10 modules that I use for my holiday displays and decorations and the added number of these devices is making the issue pretty much unmanageable. Some of these items are the Smarthome X10 modules which are leading me to believe that the line noise warning is invalid and the waiting for CM11a to send data is equally invalid. The Smarthome X10 devices all have a power / data light that glows on showing the unit is powered up and flickers when the unit sees X10 data. Whenever HS attempts to control any X10 device, these data lights on the Smarthome X10 devices start blinking like crazy and do it for the entire time the HS logs are kicking out that "Still Waiting" message which indicates that the CM11a is in fact transmitting but your driver is not seeing it and is constantly telling the CM11a to transmit over and over. It does take a long time for the X10 devices to respond so it appears that the transmissions are not clean. In fact, it is also turning on other devices in the same house code that were not intended to be controlled at all.

As another test, I dug up an old X10 clock that can control up to 8 devices on a single house code. It is the one that has 4 sets of buttons and a slider switch that allows you to directly control either channels 1 to 4 or 5 to 8. I set it up to house code C "Christmas" and when I press any of the buttons, the data light on the Smarthome devices flicker briefly and the device being controlled responds instantly so like noise does not appear to be an issue. It seems that all the issue is with HS and the CM11a. I don't recall any of these issues on the much older versions of this plugin, just on this newer one. Is there any way to get a older version or a dumber version of this plugin that just sends the command to the CM11a and ignores anything after that because right now, this is pretty much useless and unusable. Thank you for your time.

[Pete]

I still utilize X10 here for Christmas decorations and pack the X10 modules with the Christmas stuff. Over the years have used / tried UPB, ZWave and Zigbee. Settled on using the old Black and Decker Freewire modules outside and standard X10 appliance or light modules inside.

Here just configured a C1 device using the CM11A and enabled X10 debug.

Please enable debug and send out a C1 on and off command. Copy and paste your X10 debug log stuff here.

In this example I edited out all of the other plugins running and kept the X10 debug info using Linux notepad using the ./go command to start HS4 in a terminal window.

04:28:19:8565:[Database]->Opening (Mode=Read Only) up HomeSeer LOG database /opt/HomeSeer/Logs/HomeSeerLog.hsd
04:28:22:0166:[Startup]->Loading Settings
04:28:22:8300:[Startup]->Settings Loaded.
04:28:25:5282:[Startup]->
04:28:25:5301:[Startup]->*********************************************************** *********************
04:28:25:5346:[Startup]-> HomeSeer version 4.2.7.0 Edition: HomeSeer HS4 Pi Starting Now
04:28:25:5370:[Startup]->*********************************************************** *********************
04:28:34:6045:[Plug-In]->Found plug-in: X10, version: 3.0.0.50
04:28:37:2352:[Startup]->Initializing Plug-Ins
04:28:40:1864:[Info]->Plugin X10 has connected. IP:127.0.0.1:37382
Connected, waiting to be initialized...
04:28:40:2661:[Starting Plug-In]->Initializing plugin X10 ...
04:28:40:9047:[X10 INFO]->Initializing CM11A/12U on COM port /dev/ttyUSB0
04:28:41:4382:[Starting Plug-In]->Plugin X10 started successfully in 1171 milliseconds
04:28:41:5245:[Starting Plug-In]->X10 loaded in 4221 milliseconds
04:28:41:5266:[Plug-In]->Finished initializing plug-in X10
04:35:05:0298:[X10 DEBUG]->CM11A.SendIt(): Sending 2 bytes: 0x 04 26
04:35:05:0355:[X10 DEBUG]->CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
04:35:05:0477:[X10 DEBUG]->CM11A.SendIt(): Received a good checksum: 0x2A
04:35:05:0549:[X10 DEBUG]->CM11A.SendIt(): Sending 0x00 to CM11a (command to execute).
04:35:05:5110:[X10 DEBUG]->CM11A.SendIt(): Got ack of: 0x55
04:35:05:5217:[X10 DEBUG]->CM11A.SendIt(): Success! 0.455 seconds for CM11a to send.
04:35:05:5295:[X10 DEBUG]->CM11A.SendIt(): Sending 2 bytes: 0x 06 22
04:35:05:5356:[X10 DEBUG]->CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
04:35:05:5471:[X10 DEBUG]->CM11A.SendIt(): Received a good checksum: 0x28
04:35:05:5528:[X10 DEBUG]->CM11A.SendIt(): Sending 0x00 to CM11a (command to execute).
04:35:06:0075:[X10 DEBUG]->CM11A.SendIt(): Got ack of: 0x55
04:35:06:0152:[X10 DEBUG]->CM11A.SendIt(): Success! 0.456 seconds for CM11a to send.

This is a test HS4 box that I am still working on. The CM11A is plugged in to a power strip near the kitchen. Production X10 CM11A and Volp X10 controllers are plugged in next to the fuse panel in the basement here with long serial cables going to Homeseer 3/4 and OmniPro 2 panel devices. I do leave an Elk X10 signal tester on line on the computer rack in the basement. I am not seeing any noise on it. 2 years ago here saw much noise prior to outdoor AC compressor motor failing. It failed and I replaced outdoor AC compressor and I have not seen any noise since. Years ago tested using another power strip in the basement and the CM11A did not work on that power strip. Not sure why.

If you have more than one USB to Serial device it is better to statically assign the USB to serial device to the RPi such that you configure a name to the device using the serial number of the device. IE: /dev/ttyX10 instead of /ttyUSBXX

Quickie static name for USB port assignment for my /dev/ttyUSB0 device.

NOTE: This is optional

1 - sudo su
2 - List USB attributes for the device:
udevadm info --name=/dev/ttyUSB0 --attribute-walk
3 - In the attribute list you should look for an attribute that is unique for a device (check idVendor and idProduct).
4 - Create (or open) a file /etc/udev/rules.d/99-usb-serial.rules_
If you found an unique attribute of the device then write a following line in the rules file.
5 - SUBSYSTEM=="tty", ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", MODE="0666", SYMLINK+="ttyX10"
6 - udevadm control --reload-rules
7 - ls /dev/ttyX*
8 - noticed that the X10 configuration drop down doesn't show "ttyX10". Not sure if this is a HomeSeer issue or plugin issue. I manually installed the configuration serial port in the /Config/X10.ini file as shown:

[Default]
PluginDebug=True
Protocol=0
ComPort=/dev/ttyX10

Tested it to work fine this way.

06:24:42:7906:[Startup]->Initializing Plug-Ins
Connecting to server at 127.0.0.1...
06:24:45:7409:[Info]->Plugin X10 has connected. IP:127.0.0.1:57800
Connected, waiting to be initialized...
06:24:45:8188:[Starting Plug-In]->Initializing plugin X10 ...
[B]06:24:46:4812:[X10 INFO]->Initializing CM11A/12U on COM port /dev/ttyX10[/B]
06:24:48:4681:[Starting Plug-In]->Plugin X10 started successfully in 2649 milliseconds
06:24:48:4795:[Starting Plug-In]->X10 loaded in 5621 milliseconds
06:24:48:4817:[Plug-In]->Finished initializing plug-in X10
06:25:08:2662:[X10 DEBUG]->CM11A.SendIt(): Sending 2 bytes: 0x 04 26
06:25:08:2775:[X10 DEBUG]->CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
06:25:08:2889:[X10 DEBUG]->CM11A.SendIt(): Received a good checksum: 0x2A
06:25:08:2980:[X10 DEBUG]->CM11A.SendIt(): Sending 0x00 to CM11a (command to execute).
06:25:08:7505:[X10 DEBUG]->CM11A.SendIt(): Got ack of: 0x55
06:25:08:7631:[X10 DEBUG]->CM11A.SendIt(): Success! 0.454 seconds for CM11a to send.
06:25:08:7747:[X10 DEBUG]->CM11A.SendIt(): Sending 2 bytes: 0x 06 22
06:25:08:7827:[X10 DEBUG]->CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
06:25:08:7924:[X10 DEBUG]->CM11A.SendIt(): Received a good checksum: 0x28
06:25:08:7995:[X10 DEBUG]->CM11A.SendIt(): Sending 0x00 to CM11a (command to execute).
06:25:09:2546:[X10 DEBUG]->CM11A.SendIt(): Got ack of: 0x55
06:25:09:2620:[X10 DEBUG]->CM11A.SendIt(): Success! 0.455 seconds for CM11a to send.

[Pete]

BTW when shutting down HS4 via terminal mode see this:

Shutdown IO called
Unhandled Exception:
System.NotImplementedException: implement me: Erl
at Microsoft.VisualBasic.CompilerServices.ProjectData.SetProjec tError (System.Exception ex, System.Int32 lErl) [0x00001] in <d1dad1a8bba2460091cc7ed2c3f04e36>:0
at HSPI_X10.CM11A.CheckThread () [0x004a5] in <98e8f2ad3e364f47ae717178344f58ef>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <533173d24dae460899d2b10975534bb0>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.NotImplementedException: implement me: Erl
at Microsoft.VisualBasic.CompilerServices.ProjectData.SetProjec tError (System.Exception ex, System.Int32 lErl) [0x00001] in <d1dad1a8bba2460091cc7ed2c3f04e36>:0
at HSPI_X10.CM11A.CheckThread () [0x004a5] in <98e8f2ad3e364f47ae717178344f58ef>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <533173d24dae460899d2b10975534bb0>:0

/opt/HomeSeer# mono -V
Mono JIT compiler version 6.12.0.122 (tarball Mon Feb 22 17:33:28 UTC 2021)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(610)
Suspend: hybrid
GC: sgen (concurrent by default)

[tbonini]

This is the debug of turning on and then off of C1 as you did. Because I just copied it directly from the log output, you have to read it from the bottom up and as I said before, the entire time I am getting these warnings, the lights on my smarthome X10 modules are flickering away which indicates a data storm of worthless and corrupt X10 transmissions. Where the device being controlled for the most part eventually responds correctly, any other number of devices on the same house code can be affected. When I manually control them with the ancient X10 clock, the indicators on the Smarthome controllers flicker briefly and the device responds immediately with no other random devices on that or any other house code being affected so it is not line noise or other components in the system causing it.

Dec-11 9:17:28 AM

X10 WARNING

3.795 seconds for CM11A to send data. Possible noise or interference on power line.

Dec-11 9:17:28 AM

X10 DEBUG

CM11A.SendIt(): Got ack of: 0x55

Dec-11 9:17:27 AM

X10 WARNING

Still waiting for CM11a to send data... (3.049 sec)

Dec-11 9:17:26 AM

X10 WARNING

Still waiting for CM11a to send data... (2.04 sec)

Dec-11 9:17:25 AM

X10 WARNING

Still waiting for CM11a to send data... (1.019 sec)

Dec-11 9:17:24 AM

X10 DEBUG

CM11A.SendIt(): Sending 0x00 to CM11a (command to execute).

Dec-11 9:17:24 AM

X10 DEBUG

CM11A.SendIt(): Received a good checksum: 0x29

Dec-11 9:17:24 AM

X10 DEBUG

CM11A.SendIt(): Data sent, waiting for checksum From CM11a...

Dec-11 9:17:24 AM

X10 DEBUG

CM11A.SendIt(): Sending 2 bytes: 0x 06 23

Dec-11 9:17:24 AM

X10 WARNING

6.1 seconds for CM11A to send data. Possible noise or interference on power line.

Dec-11 9:17:24 AM

X10 DEBUG

CM11A.SendIt(): Got ack of: 0x55

Dec-11 9:17:23 AM

X10 WARNING

Still waiting for CM11a to send data... (5.076 sec)

Dec-11 9:17:22 AM

X10 WARNING

Still waiting for CM11a to send data... (4.054 sec)

Dec-11 9:17:21 AM

X10 WARNING

Still waiting for CM11a to send data... (3.033 sec)

Dec-11 9:17:20 AM

X10 WARNING

Still waiting for CM11a to send data... (2.028 sec)

Dec-11 9:17:19 AM

X10 WARNING

Still waiting for CM11a to send data... (1.009 sec)

Dec-11 9:17:18 AM

X10 DEBUG

CM11A.SendIt(): Sending 0x00 to CM11a (command to execute).

Dec-11 9:17:18 AM

X10 DEBUG

CM11A.SendIt(): Received a good checksum: 0x2A

Dec-11 9:17:18 AM

X10 DEBUG

CM11A.SendIt(): Data sent, waiting for checksum From CM11a...

Dec-11 9:17:18 AM

X10 DEBUG

CM11A.SendIt(): Sending 2 bytes: 0x 04 26

Dec-11 9:17:18 AM

Device Control

Device: First Hallway Hallway Sleigh to Off (0) by/from: CAPI Control Handler

Dec-11 9:16:36 AM

X10 WARNING

1.995 seconds for CM11A to send data. Possible noise or interference on power line.

Dec-11 9:16:36 AM

X10 DEBUG

CM11A.SendIt(): Got ack of: 0x55

Dec-11 9:16:35 AM

X10 WARNING

Still waiting for CM11a to send data... (1.01 sec)

Dec-11 9:16:34 AM

X10 DEBUG

CM11A.SendIt(): Sending 0x00 to CM11a (command to execute).

Dec-11 9:16:34 AM

X10 DEBUG

CM11A.SendIt(): Received a good checksum: 0x28

Dec-11 9:16:34 AM

X10 DEBUG

CM11A.SendIt(): Data sent, waiting for checksum From CM11a...

Dec-11 9:16:34 AM

X10 DEBUG

CM11A.SendIt(): Sending 2 bytes: 0x 06 22

Dec-11 9:16:34 AM

X10 WARNING

3.949 seconds for CM11A to send data. Possible noise or interference on power line.

Dec-11 9:16:34 AM

X10 DEBUG

CM11A.SendIt(): Got ack of: 0x55

Dec-11 9:16:33 AM

X10 WARNING

Still waiting for CM11a to send data... (3.045 sec)

Dec-11 9:16:32 AM

X10 WARNING

Still waiting for CM11a to send data... (2.023 sec)

Dec-11 9:16:31 AM

X10 WARNING

Still waiting for CM11a to send data... (1.015 sec)

Dec-11 9:16:30 AM

X10 DEBUG

CM11A.SendIt(): Sending 0x00 to CM11a (command to execute).

Dec-11 9:16:30 AM

X10 DEBUG

CM11A.SendIt(): Received a good checksum: 0x2A

Dec-11 9:16:30 AM

X10 DEBUG

CM11A.SendIt(): Data sent, waiting for checksum From CM11a...

Dec-11 9:16:30 AM

X10 DEBUG

CM11A.SendIt(): Sending 2 bytes: 0x 04 26

Dec-11 9:16:30 AM

Device Control

Device: First Hallway Hallway Sleigh to On (100) by/from: CAPI Control Handler

[Pete]

The above stuff was done on a new HS4 build using same said plugin. Here have only utilized CM11A's with Homeseer over the years. Been doing X10 since the 1970's.

Let me test same on the HS3 builds with same plugin.

If you are familiar with Linux command line stuff then shut down HS3 and run it via command line in the terminal window.

Years ago on HS3 and using a power strip to test with did see that same stuff...and between Mark and I debugging it was related to using the original Volp X10 amplifier.

IE: the CM11A was plugged in to the original Volp X10 amplifier.

[mfisher]

In order to troubleshoot your X10 system issues (HS, the X10 plugin CM11a) it will be important to understand how the X10 plugin works and what the debug entries in your log mean. I'll use your supplied log entries to illustrate how the process works:

HS instructs the X10 plugin that virtual device C1 (First Hallway Hallway Sleigh) has changed to a status of ON

Dec-11 9:16:30 AM Device Control Device: First Hallway Hallway Sleigh to On (100) by/from: CAPI Control Handler

The X10 plugin transmits (via RS232) address C1 to the CM11a

Dec-11 9:16:30 AM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x 04 26

Then waits for the CM11a to send back a checksum

Dec-11 9:16:30 AM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...

The CM11a immediately responds with a checksum (and it was good), indicating it received a good command from the plugin. This also indicates that the RS232 communication link is working properly.

Dec-11 9:16:30 AM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x2A

Knowing the CM11a now has a good command, address C1 in this case, the plugin instructs the CM11a to transmit the address onto the powerline

Dec-11 9:16:30 AM X10 DEBUG CM11A.SendIt(): Sending 0x00 to CM11a (command to execute).

The CM11a transmits the address C1 onto the powerline, and as it is sending each bit of the code it also listens to the powerline to verify that the bits are being sent properly and there is no interference. In a "clean" X10 powerline environment the CM11a responds in less than 1 second with an acknowledge code (0x55) to let the plugin know the command was successfully transmitted onto the powerline. If the CM11a detects any interference while transmitting, it attempts to resend the command until it is successful. I do not recall how many times it tries to do this before giving up.

In your case, the CM11a has not responded to the plugin within 1 second so the plugin logs the anomaly

Dec-11 9:16:31 AM X10 WARNING Still waiting for CM11a to send data... (1.015 sec)

Another second later and the plugin still hasn't heard back from the CM11a

Dec-11 9:16:32 AM X10 WARNING Still waiting for CM11a to send data... (2.023 sec)

And another...

Dec-11 9:16:33 AM X10 WARNING Still waiting for CM11a to send data... (3.045 sec)

Finally, after 3 seconds the CM11a was able to successfully transmit the address C1 onto the powerline without any interference and it sends an acknowledge code of 55 back to the plugin

Dec-11 9:16:34 AM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55

The plugin then logs the fact that it took longer than normal to send this single piece of data on the powerline - hence the warning.

Dec-11 9:16:34 AM X10 WARNING 3.949 seconds for CM11A to send data. Possible noise or interference on power line.

Based on the above and the other similar entries in your log it is apparent that there is interference on your powerline that is being detected by your CM11a on almost every transmission attempt. This is why you see your SmartHome device LEDs "blinking like crazy" whenever the CM11a tries to transmit, because it is continually retransmitting until it thinks it successfully sent the command. Recall from above that it is the CM11a doing the retransmitting and not the X10 plugin.

When you used your other controller in to test your X10 environment did you plug it into the same outlet your CM11a is plugged into?

Have you plugged in anything new near your CM11a like a UPS or other electronic device? Any new devices plugged in elsewhere in your home? Devices like microwaves, garage door openers, flourescent lights, cell phone and tablet chargers, computer power supplies, TVs & A/V equipment, Uninterruptable Power Supplies (UPS), etc. can all create 120kHz noise on the powerline and/or can absorb ("suck") the small and weak X10 signals.

My suggestion would be to determine what has changed (been plugged in) since your system was working properly. Unplug all of those devices and verify that your CM11a transmits every command in under 1 sec (using the debug log entries) as it did before. Then, one-by-one, plug devices back in, send an X10 command from HS and verify the CM11a is still working correctly. When the "Still waiting" messages appear in the log you've found your offending device, or plugged in enough slightly-offending devices to create the problem.

Troubleshooting X10 powerline issues can be challenging and some additional searching on the 'net might be helpful. Here are a couple of links to get you started:
http://kbase.x10.com/wiki/Identifyin...ntrol_Problems
http://kbase.x10.com/wiki/Troublesho...ome_Automation

Please let us know how you fare.

[George]

Yup, X-10 is really sensitive to powerline noise. It got so bad that I speed up my conversion to Z-Wave. Problem is that the Omni-Pro only talks X-10 so I have to keep some around for interoperabilty. And like Pete, it's not worth the hassle or cost to change my Christmas plugs.

A while ago I wrote a script for HS 1.7 which listens to the X-10 comm and reports on invalid X-10 commands. This is also verified by the X-10 XTBM Powerline monitor. Corrupted X-10 packets. When one occurs, a ton of retransmission attempts are made by my active signal couplers resulting in an X-10 storm that can last for a minute or so.

Here is a sample of what can happen on the power line. I changed the script to only report on the J house code as I have nothing on J. So how is J being sent? My guess is J is special in binary X-10.

12/11/2021 11:59:42 AM~!~X10_anal~!~X10 data received = J;J1;3;0;0
12/11/2021 11:59:42 AM~!~X10_anal~!~X10 data received = J;J13;3;0;0
12/11/2021 11:59:43 AM~!~X10_anal~!~X10 data received = J;J11;3;0;0

12/11/2021 10:39:13 AM~!~X10_anal~!~X10 data received = J;J16;3;0;0
12/11/2021 10:39:13 AM~!~X10_anal~!~X10 data received = J;J4;3;0;0
12/11/2021 10:39:13 AM~!~X10_anal~!~X10 data received = J;J3;3;0;0
12/11/2021 10:39:13 AM~!~X10_anal~!~X10 data received = J;J2;3;0;0
12/11/2021 10:39:13 AM~!~X10_anal~!~X10 data received = J;J9;3;0;0

[tbonini]

First, I really want to thank everyone who took the time during this busy holiday season to try and help me out but I think that in this case, I'm going to have to throw in the X-10 towel. The sad truth is that X-10 is an ancient and dying tech and is really no longer compatible with my house and unlike Pete, it is completely worth it for me to change out the X-10 to put an end to the hassle. I can't change the position of the Pi that runs the system and I have not added anything that should be causing these issues. I already tried shutting down and unplugging various items that may cause issues such as my UPS's, and even the Refrigerator (that has a wired in X-10 filter on it) and nothing changed. Actually, yesterday afternoon it was running clean with no errors and then later that night, it went back to junk with no changes by me. Fortunately, I did find a plug-in for the TP-link smart plugs and it set it up today with a pair of these plugs that came in yesterday and it seems to work well and unlike my current X-10 situation, seems to be reliable as well. These plugs are low cost compared to Z-wave and will more than suite my needs for most of my holiday decorating needs. Currently I know that I will not be able to get them in time for this year but by next season, I hope to be X-10 free. Come to think of it, much of this equipment is well over 20 years old so it really owns me nothing and is due for an upgrade. Once again, thanks so much for your help and good luck in the future with your X-10 equipment.

[Pete]

It's really all about what works the best for you Tom.

Hate to see you give up on X10. There are many users here on the forum that continue to use it as their main automation protocol.

Merry Christmas to you and your family.

Lately here have been playing much with MQTT with little or no cloud interaction. (using custom firmware which removes the cloud pieces).

[tbonini]

Merry Christmas to you and your family as well Pete. I really didn't want to give up on X-10 and as I said, I have been using it for well over 20 years but it is becoming less and less reliable and more and more frustrating and that is just about the opposite of what you want in home automation. Equipment that this house requires to keep X-10 reliable is no longer available and newer household items just adds noise on the lines that the CM11a cannot deal with. Apparently, the Kasa outlets don't need the cloud for basic on / off commands with local control. If you want to use the built in advanced features then it need to get to the cloud but I will use HS for those abilities. I will further test in the next few days by blocking their internet access on the router and see if they are still controllable from HS and FPP and I will post back the results if you want to know.

[Pete]

Off the main topic ....

I have been able to convert X10, UPB, ZWave and Zigbee to MQTT now here which works for me but not too well with my ancillary combo OmniPro 2 alarm panel / automation panel.

Here always preferred metal conduit / boxes for my electric. In FL had the contractor install conduit at an added cost. In the midwest it is starting to change here from metal to plastic which I do not like. I am old fashioned a bit here.

I am not an electrician but have learned much in the last 40 years of tinkering with electricity. IE: last home redid the electric in the great room / TV room adding autonomous circuits for the multimedia, other outlets and lighting and fireplace stuff. IE: 4 breakers for the family room. A breaker per bedroom and separate for bathroom breakers type of stuff which involved pulling wire from the basement to the 2nd floor conduit type of stuff.

Here is the other option using Tasmota firmware on a wireless dual fan light switch which works in a metal box just fine. Using Ruckus WAPs today. All of my in wall switches are still using UPB today mostly because I can manage them with my Leviton OmniPro 2 combo alarm automation panel (not made any more) and Homeseer and Home Assistant. Never found an inwall combo fan / light switch that I liked until recently. I installed four of these a while ago and they have worked well. These can be configured independently from an automation controller using the built in timer functions and clock functions (IE: NTP). I have never been much of a wireless person here. House #2 is now all wireless using MQTT. I did add the Ring Alarm system and not managing it with my phone or android tablets but rather MQTT only and it works well locally and remotely from house #1.

[mfisher]

Sorry to see you give up on X10, but certainly understand your frustration. I still use X10 as my primary lighting protocol and while it's 99% reliable I do have occasional issues.

Please let me know if you end up throwing in the X10 towel and want to find a home for your equipment - I'm always on the lookout for spares.

Merry Christmas!

[concordseer]

Just before you pull the pin on this one could you clarify the following

Raspberry Pi model you are using
Version of Raspberry Pi OS installed
Version of Mono currently in use.

I understand your desire to bail on X10 but it would be of benefit to other users to track down the issue at play here. I notice you are still using HS3 and while Mark may still be tracking X10 issues on that version of HS from what I can gather no further development is being carried out on the core HS3.

I did notice that you have quite an updated version of Mono running on your system and that’s what caught my attention hence the reason for asking you to clarify the above.

As an aside I’m assuming neighbourly noise is not an issue here.

[tbonini]

The Pi is a Model 2B that I had lying around. I started way back with Ver 1 of HS on a Win XP PC. When Ver 2 came out, the interface was so horrible that I never fully installed it and stayed with Ver 1. I don't know why I was on the HS site but they were offering HS 3 Pi version fully licensed for free. I thought that there must be some catch all to it but since I had a spare Pi 2B sitting on the bench, I gave it a shot and ordered it and to my amazement, they sent me a license key. I downloaded the software as a Pi image file ald created the image on a SD card and entered the license file and it came up. According to the help file
HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.548
Linux version: Linux HS3Pi3v6 4.19.42-v7+
I don't know what Mono is so I can't answer that one but I have added nothing to the Pi other than the plug ins from HS for X-10 and Z-wave and recently a plug in for smart plugs that will be replacing the X-10 modules. I have set up a small V4 Pi version (whole thing from HS) for my sister and really don't like what they did on V4 so there is little chance of me ever gong there. I think that I would rather go with Home Assistant than do that.