Tailscale
tailscale
The Tailscale integration monitors the devices in your Tailscale network (Tailnet) from Home Assistant. Tailscale is a VPN service that creates secure connections between your devices using WireGuard.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
binary_sensor | Sensor (motion, contact, leak, smoke…) |
What people report
Read-only cloud integration for Tailscale devices. Since Oct 2026 shared-in devices break setup due to a Tailscale API change.
- Partly works1
- Not working1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Tailscale tailnet devices | Partly works Cloud | Read-only sensors; OAuth client credentials replace expiring 90-day tokensSaved copyBreaking change Tailscale now authenticates with OAuth client credentials only. OAuth clients do not expire, unlike the API access token this integration previously used, which Tailscale caps at 90 days. Entries that were set up with an API access token stop loading after this update and start a re-authentication flow. Entering OAuth client credentials once migrates the entry, after which it keeps working without the recurring 90-day re-entry. ## Proposed change Tailscale API access tokens are capped at 90 days, so this integration had to be re-authenticated by hand every quarter. The … Excerpt saved from GitHub on 2026-10-23. | PR #176874 · 2026-07 | |
| Tailscale tailnet with shared-in devices | Not working Cloud | Fails with misleading authentication error when shared-in devices exist; Tailscale API changeSaved copyThe problem # Tailscale integration fails with misleading "authentication" / "failed to connect" error when the tailnet contains external (shared-in) devices ## A note from the reporter I'm not very experienced with this kind of troubleshooting. The diagnosis below was worked out step by step with Claude (an AI assistant made by Anthropic), which designed the tests and identified the root cause. The discovery should be credited to Claude. I ran the commands and pasted back the results. Please treat the technical details as AI-assisted and feel free to ask me to re-run anything. ## Summary The … Excerpt saved from GitHub on 2026-10-23. | Issue #185079 · 2026-10 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud polling
Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.
Details
| Installs (analytics) | 5,376 (0.76%) |
|---|---|
| Added in | Home Assistant 2021.12 |
| Set up in the UI | Yes |
| Maintainers | @frenck |
Limitations from the docs
- The integration is read-only. You cannot change devices or your Tailnet from Home Assistant.
- The Connected to control binary sensor indicates recent control-plane connectivity, while the Last seen sensor indicates recency. Neither guarantees peer-to-peer reachability or traffic.
- Tailscale API access tokens are valid for 90 days. When a token expires, the integration stops updating and asks you to enter a new token.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
