I'm showing quite a few sensor values from @homeassistant on our #DAKboard digital calendar. To avoid handing over a long-lived access token to DAKboard, and to limit what it can access — I set up #Caddy to enforce a limited access scope.
https://www.cavelab.dev/posts/secure-home-assistant-api-caddy/

Securing Home Assistant API access for Dakboard — with Caddy
Back in 2021 I added Home Assistant sensor data to our Dakboard monitor. But I did so using a long-lived access token directly on the Dakboard blocks — which is not great for a couple of reasons: Tokens have no access scope, meaning they grant full admin access to everything The token was stored on Dakboard’s servers I want Dakboard to be able to pull data from my locally hosted Home Assistant, but I’d like to restrict access. I did this using Caddy as a reverse proxy 🤓





