I want to add a doorbell sensor to my chime and I am already aware of using zwave magnetic reed switch sensor trick but with Sage Doorbell Sensor widely available online for 3 to 5 dollar each. I brought one to play with and wonder if anyone here have successfully pair it to Home Assistant?
Here a link with more info about the doorbell sensor
Doable on Home Assistant?
Someone mentioned on discord chat there is a Sage Doorbell handler developed for a different hub on Git at https://github.com/lmosenk/SAGE-Doorbell-Sensor-ST/blob/387b2d8762324fe9d9408268fb254483b301a2bf/SAGE_Doorbell_Sensor_ST.txt
Can it be converted into a Home Assistant handler?
+1 from me. Got it working via Smartthings hub, but want to move it to HomeAssistant & zigbee2mqtt.
+1 from me as well. It would be awesome if there was a way to add it without having to install zigbee2mqtt. I’m not sure what the level of effort is to port it to Home Assistant. I have RZ ravens and a couple hacker rf ones lying around. Never developed anything for Home Assistant before but if someone could point me in the right direction I would like to help.
I’ve just received my Sage sensor. I tried to pair it with Deconz. I can see it in the Deconz VNC viewer but in the webapp it fails to appear. I also cannot see it in any of the even logs but that might be because I haven’t got it connected to the chime correctly. I’m not sure how to integrate it with my chime as the instructions are US designed and I’m in the UK with a totally different doorbell setup.
I just got the Sage Doorbell Sensor also, I do have a zigbee2mqtt server running on a Pi. The zigbee2mqtt can see the device, but obviously it’s unknown. But I can see the device ID, and brand, and that its a bell.
I tried following the Add your own device instructions here but when I opened up the devices.js I was lost after that. I know almost little to nothing on programming languages.
I don’t know why this hasn’t been added sooner, as I believe this device would be great in Home Assistant.
If anyone wants to help and walk me through adding a new device, I’d be up for it.
I just opened 2 PR on GitHub! We have to wait for them to be approved and in the new release of zigbee2mqtt the magic will be done!
Thank you very much. Just updated the Zigbee2Mqtt to the latest 1.14 and the Doorbell sensor is working perfectly.
Thank you very much.
So I caved and did some research myself because I don’t have a zigbee controller compatible with zigbee2mqtt. I found a solution for ZHA based on the URL below:
logger:
default: error
logs:
homeassistant.components.zha: debug
Restart home assistant
Once restarted, go to “Developer Tools > Events > Listen to events”. Set “Event to subscribe to” to zha_event and click “Start Listening”. Press the doorbell. You should see a message like this:
{
"event_type": "zha_event",
"data": {
"device_ieee": "00:08:89:00:01:d4:a5:79",
"unique_id": "00:08:89:00:01:d4:a5:79:18:0x0006",
"endpoint_id": 18,
"cluster_id": 6,
"command": "on",
"args": []
},
"origin": "LOCAL",
"time_fired": "2020-07-20T23:39:39.179450+00:00",
"context": {
"id": "adb05b67cd464ac9be093224a5b74d0e",
"parent_id": null,
"user_id": null
}
}
id: '1595288207509'
alias: Doorbell Automation Test
description: ''
trigger:
- event_data:
command: 'on'
device_ieee: 00:08:89:00:01:d4:a5:79
platform: event
unique_id: 00:08:89:00:01:d4:a5:79:18:0x0006
event_type: zha_event
platform: event
condition: []
action:
- data: {}
entity_id: switch.inovelli_unknown_type_0004_id_0001_switch_3
service: switch.turn_on
I was hoping to build a sensor from this but I can’t find a solution. If I come across something I’ll let you guys know. It also seems odd that I have to set the device to debug mode to see zha_events. I’m sure there is a reason but I’m not a developer for the system so idk.
Just for info…
I have a solution based on zigbee2mqtt and a Aquara DJT11LM motion sensor stick on my doorbell.
That simple…
More info if needed
Hi, It just installed the SAGE doorbell sensor on a AC Friedland doorbell model D117 ( DingDong).
The doorbell is connected to a Friedland doorbell transformator D770 8V - 0,5A.
I connected the Sage Green wire to terminal 0 (first doorbell) and the Sage White wire to the terminal T (Common).
Since I don’t have an extra backdoor bell, I left the Sage yellow wire unconnected.
I then paired it succesfully with ZHA (it’s the default Zigbee integration running on Home Assistant).
Zigbee controller is a tasmota flashed Sonoff Zigbee Bridge.
The doorbell get’s recognized as “Echostar Bell”, I then added a first automation to alert me me of the included “First button” button pressed Trigger available on the device.
I notice I don’t get a trigger when I press the doorbell. If I sometimes press 2 times fast I get the notification.
My question : what is the requested minimum AC voltage/current for this sensor the “see” a doorbell press.
My current transfo is 8V AC (0,5A). Is this to low ? Do I need a higher voltage transfo ?
My Friedland doorbell model D117 has 8-16V AC or 6V DC (batteries), max. 15 Watt connection.
Maybe I should replace my AC transfo with a 12V 0,5 A or 1 A ?
Hopefully this will also give a louder dingdong sound since it’s pretty low now.
It is also one of my issue. I can’t find much information on how to create a binary sensor out of the event it generates. Also, one issue being that this device can send multiple events for one ring. Especially if it is a long one. So even if I was able to create a binary sensor out of it, I would need to filter those repeated events.
edit: I replaced the trafo with a 12V AC 1,5A model and now the sage doorbell module “sees” every doorbell press 
Doorpress launches an event, it can’t be that hard to link a input_boolean to that event for your binary sensor ? Just set the boolean on doorbell press and reset the boolean after x sec (both with a HA automation)
Yeah that could be a way to do it. Not terribly clean but yeah that would be one solution. Ideally it would have been with a binary sensor.
You’re running at 4VAC, that’s definitely too low. For a mechanical doorbell you should go for a 18-24VAC transformer. I use a 24VAC transf. with the SAGE since 2y with an EZVIZ DB1, it works great, but you need a good transformer. It will also solve your loudness issue.
Here’s my automation (I use ZHA) for Doorbell announcement through Alexa, plus a mobile notification. There’s a delay: 10 that throttles the multiple events coming from SAGE. It’s working perfectly since 2 days. The SAGE is managed like a 2 button switch, one button for each input. I only use one.
alias: Doorbell Alexa Announcement
description: 'automation: doorbell/alexa/mobile'
trigger:
- device_id: 3c63c79617fd138533bd5fe7472a18f7
domain: zha
platform: device
type: remote_button_short_press
subtype: button_1
condition: []
action:
- device_id: f54a02af11b8f01662c0a8fd8c095540
domain: mobile_app
type: notify
message: Someone's at the door...
title: Doorbell DB1
- service: notify.alexa_media
data_template:
target:
- media_player.cucina
- media_player.camera_genitori
- media_player.bagno_genitori
- media_player.camera_bimbe
- media_player.portico
- media_player.locale_caldaia
- media_player.mansarda
message: Someone's at the door...
data:
type: tts
- delay: '10'
mode: single
The only problem I have with the current driver is that the battery level of the SAGE is not being reported.
I’m new to HA, I just migrated all my sensors/devices/buttons/switches/lights (zigbee/z-wave/wifi) from Hubitat to HA, and started porting my automation scripts. Lot to learn, lot of fun. 
Ciao,
Alessandro
Has anyone successfully been able to pair the SAGE DoorBell with the ConBee II and get it into Home Assistant?
Mine showed up in Phoscon like this (automatically):
And I can see it in deConz:
And also it is found in the REST-API:
{
"config": {
"group": "19",
"on": true,
"reachable": true
},
"ep": 18,
"etag": "cff7bbecb8156fcbfe4845d421e19f5a",
"lastseen": "2021-03-20T20:34Z",
"manufacturername": "Echostar",
"mode": 1,
"modelid": "Bell",
"name": "Doorbell Sensor",
"state": {
"buttonevent": null,
"lastupdated": "none"
},
"swversion": "3.2.2",
"type": "ZHASwitch",
"uniqueid": "00:08:89:00:01:d9:af:d2-12-0006"
}
It is listed as a device in HA, but with no entities. Listening to deconz_events in HA produces nothing, even though I have checked with my voltmeter that pressing the doorbell button sends approx 22VDC to the green wire with the white connected to ground.
So, what am I missing ?
Of the top of my head I thought the unit needs AC to switch not DC?
That could well be, but wouldn’t you expect it to be “reachable” independent of whether it has been switched or not?
The strange thing is that in the REST-API it says reachable: ture, while Phoscon says “Not reachable”.
And as long as the item doesn’t show in HA (only the device shows), there isn’t much to be done.
Do you have one that works?
I’m using the standard zigbee integration and that sees the device but have no entries in the driver it uses. I can see the press in the event logs
Hi all, can someone help me please? I have installed a Sage Doorbell sensor and linked it to Zigbee2MQTT, using Mosquitto as the broker. In node red, I have successfully connected a debug node to the entity and it is getting messages through. What is worrying me is that without pressing the doorbell button, I am getting a constant stream of messages from the sensor. They look like this (repeated over and over, several times per second).
“{“action”:“on”,“linkquality”:44}”
01/04/2021, 14:09:04node: de75a021.ad3b58
zigbee2mqtt/switch.doorbell : msg.payload : string[30]
“{“action”:”",“linkquality”:44}"
01/04/2021, 14:09:04node: de75a021.ad3b58
zigbee2mqtt/switch.doorbell : msg.payload : string[32]
“{“action”:“on”,“linkquality”:44}”
01/04/2021, 14:09:04node: de75a021.ad3b58
zigbee2mqtt/switch.doorbell : msg.payload : string[30]
“{“action”:”",“linkquality”:44}"
01/04/2021, 14:09:04node: de75a021.ad3b58
zigbee2mqtt/switch.doorbell : msg.payload : string[32]
Is this normal? If not, what do I need to do to fix it?
Thanks