@Alain-Coderre, @nick-beau, great news! Google finally approved French and German! That clears the way to add Spanish, then Italian too.

@erin-leiker, please give this a try: Run this as your pi user to allow root to send stuff to your pi user's Xwindows: xhost si:localuser:root Install the background service as root with: /usr/share/triggercmdagent/app/src/installdaemon.sh Make sure this variable is set when your command runs as root in the context of your triggercmdagent: export DISPLAY=:0.0 Your agent will be running in background mode, so the commands need "ground": "background" to run that way. I suggest testing with galculator. It's an xwindows calculator app.

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

thanks a lot for a so quick awnser, that did the trick :)

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

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

@Atmosphere, I'm going to try to make it so when you link your Google account to your TRIGGERcmd account it doesn't replace the link, it adds a link. That way you could have her link her Google account to TRIGGERcmd in the Home app, and you'll both be able to use the same TRIGGERcmd account. Please confirm that would work for you. Sorry this is taking forever. It's a difficult thing to do, but I'll make it a priority now. Your feedback helps. EDIT: I started looking at the code and it's not going to be practical to allow multiple Google accounts to link to the same TRIGGERcmd account, so now I'm looking into the idea of being able to share a computer with another TRIGGERcmd user. In the meantime, you could use her IFTTT account to trigger your TRIGGERcmd commands. I know it's a relative pain to set that up though. EDIT2: I'm making progress on the ability to share your computers with other TRIGGERcmd users. @Atmosphere, when it's ready, you'll be able to share your computers with your wife's TRIGGERcmd account, and she'll be able to link her Google Home account to her TRIGGERcmd account. EDIT3: I'm very close. I have a system for sharing your computer so another user can trigger your commands. So far the commands on the shared computer can only be triggered via the website though. I'll update the live system when I test it more and I get Google Assistant working.

@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

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

@Nate-Hales you said "I have alexa on the "Line in" with "Listen" enabled, so I can hear her and whatever is running on my windows 10" I tried this with alexa and got some odd noises when she was listening so i had to unplug her. Did you have that problem and find a fix or just didnt have it? im in the same setup.. htpc does all the sound.

@Jim-Potash, in your Alexa app it shows you what Alexa is hearing you say, so you can use that to match your voice words for your computer and your command. The word "reboot" for the command should be no problem, but you might have better luck using a different voice word for the computer.

@djmalcom, I used to have the SmartThings code immediately turn the switch back on every time you turn it off, so effectively it's always on. I left the line that did that remarked out. Just un-remark (remove the //) that off() line. // handle commands def on() { log.debug "Executing 'on'" sendEvent(name:"switch",value:on) parent.on(this) // off() } https://github.com/rvmey/SmartThingsPublic/blob/MSA-2199-2/devicetypes/vandermeyconsulting/triggercmd-switch.src/triggercmd-switch.groovy

This not only runs the process in background, also generates a log (called .... You put a command in the background by adding & after the command: ... bad connection to the server https://www.puttygen.com/linux-commands