@Russ
Been busy testing and trying things. Thanks for the logging script. Here is a bat file script:
if "%1"=="on" curl http://127.0.0.1:8086/?x10command=DEVICE~sendplc~%"K12% on%"
if "%1"=="off" curl http://127.0.0.1:8086/?x10command=DEVICE~sendplc~%"K12% off%"
echo "Study light script ran with param %1" >> c:\scripts\x10_log.txt

Like all of my scripts, they're a cut and paste from your forum with the name, house code and unit codes changed. I had the same results (intermittent) running it from a command prompt. But the script log showed me your end is working 100%. Problem is on my end. Started after a Win 10 update.

Also tested the phase coupler I installed in the breaker box. It's working fine.

On a whim, I reformatted the SSD in the COOFUN mini computer as GUID instead of MBR and restored with Acronis. Now I'm getting about 95% reliability. May do it again with an older backup and keep a closer eye on updates. I disable all the related services and tasks with a utility called execTI (execute trusted installer). Also added registry entries for NoAutoUpdate.

If I can't get back to 99.9% reliability I'm going to switch to my other computer I have registered with TRIGGERcmd. It's running Windows 7 64-bit. It's in use as a Plex server so I wanted to keep the X10 stuff on a dedicated computer.

BTW, talked to the X10 company about the new hub they're working on. They were turned down by Amazon to interface it with Alexa! And yet you were able to get approved! Nice!

Thanks again for your help.

Ken

@Russ I restored to an older backup and uninstalled update KB5022282. It's working MUCH better. Although even though I deleted everything in the update folder Windows/SoftwareDistribution/Download, Windows installed 2 other updates when I rebooted to remove the update. Also, when I give a command from on echo dot and it doesn't work, then give the same command to another echo it works. Probably just from giving the command again as they all go to the same computer/CM15a. Things are working better (but not perfect) today.
If you know a way to prevent windows updates I'd appreciate the info. If not appropriate on this forum, I can be reached at ken@homewithwine.com.

@tuicemen Thanks!

@Russ
Been busy testing and trying things. Thanks for the logging script. Here is a bat file script:
if "%1"=="on" curl http://127.0.0.1:8086/?x10command=DEVICE~sendplc~%"K12% on%"
if "%1"=="off" curl http://127.0.0.1:8086/?x10command=DEVICE~sendplc~%"K12% off%"
echo "Study light script ran with param %1" >> c:\scripts\x10_log.txt

Like all of my scripts, they're a cut and paste from your forum with the name, house code and unit codes changed. I had the same results (intermittent) running it from a command prompt. But the script log showed me your end is working 100%. Problem is on my end. Started after a Win 10 update.

Also tested the phase coupler I installed in the breaker box. It's working fine.

On a whim, I reformatted the SSD in the COOFUN mini computer as GUID instead of MBR and restored with Acronis. Now I'm getting about 95% reliability. May do it again with an older backup and keep a closer eye on updates. I disable all the related services and tasks with a utility called execTI (execute trusted installer). Also added registry entries for NoAutoUpdate.

If I can't get back to 99.9% reliability I'm going to switch to my other computer I have registered with TRIGGERcmd. It's running Windows 7 64-bit. It's in use as a Plex server so I wanted to keep the X10 stuff on a dedicated computer.

BTW, talked to the X10 company about the new hub they're working on. They were turned down by Amazon to interface it with Alexa! And yet you were able to get approved! Nice!

Thanks again for your help.

Ken

@Russ This morning I gave the "patio lights off" command multiple times, and it never worked (although they did turn on.) Here's the list:
Command ran Thu Mar 16 2023 07:22:25 GMT-0500 (Central Daylight Time)
Trigger sent from Alexa Smart Home params = off Thu Mar 16 2023 07:22:25 GMT-0500 (Central Daylight Time)
Command ran Thu Mar 16 2023 07:19:54 GMT-0500 (Central Daylight Time)
Trigger sent from Alexa Smart Home params = off Thu Mar 16 2023 07:19:54 GMT-0500 (Central Daylight Time)
Command ran Thu Mar 16 2023 07:19:49 GMT-0500 (Central Daylight Time)
Trigger sent from Alexa Smart Home params = off Thu Mar 16 2023 07:19:48 GMT-0500 (Central Daylight Time)
Command ran Thu Mar 16 2023 07:19:43 GMT-0500 (Central Daylight Time)
Trigger sent from Alexa Smart Home params = off Thu Mar 16 2023 07:19:43 GMT-0500 (Central Daylight Time)
Command ran Thu Mar 16 2023 07:19:15 GMT-0500 (Central Daylight Time)
Trigger sent from Alexa Smart Home params = off Thu Mar 16 2023 07:19:15 GMT-0500 (Central Daylight Time)

I'm using the TRIGGERcmd Smart Home skill and the TRIGGER command skill. This has been working fine for 10 months, very reliable.

I'm wondering if a Windows 10 update is causing the problem. I go to great lengths to prevent updates, but one slipped through that caused X10 Commander to disappear from the sys tray when I minimized it. I backed the update out and it was fine although Windows indicated "not all of the update was removed."

I'm running your software on a dedicated COOFUN mini computer. Wish I could run Windows 7 on it, might solve the problem.

In about the last week my X10 commands have worked intermittently. Nothing changed here, running the software on a dedicated mini computer for about 10 months. Any other such reports? Has your customer base grown needing more servers on your end? Thanks.
Ken

@russ Do you know of a .bat file parameter to turn a light on dim?

@russ You're awesome! Got it working and subscribed. So happy to have voice control back since Insteon died! Luckily my Insteon wall switches were all programmed with X10 codes. Just had to rebuy new plug in modules and in line modules.

@johnnyx10 Could you please post the commands you used? And where do the .bat files go? I'm guessing the file name for the .bat files goes in the "Select Trigger" field? If not, what goes in that field? Thanks!

@russ

Does this work with a Firecracker? It would be my preference to use that if so. That seems to be the main device X10 Commander works with. Thanks.

Ken Arnold