@abaratz, you're welcome. I'm glad that worked as a work-around. Thank you for reporting the problem too.
If anyone else experiences this problem, please tell me.
@abaratz, you're welcome. I'm glad that worked as a work-around. Thank you for reporting the problem too.
If anyone else experiences this problem, please tell me.
@abaratz, ok, we have the same OS. I meant 14.4.1 when I wrote 4.4.1 above. I hope it's not a CPU issue but I'll do some research and testing with Apple silicon. I'm pretty sure it has worked on Apple silicon though, so I doubt that's it.
If you haven't tried uninstalling / re-installing, that's something you could try. Also, what antivirus software do you have, if any.
Thank you for your help and patience BTW.
EDIT: I just tried it on a Mac with an M1 Applic silicon chip and it worked for me.
@abaratz , I don't see the same problem on my mac. Which Mac CPU are you running? I'm running an Intel.
FYI, I also deleted my agent and re-installed it after upgrading to 4.4.1 and it's still working for me.
@abaratz, no, there's no way that I know of to manually invoke the GUI Editor except via the Tray icon. I'm upgrading my mac to Sonoma 4.4.1 right now. If I can reproduce it I should be able to solve it. In the meantime, you could edit your commands.json file manually to add commands. It's a text json file at this path:
~/.TRIGGERcmdData/commands.json
~ is your home folder.
If you haven't tried closing and re-opening the TRIGGERcmdAgent, please try that.
@abaratz, if you run the TRIGGERcmdAgent app from your Applications folder, does it show up in your menu bar at the top?
I'm running Sonoma and it's working for me - it also auto-starts when I login.
There's one thing I don't understand about what you wrote. You cannot use one computer to create a command on a different computer, unless maybe you're using some sort of remote control, or editing the commands.json file across the network. You can only create commands using the computer the commands will run on.
Are you able to click the green Trigger button on the triggercmd.com website and see your command run on your second Mac? You should make sure that works before attempting to run it via Alexa or Google Assistant.
@Mateo-Fernandez, yes, unfortunately you'll need to make it faster. Alexa only gives a few seconds before a reply must be returned to Alexa, so TRIGGERcmd has to impose the same time limit.
@Emanuel-Esteves, in your user profile folder, there's a subfolder called .TRIGGERcmdData, for example:
C:\Users\russe\.TRIGGERcmdData
In that folder there's a commands.json and a computerid.cfg file. If you put the ID of the old computer in the computerid.cfg file, it will login as that computer. The commands.json file contains your commands, so if you still have a copy of that, you'll be able to restore your commands. Otherwise, you'll need to rebuild your commands. When your computer logs in, it synchronizes the commands in commands.json with the computer record in your TRIGGERcmd account.
To find the ID of your old computer, you can click View Triggers for that computer, then you'll see the computer ID in the browser URL:
I hope this helps. Sorry if this means you lost your commands and you need to rebuild them. At least you have a list of them in your account in the old computer record.
@Mateo-Fernandez, will you please try changing the action to this?
Alexa, pedirle Ejecuta Comando ejecuta saldo.
I think it might need to be in Spanish, unless you already know you're able to say to your Echo Dot, "Alexa, ask trigger C M D to run saldo" and it works.
@Thiago-Soares, which Alexa skill did you link? You need to link the TRIGGERcmd Smart Home skill for Alexa devices to appear for each of your commands. Your commands also need to have the voice field filled in. Your computer also needs the voice field filled in or it needs to be your default computer. You can set your default computer in your profile.
@Brunera-EL, one of the advantages of the background service is it runs before you login. It also runs background commands as root on Linux.
If you create a background command, does it show up on the website? If so, that means the background service is working. Please try changing the ground setting on your shutdown command to background, and try running it before you login. It should work.
@Igor-Marinho, Alexa talks to the TRIGGERcmd servers, and the TRIGGERcmd servers talk to the agents. Next time, please test the agent first by running your commands from the triggercmd.com website. If that works, there's no need to troubleshoot the agent and you can move on to troubleshooting the Alexa integration. Also if you do have an agent problem, instead of uninstalling/re-installing it, you should try restarting it.
We can troubleshoot Alexa after you re-install the TRIGGERcmd agent and test it from the triggercmd.com website.
Please try deleting your C:\Users\(your user)\AppData\Local\triggercmdagent directory, then re-install the TRIGGERcmd agent. Hopefully that will work around the installation error.
@Smart-Communities, you could install the background service and make your commands background commands. Then they'll run in the context of the TRIGGERcmdAgent Windows service.
@marti-ruiz, the parameters you send with your trigger always get tacked on to the end of your command, so you should put that same command in a .bat file if you want the parameter where the %1 is.
Your TRIGGERcmd command would run your .bat script like this:
Your label.bat script contents:
type "C:\BC\%1" > \\mycomputer.local\ZEBRA
@Smart-Communities, if you give the new device the same computer name, the short bookmarks should still work. They specify a computer name and trigger name.
Normal bookmarks specify the trigger ID so those stop working if you even change certain fields in the trigger, like the name because that deletes and recreates the trigger with a new ID.
@El-Kortungas, what does it show in your Runs list for the command? I just ran Calculator using the TRIGGERcmd Smart Home skill and it ran only once as you can see here:
Also, which Alexa skill are you using? The runs list will show that too. I recommend the TRIGGERcmd Smart Home skill.
You could try unlinking and re-linking the skill.
@Marcos-Raldes, sorry you're right - I see that now. I'm still not sure why the TRIGGERcmd devices don't show up in Home app as a routine (aka Automation) starter option, but you can create routines that work with TRIGGERcmd using Google's script editor, then after it's created you can edit it in the Home app.
I made this video to demonstrate it: https://youtu.be/aP3FAuh291s
Here's my test routine that works for me:
The editor makes it easy to select your devices. You just start typing the name and it brings up a list of your devices that contain those letters.
Your TRIGGERcmd commands will only show up as Google devices if they have the voice field filled in. The computer also needs the voice field filled in, unless it's your default computer (set in your profile).
You'll also need to add your command's Google device to a home and a room before it will work. Long-press the device, then tap the gear in the upper-right, then tap Home (Add to a home).
Notice you specify whether the routine should run when the TRIGGERcmd device is flipped on or off. That's different from Alexa where triggering a command is like a doorbell press that runs the routine.
The state defaults to on unless you send off as the parameter, so you can run Google routines without having to send a parameter when you trigger your commands.
You can also create a routine (aka Automation) that triggers a command. You can use TRIGGERcmd device as a starter or an action but either way, you have to use the script editor to create the routine, not the Google Home app on your phone.
Anyone still use Winamp to play .mp3 files?
The Milkdrop visuals are still the best - for example.
I built a TRIGGERcmd panel to control Winamp, including a set of my favorite visual "presets."
Here's a Youtube video showing how it works.
This is the panel:
The "Preset Favorite" panel buttons run my winamp_preset.bat script with the letter as the parameter, and uses nircmd to press a series of buttons to pick the preset that starts with that letter.
You can see here I copied some of my favorite presets to a folder called russ, and prefixed each one with a letter from a to h:
This my panel JSON:
[
{
"name": "Preset Favorite",
"trigger": "DS | winamp preset",
"params": "a,b,c,d,e,f,g,h"
},
{
"name": "Next/Previous Preset",
"trigger": "DS | winamp next/previous preset",
"params": "previous,next"
},
{
"name": "Volume",
"trigger": "DS | winamp volume",
"params": "up,down"
},
{
"name": "Show Song Title",
"trigger": "DS | winamp show title",
"params": ""
},
{
"name": "Presets List",
"trigger": "DS | winamp preset folder",
"params": "russ,all"
},
{
"name": "Forward/Reverse",
"trigger": "DS | winamp forward reverse",
"params": "reverse,forward"
}
]
My commands.json entries:
{
"trigger": "winamp preset",
"command": "c:\\tools\\winamp_controller.bat",
"offCommand": "",
"ground": "foreground",
"voice": "",
"voiceReply": "",
"allowParams": "true"
},
{
"trigger": "winamp show title",
"command": "nircmd sendkeypress t",
"offCommand": "",
"ground": "foreground",
"voice": "",
"voiceReply": "",
"allowParams": "false"
},
{
"trigger": "winamp preset folder",
"command": "c:\\tools\\winamp_preset_folder.bat",
"offCommand": "",
"ground": "foreground",
"voice": "",
"voiceReply": "",
"allowParams": "true"
},
{
"trigger": "winamp volume",
"command": "c:\\tools\\winamp_volume.bat",
"offCommand": "",
"ground": "foreground",
"voice": "",
"voiceReply": "",
"allowParams": "true"
},
{
"trigger": "winamp forward reverse",
"command": "c:\\tools\\winamp_ff_rw.bat",
"offCommand": "",
"ground": "foreground",
"voice": "",
"voiceReply": "",
"allowParams": "true"
},
{
"trigger": "winamp next/previous preset",
"command": "c:\\tools\\winamp_next_previous_preset.bat",
"offCommand": "",
"ground": "foreground",
"voice": "",
"voiceReply": "",
"allowParams": "true"
}
These are the .bat files in my c:\tools folder:
winamp_ff_rw.bat
if "%1"=="reverse" nircmd sendkeypress left
if "%1"=="forward" nircmd sendkeypress right
winamp_next_previous_preset.bat
if "%1"=="next" nircmd sendkeypress spc
if "%1"=="previous" nircmd sendkeypress backspace
winamp_preset.bat
nircmd sendkeypress l
nircmd sendkeypress %1
nircmd sendkeypress enter
nircmd sendkeypress esc
winamp_volume.bat
if "%1"=="+" nircmd sendkeypress up
if "%1"=="-" nircmd sendkeypress down
if "%1"=="up" nircmd sendkeypress up
if "%1"=="down" nircmd sendkeypress down
winamp_preset_folder.bat
rem bring up the current presets path
nircmd sendkeypress f8
if "%1"=="russ" goto russ
if "%1"=="all" goto all
goto end
:russ
rem backspace for each letter in "presets"
nircmd sendkeypress backspace
nircmd sendkeypress backspace
nircmd sendkeypress backspace
nircmd sendkeypress backspace
nircmd sendkeypress backspace
nircmd sendkeypress backspace
nircmd sendkeypress backspace
rem type out russ
nircmd sendkeypress r
nircmd sendkeypress u
nircmd sendkeypress s
nircmd sendkeypress s
goto select
:all
rem backspace for each letter in "russ"
nircmd sendkeypress backspace
nircmd sendkeypress backspace
nircmd sendkeypress backspace
nircmd sendkeypress backspace
rem type out presets
nircmd sendkeypress p
nircmd sendkeypress r
nircmd sendkeypress e
nircmd sendkeypress s
nircmd sendkeypress e
nircmd sendkeypress t
nircmd sendkeypress s
goto select
:select
rem press enter
nircmd sendkeypress enter
nircmd sendkeypress esc
nircmd sendkeypress escape
:end
@Mike-Vecchiarelli , can you send me a copy of your debug.log file?
I wonder if you see multiple instances of something like this:
|> Now connected to https://www.triggercmd.com.
\___/ For help, see: http://bit.ly/2q0QDpf
(using sails.io.js node SDK @v1.2.1)
Connected at: Fri Mar 15 2024 18:24:00 GMT-0400 (Eastern Daylight Time)
Also, can you tell me the versions of the agent on your 4 computers? If they're different, that could be a clue.
Also, I have better logging now, so I can probably track down the server logs related to your issue if you give me the time and your computer ID or account email address if/when it happens again.
@AZRushFan, I suspect maybe you didn't close the SmartThings app after you enabled Developer mode. You can't just navigate away from it. Also I think they updated the app so you no longer have to scroll way to the bottom to find My Testing Devices. I see it near the top now.
@Marcos-Raldes, unfortunately Google Assistant does not offer the ability to activate a routine when something like a doorbell button is pressed. Alexa does, and that's why you're able to run an Alexa routine when one of your TRIGGERcmd commands is triggered. <- Correction, I was wrong about this. You can create routines but you have to use the script editor. See post below.
That said, you could run a routine from a python script on your computer if you wanted. I asked the AI Script Assistant to generate a script to do that. This is what it gave me:
AI Prompt: python script on Windows to run a google assistant routine
To run a Google Assistant routine on Windows using Python, you can use the google-auth and google-assistant-sdk libraries. Here’s an example script:
import os
import json
import google.auth.credentials
from google.assistant.library import Assistant
from google.assistant.library.event import EventType
from google.assistant.library.file_helpers import existing_file
# Set the path to your credentials file
credentials_file = 'path/to/credentials.json'
# Load the credentials from the file
with open(credentials_file, 'r') as f:
credentials = google.auth.credentials.Credentials.from_authorized_user_info(json.load(f))
# Define the routine you want to run
routine = 'Good morning'
# Create an Assistant instance
with Assistant(credentials) as assistant:
# Start the conversation
assistant.start_conversation()
# Send a text query to trigger the routine
response = assistant.send_text_query(routine)
# Print the response
print(response)
Make sure to replace path/to/credentials.json with the actual path to your credentials file. You can create a credentials file by following the instructions in the Google Assistant SDK documentation.
To run the script, open a command prompt or PowerShell window and navigate to the directory where the script is saved. Then, run the command python script_name.py, replacing script_name.py with the actual name of your script file.