Sage Doorbell Sensor Wiring

mikejclark · December 24, 2022, 2:27pm

I’ve just bought a Sage doorbell sensor but struggling to get it wired correctly.
I’ve wired the doorbell (Byron 776) per instructions (see attached image) and I’m able to pair the sensor in zigbee2mqtt.

The sage instructions say to connect the green wire to front and white wire to trans (I have ignored the yellow wire as this is for a second/rear push button). But when I look at my connections they are labelled 0, 1, 2, 3. The push button is connected to 0 & 2 (per instructions).

So far I have connected the green wire (front) to 0 and white (trans) to 2. I have setup an automation to send a notification when the bell is pushed but when the system is powered on I get constant notifications to my phone. The same happens switching the wire colours.

I’ve followed this video as best as I can but the connections are very different from mine.
https://www.youtube.com/watch?v=dmK4b02wZrI

Any idea what I’m doing wrong?

Anto79-ops · January 22, 2023, 1:20am

I just bought one of these Sage doorbell Sensors and should be coming in next week. My doorbell is the same as the video, only has 3 terminals, so, hopefully be straightforward.

Did you manage to figure out your doorbell? Maybe it needs a jumper? Probably manufacturer would know.

If you did, how did it pair into HA?

k8gg · January 22, 2023, 7:36am

It would be straightforward.

In terms of pairing, you would just pair it via your zigbee controller. I am using zigbee2mqtt + sonoff ZBDongle-P… battery % status is not supported on mine, and looks like it has been that way for years now - regardless which zigbee controller combo you are using.

Anto79-ops · January 22, 2023, 11:58pm

Thanks!

Good to know.

Does the doorbell state show up or do you have to dig into ZHA events? I guess you wouldn’t know if you are using Z2M.

mikejclark · January 24, 2023, 9:44pm

For anyone else that has the same doorbell as me I used connections 0 for Trans and 3 for Front. Some useful information from the seller on eBay:

You need to work out where the low voltage AC connections are on your bell, they are typically:

Low Voltage A/C Live
Low Voltage A/C Neutral
Low Voltage A/C LIve (to the bell push)
Low Voltage A/C Switched Live (from the bell push)

The White wire on the sensor needs to go to Low Voltage A/C Neutral and either the Green or Yellow wire needs to go on the Low Voltage A/C Switched Live that comes back from the bell push.

Anto79-ops · January 28, 2023, 12:51am

Awesome! Just got mine and it works really well.

I made some slight modifications to the doorbell box using a simple drill bit so that way I can get the wire under and the cover on nicely.

k8gg · February 3, 2023, 3:05am

I am using zigbee2mqtt, and I noticed that mine would update its status every few seconds (anywhere from 5-20 seconds), which does seem too chatty.

Does yours do this?

I mean, linkquality does change a bit, but, still, I don’t see the need to send updates every few seconds…

= = = = =
EDIT: after further investigation… looks like the device keeps asking OTA updates every few seconds. Here are some of the logs:

