Hola @Russ ¡Feliz año nuevo! Finalmente, con el cambio en la versión, todo funcionó perfectamente. ¡Gracias por tu fantástico trabajo y soporte! ¡Éxitos!

@Russ Ty.. works for me.. Now, I will try turn off this.. lol

Awesome @Valter-Santos ! Thanks for your patience, and for showing me this bug. I'm working on the fix now. EDIT: It should be fixed now, so it won't error even if you do have multiple triggers with the same name on the same computer.

@ANDRES-ROJAS, I might be having the same problem you are. I tried creating a Google Assistant routine that flips one of the virtual switches on, but it won't allow me to select the switch now. I'll look into that, but there's another way that does work. Here's what worked for me: Open the Home app Tap Routines Tap the + to create a routine Tap Personal Tap "Add starter" Tap "When I say to Google Assistant" Type "calculator" Tap "Add action" Tap "Try adding your own" Type "turn on calculator" [image: 1677538475551-google_assistant_action.png] For this to work, you have to enable the TRIGGERcmd Smart Home action first.

@Russ Ah, that could be why - when I was trying to get things to work I did have a routine. Thanks again. Now I really don't see a need to have them.

@russ thank you!

@Dominik-Pellkofer, thank you for reporting this. You're now the 3rd person to report it. I'm working on it now. Which Google action are you using? TRIGGERcmd (ask TRIGGERcmd to run TRIGGER command (ask TRIGGER command to run TRIGGERcmd Smart Home (turn on It seems Google changed something in their oauth2 authentication system that's causing problems with TRIGGERcmd. Last night I found an error like this in the logs on the Google side. https://github.com/actions-on-google/smart-home-nodejs/issues/388 I made a change to the TRIGGERcmd and TRIGGER command actions which might fix them. The change only takes effect next time people link their accounts. Unfortunately it doesn't happen very often, so only time will tell if it's fixed. In fact for some reason it's never happened to me yet. I'll be working on this this weekend. Please keep reporting the problem when you see it. If you tell me the exact time it might help. EDIT: I think I found the root cause and fixed it today, 9/12/2020 at about 12:30pm EST. You might have to re-link one more time, but after that it should stay linked. Thank you for reporting the problem. After adding logging for this problem I see it was also affecting Alexa users.

I know this is an old post but I have found that using IFTTT to trigger the command doesn't give the "here's trigger cmd etc." Hope this helps!