Well, that was frustrating. In my tests last night, I was seeing major issues getting notification from the doorbell sensor. I even went back to a stock Z-Wave sensor for testing - and a good portion of the time, I was seeing missed presses, releases, and sometimes both. I was also getting issues pairing with the fingerprint on the DH - often it would choose the default sensor.
After awhile, things just seemed to settle down and basic presses were working just fine. I can’t say that I ever tested very short button presses before, but with the debug log in place, I did find that very light flicks of the doorbell button did not trigger any kind of notification, even though the doorbell itself would chime. If I pressed the button in what I would consider a somewhat normal manner until it bottomed out, it worked OK. I didn’t try measuring the doorbell contacts with a multimeter, but I’m wondering if the quick presses just aren’t triggering the required 14VAC for the sensor. I imagine the behavior would vary with different buttons, bells, and transformers. I also tried waiting an hour between presses and that worked fine for me - as long as I did a full button press.
I wish there was a way to set the required trigger voltage for this thing either physically on the device or via config parameters, but the very limited documentation I can find doesn’t show any options here.
Anyway, I can possibly understand the issue with the short presses, although I’m not happy about it. If the bell rings, the device should trigger. The general reliability issue on ‘normal’ presses is very bothersome. I was also seeing an odd issue with the new HomeSeer Z-Wave on/off switches last night, so maybe there’s a more of a systemic issue happening there. Suffice is to say I’m a little less pleased with the device and/or its integration this morning.