Add documentation for Bang & Olufsen button Event entites (#35062)

Co-authored-by: Franck Nijhof <frenck@frenck.nl>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
This commit is contained in:
Markus Jacobsen 2025-01-02 11:06:49 +01:00 committed by GitHub
parent 8aa64ed985
commit cc168b332a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -4,12 +4,14 @@ description: Instructions on how to integrate Bang & Olufsen devices into Home A
ha_category: ha_category:
- Media Player - Media Player
- Multimedia - Multimedia
- Event
ha_release: 2024.2 ha_release: 2024.2
ha_iot_class: Local Push ha_iot_class: Local Push
ha_domain: bang_olufsen ha_domain: bang_olufsen
ha_platforms: ha_platforms:
- diagnostics - diagnostics
- media_player - media_player
- event
ha_codeowners: ha_codeowners:
- '@mj23000' - '@mj23000'
ha_config_flow: true ha_config_flow: true
@ -484,6 +486,30 @@ target:
WebSocket notifications received from the device are fired as events in Home Assistant. These can be received by listening to `bang_olufsen_websocket_event` event types, where `device_id` or `serial_number` can be used to differentiate devices. WebSocket notifications received from the device are fired as events in Home Assistant. These can be received by listening to `bang_olufsen_websocket_event` event types, where `device_id` or `serial_number` can be used to differentiate devices.
### Events
Event entities are created for each of the physical controls on your device. These controls usually have their own behaviors, so using them for automations is not always ideal.
Available event entities:
- Bluetooth
- Microphone
- Next
- Play / Pause
- Favourite 1
- Favourite 2
- Favourite 3
- Favourite 4
- Previous
- Volume
All of these event entities support the following event types:
- Release of short press
- Long press
- Release of long press
- Very long press
- Release of very long press
All devices except the [Beoconnect Core](https://www.bang-olufsen.com/en/dk/accessories/beoconnect-core) support device controls.
### Getting Deezer URIs ### Getting Deezer URIs
To find Deezer playlist, album URIs, and user IDs for Deezer flows, the Deezer website has to be accessed. When navigating to an album, the URL will look something like: <https://www.deezer.com/en/album/ALBUM_ID>, and this needs to be converted to: `album:ALBUM_ID` and the same applies to playlists, which have the format: `playlist:PLAYLIST_ID`. To find Deezer playlist, album URIs, and user IDs for Deezer flows, the Deezer website has to be accessed. When navigating to an album, the URL will look something like: <https://www.deezer.com/en/album/ALBUM_ID>, and this needs to be converted to: `album:ALBUM_ID` and the same applies to playlists, which have the format: `playlist:PLAYLIST_ID`.