Google Home Triggercnd smart home is unavailable

[Csaba Ferenc László]

For a few weeks now, I'm fighting with the following:

• google home says that triggercmd smart home is unavailable right now
• I go to the google home app and reconnect triggercmd smart home
• everything works
• after a few days (yesterday after a few hours), it stops working again.

[Russ]

@Csaba-Ferenc-László, the only time I have seen that "TRIGGERcmd Smart Home is unavailable right now" error is when I've been logged in as a different Google Assistant account when I connected it to my TRIGGERcmd account. You can only have one Google Assistant account connected to your TRIGGERcmd account at a time.

I just reproduced the error by using my wife's phone to log her Google Assistant into my TRIGGERcmd account.

Is it possible that's what's happening to you? I wonder if you're basically alternating between two Google Assistant accounts.

[Csaba Ferenc László]

@Russ hi
In this case, all my other integrations would fail as well (I have shelly, ikea, sonoff, midea) which all work fine

[Russ]

@Csaba-Ferenc-László, you might be able to log multiple Google Assistant accounts into a single shelly, ikea, sonoff, or midea account, but I know you can't log multiple Google Assistant accounts into one TRIGGERcmd account. If you do, only the last Google Assistant account you link will work.

What you could do though is have two TRIGGERcmd accounts, and link each Google Assistant account to a separate TRIGGERcmd account, then share computers in one TRIGGERcmd account with the other account.

[Csaba Ferenc László]

I'm not doing cross-accounts. I'm using laszlocsaba(at)gmail.com on my ghome app (and speakers) and also with triggercmd. Can you try to look at some logs please? This bugs me a lot, pretty much makes triggercmd useless for me

[Russ]

@Csaba-Ferenc-László, yes, I will try. Next time the error happens, please post the time and day here. That would help me find the problem in the logs.

Also please try this - instead of using "Reconnect account" use "Unlink account", then re-link.

I found an error in the Google logs that might be giving me a clue, but I need more time to research and test it.

BTW, it's ok to have a different email addresses for your Google Home and TRIGGERcmd accounts.

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.