search

bang-olufsen / bang_olufsen-hacs

Home Assistant integration for Bang & Olufsen products. Compatible devices: Beoconnect Core, Beolab 8, Beolab 28, Beosound 2 3rd gen, Beosound A5, Beosound A9 5th gen, Beosound Balance, Beosound Emerge, Beosound Level and Beosound Theatre
MIT License
30 stars 3 forks source link

Volume entity not working anymore #21

Closed Jydepotte closed 8 months ago

Jydepotte commented 8 months ago

Hi,

Noticed that the sensor.beosound_volume entity does not work correctly anymore with my Beosound Theatre. Not sure whether this is related to the new firmware (3.4.1.8) on the Beosound, Home Assistant 2024.3.3 or the Bang & Olufsen integration.

You can still set the volume using the slider but the sensor.beosound_volume entity does not change.

I have scripts to change the volume up/down that does also not work anymore because they depend on the current volume level to work.

Kind regards

/Jan Lebeck

Jydepotte commented 8 months ago

Example of a script to change the volume down by 5:

service: media_player.volume_set target: entity_id: media_player.beosound_theatre_36199013_3 data: volume_level: >- {{ states.media_player.beosound_theatre_36199013_3.attributes.volume_level - 0.05 }}

Jydepotte commented 8 months ago

Volume Never changes...

Jydepotte commented 8 months ago

Have checked on a completely fresh installation of Home Assistant also - same problem.

mj23000 commented 8 months ago

I'm guessing that you have tried rebooting the Theatre.

What version of this integration are you using? If it is 2.1.1, can you try downgrading to 2.0.0? And are any other WebSocket notifications working?, for example does changing source change artwork and metadata as expected?

Kind regards

Jydepotte commented 8 months ago

After downgrading everything works... tried to upgrade to 2.1.1 again - then NOT working again. Going back to 2.0.0. Repeated this a few times to verify. 1.8.1 also works.

mj23000 commented 8 months ago

Ok. I have not been able to replicate this issue with WebSocket notifications on 2.1+, but you are the second one reporting problems. The issue seems to be the new WebSocket backend for the API client. I'll try to revert to the old backend and release a new version tomorrow.

mj23000 commented 8 months ago

Can you try updating to 2.1.3?

Jydepotte commented 8 months ago

Hi ... just upgraded and tested... and it now works as usual on 2.1.3.

mj23000 commented 8 months ago

Good. I'll stay with the old WebSocket backend.