Give users an option to create binary sensors instead of only using device events

Since version 1.x.x of Home Assistant, some integrations are using ‘device events’ instead of creating binary sensors for motion,sound,person detected etc.

“We should not show motion events as binary sensors. Instead, they should be fired as events of type nest_event and the pubsub → HA events logic should be instantiated from async_setup_entry in init.py, it should not be tied to an entity.”
Add nest SDM API camera/doorbell events by allenporter · Pull Request #42700 · home-assistant/core · GitHub

Great for people that make use of the automations inside Home Assistant, but not so great for people that are using node-RED for example. Do I really need to listen to events instead of using a simple binary sensor?!
Now i need to create an automation in Home Assistant, edit the automation in YAML in order to get the device id and what events are supported? Or do i need to wave in front of the camera, press buttons and run by while i’m listening to events in the ‘event’ option?

  - platform: device
    device_id: c085bc6c168c11ebb4ce47b3ea4f092c
    domain: nest
    type: camera_person

Please add an option in the integration page to create binary sensors, or make it more simpler to use these events outside Home Assistant.