Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[amazonechocontrol] volume does not get updated with Sonos devices #14328

Open
TheNinth7 opened this issue Feb 3, 2023 · 1 comment
Open
Labels
bug An unexpected problem or unintended behavior of an add-on

Comments

@TheNinth7
Copy link
Contributor

I have been using the Amazon Echo Control binding to send Alexa voice notifications to my Sonos speakers that are Alexa-enabled. Those can be added as things of type "echo" with the serial numbers from the Amazon Echo Control page. See also this community díscussion on the topic.

By and large this works well, but there is an issue with the volume, with the volume channel and the linked items not getting updated when the volume is changed on the Sonos app or the device. The resulting problem is that after the Alexa voice notification is played, music is resumed with the volume stored in the volume channel, which is not the actual volume at which the music was played before.

Expected Behavior

When the volume is changed via the Sonos app, on the Sonos device, or via any other means, the volume channel of the Echo binding should be updated.

Current Behavior

When the volume is changed via the Sonos app, on the Sonos device, or via the Sonos binding, the volume channel of the Echo binding is not updated. The other direction works, when changing the volume on the Echo binding, the Sonos binding, app etc. do show the change, albeit there is a noticeable lag.

Here screenshots of my two Points. The first is representing the volume channel of the thing created for the device via the Sonos binding, which I just updated to 20. The second the volume channel of the thing created for the same Sonos device via the Echo binding, which stays at the value of 40.

Screenshot - 03_02_2023 , 17_25_51

Screenshot - 03_02_2023 , 17_26_24

Steps to Reproduce (for Bugs)

  1. Setup the Sonos device in the Sonos app
  2. Add Alexa via the Sonos app
  3. Create thing/items for the Sonos device via the Sonos binding
  4. Create thing/items for the Sonos device via the Echo binding
  5. Change the volume on the item created via the Sonos binding
  6. Result: volume for the item created via the Echo binding is not updated

Context

When sending an Alexa voice notification via the speak channel, the volume of the music previously is set wrongly to the value stored in the volume channel, which does not reflect the actual volume at which the music was played before.

Your Environment

  • openHAB 3.4.0, running in a docker container on a Synology DS420+
  • For testing I used a Sonos One (2nd generation)
@TheNinth7 TheNinth7 added the bug An unexpected problem or unintended behavior of an add-on label Feb 3, 2023
@openhab-bot
Copy link
Collaborator

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/using-sonos-speakers-as-alexa-echo-via-amazon-echo-control-binding-sonos-arc-works-sonos-move-not/136882/15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An unexpected problem or unintended behavior of an add-on
Projects
None yet
Development

No branches or pull requests

2 participants