@Chaim-Tscholkowsky, awesome.

@Haresh-Shah, please check again. I found your paypal subscription and I fixed your account - you're subscribed now. You subscribed before I moved TRIGGERcmd to new servers last night. This is one reason I upgraded. Sometimes the Paypal communication failed because of a DNS problem.

@Leo-Dobrittz, please tell me more. Do you have an Echo dot that's working otherwise? Where do you see our hear that error message? Do you see that in the Alexa app on your phone, or what? Sorry, I haven't seen that one yet, and I didn't find anything on Google either.

@Forex-BR2019, awesome, yea that's the one you want.

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

@Ricardo-Pereira, ok, I think @Xander's nircmd idea is a good one for Windows.

Also if you set up your Google Assistant commands to run as routines in the Google Home app Google assistant won't reply with anything. I have set all my commands to run as routines to avoid having to hear google verbally confirm after every command. After setting it up I spent hours trying to figure out why sometimes Google would run my command silently and other times I would get an annoying reply, "Ok, turning on the bedroom light" for example. I finally realized that I had set my routine up with a command like "Turn on the bedroom light" but I would sometimes unknowingly speak it reversed "Turn the bedroom light on" and Google would just run the standard command and not my routine. Setting up the routine with two commands, stated both ways, fixed the problem.

@Ricardo-Horibe, please try closing and re-opening the agent, or try changing your commands to foreground commands if they're currently background commands.

@edgard, do you have commands that work from the website but don't work from the GUI editor? Or are you saying that some of your commands don't work at all - from the GUI editor or from the website? If some commands just don't work at all, please send me the command you're trying to run. Maybe I'll see what's wrong. Also, if you've set the Ground field to background, you'll need to install the background service to run those, and you won't see them when they run. In most cases you'll want to use foreground commands.

@George-Hatzisymeon, I'm really sorry. It was down while I was sleeping last night. I brought it back up just now.

@Diego-Alonso-Aldave-V, awesome. Thanks for letting me know it's working.

@clarkzara, I'm glad you got it working. There's no problem installing the agent on a VM - I've done it many times. Connecting through a proxy is a problem though. I've tried to add support for a proxy server, but so far I haven't had much luck.

@Russ Thank u Ross.

@nstefi, I recommend you try the Smart Home Alexa skill - it recognizes your words much better than the original skill. That said, what exactly are you saying to Alexa? I just said these and they both worked for me: Alexa, ask TRIGGERcmd to run calculator. Alexa, ask TRIGGERcmd to run calculator on downstairs.

@Russ thanks!

@Russ got it to work (spaces need %20 in names for anyone looking this up in the future). Thanks a million. So cool to use commands on my fossil

Thats delightfuly simple Ill just toss that in my xboxvol script Thanks

Its back up now! Cool!