Dang, that sucks.I would expect that the solution should be within the smart plug example action code that I am assuming exists. I have an Echo too so I use Alexa for my commands as the activation is easier without saying "ask TRIGGERcmd to" first before "run <command> on <computer>" but I like the redundancy.

@Russ What are your thoughts on this?

I recently added Google Home Hub and Google Home Mini to my place. With just my Gmail account and me as the only household Member, I had no problem finding the "TRIGGERcmd | Google Assistant" web page and linking my TRIGGERcmd account, then successfully triggering commands from the Google Homes.

So I thought all was well and I added the other house members to the Google Home app. When they accepted the invite, it outlined all the smart plugs they could now control (even though they are 3 different brands I linked from the primary Google account), but made no mention of TRIGGERcmd.

Another household member attempted to trigger a command and it said use the Google Home app to link your account. I used the aforementioned and quoted web page to Link that Google account and got it working for that person but it stops another member from staying linked so hers works now but mine doesn’t anymore. I would have expected this linking to be shared throughout the Google Home household members like the smart plugs.

I have Unlinked and Linked all the accounts trying to solve this and it seems to be limited to 1 or 2 accounts or maybe the "'Skill" needs a configuration change to allow at least 3 Google Home members when the primary account is linked. Thanks.

Thank you the dropdown is great!

Both TRIGGERcmd and Trigger Command work well when she hears proper, though the latter is more swayable.

If the room is quie, it works reliably. My example commands were missing for the first computer I ever added so I deleted them all and after getting the Raspberry to request a token they came back and I got examples. Is this a bug or expected?

To answer your question, I am saying "Alexa, ask TRIGGERcmd to run blackout on inside" with expected results if it’s quiet enough. Thanks.

I found in my Profile I had the Default Computer entered as gate. That should be on the page with the computers as a dropdown of configured computers so it’s not overlooked and misconfigured. I am still having problems with Alexa running a command.

I finally got one command working on the trial and subscribed, and now it will not work at all from the Echo, but I can trigger everything from the web. I have moved Echo twice and changed voice words many times. The error in my subject gave me a clue that it is not something I have wrong. Please help.