Add button platform and associated buttons to Squeezebox (#38042)

* initial

* quotes

* remove blank

* review
This commit is contained in:
peteS-UK 2025-03-20 16:47:01 +00:00 committed by GitHub
parent 03ed223cf2
commit 7de735db17
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -147,6 +147,13 @@ data:
- **Needs restart**: Server Service needs to be restarted (typically, this is needed to apply updates).
- **Library rescan**: The music library is currently being scanned by LMS (depending on the type of scan, some content may be unavailable).
### Buttons
- **Preset 1 ... Preset 6**: Play media stored in Preset 1 to Preset 6 on Squeezebox.
- **Brightness Up, Brightness Down**: Adjust the brightness on Logitech Squeezebox players with built-in screen, such as Radio and Boom.
- **Bass Up, Bass Down**: Adjust the bass on Logitech Squeezebox players, such as Radio and Boom.
- **Treble Up, Treble Down**: Adjust the treble on Logitech Squeezebox players, such as Radio and Boom.
### Sensors
- **Last scan**: Date of the last library scan.
@ -189,9 +196,8 @@ When specifying additional parameters in the Visual Editor, each parameter must
For example, to create an automation to mute playback, use the command `mixer` and the parameter `muting`:
| Row | Parameter | Description |
| --- | -------- | ----------- |
| --- | --------- | ---------------------- |
| 1 | - muting | Toggle muting on / off |
| 2 | | |
resulting in the YAML:
@ -210,7 +216,7 @@ Where a parameter is an increment or decrement, it is necessary to place the val
For example, to increase the playback volume, use the command `mixer` and the parameters `volume` and the amount to increment:
| Row | Parameter | Description |
| --- | -------- | ----------- |
| --- | --------- | ----------------------------- |
| 1 | - volume | Parameter to change |
| 2 | - "+5" | Increment volume by 5 percent |
@ -227,7 +233,6 @@ data:
- "+5"
```
### Action `call_query`
Call a custom Squeezebox JSON-RPC API. The result of the query will be stored in the 'query_result' attribute of the player.