Hi Andrzej,
Thank you so much for the answers!
Today I've also posted the question regarding iBeacon (https://tedee.freshdesk.com/en/support/discussions/topics/77000264316) thinking of it as some hardware device/key to auto-unlock Tedee without a phone. Based on your answer this seems more like a communication ids broadcasted from bridge to the phone. It would be nice to have some more details in that thread.
Hi Lars, to pull the spring you can either double click on the lock icon or swipe the switch down and up with one move in the lock details view. As for HomeKit's response you described, that's the standard. How far is the lock from the hub and what hub do you use?
Hey Lars, there is no such thing as "implementation" for it suggests there is more than one way to "implement" how HomeKit works. It's Boolean: true or false. You pass the certification or you fail. BTW, do you have any other battery-operated locks in your network to compare? Homebridge is almost as fast as the bridge and it's not any surprise. It's just something completely different. Whatever is left to be fixed, it's not our "implementation". Have a good one!
Because then it really works over our bridge and not over a HomeKit hub.
It works for me here without a hitch. There is a slight delay when using the home app, but it is barely noticeable.
Hello Lars,
Are you still using Homebridge for any other non Homekit devices ?
Would it be possible that your previous Tedee lock Homebridge implementation is somehow interfering with the new Native HomeKit version ?
I am not a homebridge expert, but since other users have no issue with HomeKit native Tedee lock, it is probable there is something in your "home" config that is causing the problem.
I know this is a nightmare to do, but have tried re-installing every device from scratch ?
If I were you and serious about finding the culprit, I would erase my HomeKit and Homebridge configs and start by installing the Tedee Lock in HomeKit. Then I would try to add the other devices one by one (testing the lock every time until I would find the source of the problem.
I sincerely hope you find a solution and perhaps Tedee will be able to help you with troubleshooting (after all, it is in their interest to squash any bugs you find).
Good luck Lars,
David
Konrad Sikorski
Hello tedee users,
We've been working hard on HomeKit integration. In the upcoming weeks we will release few beta versions for mobile and devices and we'll ask you for help. Please note that the "beta" versions may be unstable. By joining the testing program, you acknowledge that application may not match quality standards as a regular version does.
How to join for Android Beta
If you want to join the beta program please sign up for using this link or directly from Google Play app link.
You can leave the testing program any time using the same link and install the public version from store.
How to join for iOS Beta
You can join iOS beta using this public link.
In order to install the app, you will need to download and open TestFlight. Please follow the steps from the manual: https://testflight.apple.com/.
To leave testing program, you can delete yourself as a tester in the app’s Information page in TestFlight by tapping Stop Testing and install the public version from store.
Version 1.115.01 beta (iOS), 1.115.1.1 beta (Android)
This version introduce new way of discovering and connecting to tedee devices via Bluetooth that will be released later with a HomeKit firmware update. During this test we want to make sure that backward combability is working and users doesn't have issues with connecting to exiting devices via Bluetooth.
What to test:
We already have tested this and everything worked fine. Please share your feedback under this post.
5 osób lubi to