Doorbell

Doorbell

The Lync protocol has no documented doorbell message — this integration discovered one by reverse engineering (see Protocol): the unit sends 0x1F / 0x02 when the chime starts and 0x1F / 0x00 when it ends.

What you get

• binary_sensor.*_doorbell_ringing — on for exactly the chime duration; attribute doorbell_input tells which doorbell terminal
• Event htd_lync_pro_doorbell — fired once per press, at chime start

What the chime does to your zones

When the doorbell rings, the unit powers zones on and switches them to the Intercom source to play the chime — and leaves them that way afterwards. Zones with DND on or the Doorbell switch off are not interrupted.

The integration fixes the aftermath automatically: it snapshots every zone when the ring starts and restores power/source/volume when the chime ends (2-second settle, then only changed zones get commands). Disable in Options if you want raw behavior.

Example automation

automation:
  - alias: "Doorbell → camera on TV"
    trigger:
      - platform: event
        event_type: htd_lync_pro_doorbell
    action:
      - action: camera.play_stream
        target: { entity_id: camera.front_door }
        data: { media_player: media_player.living_room_tv }

Two doorbell terminals? Branch on trigger.event.data.doorbell_input to route front vs. back door to different cameras.