Google Assistant bug fixed
Russ last edited by Russ
I saw failure entries in the log like this:
Gassistant: Could not find a trigger called X on Y on Y, sorry.
Google started sending the " on Y" part of the sentence in the trigger field. I added code to parse that out.
Sorry about the issue for anyone who experienced it.
If you ever see problems with TRIGGERcmd, or just have suggestions for improvement, please tell me.