[RELEASE] Sage doorbell driver release v2.8.4

iris · September 25, 2022, 1:58pm

Sage doorbell driver fixes problems with internal driver v2.8.4

Totally rewritten driver. Simulated battery using presence detection.
All works no problems reported.

tmastersmart/hubitat-code/blob/main/sage_doorbell_echostar.groovy

/**
 *  SAGE Doorbell Sensor 
    Presence and bat support
    Hubitat driver. 



Adds battery support (simlated) if stops reporting bat goes to 0

White wire:  common
Green wire:  doorbell 1  front
Yellow wire: doorbell 2  rear


If device keeps sending 0000 0006 pings switch to internal driver 
and use config option then switch back.
Help is needed do you know the command to send to stop the reporting above?


 Factory reset:

This file has been truncated. show original

kahn-hubitat · September 25, 2022, 2:27pm

Yep seeing the same thing but have not noticed it as only using button 1.

Ie
@bravenel

steve.maddigan · September 25, 2022, 2:50pm

I am only using the button 1 input as well but I just checked the device events and I am not seeing any events from the second button. Hmmm.

steve.maddigan · September 25, 2022, 2:57pm

Ah, I am not using the built in driver for this device.

I am using this ported version.

kahn-hubitat · September 25, 2022, 10:08pm

@bobbyD

Why no comment? Can we get this also fixed in.next release?

Extra unneeded events every 2 minutes cannot be good for hub load.

mike.maxwell · September 25, 2022, 10:46pm

We are looking into it.

mike.maxwell · September 26, 2022, 2:54pm

can you enable debug logging then post a screen shot of the live logs?

kahn-hubitat · September 26, 2022, 3:01pm

Debugging doesnt show anything extra.

Just button 2 was pushed.

mike.maxwell · September 26, 2022, 3:03pm

yeah, just noticed that.
I've added some logging in the next build so we can see what's going on.

kahn-hubitat · September 26, 2022, 3:10pm

Ran configure. No change.

If you want to send me code to try prior to next build im game.

kahn-hubitat · September 27, 2022, 12:38am

Here u go

mike.maxwell · September 27, 2022, 1:29am

Can you do another?, this time set off button 2 on the device.

kahn-hubitat · September 27, 2022, 2:16am

I cannot set.off button 2 ..button 2 is not.connected to.anything.

I can do.button 1 and post it.

mike.maxwell · September 27, 2022, 2:39am

Ok

kahn-hubitat · September 27, 2022, 3:11am

Ok here it.is

Dont see much except if the data is blank.ignore it. But not.sure why.my and other peoples devices

Seem to be sending bogus presses.

No that wont.work

kahn-hubitat · September 27, 2022, 3:13am

I only rang it.once.

Screwy

kahn-hubitat · September 27, 2022, 3:18am

Data seems to be blank on a real press but not sure why there are multiple. It actually only rang once.

kahn-hubitat · September 27, 2022, 3:26am

It only rang once but hubitat did report.multiple

.

Probably.also.need to.limit.reporting if.they
Come.in.to.fast.

kahn-hubitat · September 27, 2022, 3:32am

Zigbee routes

iris · September 27, 2022, 4:25am

OK here is what im seeing after I started dumping the raw data.

Its sending cluster 0006 data and the driver is reading it as button 2 press....

[raw:catchall: 0000 0006 00 00 0040 00 F7F6 00 00 0000 00 00 F30000040101190000, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:F7F6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[F3, 00, 00, 04, 01, 01, 19, 00, 00]]

A valid door 2 press gives this
[raw:catchall: 0104 0006 12 01 0040 00 F7F6 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:12, destinationEndpoint:01, options:0040, messageType:00, dni:F7F6, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

Its reading both as a button 2 press

Weird thing is this didn't happen until hrs after the update. And on my other hub 24 hrs after the update.