@Wayne-TP 

Let's say that we accept the risks, as end users and owners of the hardware and data. Is there really no opening tot reach out to a community?

If it is a matter of liability i'm sure your lawyers will be Able to concoct a twelve page waiver to agree to. I think most of the community would gladly accept it to increase the use and hence value of the device and it's features.

  @Kyomity Agree, I need button press to be exposed so I can do stuff with it in home assistant. Huge limitation to one of the most important features of the device.

  @John21 The only -insane- solution right now is to train AI to detect visually when someone rings the bell. Absolute craziness.

I can get behind a lot of BS. But hiding behind the guise of privacy is laughable, as I've already said; the moving images and motion alerts are freely accessible by anyone with the password. But WHOA if you're asking for a shared button press event...

The only way I can see is that there is some kind of patent, or some kind of corporate bull-excrement holding this back? Maybe they want to force us in to working with their app? And the only way I can see some incentive for them to do that is, ironically, to breach our privacy and collect more data about us?
Money from hardware sales is good, at most. Revenue from collecting data to train AI, predict human behavior and future sales, is priceless...

I might have my conspiracy glasses on right now, and I'd love to know if I'm wrong. But I'm guessing there will be no response from any official here because I might just, maybe, be a little bit right?

  @Wayne-TP This is not a matter of exposing the TP Link API, more a question of exposing doorbell pressed events via ONVIF. That is a request that comes with zero privacy concerns that you have not already addressed as it requires the user to create a local camera account and accept the terms and conditions associated with setting up a local camera account. All of which is handled locally within the user's own network. This is something offered by both Reolink and Amcrest, and numerous others.

I'm a little fed up with how generally buggy my D235 is, RTSP is apparently fully supported yet the stream constantly fails. The doorbell seems to have a mind of it's own and the latest bug is that it couldn't cope with daylight savings and has in fact started to change the time on its own.

I bought this doorbell to free myself of the Ring subscription trap, but even Amazon are more liberal with exposing basic events from their cameras.

Seriously considering selling and buying a Reolink PoE doorbell instead.