Best posts made by tuicemen

I realize this is an old thread but it needs to be pointed out that this is not the only way to control X10 from TRIGGERcmd.
The software "X10commander" is a third party software built using the X10 SDK sample program AHCMD which uses the x10 driver (dll). You can directly call this Windows sample program with TRIGGERcmd or use 1 of many other programs that use AHCMD, the x10 driver or their own drivers.

I have nothing against X10commander so please don't take my comments as such. Originaly AHCMD was only in the AHP SDK but later included with the ActiveHomePro (AHP)x10 software. It was only intended to use for simple single command sends and to help debug AHP. Pushing to many commands in a row to AHCMD can cause it to behave erratic or even lock up. If you intend to use AHCMD please besure to use the one that came with AHP 3.318 as it will be the most stable.

@russ Thanks, I found my error, the line in the commands.json file was correct.
I was putting in the wrong X10 address for my test thus it was turning on/off a light in the basement not my test light.

@mevlüt-bora there are several reasons a windows PC will refuse to shut down A failed update is usually the reason. However here are a few things you can try. https://www.minitool.com/backup-tips/windows-10-wont-shut-down.html

I've been controlling my Pan& Tilt cameras via a variety of different apps for decades even before WiFi Cameras were available.
Most of these were X10 cameras and some fosscams. I've moved away from my old wired and RF wireless X10 cameras and now use HD X10 wifi cameras and still some older fosscam low def wifi cameras.
I prefer the Pan & tilt cameras over the stationary ones as you get a much larger coverage area.
I currently have my cameras pan to a door or window when they are opened via HomeGenie. The cool factor of doing it via Alexa voice was achieved via HA-Bridge but for google it wasn't. With TRIGGERcms Smarthome I now believe I can do this via Alexa & or Google which adds a bigger cool factor.

Most any IP Cammera can do this provided you can get your hands on the control protocols.
Luckily I have these for the X10 XX70A HD Airsight & X10 XX69A HD Airsight
To turn one to a preset is a simple url api call for the
XX70A
X10 still sells this and is in stock last time I checked.
Preset 1 calls are simple and would look like:

IP&port/cgi-bin/decoder_control.cgi?&type=2&cmd=0&user=******&pwd=*****

Naturaly you change the IP&port to that of the camera and change the user and pwd.
For preset 2 you'd change the cm=0 to cmd=1
For preset 3 you'd change the cm=0 to cmd=2 and so on
The XX69A uses the same api calls not sure if it is out of stock or no longer available.

I do have a couple older Pan&tilt foss & easyn cams and the preset codes for them but the model numbers I'm not sure of till I can get up to look at them.

@russ, I did know the smarthome skill wouldn't work for this. But didn't realize I could have Alexa or Google respond to a script ran manualy with a TRIGGERcmd call inside to enable a voice responce. This is cool and has me thinking of some new Ideas.

@russ the cool thing is, like TRIGGERcmd it can be used on a variety of OSs, Mac, Windows, Linux, Raspi

@karnold69 Windows updates in particular Driver updates are a issue for X10 If driver updating is not disabled. Windows will install the newest X10 driver which is not compatible with the USB driver for AHPSDK.exe that x10 commander uses. The fix for this is to reinstall the x10 driver found on your PC If I remember their in program files/common files/X10/drivers.

@tal-sabadia, there is a way to get a simple "failed" or "succeeded" voice response for a long script run or a script that you trigger manually.

• 1: It requires creating two TRIGGER.cmd dummy scripts (dummy1 & dummy2) that simply echo "OK" when ran from command line.
• 2: At the end of the backup script have them triggered (using the tcmd tool found here https://www.triggercmd.com/forum/topic/196/tcmd-go-command-line-tool-is-available-now) based 1 on a fail and other on a succeed result.
• 3: In Alexa routines create two, one for dummy1 that Alexa says something like, "Trigger C M D reports script succeeded"
  The other for dummy2 that Alexa says something like, "Trigger C M D reports script failed"

This way you can use the same routines and dummy scripts for several different long running scripts and even for scripts that aren't started by TRIGGERcmd

@Russ , seems Alexa and Google send lower case on/off commands and HomeGenie requires the commands to start with upper case. I'm not sure why with using just 1 parameter this seems to work but with 3 parameters it doesn't

In any case I've got a work around for this in the Bash script which I edited to look like this now

#!/bin/bash
foo=$(echo "${3}" | awk '{$1=toupper(substr($1,0,1))substr($1,2)}1')
echo Sent HomeGenie the $1 command $2 to turn $foo >> /home/pi/scripts/HGsents.txt
echo "Sending HomeGenie the $1 command $2 to turn $foo"

curl http://192.168.0.24:8084/api/HomeAutomation.$1/$2/Control.$foo

next I'll start to play with adding dim commands but not sure if TRIGGERcmd will process them from Alexa/Google

@steve-porter here is the script : X10.sh
you can test in in the command line by typing sh X10.sh i6 on
to turn your fan off simply change the on to off

@russ, Ok I see what I'm doing Wrong!
For some reason my samsung browser loaded with display panels and edge loaded with display computers.
All is good!

@russ, Thanks. It took me A few times to get it to work I was using TRIGGERcmd as one word needed the spaces ( C M D).

I created a bash script for my off grid HomeGenie Server similar to this which displays the Status and current IP in a widget.
It is on a DSL line so the IP does change from time to time. The url calls are posted on the DuckDNS.org site.
I converted it to a python3 Ducks.py script for TRIGGERcmd.
you'll need a free DuckDNS account and create a domain and get a token for that domain name
the script looks like this:

#Libraries

import requests
import os
url = "https://www.duckdns.org/update?domains=YOURDOMAIN&token=YOURTOKEN"
result = requests.get(url)
if result.text == "OK":
 os.system ('~/.TRIGGERcmdData/sendresult.sh ' + result.text)
else:
 os.system ('~/.TRIGGERcmdData/sendresult.sh ' + 'Broken')
# Print to commandline
print (result.text)

replace "YOURDOMAIN" with the one you created and replace "YOURTOKEN" with what DuckDNS asigns you.

I added this line to my commands.json text

{"trigger":"Duck D N S","command":"python3 /home/pi/scripts/Ducks.py","ground":"background","voice":"Duck D N S","voiceReply":"The Duck D N S conection is {{result}}","allowParams": "false"}

If your like me and find the decimal point in the return a bit confusing you can change the line

 os.system('~/.TRIGGERcmdData/sendresult.sh ' + 'Temp={0:0.1f}  Humidity={1:0.1f}'.format(t,h))

to

os.system('~/.TRIGGERcmdData/sendresult.sh ' + 'Temp={0:0.0f}  Humidity={1:0.0f}'.format(t,h))

if you wish the return to send a Fahrenheit value instead of Celsius you can add the line

t = (t* 1.8) + 32

just after the line

#Print Temperature and Humidity on Shell window

@russ thanks, I removed the deviceType from my json file and had Alexa rediscover and they do still dim. I edited my previous post.
It should be noted that using dim turns the device to that value. So if you turn a light on (100%) then say dim 20% it doesn't set the light level to 80 but instead sets the light level to 20.
At least that's the way it works for HG.