I read other users complaining that the default driver didn't work (@steve.maddigan):
What happens is that after the factory reset and the pairing, the first couple of rings were intercepted, then it stopped catching other ring events. I tried removing and inserting the battery from the sensor, but it still didn't work. If I factory reset and pair it again, it does the same thing, it works at the beginning, then it stops working.
What I noticed is that when it stops working these State Variables are shown under the device page. When it works they are not present. Also, I didn't understand what the "Configure" button does there.
I didn’t install the sage doorbell until it was supported with in HE but I had purchased it based on this thread so I knew alternate drivers were out there.
I wasn’t sure if it was my wiring or not. I have a pretty old gear driven four chime door bell and I had to add a cct to pulse stretch the doorbell press so initially I thought it was my fault.
Connecting it directly to the transformer would get it working and by the time I reconnected it to the doorbell it would work once then nothing. I mean how hard can this wiring be?? It’s a doorbell !!
Anyway, tried the other driver and bingo.
Tried the built in driver again, hit config, worked a couple of times and nothing.
Went back to the other drive and we were good to go. I never looked back.
One of my biggest gripes with the internal apps and drivers is you don’t have any visibility. I’m not opening the can of worms again but just saying.
Same reason why I do not use HSM for my leak sensors. It don’t work after being disarmed once so I wrote my own rule to handle them.
Some day I will figure out how to write apps but that hasn’t happened yet.
Thanks for sharing your experience Steve, pretty much similar to mine. I spent 3 days because I thought it was the wiring, but it turned out it was the official driver.
I've used both drivers with no issues with either. I switched to the present Hubitat native driver when it became available to stay with native Hubitat drivers when they are posted. I saw no difference with either driver. I do only have it connected to just one doorbell, my front doorbell and NOT any back. Hope that gives some incite to clearing up any issues.
Did you try changing the "Device preferences" to 5 verses 10? Somewhere I read someone was having multiple ring issues and he change his to 5 ( which I've also done) to correct the problem.
Has anyone been able to get a battery report from the Sage Doorbell sensor. I see drivers with the battery capability remarked out and the built in driver has no battery references.
Thanks for the response. Actually I shouldn't have limited it to battery. What I really need is some periodic "heartbeat" to be sure the device is still there and working.
I don't know if Zigbee has on in its basic report.
Hi - I know I'm not supposed to ask for anything on a beta driver, but just looking for a bit of info.
I set up a sage sensor - works for the front doorbell but not the rear. I'm assuming it's either a bad sensor or something about it being a shorter chime response. The actual chime works for rear doorbell, but sage doesn't pick it up. I'll probably just order another but curious if there's anything about driver that could relate.
Also - what does Enroll Response button do? Is it something I need to do as part of setup?
Thanks! I have it working but only one of the two doorbells is detected. I suspect it's the sensor itself. Will have to swap wires to be sure. But the front one is the one I care about so may not bother!
Please make certain you have selected the device type correctly or else you may not see the two Buttons. Take a look at these photos and make certain to replicate. I am using the OP device type above.
