You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Steps to Reproduce (for Bugs)
Setup the Sonos device in the Sonos app
Add Alexa via the Sonos app
Create thing/items for the Sonos device via the Sonos binding
Create thing/items for the Sonos device via the Echo binding
Change the volume on the item created via the Sonos binding
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)
The text was updated successfully, but these errors were encountered:
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.
Steps to Reproduce (for Bugs)
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
The text was updated successfully, but these errors were encountered: