node-sonos-http-api
node-sonos-http-api copied to clipboard
Recovery after 'say' doesn't work for Sonos AMP
My issue might be similar to #660. I'm having a group playing radio. When I execute a 'say' just on one single speaker the grouping gets lost. I found out that it works perfectly on a Sonos3 but unsuccessfully on a Sonos CONNECT:AMP. Per description the API should recover the speaker setup before executing 'say'
Kind regards Volker
I think this is not only a story while group playing. I have this even one player is playing. When I play Spotify stuff on my playbar and an interrupt occured due to doorbell or an smarthome announcement Spotify gets not resumed. Would be really nice to get a fix for this.
Are you playing Spotify through sonos app, or Spotify app? (Spotify direct)?
On Mon, 16 Dec 2019, 13:38 0rTiN, [email protected] wrote:
I think this is not only a story while group playing. I have this even one player is playing. When I play Spotify stuff on my playbar and an interrupt occured due to doorbell or an smarthome announcement Spotify gets not resumed. Would be really nice to get a fix for this.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jishi/node-sonos-http-api/issues/735?email_source=notifications&email_token=AAYE2I4YSBDLE2LALHC2OJ3QY5ZDLA5CNFSM4JUUM7GKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG6SIZY#issuecomment-566043751, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYE2IYPI2UKKAZRYWDEBDLQY5ZDLANCNFSM4JUUM7GA .
I am using both methods. But the normal way is using Google Assistent.
To add. I was able to get it run with the CONNECT:AMP. I was executing two commands, 1st set a volume and 2nd say which volume was set. I found out that the CONNECT:AMP was too slow in processing. When the 2nd command was sent to the AMP recovery didn't work. With 4 sec pause it worked. But now I replaced the CONNECT:AMP with the new AMP and recovery doesn't work at all. Has the API changed??
ok, after reinstalling it works.
Sorry, fails again. Recovering after "say" with Sonos AMP doesn't work.
I have same issue on Play:1/Play:5, still on S1. Using it with media data base or streaming with Amazon Music: After SAY using VoiceRSS or a local MP3 clip, it completely looses the connection to previous Song/Queue/Amazon Music stream or whatever. I'm not sure if an autmatic recovery solves all problems, especially when several Say or Clips commands are sent.
Question: Is it possible to have a command that somehow pushes the current play state somewhere, to be fully restored on request?
BTW: Library is great. All significant communication for my Smart Home, especially for error conditions, runs over this library! Thank you very much.
-jayvee