Incoming webhook from Tedee PRO not updating the door sensor state

Configuration
1

Hello everyone,

I have a Tedee PRO lock with Tedee Bridge, HA integration seems to be working (mostly) smoothly.

I pair the lock, bridge and door sensor in the Tedee app, enable API and use the API key to add it to HA. All well.

However, the door sensor state only updates when HA polls the bridge, not when the bridge sends a webhook.

I set the log level to debug and I see this in the logs:

homeassistant  | 2026-02-02 13:11:00.611 DEBUG (MainThread) 
[homeassistant.core] Bus:Handling <Event state_reported[L]: 
entity_id=binary_sensor.locktedee_vrata, 
last_reported=2026-02-02T13:11:00.611858+01:00, 
old_last_reported=2026-02-02T13:10:30.824086+01:00, 
new_state=<state binary_sensor.locktedee_vrata=on; 
device_class=door, 
friendly_name=LockTedee Vrata @ 2026-02-02T13:05:25.747658+01:00>>

When I “open” or “close” the sensor (it’s currently on my table, not on the door), the bridge sends a webhook to HA and I get the above log entry.

new_state in the HA log is always the same as the current state of the sensor in HA. I do not believe this to be an error in the data submitted by the bridge because it properly shows the state changes in the Tedee app on the phone.

For instance, at the moment the magnet is next to the sensor, i move it away. It takes a second or two, what happens:

  1. tedee app shows the door is open
  2. almost at the same time I see the webhook request in HA logs that states the new state is the same as the current state in HA (see example above)
  3. after up to a minute, the integration polls the bridge and properly updates the state in HA

If I go the other way (door is open and I close it) I get the same symptoms, the state in HA does not change until polling (and a webhook is received).

What should I look at next? I see that webhook parsing is done in the aiotedee library, not internally in HA (core/homeassistant/components/tedee/coordinator.py at c42d47a61929d39df5a20255d0a3b946fb01a732 · home-assistant/core · GitHub) so I’ll also have a look at that.

2

As suspected, tedee bridge is sending the correct data (this is close, open, close on door sensor):

image
image474×598 15.9 KB

source for the screenshot above:

- alias: "Debug webhook data"
  trigger:
    - platform: webhook
      webhook_id: XXXXXXXXXXXXXXXXX
  action:
    - service: persistent_notification.create
      data:
        message: "received doorState: {{ trigger.json.data.doorState }}"
3

webhook_received() in homeassistant/components/tedee/coordinator.py calls self.tedee_client.parse_webhook_message() which ONLY sets the lock state, not door state:

       elif message_type == "lock-status-changed":
            lock.state = data.get("state", 0)
            lock.state_change_result = data.get("jammed", 0)

(aiotedee/aiotedee/tedee_client.py at a5f2037208f499bf141f44c9923bdcecfe3bbe7f · zweckj/aiotedee · GitHub)

After this, webhook_received() calls self.async_set_updated_data().

I believe more things could and should be parsed by tedee_client, looking further into how it’s done when the integration polls the bridge, because it works there.

4

fix here: change door sensor state when parsing webhook message by borutmrak · Pull Request #7 · zweckj/aiotedee · GitHub