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

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

@avs2020, it looks like you figured it out because I see commands associated with your raspberrypi computer now. Please confirm.

@TigoleBitties, I just tried it and it's working for me. Can you verify your phone has Internet access? Also, you installed both the SmartApp and the Device Handler, correct?

@Fernando-Mateos, @Fernando-Mateos-Lopez and @David-Jiménez-Lamas, Amazon approved the spanish version today. You'll find it as Ejecuta Comando.

@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 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 :)

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

@Neflhiem, I'm glad you got it working. I like how it turned out too. Thanks again for your questions - I wouldn't have thought to implement this if you hadn't asked.

@batteryxsnare, unfortunately I see no smoking gun in that output.

Both German Alexa skills are live now! https://www.amazon.de/VanderMey-Consulting-LLC-TRIGGER-command/dp/B074TV61DK/ https://www.amazon.de/VanderMey-Consulting-LLC-TRIGGERcmd/dp/B06XFN2TZN/ If you confirm they're working fine, please tell your friends. :) Thanks again for all your help @MarcusV!

@xander, good progress. The reason only Calculator and Notepad show up is you're only running a foreground agent. The background agent won't work in your case because you're using the basic 32bit Windows agent. The foreground agent reads foreground commands from commands.json, and the background agent reads the background commands. Are you able to run the commands from the green Trigger buttons on the website? Do you get any output in your cmd window when you trigger a command from the website?

@gabi92a, I found out why Fiddler wasn't working. For NodeJS apps like the TRIGGERcmd agent, you have to set these environment variables before you run the node src\agent.js --console command: set https_proxy=http://127.0.0.1:8888 set http_proxy=http://127.0.0.1:8888 set NODE_TLS_REJECT_UNAUTHORIZED=0 That tells the NodeJS app to use Fiddler as a proxy server. I found that here: https://weblogs.asp.net/dixin/use-fiddler-with-node-js Can you try that? Maybe that will give us a clue. Also, you could try running it after setting this variable to get a bunch of debug output: set NODE_DEBUG=* One thing you should know - the agent uses a websocket to connect to the server, and that connection doesn't use the https_proxy variable so Fiddler won't pick that up. The request that's giving us this error doesn't use websockets though, so that shouldn't matter for this troubleshooting.

@sailoreffinmoon, I get that "Target label does not exist" for "Gosub, %1%." error if I run the ahk script with no parameter. So maybe you just need to add one of the parameters, like mute to the command line. Example command: start C:\autohotkeyscripts\media.ahk mute

@Tiago-Mártires, awesome, thank you!

@Christian-Robinson , I fixed that bug. Sorry it took so long. I posted v1.0.5 just now. To remove your existing duplicates, just change the trigger name and save commands.json. Thanks again for telling me, and thanks for your patience.

@Daniel-Millan, sorry. I think it would be a security flaw to allow any process to simulate key presses at that point. That said, there might be some way to do it.

Very nice