jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-15 21:36:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update tedee docs with encrypted token hint (#35674)

Browse Source
This commit is contained in:
Josef Zweck 2024-11-10 11:30:04 +01:00 committed by GitHub
parent 6c05dcd861
commit 5a47d817b3
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
source/_integrations/tedee.markdown
View File

@ -26,7 +26,7 @@ This integration interacts with your [Tedee](https://tedee.com) locks by communi
## Prerequisites
- You will need the bridge to add your locks using this integration.
- You need to have the local API enabled.
- 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](/integrations/homekit_controller/) (only for PRO model). Communication will happen over Bluetooth in that case, and features will be limited.
@ -113,9 +113,15 @@ This integration only supports functionality that is available locally. This mea
## Troubleshooting
{% details "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 ({% my network title="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.
{% enddetails %}
{% details "Authentication failures when trying to use the integration" %}
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.
- This integration works with *local* tokens only, tokens from the cloud won't work
- In the [bridge settings](https://docs.tedee.com/bridge-api#tag/Authenticate) **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.
{% enddetails %}