Tedee
tedee
This integration interacts with your Tedee locks by communicating with the Tedee bridge through HTTP. The integration will communicate with your lock locally.
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 |
|---|---|---|
lock | Lock | Needs its own HomeKit Bridge in accessory mode |
binary_sensor | Sensor (contact) |
What people report
Tedee PRO and GO locks work locally through the bridge. Several users see repeating 'Authentication expired' repairs after bridge firmware updates, though the locks keep working.
- Works2
- Partly works1
- Won’t be supported1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Tedee GO | Works Local | Lock control via local bridge APISaved copySupported devices: Tedee PRO; Tedee GO. Limitations: Activity logs Excerpt saved from home-assistant.io on 2026-10-23. | Docs | |
| Tedee PRO | Works Local | Lock control via local bridge APISaved copySupported devices: Tedee PRO; Tedee GO. Limitations: Activity logs Excerpt saved from home-assistant.io on 2026-10-23. | Docs | |
| Tedee Bridge | Partly works Local | Repeating 'Authentication expired' repair after firmware updates; locks keep workingSaved copyStill haven't given up on this one :) Yesterday I got a notification from the Tedee app that there was a new firmware available. So I knew it would happen during the night, and I turned on Debug before going to bed, just in case. Sure enough, around 4:24AM the update must have started, since I see a few exceptions of 'pytedee_async.tedee_client' (with the message `Connect call failed`). As expected, eventually they stopped and everything went back to normal (as you described). However, very interestingly, hours before that, at around 1:16am, I found this in the debug log: ``` 2024-08-20 … Excerpt saved from GitHub on 2026-10-23. | Issue #122643 · 2024-07 | |
| Tedee Keypad | Won’t be supported Local | Keypads, activity logs and updates not available through the local APISaved copySupported devices: Tedee PRO; Tedee GO. Limitations: Activity logs Excerpt saved from home-assistant.io on 2026-10-23. | Docs |
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
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Details
| Installs (analytics) | 1,049 (0.15%) |
|---|---|
| Quality scale | Platinum |
| Added in | Home Assistant 2024.2 |
| Set up in the UI | Yes |
| Maintainers | @patrickhilker, @zweckj |
Devices listed in its documentation
- Tedee PRO
- Tedee GO
Limitations from the docs
- Activity logs
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.