@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.