Reolink automation with old chime

Configuration
1

Who can help me. I’ve been puzzling for quite some time and can’t figure it out.
I have a Reolink front door bell but we find the chime too soft, we can’t hear it throughout the house. We would like to have the old mechanical gong go when someone presses the button.

I thought about making an automation for this, I see the front door bell (binary_sensor.d340p_visitor) and the old chime (binary.sensor.doorbell) in HA but the automation doesn’t work.
My automation:

alias: New automation
description: ""
triggers:
  - trigger: state
    entity_id:
      - binary_sensor.d340p_visitor
    to: "on"
conditions: []
actions:
  - action: switch.turn_on
    metadata: {}
    data: {}
    target:
      entity_id: binary_sensor.doorbell
      device_id: 5981218be0c2f362e26c8ba532c31b9c
mode: single

Thanks in advance
Bas

2

Ik voed de Reolink deurbel via onze oude deurbel trafo waar de gong nog op aangesloten zit, in de Reolink kiezen voor mechanical chime en dat werkt perfect. Geen automatisering voor nodig.

3

Dank voor uw reactie.
Ben even benieuwd hoe u dit voor elkaar heeft gekregen. Heeft u een POE versie van de Reolink?
Ik heb de POE versie. Kwam op internet een beschrijving tegen van iemand die een mechanische gong had aangesloten met de voeding van de bestaande bel.
Maar volgens mij kan dit (nog) niet met de POE versie.

Hoor het graag

4

How did we start off with English posts and end up with Dutch?

1 Like
5

thanks for pointing that out to us.
do you also have a solution for the above question?

6

I have the new version which can both be run on battery and be powered via hardwire. I used my exsting cable, trafo and gong. Just simply choose mechanical chime in the app.

7

As far as I know, you can only choose this option if you have the Reolink doorbell on wifi, possibly with fixed wiring. Not the POE version.

8

The Reolink battery devices are only recognized in HA when coupled with the Reolink Home Hub( definitely worth the money). I run 10 Reolink cams

Given that, I don’t think that is the main issue, correct? With the language barrier, I missed some of the conversation.

So I am clear, is the Reolink isn’t even a part of the equation, correct?

Main issue I see

your action is switch.turn_on but the entity targeted is a binary sensor, not a switch.

actions:
  - action: switch.turn_on
    metadata: {}
    data: {}
    target:
      entity_id: binary_sensor.doorbell
      device_id: 5981218be0c2f362e26c8ba532c31b9c
mode: single

You can do something like this

alias: Doorbell
description: ""
triggers:
  - trigger: state
    entity_id:
      - binary_sensor.doorbell
    to: "on"
conditions: []
actions:
  - action: switch.turn_on
    metadata: {}
    data: {}
    target:
      entity_id: switch.xxxxx
mode: single
9

unfortunately this does not work. I changed the sensor to a switch but when I press the Reolink front doorbell the ‘old’ doorbell does not ring/turn on

I have a V2 version Reolink with POE. I do indeed read on the internet that if you use the existing wiring you can use your old chime in the app but that this option is not available with a POE powered doorbell.

10

Any Reolink device that is not powered constantly requires the Home Hub for HA. It’s not ideal.

11

I don’t understand. My POE doorbell isn’t constantly powered? I have a NAS where I store my camera images. I have the Reolink integration in HA, why I should buy the Home Hub?

12

I found out that my Reolink Doorbell is not sending the visitor event anymore (binary_sensor.porte_visiteur is always off).
The last working firmware was the July 2024 version, before “AI vehicle detection” was introduced.

EDIT: Downgrading is possible and fixed that specific issue.
EDIT2: And this is how I solved the issue of the OP, I’ve an automation that broadcast a “visistor at the door” to all my home speakers :slight_smile:

alias: Quelqu'un sonne
description: ""
triggers:
  - entity_id: binary_sensor.porte_visiteur
    from: "off"
    to: "on"
    trigger: state
actions:
  - target:
      entity_id: script.annonce_partout
    data:
      variables:
        message: Visiteur à la porte
        important: true
        chime: false
    action: script.turn_on
trace:
  stored_traces: 20
mode: queued
max: 10
13

I have a Synology RS1221+ server and ran their Surveillance Station, but abandoned it. The Home Hub consolidated all my battery, POEs and wired cams. Your doorbell model matters when integrating with HA. Some work directly others do not so you may be fine, I just don’t know enough about your Reolink hardware to say one way or another.

My point with your automation was to go simple to start. Try activating a light then move to the second part of your automation. action: switch.turn_on and then debug that.

alias: TEST
description: ""
triggers:
  - trigger: state
    entity_id:
      - binary_sensor.doorbell
    to: "on"
conditions: []
actions:
  - action: light.turn_on
    metadata: {}
    data: {}
    target:
      entity_id: light.xxxx
mode: single

Use choose entity vs choose device
image

Triggered by the state of binary_sensor.argus_pt_ultra_motion at February 9, 2025 at 5:55:28 AM

Light ‘Turn on’ on TV Lights

Finished at February 9, 2025 at 5:55:28 AM (runtime: 0.01 seconds)

14

Thanks, that’s a good idea. Will try that later :+1: Now I am on the run.

15

This test works. I can control a lamp with this automation, so now I know which sensor is triggered when the front doorbell is pressed.
But now I still have to find the switch to make the old chime go off.

Before I got the Reolink doorbell I had made my doorbell ‘smart’ with an esp3266 from:
zuidwijk.doorbell: github://zuidwijk/esphome-doorbell/doorbell.yaml@main

16

Some binary_sensors are not read/write.
By that I mean, for exemple, my smoke detector, there is a binary_sensor.smoke_detector_test.
It is on when I press the test button but if I turn it on from home assistant, it is not doing a test, it is a read-only sensor.