I think you can officially call it an obsession now for me. I’ve been suggesting a smart doorbell sensor for awhile now in the Must Have Home Automation Devices page as a means to receive phone notifications and trigger other actions when your doorbell is rung, but I keep running into issues finding the perfect product to suit my needs. My preference is to be able to have this notification capability, while keeping my existing door chime and doorbell button.
In this post, I will attempt to quell my doorbell obsession and provide a quick overview of my findings and impressions while briefly testing the new SAGE Zigbee Doorbell Sensor by Hughes.
I’ve looked at relatively complex and expensive doorbells out there such as SkyBell and Ring that include cameras and two-way communication, but I really do not care for how bulky and obtrusive these devices are. I would like my home entry to be clean and welcoming with a simple door bell. I still may have a discreet security camera in the corner of the entryway ceiling, but it doesn’t scream “I’m watching your every move” to friends and family as does a camera-equipped doorbell.
There are many roll-your-own options out there, but ideally, I would like to use a dedicated device that was designed specifically for this purpose rather than going through the effort, expense and potential, albeit unlikely liability issues of re-purposing a device that is not quite designed to handle typical doorbell voltage. I could add a dry contact bridge relay to the mix, but frankly I haven’t been willing to invest the effort to create such a one-off Frankenstein custom device.
I’ve examined both the Aeon Labs Aeotec ZW056 doorbell and the Nexia DB100Z Doorbell Sensor Z-Wave devices, and ran into issues with both of these products, making them less than ideal for me as a doorbell sensor – although I did ended up being somewhat impressed with the Aeotec Doorbell speaker for use as a generic Z-Wave speaker for playing MP3 clips based on events that take place in my home or relayed via IFTTT.
The SAGE Doorbell Sensor by Hughes
I just received the device yesterday, and have very little time with it – but so far, so good.
The SAGE sensor is a Zigbee device manufactured by Echostar for Hughes. To receive doorbell press notifications, it requires a smart home automation controller such as the Hughes SAGE or the Samsung SmartThings Hub (see the DarwinsDen.com Best of the Home Automation Controllers round-up and the SmartThings Hub review).
At 3″ x 1.5″ x .7″, the SAGE doorbell sensor is reasonably compact – at least compared to a dry contact bridge and relay. The device is similar in design, but slightly smaller than the Nexia Z-Wave Doorbell sensor. Both the Nexia and the SAGE sensors are battery powered, and both are designed to be installed within or discreetly around the doorbell chime housing.
The main difference between the SAGE and Nexia, aside from the Z-Wave and Zigbee interfaces, is that the SAGE sensor also supports distinct notifications from a second doorbell for those that have two doorbell buttons connected to the same chime assembly. My only complaint so far is that just as with the Nexia sensor, I wish there were an option to power this device using the low-voltage doorbell transformer itself, for those with easy access to the doorbell power source. The cable on the SAGE sensor is also a bit shorter and thicker than the Nexia sensor making mounting a bit more of a challenge than it should have been.
The SmartThings SAGE Doorbell Device Handler
Although the SAGE sensor paired fine for me with the SmartThings Hub, it was not able to receive notifications or battery status using any of the available SmartThings device handlers that I tried – and so I ended up writing a custom SAGE doorbell SmartThings device handler.
Details and download information on this SAGE doorbell sensor SmartThings device handler are provided below. I’ve only had a chance to briefly try this out with just a few doorbell presses. So far, though, with minimal testing, this device does not appear to suffer from the same “quick flick” missed button press issue I experienced with the Nexia sensor. The device handler provides a two button ‘pressed’ notification supporting the SAGE’s two distinct doorbell notifications capability (eg. front door/back door).
Unfortunately, I haven’t yet been able to get battery status from the device, so this the battery status field currently shows as blank. Please let me know if you run into issues. There may be some oddities when used with different doorbell types and buttons. Any and all suggestions and updates welcome. I will continue to focus on getting battery status information from the device.
Device Handler Download Location:
The initial Alpha SAGE Doorbell Sensor Device Handler for the SmartThings Hub can be downloaded from:
Installing the Device Handler:
- Login at https://account.smartthings.com/
- Select “My Device Handlers” and select “Create New SmartDevice”.
- On the “Create New Device Handler” page, select the tab “From Code”, and paste in the code from the above GitHub link into the IDE editor window.
- Click the “Create” button at the bottom.
- Click the “Save” button above the editor window.
- Click the “Publish” button and select “For Me”.
The SAGE Doorbell Sensor device handler is now ready for use.
Performing SmartThings actions based on doorbell button presses
You can set up different notifications and simple automations for each of the two doorbell buttons supported using the stock SmartThings Button Controller SmartApp and the stock Smart Lighting SmartApp. Or if you are adventurous, you can use CoRE (the SmartThings Community’s own Rule Engine) to do pretty much any SmartThings supported action you can envision.
Example: Sending SMS and Push notifications using the stock Button Controller SmartApp
I’ve been asked to detail out this process a little more, so as an example, here are the steps for triggering text and push notifications using the stock Button Controller SmartApp:
- Select “MarketPlace” from the bottom panel of the mobile app
- Select “SmartApps” from the top panel
- Scroll down, and select “More” from the selection list
- Select “Button Controller”
- Select “Tap to Set” under “Button”
- Select your SAGE Doorbell Sensor
- Select “Next”
- Enter the actions for the 1st doorbell button (green wire connection)
- Scroll down to “Custom Message”, select Tap to set, end enter your custom message for button 1, eg “Front Doorbell Pressed”
- Scroll down to the “Push Notifications” section, and select “pushed”
- Scroll down to the “Sms Notifications” section, select “pushed” and enter the phone number for receiving SMS text notifications
- Select Next
- Enter the actions for the 2nd doorbell button (yellow wire connection)
- Scroll down to “Custom Message”, select Tap to set, end enter your custom message for button 2, eg “Back Doorbell Pressed”
- Scroll down to the “Push Notifications” section, and select “pushed”
- Scroll down to the “Sms Notifications” section, select “pushed” and enter the phone number for receiving SMS text notifications
- Select Next
- Select Next
- Select Done
You should now receive both push and text notifications for each doorbell. Note, although the Button Controller app can trigger lights, this app only toggles them from off to on or vice versa. If you want to add a lighting automation, to say to turn on your front porch light, you’ll likely want to use the stock SmartLighting SmartApp or another smart app, such as CoRE instead of the button controller app.
The SAGE Doorbell Sensor mounted using the included double-sided tape
The SAGE Doorbell Sensor is powered by a single Lithium CR2 3V battery
SAGE Doorbell Sensor (left) as compared to the Nexia Doorbell Sensor
Visit the DarwinsDen.com reference pages for an overview of which controller hubs and devices may be best for your specific system needs:
Reference these other DarwinsDen.com Feature Comparison Tables:
Just a quick update that my Sage Doorbell is still going strong after nearly 6 years. I still really like this device. I never did get the battery reporting to work, but I’ve preemptively replaced the batteries in this device every 2-3 years and have never had an issue. Granted, there’s not much this device needs to do, as we maybe get a doorbell press only a few times a week. You can often find the Sage now on ebay for under $10 including shipping (US): https://www.ebay.com/sch/i.html?_nkw=sage+doorbell.
Hi – I found the device on eBay in the UK and your device handler so decided to give it a go as I have a traditional doorbell in my house which I like and wanted to make it smart. I’ve not managed to get the device handler to detect any button presses so far though… the Zigbee device was detected straight away by my SmartThings hub and I changed the device handler to your one. It doesn’t appear properly in the new SmartThings app but no errors. Pressing the doorbell results in no events being fired though or state change of the button.
The Sage Doorbell is wired in parallel to the doorbell press button so should detect when the circuit is made.
Any thoughts as to what I’m doing wrong? Thanks in advance!
Hi Simon – I too am in the UK and have had this working with smartthings for over a year – I get a notification when someone rings my dumb doorbell as well as having a light come on a few seconds later. It is very hard for me to diagnose your issue as I’m not as techy as most on this forum. I used a Byron door bell – I wired the device into the door bell box, installed the device handler and it worked. Keep trying – you are almost there. Maybe you have wired it wrong in the box? Good luck!
Hi Robert, thanks for your reply. I’m also using a Byron doorbell – or at least a Byron 9v transformer and separate Byron bell. I’ve tried it wired in parallel with the switch and in parallel with the bell (which I cant see making any difference) but doesn’t work either way… so I don’t think it’s down to the wiring!
I have a 776 and I used this youtube video to help me https://www.youtube.com/watch?v=dmK4b02wZrI&ab_channel=HarperVoice
Thanks Robert. I saw that video but as I made mine from separate button, bell and transformer couldn’t quite translate to my setup. Good news is I now have it working! I changed the wiring so the sage box is in parallel with the bell (I thought I tried it like that before).
I have a web core piston sending a push notification when the doorbell is pressed.
Next I’m going to see if I can change the device handler so that the button can be used by a routine natively in the SmartThings app rather than having to use WebCore…
Hi Simon
Very pleased to hear you have sorted the first part. The device handler definitely works and I use mine in the Smartthings app. The work will pay off – I am still pleased with the way mine works as most people would not suspect a dumb doorbell can give smart notifications
Has anyone successfully been able to pair the SAGE DoorBell with the ConBee II Gateway using deConz and/or Phoscon ?
Ignore my previous post. I got it working following the instructions you provided above. Strangely, it shows up as a Sage Doorbell Sensor in the IDE and has both Presence and Button actions in the app, but it does not appear to distinguish between front and rear doorbells. The history log shows:
2021-02-27 11:20:33.000 AM EST
moments ago DEVICE button pushed Doorbell Sensor button is pushed
2021-02-27 11:20:33.000 AM EST
moments ago DEVICE presence present Doorbell Sensor presence is present
2021-02-27 11:10:58.000 AM EST
10 minutes ago DEVICE presence not present Doorbell Sensor presence is not present
2021-02-27 11:10:53.000 AM EST
10 minutes ago DEVICE button pushed Doorbell Sensor button is pushed
2021-02-27 11:10:53.000 AM EST
10 minutes ago DEVICE presence present Doorbell Sensor presence is present
2021-02-27 11:03:56.000 AM EST
17 minutes ago DEVICE presence not present Thing presence is not present
The first ones are from the front button push and the second from the rear.
Also, the device does not show up in automations. I would love to have it turn on interior lights near the affected door when pressed. What am I missing?
Any ideas on getting the sensor to pair with the new app? The old app is not available.
Thank you so much for this. I have been looking for this solution in London England for years! A normal doorbell which sends a notification to your phone when it is rung. I needed it as it looks more authentic to a burglar and it is quicker than cloud based cameras (I have 2 types). So easy to set up with your instructions – I really appreciate it.
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.
This new URL really helped, I can now see the MyHub and MyDevices. Once I have registered your DeviceHandler, registering the device comes up with “SAGE Doorbell Sensor” and I can setup the Button handler. But I am not getting any messages from the Device after it is switched on. (from the devices event logs) I will play with it some more.
Many thanks for the help.
Just a quick follow up on this. I now have it working. The last step was to get it wired up correctly in the doorbell. Nothing happens until it is wired in and I had to wire across the bell and not across the button.
Again, many thanks for the help.
Great! Glad to hear it’s working. Thanks for following up.
“if you haven’t tried it yet, manually change the device type and see if that helps any. In the SmartThings IDE “My Devices” tab, select the Sage doorbell sensor device (sounds like yours will just be labeled ‘Thing’), select EDIT, and then change the type to “SAGE Doorbell Sensor”.”
I am not actually seeing any devices in My Devices. I am also getting an “Error: 500: Internal Server Error” under “My Hubs”!
You may not be on the correct IDE shard for your account. Samsung at some point created a more generic URL for accessing the IDE. Try logging in from this URL: https://account.smartthings.com/
I have managed to get my hands on one of these Sage Doorbell Sensors. I can get my SmartThings Hub V3 to register that the device is there, but after that it seems to just think it is not present. If I click on it in the UI I just get “Can’t connect to device. Check….”.
Do you still have yours working?
Or have I messed up some part of the setup?
Thanks
Hi Duncan. The Sage doorbell is still working for me. Custom device types such as this one don’t currently show up correctly on the new SmartThings app. If you haven’t tried checking the device operation out on the classic SmartThings app, you might give that a try and see if looks any better there.
Per your suggestion, I have tried the SmartThings Classic application. I just get a “Please Wait” on the device. 🙁
Thanks
When the device was paired with SmartThings, was it correctly identified as the Sage Doorbell sensor? I’m wondering if it didn’t pair successfully for some reason. You can verify that SmartThings used the correct Sage custom device type, by going into the SmartThings IDE “My Devices” tab, selecting the “Sage doorbell sensor” device, EDIT, and then verifying that the type is set to “SAGE Doorbell Sensor”.
You can also try first deleting the Sage from SmartThings and then re-pairing the device after performing a factory reset of the Sage per the user manual: “Remove the plastic cover and the battery.
Press and hold the tiny RESET button (next to where the wires attach to the circuit board) while you reinstall the battery.Continue holding RESET until the red LED blinks. Re-pair the Doorbell Sensor.”
Hopefully something here helps!
No it does not look like it is registering correctly. It just comes up as “Thing”. I even tried a newer battery, which definitely made the LED brighter.
I have a magnet sensor in the post, which I will try out. And I will keep an eye out on ebay for more of the Sage devices.
Thanks for the help.
if you haven’t tried it yet, manually change the device type and see if that helps. In the SmartThings IDE “My Devices” tab, select the Sage doorbell sensor device (sounds like yours will just be labeled ‘Thing’), select EDIT, and then change the type to “SAGE Doorbell Sensor”.
Cross-post from Nexia Doorbell Sensor Review: Disappointingly, EchoStar has discontinued the SAGE product line on September 30, 2016 – shortly after its release. I keep hoping the SAGE Zigbee doorbells would be picked up by another reseller, but to no avail. My SAGE doorbell has performed flawlessly now for months, and I would willing to do what I can to help distribute inventory that might remain or be produced, but it doesn’t appear that they are being made available at this time.
Please let me know if you happen across any SAGE doorbell stock anywhere. I would love to get one since this Nexia device is a POS.
Great review. Was looking for an easy option to turn outside lights on when doorbell was pressed
Any idea where i can buy one ? the Sage website seems to be out of stock on this device
thanks
Unfortunately, SAGE products are only currently available via the SAGE store as far as I can tell. It appears to be a great product, and I’m hoping that Hughes will recognize the potential for significant sales of this device for use with other systems – and increase production as well as add 3rd party distributors. I will update this post if and when I hear of it becoming available elsewhere.