Did Google Assistant kill TriggerCMD workings?
So today after what has seemed years of working almost flawlessly it appears there has been a suicide in the family. I've done nothing in years except update TriggerCMD on my PC and as of today now when I ask Assistant to do any of the TriggerCMD things it was doing fine just 48hrs ago it now responds "Sorry, I don't understand." Does this mean that its all over now? Why did this all stop working all of the sudden? I know this has been a set it and forget it for me for what has seemed a few years now but has something changed and do I have to redo the "set it" all over again to make it start working so I can get back to "forget it" and have it working flawlessly again? What will it now take to get working again?
Wow... I checked my Google Home app for the first time in years to check my routines. They all were formatted saying "tell" triggerCMD instead of "ask" triggerCMD. Strange how "tell" worked for the past few years all the way up till the other day. Changed them all to "ask" and they are working again. Sorry to bother you...