Debug 2023-02-02 22:45:28Device 'Doorbell Sensor' requested OTA
Debug 2023-02-02 22:45:28Responded to OTA request of 'Doorbell Sensor' with 'NO_IMAGE_AVAILABLE'
Debug 2023-02-02 22:45:33Received Zigbee message from 'Doorbell Sensor', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":9,"imageType":2,"manufacturerCode":4116}' from endpoint 18 with groupID 0
Info 2023-02-02 22:45:33MQTT publish: topic 'zigbee2mqtt/Doorbell Sensor', payload '{"action":null,"battery":null,"last_seen":"2023-02-03T03:45:33.884Z","linkquality":123}'
Debug 2023-02-02 22:45:33Device 'Doorbell Sensor' requested OTA
Debug 2023-02-02 22:45:35Responded to OTA request of 'Doorbell Sensor' with 'NO_IMAGE_AVAILABLE'
Debug 2023-02-02 22:45:42Received Zigbee message from 'Doorbell Sensor', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":9,"imageType":2,"manufacturerCode":4116}' from endpoint 18 with groupID 0
Info 2023-02-02 22:45:42MQTT publish: topic 'zigbee2mqtt/Doorbell Sensor', payload '{"action":null,"battery":null,"last_seen":"2023-02-03T03:45:42.976Z","linkquality":127}'
Debug 2023-02-02 22:45:42Device 'Doorbell Sensor' requested OTA
Debug 2023-02-02 22:45:43Responded to OTA request of 'Doorbell Sensor' with 'NO_IMAGE_AVAILABLE'
Debug 2023-02-02 22:45:55Received Zigbee message from 'Doorbell Sensor', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":9,"imageType":2,"manufacturerCode":4116}' from endpoint 18 with groupID 0
Info 2023-02-02 22:45:55MQTT publish: topic 'zigbee2mqtt/Doorbell Sensor', payload '{"action":null,"battery":null,"last_seen":"2023-02-03T03:45:55.041Z","linkquality":127}'
Debug 2023-02-02 22:45:55Device 'Doorbell Sensor' requested OTA
Debug 2023-02-02 22:45:56Responded to OTA request of 'Doorbell Sensor' with 'NO_IMAGE_AVAILABLE'
Debug 2023-02-02 22:47:14Received Zigbee message from 'Doorbell Sensor', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":9,"imageType":2,"manufacturerCode":4116}' from endpoint 18 with groupID 0
Info 2023-02-02 22:47:14MQTT publish: topic 'zigbee2mqtt/Doorbell Sensor', payload '{"action":null,"battery":null,"last_seen":"2023-02-03T03:47:14.757Z","linkquality":127}'
Debug 2023-02-02 22:47:14Device 'Doorbell Sensor' requested OTA
Debug 2023-02-02 22:47:14Responded to OTA request of 'Doorbell Sensor' with 'NO_IMAGE_AVAILABLE'
Debug 2023-02-02 22:47:19Received Zigbee message from 'Doorbell Sensor', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":9,"imageType":2,"manufacturerCode":4116}' from endpoint 18 with groupID 0
Info 2023-02-02 22:47:20MQTT publish: topic 'zigbee2mqtt/Doorbell Sensor', payload '{"action":null,"battery":null,"last_seen":"2023-02-03T03:47:20.037Z","linkquality":127}'
Debug 2023-02-02 22:47:20Device 'Doorbell Sensor' requested OTA
Debug 2023-02-02 22:47:20Responded to OTA request of 'Doorbell Sensor' with 'NO_IMAGE_AVAILABLE'

Now, anyone know how I could turn that off?

Anto79-ops · February 3, 2023, 3:59am

I’m using ZHA and not sure how I can even see this information. My logbook is empty unless the doorbell is pressed.

But, there is no OTA update entity in ZHA.

k8gg · February 3, 2023, 4:30am

Hmm… OK, if ZHA,
How often do you see this “last seen” field being updated?

Anto79-ops · February 3, 2023, 5:13am

Just checked that field and it was last seen 2 hrs and 9 minutes ago (from now).

k8gg · February 9, 2023, 7:18am

For the record:

jay.p · March 27, 2023, 12:39pm

Hello,

I have recently bought the Sage doorbell,

I have wired it all up, however in Zigbee2MQTT, for the action state I only see N/A.

Has anybody experienced this?

mikejclark · March 27, 2023, 12:57pm

I’ve just had a look and I see the same thing. Are you having problems getting it to work? Have you created an automation for it yet?

jay.p · March 27, 2023, 1:04pm

Yes having problems getting it to work as it does not report when the doorbell is pressed.

Under the MQTT everything is unknown, so unable to create an automation.

Not sure what the problem is

mikejclark · March 27, 2023, 1:34pm

This is what I get in my z2m log when I push the doorbell. What do you get?

jay.p · March 27, 2023, 1:47pm

Sorry, sorted the problem, I have the DB1C and had to reconfigure to let it know I have a mechanical door bell.

Once reconfigured, all is now working.

Thank You

k8gg · August 1, 2023, 5:46pm

Another update to this “it keeps asking OTA updates every few seconds” issue:

after a few weeks (or months) this “keeps asking OTA updates” issue kind of dissipated by itself.
I do not have this symptom anymore.
I didn’t do much else to the doorbell sensor itself, other than keep the zigbee2mqtt up to date.
The 1st CR2 battery died within 1 week after I install my doorbell sensor, likely due to this OTA-request-every-few-seconds thing. I have since fitted a new battery in Jan 2023, and 6 months later it is still working.

So now it is a reliable doorbell sensor, working as it should be, as designed.

= = = =
Also, @jay.p and @mikejclark , you guys probably knew this by now, but for everyone else coming to this thread in the future:

The action sensor reading “Unknown” or “None” or “N/A” is typical. Mine behaves the same when no one is ringing the bell.
When the mechanical doorbell chime rings, as Mike mentioned above, you would get the action of bell1 (or bell2 depends on whether you have another doorbell button wiring to the same chime.)

So, here is the trigger of my automation:

alias: Doorbell Press - Send Notification
description: ""
trigger:
  - platform: device
    domain: mqtt
    device_id: <your device id here; mine was a 32-digit string>
    type: action
    subtype: bell1
    discovery_id: 0x<another id here; mine had 16 digits> action_bell1

Anyways - hope this helps.