Tedee
This integration interacts with your Tedee
Prerequisites
- You will need the bridge to add your locks using this integration.
- You need to have the local API and encrypted token enabled.
- The bridge firmware needs to be at least version
2.2.18086
for push updates to work without errors.
If you do not own the bridge, you can still add your locks to Home Assistant through the HomeKit device integration (only for PRO model). Communication will happen over Bluetooth in that case, and features will be limited.
The integration will try to configure webhooks to receive near-real-time push updates from your bridge about your lock state changes. For this to work properly, the bridge must be able to reach your Home Assistant instance. It will prefer the configured internal_url
, so ensure this address is reachable from your bridge on your network. If communication through the webhooks is not possible, the integration will query for an update every 30 seconds.
Configuration
To add the Tedee integration to your Home Assistant instance, use this My button:
Manual configuration steps
If the above My button doesn’t work, you can also perform the following steps manually:
-
Browse to your Home Assistant instance.
-
In the bottom right corner, select the
Add Integration button. -
From the list, select Tedee.
-
Follow the instructions on screen to complete the setup.
Supported devices
This integration supports
- Tedee PRO
- Tedee GO
Binary sensors
- Charging: indicates whether the battery is currently charging.
- Pullspring enabled: indicates whether the pull spring setting is enabled.
- Semi locked: indicates whether the lock is in a “semi-locked” position. “Semi-locked” means the lock has been turned manually and is between its normal end positions. The lock itself will be unavailable in this position.
- Lock uncalibrated (disabled by default): Shows when the lock is in an “uncalibrated state”.
Sensors
The integration currently offers two sensors: A battery sensor, indicating the charge of your lock, and a “pull spring duration” sensor, indicating how long (in seconds) your latch will stay pulled after a pull operation (if supported).
Possible use-cases
- Auto lock/unlock the door based on presence
- Control your lock from smart home panels
- Get alerts when battery is low
Automations
Get started quickly with these automation examples.
Automatically lock the door when the last person leaves home
Example YAML configuration
alias: Lock door when last person leaves
description: Lock the door when last person leaves the home
mode: single
triggers:
- trigger: state
entity_id:
- zone.home
to: "0"
conditions: []
actions:
- action: lock.lock
metadata: {}
data: {}
target:
entity_id: lock.lock_a1b2
Known Limitations
This integration only supports functionality that is available locally. This means that the following elements are not supported:
- Activity logs
- Updates
- Key pads
Removing the integration
This integration follows standard integration removal. No extra steps are required.
To remove an integration instance from Home Assistant
- Go to Settings > Devices & services and select the integration card.
- From the list of devices, select the integration instance you want to remove.
- Next to the entry, select the three-dot
menu. Then, select Delete.
Troubleshooting
Lock state is not updated in real-time
Make sure your bridge can reach your Home Assistant instance. This means that if you use separate VLANs, you need to configure your Firewall appropriately. Additionally, if you have configured an SSL-enabled endpoint for your Internal URL (Settings > System > Network> Home Assistant URL), try setting it back to the IP address of your instance (or a non-HTTPS URL), as HTTPS sometimes leads to problems with the push updates.
Authentication failures when trying to use the integration
- This integration works with local tokens only, tokens from the cloud won’t work
- In the bridge settings
encrypted token must be enabled - The token that is used to talk to your lock is time-limited. Sometimes there were issues when the clock of the Home Assistant host was slightly out of sync, so try to sync your host’s clock.