@theotherclub, your second computer needs to have a "Voice Name" before Alexa will create devices for each of that computer's triggers.
Your first computer doesn't need a Voice Name because it's your default computer by default.
This page in the documentation explains further:
https://docs.triggercmd.com/#/./SmartHomeSwitches
@Mark-Hollis, your commands are not stored in the cloud. They're only stored on your computer, so if you don't have a backup of your commands.json file, you'll need to recreate them. One Windows you can find your commands.json file in this folder:
c:\Users\(your user)\.TRIGGERcmdData
If you're not subscribed, you'll need to delete your current computer before you can create another one.
@JRSF-Home , this worked for me to open and close the Trigger CMD PWA:
Command:
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge_proxy.exe" --profile-directory=Default --app-id=ehccgonefendpahldcmdgdmbkpbdmhbg --app-url=https://app.triggercmd.com/ --app-launch-source=4
Off Command:
taskkill /FI "WINDOWTITLE eq Trigger CMD"
I got that "Trigger CMD" text from the title of the PWA window.
@cesaronte, you should see an icon like this to open the side panel:
You can also find the token on your profile page which you can get to by clicking your name in the upper-right.
Awesome @Santiago. Thanks for letting me know. Sorry about the trouble.
@Santiago, will you please send the contents of your debug.log file? It might tell me what's going wrong.
Then, please try uninstalling and reinstalling the latest version.
If that still doesn't work, please try this old version;
https://agents.triggercmd.com/TRIGGERcmdAgentSetup36.exe
@Abel-Boby, do you see a list of voice commands on this page?
You should have one voice command for each of your triggercmd commands that has a voice word, but only if the computer is your default computer or it has a voice word assigned to it. You can set your default computer on your profile page.
In other words, these are the requirements for creating virtual devices in Google Home for your commands:
@karnold69 sorry, I didn't read your first post well enough. Now I understand you want to be able to dim your X10 bulbs with a Windows batch file using Alexa. Please try this script:
Be aware though, you can't dim smart bulbs or send a percentage to a triggercmd acommand by saying to Alexa, "Alexa, dim bulb X". You have to say "Alexa, dim bulb X to 20 percent", or something like that (where X is the bulb name or voice name for your triggercmd command.
I used ChatGPT to create this script, and tested it. I think it could work for you.
https://chatgpt.com/share/67a91dfc-f4a4-8004-bfd5-09f488830d9e
Here’s a revised version of your script that allows you to specify a percentage instead of the word "dim." It ensures the dim level is one of the allowed values (10, 20, 30, etc.) and calculates the number of dim commands needed accordingly.
script.bat:
batch
@echo off
set "level=%1"
:: Ensure the input is a valid percentage (10, 20, ..., 90)
if "%level%"=="10" goto valid
if "%level%"=="20" goto valid
if "%level%"=="30" goto valid
if "%level%"=="40" goto valid
if "%level%"=="50" goto valid
if "%level%"=="60" goto valid
if "%level%"=="70" goto valid
if "%level%"=="80" goto valid
if "%level%"=="90" goto valid
echo Invalid dim level. Please enter 10, 20, 30, ..., 90.
exit /b
:valid
:: Turn on the light (assumes it starts at 100)
curl http://127.0.0.1:8086/?x10command=DEVICE~sendplc~"K4 on"
:: Calculate the number of dim commands (each step reduces by 10%)
set /a "steps=(100 - %level%) / 10"
:: Send the dim commands
for /l %%i in (1,1,%steps%) do (
curl http://127.0.0.1:8086/?x10command=DEVICE~sendplc~"K4 dim"
)
echo Dimmed to %level%%