Hi,
I've read about how Google would not allow generic and Smart Home apps to co-exist and HomeSeer opted for the more direct control, which is understandable. However, I really have a need to send the spoken text to HS and get a custom response.
Therefore, I created my own action: https://forums.homeseer.com/forum/ho...stom-responses
This had worked beautifully for a long time, but unfortunately, Google Assistant recently changed the behavior when invoking actions and it now announces the action name ever time, which is a waste of time and very annoying.
Example:
Me: Ok Google, ask HomeSeer what the thermostat is set to.
Assistant: Getting HomeSeer (or Let's get HomeSeer, or Here's HomeSeer) <--- I don't want to hear this line
(chime sound)
HomeSeer: The thermostat is set to 69 degrees.
(chime sound)
The action announcement used to go away after a number of frequent invocations, but not anymore. This is very annoying. Actions on Google support says this behavior is within Assistant, and they think what I used to experience was a glitch. In other words, they claim nothing changed in regards to this behavior on their end.
rjh, is this how your generic action used to behave in regards to Assistant announcing the action name every time? Any news on Google allowing the two to co-exist? Could you get around the restriction if you called one "HomeSeer" and the other "Home Seer"? Or maybe somebody else could host the code in their Google account? I recall having to mess around with my Action Name and Pronunciation before it would "take". I think my action name is "HomeSeer" but pronunciation is "Home Seer". Maybe what Google should do is allow their to be a trigger phrase in the Smart Home App to skip looking for direct control and just send the transcribed text to the home automation system. If there is any way we can help push for change at Google to support this, please let us know.
This is an important feature for me. I send many questions to HomeSeer and do not want to hear that introduction every time.
Thanks!
I've read about how Google would not allow generic and Smart Home apps to co-exist and HomeSeer opted for the more direct control, which is understandable. However, I really have a need to send the spoken text to HS and get a custom response.
Therefore, I created my own action: https://forums.homeseer.com/forum/ho...stom-responses
This had worked beautifully for a long time, but unfortunately, Google Assistant recently changed the behavior when invoking actions and it now announces the action name ever time, which is a waste of time and very annoying.
Example:
Me: Ok Google, ask HomeSeer what the thermostat is set to.
Assistant: Getting HomeSeer (or Let's get HomeSeer, or Here's HomeSeer) <--- I don't want to hear this line
(chime sound)
HomeSeer: The thermostat is set to 69 degrees.
(chime sound)
The action announcement used to go away after a number of frequent invocations, but not anymore. This is very annoying. Actions on Google support says this behavior is within Assistant, and they think what I used to experience was a glitch. In other words, they claim nothing changed in regards to this behavior on their end.
rjh, is this how your generic action used to behave in regards to Assistant announcing the action name every time? Any news on Google allowing the two to co-exist? Could you get around the restriction if you called one "HomeSeer" and the other "Home Seer"? Or maybe somebody else could host the code in their Google account? I recall having to mess around with my Action Name and Pronunciation before it would "take". I think my action name is "HomeSeer" but pronunciation is "Home Seer". Maybe what Google should do is allow their to be a trigger phrase in the Smart Home App to skip looking for direct control and just send the transcribed text to the home automation system. If there is any way we can help push for change at Google to support this, please let us know.
This is an important feature for me. I send many questions to HomeSeer and do not want to hear that introduction every time.
Thanks!
Comment