Comment on: Chances of getting this in Docker
Repo: magnum6actual/flipoff by vultuk
I’ve implemented the multi-display part of this and it’s included in my PR (#2)
FlipOff now supports multiple boards, each with its own set of screens. Boards can be served from their own route using `/board-slug`, and one board can be marked as the default so it appears at `/`.
The API now supports targeting a specific board with `boardSlug`, and manual screens can also be targeted directly with `boardSlug + screenSlug`.
For Home Assistant, the call can now look like this for a specific board:
```yaml
rest_command:
flipoff_send_message:
url: "http://YOUR_FLIPOFF_HOST:8080/api/message"
method: POST
content_type: "application/json"
payload: >
{
"boardSlug": "{{ board_slug }}",
"message": "{{ message }}"
}
```
Example service call:
```yaml
action: rest_command.flipoff_send_message
data:
board_slug: bedroom
message: Washer cycle complete
```
If `boardSlug` is omitted, FlipOff sends the message to the current default board.
I’m not ...
GitHub Issue
SaaS Metrics