@Nico-Ramirez, Google Translate translated what you said to this:
Question, I use python, when I make sure that the argument is empty, could you help me with what serious or problem, please

I'm not sure what the problem is. Please clarify.

@buaamm, so far I've added Japanese support for TRIGGERcmd Smart Home - both Alexa and Google Assistant.

Would you mind testing? Please tell me if I got anything wrong.

@William-Santiago-Ortiz-Trejos, for some reason your files with a .ahk extension aren't associated with AutoHotkey. That's supposed to happen when you install it, but maybe an antivirus program blocked it?

To fix it you could try running the batch file in this article from your C:\Program Files\AutoHotkey folder:
https://www.autohotkey.com/board/topic/13627-no-ahk-file-association/

@Antonio-Leaños, when I tried a command like this, it worked for me.

start /min /wait timeout 5 & calc

It waited 5 seconds, then ran calculator.

Does that work for you? If not, can you tell me what command you're trying?

@Joe,

1 - Only Foreground Triggers work in a user's regular account - because the background service only runs as root and uses /root/.TRIGGERcmdData.

2 - Root can support both Foreground and Background Triggers - because you can install the background service (see #1), and because you can login as root and run the agent in foreground mode.

3 - But running Triggers as Root will mask/override all the Triggers in your regular account - I wouldn't say mask/override, it's just separate as you covered in #4. Running the agent as root will create another separate computer entry in your account associated with /root/.TRIGGERcmdData. That computer will be named the same initially, but you could rename it.

4 - The exception to (3) is if you can instantiate two "Computers" -- one pointing to Root for the "Background", and a separate "Computer" pointing to your normal Linux account to support the "Foreground" - correct, although as you pointed out in #2, you could also run the foreground agent as root.

You create a separate computer just by running the agent as the other user. If the ~/.TRIGGERcmdData directory doesn't exist, the agent will prompt you for a token, create a computer record in your account, and store the ID for that computer in the computerid.cfg file.

Different Linux accounts could setup different computer records, or you could give everyone sudo access to be able to edit /root/.TRIGGERcmdData/commands.json to run background command via the background agent.

The agent stores the .TRIGGERcmdData directory in the home folder of the user running the agent. The files in that directory are the key point of connection to the mother ship.

Good questions @Joe.

@Paulo-Filho You can use any exe-bat converter. But Russ updated the software, now it should work even without the bat fix

@George-Hatzisymeon, sorry I never responded to this. I just noticed it because someone upvoted it.

I just verified that the offCommand commands.json value is supported in the current version of the Raspberry Pi agent. If you were using that version and it didn't work, then maybe you were missing this part:

"allowParams":"true"

Here's an example entry I just tested. It turns my led strip off if the parameter was off, and if the parameter was on, it turns the strip on and makes the leds green.

{ "trigger":"Green", "command":"\/root\/killrun.sh leds.py green", "offCommand": "\/root\/killrun.sh leds.py off", "ground":"background", "voice":"green", "allowParams":"true" },

@Russ said in SmartThings integration - flip a virtual switch to run a command:

Handler

It works like a charm!
I have just follow the instructions, and had it immediately working. Still good at 2021

@Russ Thank u Ross.

@Russ, very good. I think applying a decode('utf-8') should solve this problem. I really hadn't tried using special characters yet.

@Mittal-Makwana, nice, what command does that?

@Russ Thanks for the clarification. That was my understanding as well - to share TRIGGERcmd for all, either everybody has to use Voice Match or nobody can use it. Unfortunately, the children really want to use the Voice Match (required to teach Google Home important things such as names of our cats etc) while both me and my wife are strictly against Voice Match for us. That means that the children could share TriggerCMD but no solution for the adults. And we'd need TriggerCNS exactly mainly for the adults...

I understand it's a relatively specific situation though, so probably no solution will be available. I was hoping for something similar to Spotify (that works also for non-VoiceMatch members of the household) but I understand it may be difficult to achieve. Thanks for your efforts anyway!

@Russ said in Never used parameters before...:

@Royher-Figuera, in a .bat file, the syntax for a parameter is %1 for the first parameter, and %2 for the second parameter, etc.

So you could make a simple batch file that google's something like this:

start https://www.google.com/search?q=%1

@Russ Yes, my mistake.

I have a error in my .bat file with a "$" and "%". I compare with my google.bat and this is ok and modified the another files.

Thank You

@russ
Got it. Looks like you already set that up for me .. as I could see my laptop on the default computer field .. and it is working ! Thank you!

P.S: Is there a location on this forum or site for "How-to's" / Knowledge base - for people to find such information there .. if yes, please direct me to the same, if not, might be a good idea to create one :)

@Russ , es mi mismo caso, si esta instalado pero me sale el anuncio, me podrias ayudar por favor.

@stevef9432203, no, but you could change this line to set your "homedir" to something else.

homedir = (process.platform === 'win32') ? process.env.HOMEPATH : process.env.HOME;

Or maybe you could symlink your ~/.TRIGGERcmdData folder to a path on your hard drive.

@pico, that's interesting. I'll experiment with that. I hope it works. Thanks for the suggestion.

EDIT: I worked on it for a while and didn't get it working. I couldn't get it to add the Login item while it's quarantined. I think that's a mac security feature for apps downloaded outside of the app store.

I was facing the same problem, but solved while writing this:

If I use the old skill and say "ask trigger CMD to run terço" it works perfect, also works from pressing "trigger" in the website.
If I use the new skill and say "turn on terço" it doesn't.

What have I tried:

Disabling and enabling the skills. Deleting and adding the command again. Removing and discovering the comands again in Alexa. Removing and re-installing the triggercmdagent. Changing voice command.

Useful info:

Only happens to that command, all the other works fine. This command is a bash script that open a few chrome pages depending on week day. I'm using Linux (PopOS 20.04). I'm using it in portuguese.

Then I decide to try changing the Trigger name. I used "batata" (potato in portuguese) and it worked, then I tried "Terço" again and it didn't, then I tried "Terco", it worked. Apparently it is a problem with "ç" in the trigger name (in the voice command is working well). Since english don't have that, it's understandable. It's not a big thing or really a problem, just wanted to inform so if anyone is having the same problem, try that.

@Frank-Malczewski For anyone reading this post, we solved the problem.

Before I followed the instructions above for sharing my computer with my wife (creating a triggercmd account for her and sharing my computer), I had tried to add her to MY triggercmd account by going on HER phone to HOME / SETUP DEVICE / WORKS WITH GOOGLE and linked to TriggerCMD Smart Home, which it accepted. But after following Russ' process for sharing the computer, neither of us could use Google to turn stuff on or off.

What I had to do is DISCONNECT TriggerCMD Smart Home on HER phone, then reconnect it so it picked up her new triggercmd.com account. You cannot have two people trying to access the same account.

Problem solved and now we both can talk to Google to turn lights on and off.

Thanks Russ for working with me on this...

EDIT: I see that Russ also posted that we solved this! We must have been typing at the same time...

@Pr0k0, background commands should show up as Alexa Smart Home devices, just like foreground commands, so I wonder if you didn't install the background service yet. This command should it:

sudo sh /usr/lib/triggercmdagent/resources/app/src/installdaemon.sh