@Konrad, even body in GET request cannot be parsed so it would not help. I agree that moving all state to query is also not viable. I think the best solution here could be to add some kind of event callbacks - so define URL to call when lock gets locked, another URL when it gets unlocked, and one more when it fails to lock. Those 3 events are most important to get in real-time, all the other stuff like battery status etc can be polled and it will be fine. Alternatively a single callback URL with a placeholder which would get substituted with new state (locked, unlocked, blocked).
@Michal you are talking about webhook integration which I agree. There was already a discussion on page 2 of this thread about it. Cloud API seems to have one
Hi,
As for loxone I can tell that the body of the http response can be read. It could work as following:
- create a virtual output which calls tedee the GET /lock/{deviceid} endpoint
- store the response of this virtual output in a local file of the miniserver
- create an virtual input which reads the url of this local file every 10 seconds. The virtual input then has the option of reading out values of this local file (response from earlier)
- the virtual output can be triggered using the loxone miniserver API. So we could give the tedee bridge the correct URL to trigger this VO thru the POST /callback endpoint.
The problem with this solution is that the status is also only updated every 10 seconds due to the limitation to read the local file only every 10 seconds. So you can as well just directly call GET /lock/{deviceid} every 10 seconds in the virtual input. This is what we are doing right now.
If loxone would give us the possibility to read values from the response also for virtual outputs instead of storing the response in a file the problem would be solved. I have already asked them if that is visible for them.
Another solution would be Michals proposal which I really like! If the tedee bridge API could have different callback urls for different events we could use the loxone API to change states in real time. So one event if lock ID xyz changed to unlocked and one of it changed to locked. Basically all events you want in realtime.
One thing that would also needed to be addressed in the tedee bridge API is that callback URLs with a username and password don’t seem to work. So right now it would not even work with the loxone API because this url callback does not work:
Username:password@miniserverip/path
I have tested this kind of authorization in another project and it did not work.
Best
Stephan
hello, I can only agree with Ste Phan. A separate webhook for each status would be a solution that could be implemented in the short term. This would avoid the query time of HTTP inputs which are limited to 10 seconds in Loxone.
I can only ask you to implement this feature in this way, it would not bring any disadvantage and would give the whole Loxone community a great added value. The time delay of 10 seconds to know if the lock has really closed is not practicable for a security product. Thank you!
I am a bit puzzled by this implementation. A local api is really useful and as a result home assistant has now also integrated Tedee via this api.
Today the Azure webservice has an outage which has an impact on the remote function of the lock. So I thought that’s not a problem as that is the purpose of a local Api right?
But the bridge is not available anymore. The local api is dead, just the Bluetooth stuff via the api works.
So what is the deal here?
I can confirm Carsten’s issue. Locks are only available via Bluetooth. This is just not right Tedee. Getting the key every other day is not what customers thought they will get when they bought the product to begin with, but this is just ridiculous! Seriously, if you are not able to handle what you thought you would be able to and advertised (via resellers) to the customers, just sell your company already to someone who is capable of developing the software of this nice piece of hardware.
got the same problem with local api during outage, that’s ridiculous that “local” api requires cloud, it’s not local api at all
cannot update the previous post, so adding another one looks like it’s not even possible to connect to the bridge via bluetooth in the app during that outage
@Carsten, We’re aware of the recent outage impacting both our Azure cloud service and, unexpectedly, the local API functionality. This was not the intended behavior, as the local API should provide a reliable fallback during such incidents. Unfortunately, a bug in our bridge firmware disrupted this process. Please know our team is actively working on a firmware update to address this issue and prevent future occurrences. We deeply apologize for the inconvenience and appreciate your patience as we work to enhance the reliability of our systems.
You are selling smart door locks. This MUST NOT happen.
Hi @Konrad Sikorski Are there any news or plans about adding different callback-urls for each event? thank you!
I would like to be able to retrieve the activity log using the local API. That would enable home automation systems to check whether the lock was opened by the Mobile App. Can you please add this information to the local API? Or do I need to request this elsewhere?
Added done
From Feature Requests to Archive