mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 17:27:19 +00:00
Move Bang & Olufsen Event entity documentation (#37554)
* Move event entity documentation * Improve list formatting * Improve wording
This commit is contained in:
parent
503cb44bcb
commit
46dd0d1846
@ -53,7 +53,7 @@ The **Bang & Olufsen** integration uses the [Mozart API](https://bang-olufsen.gi
|
||||
|
||||
## Supported features
|
||||
|
||||
Currently, a single device with a `media_player` entity is created for each added physical device. For advanced automations, [events](#automations) are fired in Home Assistant.
|
||||
Currently, for each added physical device, a single device is created that includes a `media_player` entity and, if available, `event` entities.
|
||||
|
||||
### Media player
|
||||
|
||||
@ -71,6 +71,32 @@ A number of features are available through the media player entity:
|
||||
- Connect to, expand to or unexpand devices.
|
||||
- Set all connected Beolink devices to standby.
|
||||
|
||||
### 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.
|
||||
|
||||
## Limitations
|
||||
|
||||
Currently, some features of the Mozart platform are not available through the [public API](https://github.com/bang-olufsen/mozart-open-api). Some may become available at a later point, but until then the [Bang & Olufsen App](https://www.bang-olufsen.com/en/dk/story/apps) can be used to configure these settings and features:
|
||||
@ -484,30 +510,6 @@ 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.
|
||||
|
||||
### 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
|
||||
|
||||
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`.
|
||||
|
Loading…
x
Reference in New Issue
Block a user