Sonus.stop not stopping Google Speech
See original GitHub issueFrom what I try here Sonus.stop just stop to record but doesn’t cancel any Google Speech request if there some pending https://github.com/evancohen/sonus/blob/master/index.js#L153
I try to put a basic timeout because sometime it stay in listen state and never end… Basically I do like this :
Sonus.stop(this.sonus)
Sonus.start(this.sonus)
But Google Speech still streaming 😦
Issue Analytics
- State:
- Created 6 years ago
- Comments:23 (22 by maintainers)
Top Results From Across the Web
assistant stop working - Sonos Community
I installed at used the Assistant without any problems and working fine. After sine time it stop working. No respons or connection at...
Read more >Sonos says Google is blocking it from offering more than one ...
Sonos developed software called “Concurrency” that could allow voice assistants to work side by side, but Google put a stop to it, ...
Read more >Google Assistant with Sonos Beam troubleshooting
The sonos beam is not working with voice commands through the google ... “Hey Google, stop” - does work after 23 seconds but...
Read more >Hey Sonos: 7 things to know about the new Sonos voice ...
So, why do we need a Sonos voice assistant when Sonos speakers already host your choice of either Alexa or Google Assistant?
Read more >How to control your Sonos speaker with only your voice
You can then pick from Sonos Voice Control, the Google Assistant, and Amazon Alexa, ... but you'll not be able to request specific...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As I mentioned in the other issue, I’m going to dig into the API again and see if there’s a good way to examine the state of the streaming recognizer (instead of having our own internal state).
This issue is also fixed with #67