Just looked after this: “2” is set as the new state of the lock, the api calls are correct - seems like I didn’t look with enough care the last time. I will try to reproduce this on my own lock.
@mluecke Would you mind checking if your lock is calibrated correctly? The app has a setting, in german it is “Türfalle einziehen” - is this active? It seems as it always pulls the spring when unlocking when active. But this is just a suspicion.
According to the API documentation, mode 2 has find usage only when lock is in Unknown state. It is responsible for making lock to go to Unlocked state no matter what.
Without auto pull spring value (number 3) allows to unlock the lock without pulling the spring (when lock has auto pull spring enabled).
Unlock or pull spring value (number 4) allows to perform two operations depends on current lock state. When lock is in Locked state, it allows to unlock the lock (with pulling the spring when lock has auto pull spring enabled). When lock is in Unlocked state, it allows to perform pull spring.
My lock is in mode „Türfalle einziehen“. If I use mode 3 it only unlocks the door without pull spring. Mode 4 unlocks and then pulls the spring, or only pulls the spring if the door is already unlocked.
Homeassistant 2022.8 finally introduces Bluetooth support for HomeKit, which makes me hope I can get rid of the Tedee bridge and free myself from the cloud.
Unfortunately I got my lock before HomeKit was officially supported, which means I didn’t get a QR code and I also don’t have any Apple device in my home to add HomeKit via the Tedee app. Help is appreciated if anyone is aware of a workaround.
Any news on this topic. What we would love to see is two different modes: unlock / pull spring
I do not well understand what do you love to see. There is lock.lock, lock.unlock and lock.open. lock.open means to pull spring. If in app is set to automatically pull spring with unlock command it makes pull spring also from locked state with lock.unlock. If not it makes pull spring only with lock.open from unlocked state.
I tried it with different modes 0, 3, 4, there is no effect in behavior.
You could make some automation to get different behavior.
Hi joerg65, thanks for you contribution, works pretty well with my tedee.
When the pull spring feature is activated for my lock and I unlock via the API (/api/v1.28/my/lock/{id}/operation/unlock) with mode = 3 (without auto pull), then the lock gets only opened but not pulled at the same time. Leaving the mode = 0 also pulls the spring when unlocking the lock.
When the lock is open, I am able to pull it by calling /api/v1.28/my/lock/{id}/operation/pull.
Same as @tihmann I would love to see those separate commands in my dashboard, to be able to control the lock fine grained.
Have you tried contacting tedee support?
Last week I got ahold of an iPhone.
First step is to add the lock to Apple Home in the Tedee app.
Then you go to the Apple Home app and delete it from there, because a Homekit device can only cumminicate with one Homekit instance.
As soon as you do that HA Homekit Controller immediately recognizes the lock (if you have Bluetooth integration running).
My problem now is still that I need the Homekit PIN as this is a requirement in Homekit Controller. For people who bought the lock after Homekit functionality was introduced, this shouldn’t be an issue. Can someone confirm the lock works if you have the PIN?
I will contact support now to see if I can get ahold of the PIN.
@FPro I can confirm. I set up bluetooth integration, and as soon as you reset the lock (position upwards, holding the button, releasing when red led comes on), it gets autodiscovered by HA. I provided homekit PIN and lock is added. The only controls are lock/unlock and battery level (+ service to identify the lock).
It took me some time to figure out how to add it - when I reset it and it was discovered by HA, I usually paired it with phone first to do the calibration (I do not have bridge, just lock). After that I went to HA and added discovered device - but that did not work, it asked for PIN but threw an error and never got past it. Only then I figured out that once reset, I have to first add it to HA, it works flawlessly, and then pair with phone to do calibration. Until this is done, lock/unlock button is unavailable.
When not using the lock for some time, and then unlocking/locking it from HA, there was few seconds delay (~5 seconds?) to take action.
I initially also had issues when lock would work for some time, and then not anymore, or was not updating battery level. I had Edimax BT 5.0 adapter and no USB extension cable. I added 3m long extension cable, and switched BT adapter to version 4.0 - it does work now. Will see in the morning. I may switch back to BT 5.0 adapter - maybe it is the extension cable that was the cure, as I did see messages in logs about process being busy, unable to cancel connection, etc.
So far I only have lock that is not installed on door yet, so I have to calibrate it from time to time, but I wanted to see how reliable it is in HA first, before installing it.
I contacted the support and by providing the serialnummer they were able to give me a homekit PIN.
I also added the lock by first pairing it with HA and then with the phone. Thanks for the tip with resetting, so no iOS device needed. I had some issues with getting into pairing mode and had to restart it after resetting. I also noticed that the lock goes into pairing mode if you delete it from the app, so there should be no need to reset it.
I experience the same delay. If you don’t use the lock for a few minutes it takes several seconds to respond. For state updates it is the same and the delay seems to be even longer. When standing in front of the door and wanting to get in, this delay is unacceptable. I will keep it as backup, but Jörg/Patrick’s integration is much more responsive (although I need to send commands half way around the continent and it only supports polling). I hope it’s a Homekit Controller issue and gets improvement at some point.
I guess it has something to so with bluetooth connection? I wouldn’t say that it is unacceptable - i don’t have (nor want) bridge and if I open tedee app, it will take anyway around the same amount of time to connect to lock and unlock it. + i can unlock the door little earlier with HA.
Since I haven’t installed the lock yet, I can’t say how things work with pulling the spring, since there is only lock/unlock button. Do you have possibility to test it? If you select unlock, does it unlock and pulls the spring? Or do i need to select unlock once already unlocked to pull it?
In addition - do you have BT5.0 or 4.0 dongle? I have tested with both and it seems to me that at least the one 5.0 I have (edimax) is little less responsive, with more “busy” messages in logs. 4.0 works ok (with that delay after not using it for some time). I was thinking maybe that delay has something to do with 4.0/5.0 version.
Alternatively, maybe if you find out how long of inactivity it takes for lock to respond later, you could set automation to “identify” the lock. Maybe that could serve as some sort of keepalive?
I found this in one review:
One of the additional features of the tedee bridge is its built-in iBeacon (a form of locator based on Bluetooth technology), which improves and speeds up the auto-unlocking function because thanks to the constant power supply it can send a more continuously and stronger signal. When controlling the tedee lock with HomeKit, the tedee bridge is not used, and the tedee lock only communicates with HomeKit via Bluetooth.
Using the bridge and HA in combination with Android quick setting tiles this whole process takes just 1-2 seconds. No need to open an app. With HK Controller add 5 seconds on top. I don’t like to wait in front of my door.
If you set the pull spring in the tedee app it also does it with HK Controller.
5.0
Should be around 2 Minutes. While this does work you will certainly drain the battery of the lock.
This is not correct, at least with HK Controller. My lock is still connected to the bridge. Tedee auto unlocking is generally not that great, which is why I will build my own solution with the new bluetooth integration.
out of curiosity, I did try to automate “identify” button every 30 seconds, but it does not change the delay after bit of inactivity.
Like I said, at least for me, options are either to get close enough to the lock and unlock it via bluetooth (since I do not have bridge) which anyway does take a moment… Or unlock via HA which I can do earlier than that.
I am just curious - do you get more controls (lock/unlock/open maybe?) or it pulls the spring with pressing UNLOCK (so it unlocks and pulls it automatically)? What if lock is already unlocked? Does pressing UNLOCK again pull the spring?
Can I clarify, using the Homekit integration together with the new BLE integration the Tedee can be used in HA without the Bridge, even if we are an Apple free household?
@nairb Correct. I am using BT dongle (had worse experience with BT proxy via esp) and there is only one downside - if you don’t use lock for a minute or so, any further action takes (in my experience) 7-10s. But since I don’t have bridge, even to open tedee android app, connect via bt takes the same, if not longer…
Hello All,
Wondering if there is a way to install the Tedee with Home Assistant without purchasing the bridge. Did someone managed to do that? My Rashberry Pi already has bluetooth and Zigbee. Not sure which technology is using Tedee bridge.
OK, I already answered myself reading previous comments. Sorry 
Thanks!
Can someone explain how to connect Tedee lock with Home-Kit Controller? I made factory reset not showing up in HA. I have connected to Home App and removed still not showing up. In the Bluetooth logs I see the lock.
hi guys, I have a Tedee PRO lock, I try several days to pair with the HA but no luck 
, can someone explain to me how to do it? I have put my phone in 2,4 and even in 5 ghz network, but same, reset it, delete it from HomeKit and Tedee app, but no luck, I have add it yesterday to the HA, but it doesn’t work, doesn’t open/close the door, I assume I have to add it first to HA, after delete it from home app and Tedee app, in HA it will appear 2-3 locks with home controler, I enter the PIN for him but it dose’t work, after added to HA I have to calibrate his, but I can calibrate only from Tedee app, If I try to add to Tedee app I have to reset it what I am doing wrong? can someone tell me the steps? Thank you in advice, I have only the lock no bridge.
I don’t know what is the difference of Tedee pro. You could try the python example from the github of pytedee: https://github.com/joerg65/pytedee, and see what it outputs. And do you have generated your personal token as is advised in the readme?
Thanks joerg65 for the reply, the Tedee PRO it is the old Tedee lock, now thew lunch a new Tedee GO. I will try the script asap, I generat the key, now I have delete the lock now, but I will try to readd today and check if something it is changed. Thanks again.
