Sorry for the late response, but I wanted to drop in here to help.
I understand that these issues can be confusing but I definitely wanted to stop by and see how I could help.
Just wanted to double check to see if you were still needing help on this? If so, what troubleshooting steps have you tried?
I look forward to hearing from you.
I hear there's a pending release with interface reworks. I'm hoping this was resolved in that release, however I am doubtful.
This is still a thing. I tried marching over to the dev team office, but that location is not known to me.
I only installed google home within the last few months, so if the feature used to exist (if it did not, why are people mentioning it and asking where it went?) It is now gone, or if it never existed, it needs to be added.
Manually triggering routines on google home must work. It is an app breaking problem. Without this function, google home serves absolutely no purpose.
Routines need to allow the user to click on them from within the app to trigger them. As I mentioned above, I draw my data mining privacy line at having microphones throughout my house recording and sending audio to offsite servers to analyze every last thing it picks up for "hey google." (Even if the data is not stored after it determines what it heard is not hey google, it is being transmitted outside the local network and honestly the trust that such a large company will be responsible with my data, just isn't there.
Sorry to hear that you're still having issues with this. I know that there are still issues with this occurring and our engineering team knows of these issues as well as it has been an ongoing issue. They are continually working on this and unfortunately I don't have any other information on this.
Pardon my tone, but i've had little confidence in Google lately. Especially with the lovely Nest Protect support.
Not really sure what troubleshooting steps you expected us to perform knowing it is a known issue? So this tells me that yes routines are meant to have a manual function, but the template response feels cold, like "they're working on it, they might fix it someday, I don't have more info so leave me alone."
Hopefully the upcoming gui rework will address this, but it's really a simple function to add, and perhaps leaving it out better suits the interests of the devs. (Vaguebooking is worse than being straight with your users. "oh no, we took that function out because we don't want it anymore.")