Files
GarminHomeAssistant/HTTP_Headers.md
tispokes b9db9af3bf small doc suggestions
small doc suggestions

small doc suggestions
2025-08-10 18:42:28 +02:00

1.7 KiB

Home | Switches | Actions | Templates | Glance | Background Service | Wi-Fi | HTTP Headers | Trouble Shooting | Version History

User Specified Custom HTTP Headers

Principally for those who use Home Assistant add-on Cloudflared in order to provide additional security via Cloudflare's Web Application Firewall (WAF). But Garmin does not support certificates in requests. And the solution is generic enough for other use cases.

Please let us know if this solution is found to be useful for other situations.

Setup

The settings contain two options for users to specify both the HTTP header name and the value as two free form strings.

If you don't know why you need these, leave them empty and ignore.

Cloudflare WAF rule example

(any(http.request.headers["your-header-name"][*] eq "your-header-key"))

Make the key strong enough!

Support

None!

The authors of the Garmin Home Assistant application do not use, and hence do not know, the Cloudflared add-on. While we have enabled the HTTP headers to support using this add-on, it does mean you support yourself. Please do not raise issues about this functionality unless you are supplying the answers for any required changes too!

Credits

With thanks to Lars Pöpperl (@tispokes) for contributing to this solution.