@marcos-ibarra
I'm not into AU3 that much (while knowing AHK better), what about triggering OBS's Control(s) directly, instead of Send(ing) a key in a less reliable way?

https://www.autoitscript.com/autoit3/docs/functions/ControlCommand.htm

That way the window wouldn't even have to be active, only existing!

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

@Russ thanks for coming up with a solution so quickly. I followed your instructions and I am up and running again! 👍

@Russ i already have uac disable, and ticked administrator to that shortcut in that folder, but this way don't start when windows 10 start

@russ I saw that, many thanks!

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

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

@steve-porter yep that will mess things up. I remember reading another post about that so that isn't something that you alone have experienced. I found a couple times the file didn't update for me for different errors in command lines.
I've gotten into the habit of double checking if it saves.

@Russ Thank u Ross.

@newstuffoldstuff, I see. If you want to avoid reducing your User Access Control setting, you could try installing the background service and running it as a background command. It will run as Local System.

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

@prik-m said in No-GUI TRIGGERcmd agent that works on 32bit Windows:

@prik-m
I tried log out of the site to login with a diffrent google user but it automatically login with the previous one without giving me the possibility to change: can I do something about it?

Thx.

If you use Chrome, you could use a different profile logged in as the other user.

https://support.google.com/chrome/answer/2364824?hl=en&co=GENIE.Platform%3DDesktop

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