Doorbell sensors $1

💬 Lounge
20

Slip of the tongue lolo Gals too !

21

Do these things require a connection to 24V to detect a "button pushed"? Has anyone tried any other way to trigger the Zigbee radio? These could be very useful if there were ways to use them in other ways.

22

These devices are for the very specific use case of a transformer driven doorbell chime. That is, it is looking for 10-24 VAC on the inputs. It isn't likely that there is any other 10-24 VAC devices in your house other than the doorbell chime. I suppose in theory you could find where on the circuit board, this is reduced to binary logic to trigger the radio to send a button press, but other solutions (such as a contact sensor) are not that much more than $5, and are much, much smaller.

2 Likes
23

Thanks.

Thermostats and whole house humidifiers do use 24 VAC but not important here.

1 Like
24

Solenoid valves on water-to-air heat pumps use 12 VAC,

25

Anyone else have an issue with theirs? It pairs fine, but it only registers the first press. Been ringing my doorbell all night with nothing else. I have repaired and same thing happened. Using the driver here https://community.hubitat.com/t/porting-sage-doorbell-sensor-driver-help-needed/20653?

1Push
1Push.png942×396 13.1 KB

26

I just got mine today and installed and was running into same problem. Finally I changed under "Device Preferences" the 10 seconds to 5 seconds. Also for some crazy reason it was not working under notifications so I used Rule machine and used trigger event as Doorbell sensor button 1 pushed and the Action to run was Notify Pushover. Working perfectly now.

ALSO BIG SHOUT OUT to HAL9000 who aimed me in the right direction for the driver.

Tony

2 Likes
27

That should mostly go to @trunzoc .. I was led to the driver by him.

2 Likes
28

Just a heads up.

The driver as posted on github produced duplicate events for me when button 2 (rear) was pressed.

I've already notified the original poster of the driver.

The issue is a difference is the handling of button presses, specifically line 183 (duplicates) and 193 (no duplicates).

My fixed code is below

Mike

switch(buttonNumber) {
    case 0: 
        if (!isDuplicateCall(state.lastButton2Updated, state.timeBetweenPresses) )
        {
	       log.debug ("Rear Doorbell Pressed!")               
           result = [ name: 'button', value: "pushed", data: [buttonNumber: 2], isStateChange: true]
           sendEvent (name: "pushed", value: "2", isStateChange: true) 
        }
        state.lastButton2Updated = new Date().time	
        break

    case 1: 
        if (!isDuplicateCall(state.lastButton1Updated, state.timeBetweenPresses) )
        {		
	       log.debug ("Front Doorbell Pressed!")
           result = [ name: 'button', value: "pushed", data: [buttonNumber: 1], isStateChange: true]
           sendEvent (name: "pushed", value: "1", isStateChange: true) 
        }
        state.lastButton1Updated = new Date().time
}
return result
1 Like
29

Much appreciated. Having just front doorbell, hopefully this wont affect me but it would affect others. Thanks again!

30

Thank you all for posting about this...mine just arrived and is working great. Anyone else seeing battery %? Not showing up on mine for some reason.

@tony3286 , mine is sending push notifications just fine using the built in Notifications app...

48%20PM
Screen Shot 2019-11-21 at 4.39.48 PM.png1546×2152 214 KB

1 Like
31

Could have sworn I created the same notification but thinking back I could have skipped button number.

As far as reporting battery %, I to dont see it either, In fact, I took the battery out to test it and it was fine

1 Like
32

Battery is not reporting on mine either.

I'm also getting this error in the log, anyone else seeing this.

2019-11-21 09:10:49.294 pm [error] groovy.lang.MissingMethodException: No signature of method: user_driver_darwinsden_SAGE_Doorbell_Sensor_794.button1DisplayReset() is applicable for argument types: () values: [] on line 209 (refresh)

Mike

33

Try the driver I posted and you won't see that error. The device always report 0 for battery unfortunately.

34

Can you create a link to your driver. I haven't been able to locate it. I've been using the code Hal9000 pointed me to in this conversation and have received no error codes. Everything has worked perfectly. Much appreciated!

35
36

I did not even know that this type of device existed or I would have gotten one earlier. I have one on order now and will install it once it arrives. Thank you for posting this.

1 Like
37

Post the code fix to the original GitHub link.

38

Can you post your fix to the GitHub original link?

39

Got mine. It's awesome.

I changed up the driver that is floating around to include parameters to store custom names for each contact. This is convenient for logging purposes. Other than that, it's not changed

1 Like