Posts made by Russ

@gajahduduk, changing the command's voice word might be what fixed it. That deletes and recreates the Alexa device.

@gajahduduk, I built this amd64 (Apple Silicon) version. Would you mind testing it?

https://agents.triggercmd.com/TRIGGERcmdAgent-darwin-arm64-1.0.38.zip

It's a .zip instead of a .dmg, so just move the app into your Applcations folder after you unzip it.

@gajahduduk, thanks. Researching this now.

@gajahduduk, the first computer is supposed to be your default computer. If you delete it and recreate it I don't think it makes the new one your default.

I'm glad you figured it out. Sorry if the system failed to make your first computer your default.

@gajahduduk, thanks for the screenshots.

Please go into your profile page and make sure your MacStudio.local computer is your default computer. Or, make sure that computer has a Voice Name. One or the other is necessary for Alexa to create devices for your computers.

I recommand making it your default computer so you can just say, "Alexa, turn on calculator" rather than "Alexa, turn on calculator on mac" (assuming you'd make the Voice Name "mac").

https://docs.triggercmd.com/#/./SmartHomeSwitches

@Ego95, can you send a screenshot of the blank examples screen?

Also, do you see your computer and its commands in your account at triggercmd.com? Do you see anything in the Runs list for the commands after you click the Trigger button?

@gajahduduk, if you linked the TRIGGERcmd Smart Home alexa skill to your TRIGGERcmd account, you should have a device in your Alexa device list for each of your commands that have a voice word.

If you have a calculator device, Alexa will turn it on if you say turn on calculator, but Alexa will think you want to play music if you say turn on music.

You can't say "Alexa, play mac music" because you can't "play" an Alexa smart home device - you can turn it on though.

@gajahduduk, thanks. I'll look into an arm build and the icon change. Not sure why it's crashing. I'm pretty sure I tested it on an M1 arm mac.

@Colin-M Google's removal of the conversational Google action removed the voice reply capability for Google Home, but you could still do it with the Alexa Triggercmd skill.

@Adroit-Tester2, the background agent on Windows is meant to run commands that don't do anything with the GUI, like this reboot command:

shutdown /r /t 1

One benefit is the TRIGGERcmdAgent Windows service runs before you login, so you could reboot the PC even if it's not logged in.

Background commands run in the context of the TRIGGERcmdAgent Windows service that runs as Local System, which can be of benefit too because it has full access to your PC and it bypasses UAC.

Here's a test command you use try in background mode to verify it's working:

echo testing > c:\folder\log.txt

I just tried that and it produced the log.txt file when I ran it in background mode.

If you want to see the processes run, I suggest you leave them in foreground mode. You could still lock the PC after logging it on if you don't want the developers to mess with them.

@Mark-Hollis, it's not down and it looks like it wasn't down at all today. What problem are you seeing?

@tommy0981, the token is on the Instructions page and on your Profile page.

@Severus, please look for the "tray" icon. It looks like the square Triggercmd icon. You have to click the up arrow near the clock in the lower right corner of the screen to see your tray icons.

@Jeferson-Borges, have you found the GUI Command Editor?

You can use it to add your commands, like this:

To open the GUI Command Editor, right click the TRIGGERcmd Agent's tray icon first:

@Bruno-Oliveira-0 said in Run a Google Routine:

"Ok Google, run ligar abajur

Thank you for the screenshots.

I think I see the problem. When you say this, you're not running your command with the on parameter.
"Ok Google, run ligar abajur"

You should do 2 things:

• Change Permitir Parametros to true so it will accept the on and off parameters.
• Say, "Ok Google, turn on ligar abajur" so Google will send on as the parameter.

Actually, you should change the Trigger and Voice fields to just "abajur" because "ligar" means turn on, but then you'll also need to update your Automation code to use "abajur - PC" as your device under starters instead of "ligar abajur - PC". Then say, "Ok Google, ligar abajur" to run your abajur command with the on parameter which is what your Automation's starter will be looking for.

@Avik-Basu the agent is fine, no need to update. I patched it on the server side.

BTW this is where I keep track of agent version releases:
https://www.triggercmd.com/forum/topic/14/triggercmd-agent-versions

@OPTIMUS-PЯIMΞ , sorry guys. There was an outage this morning but it's fixed now.

I'm not sure, but it was likely a denial of service attack.

I figured out what was happening and patched the code so it can't happen again.

@Bruno-Oliveira-0, please confirm these things:

• The ligar abajur TRIGGERcmd device is in the PC room in Google Home.
• The Abajur do Escritório device is in the Escritório room in Google Home.
• You can turn on the Abajur do Escritório device from your Google Home app.
• You can run the ligar abajur command by saying, "Hey Google, turn on ligar abajur" or by toggling it on from virtual device in the Google Home app.
• You want your Automation to turn on the Abajur do Escritório device (the action) when you run the ligar abajur command via TRIGGERcmd with parameter on (the starter), if Abajur do Escritório is currently off (the condition).

Also, how are you running the ligar abajur command via TRIGGERcmd with parameter on? Are you using the TRIGGERcmd website?

I suggest you test using the orange Parameters button where you can enter your on parameter:

Also, please send me a screenshot of your Automation code. I'm curious if it shows a red underline like this or not. If it does, your device is probably not in a room.

Also, please confirm the automation is activated.

I just tested this myself. At first my TRIGGERcmd command's device wasn't showing up in the list because it wasn't in a room. It has to be in a room before it will work. If you change certain things about the command, you'll have to re-add it to the room because the virtual device will get deleted and re-created.

@Bruno-Oliveira-0, I just added the code for the notepad on -> lamp on example from the video. I hope that helps.

@Danilo-Vaz awesome. De nada.