Hi,
I am using Solar Forecast STATS in Home Assistant and I access my Home Assistant instance through Tailscale.
Home Assistant itself is reachable through the Tailscale connection, but the Solar Forecast STATS dashboard/API returns:
local_access_required
It looks like Tailscale/VPN access is not treated as local access.
I understand why the dashboard/API may be restricted to local access, especially if it exposes energy data or internal API endpoints. However, VPN access through Tailscale or WireGuard is a common and trusted way to access Home Assistant remotely.
Would it be possible to support this use case safely, for example by adding one of the following options?
- configurable trusted subnets
- explicit support for Tailscale/WireGuard access
- allowing Home Assistant-authenticated requests regardless of the source network
- documentation explaining which IP ranges are currently considered local
I would prefer not to disable the local-only protection completely. A configurable trusted subnet allowlist would probably be the safest option.
Thanks!
Hi,
I am using Solar Forecast STATS in Home Assistant and I access my Home Assistant instance through Tailscale.
Home Assistant itself is reachable through the Tailscale connection, but the Solar Forecast STATS dashboard/API returns:
local_access_required
It looks like Tailscale/VPN access is not treated as local access.
I understand why the dashboard/API may be restricted to local access, especially if it exposes energy data or internal API endpoints. However, VPN access through Tailscale or WireGuard is a common and trusted way to access Home Assistant remotely.
Would it be possible to support this use case safely, for example by adding one of the following options?
I would prefer not to disable the local-only protection completely. A configurable trusted subnet allowlist would probably be the safest option.
Thanks!