@Russ Stripe.com has the ability to do yearly subscriptions.

@Russ I left this alone for quite awhile (other priorities came up, and I was away from the house for awhile), and today I tried using one of my TriggerCMD commands, and it worked! Haven't changed anything here since last August, but I guess something has changed elsewhere. Now if I can find some way to get it to not announce "Triggering <command> on <host>" when doing a command, I'll be golden.

@russ I'll try that, but:

1. I've never used speech to do any of my TriggerCMD commands - I put them in routines, where it's typed, not spoken, and invoke my routine via speech. It's hard to see how speech interpretation would be involved in interpreting the TriggerCMD command I'm giving.

2. This worked fine up until the evening of Aug 19. Something changed that day, and it doesn't appear to have anything to do with my configuration.

@russ fili is the name of the computer I have the TriggerCMD running on, and is the default computer for my account. I'm not actually using the 'on <computer>' phrase in my commands to Google Voice (all of my Google Voice interactions for TriggerCMD are done through routines, so just what I type in the routine is going to TriggerCMD), it just takes the default.

So, for example, I have a routine which issues the command "tell triggercmd to trigger diningon" (diningon turns lights in the dining room on). If I run that routine, whether through speaking to my Google Home Mini, or directly in the Google Home app, Google will respond "OK, here's TriggerCMD", and then TriggerCMD responds with "Could not find a command with voice word undefined on fili". I get the same response no matter which TriggerCMD trigger I'm trying to run(I have several).

I can go to the TriggerCMD web page or use the TriggerCMD Android app, and have no problem executing these triggers by clicking on the 'Trigger' button, so the problem doesn't appear to be between TriggerCMD and my computer. I don't ever speak TriggerCMD commands to my Google Home Mini - all TriggerCMD commands are done through Google Home routines, where I have to type in the command to be done, and I get this problem even where I run the routine directly in the Google Home app by tapping on the routine, so I think we can eliminate the problem being with how Google Home 'hears', as it isn't having to hear.

That pretty much seems to leave the problem between the Google Home action for TriggerCMD and the TriggerCMD server(s) that that action talks to.

Starting last night, trying to do any TriggerCMD commands through Google Assistant fails. Google Assistant hands off to TriggerCMD, which responds 'Could not find a command with voice word undefined on fili' (fili is my primary TriggerCMD computer). TriggerCMD works fine from the TriggerCMD web page or app, so this appears to be an issue between Google Home and TriggerCMD. Has a change been made to the TriggerCMD action for Google Home/Assistant?