I don't see this topic being published. Was trying to use it for a doorbell press. 

   

(11-04-2025, 05:54 PM)srooks Wrote: I don't see this topic being published. Was trying to use it for a doorbell press. 

You have to add it like any other entity.

    - name: Doorbell
      unique_id: "comfort2_alarm_doorbell"
      default_entity_id: "binary_sensor.comfort2_alarm_doorbell"
      state_topic: "comfort2mqtt/alarm/doorbell"
      availability_topic: "comfort2mqtt/alarm/online"
      payload_on: "1"
      payload_off: "0"
      payload_available: "1"
      payload_not_available: "0"
      device_class: sound

(11-05-2025, 05:44 AM)Ingo Wrote:

(11-04-2025, 05:54 PM)srooks Wrote: I don't see this topic being published. Was trying to use it for a doorbell press. 

You have to add it like any other entity.

    - name: Doorbell
      unique_id: "comfort2_alarm_doorbell"
      default_entity_id: "binary_sensor.comfort2_alarm_doorbell"
      state_topic: "comfort2mqtt/alarm/doorbell"
      availability_topic: "comfort2mqtt/alarm/online"
      payload_on: "1"
      payload_off: "0"
      payload_available: "1"
      payload_not_available: "0"
      device_class: sound

Yes, I've done this. However documentation (and earlier thread) suggests this topic is published to - and this has the doorbell number. 

    - name: Alarm Message
      unique_id: "comfort2_alarm_message"
      object_id: "comfort2_alarm_message"
      state_topic: "comfort2mqtt/alarm/message"
      availability_topic: "comfort2mqtt/alarm/online"
      payload_available: "1"
      payload_not_available: "0"

But I'm not seeing this ever sent / triggered ?

Please post the debug log when the doorbell is pressed and answered. You should see DBxx