Allow finer grain of motion/smart detection/crossing line zones as exposed to HomeKit?
<!-- FEATURE REQUESTS THAT ARE NOT FILLED OUT COMPLETELY WILL BE CLOSED AUTOMATICALLY WITHOUT WARNING AND WILL NOT RECEIVE A RESPONSE. THE FORM IS HERE FOR A REASON. :). -->
<!-- Please ensure you read the documentation before creating a feature request to ensure the functionality doesn't already exist. -->

**Is your feature request related to a problem? Please describe:**
<!-- A clear and concise description of what the problem is or what use case you would like to see supported. e.g. I'm always frustrated when [...] -->
I have had great success using the contact sensors created with the feature options for detecting vehicles at my gate and opening it automatically if I'm home.  However, I get a fair few false positives (people like to turn around at the bottom of the drive).

Candidly, I'm a tiny bit confused as to which sensors in HomeKit correspond to what in Protect; I appreciate that it's a complex thing to expose and the options are extremely logical but quite involved.  I think part of the issue is also that reconfiguration of the options requires the removal of cached accessories that may no longer be being created but which remain in HomeKit.  

**Describe the solution you'd like:**
<!-- A clear and concise description of what you want to happen. -->
It would be nice to be able to specify a particular zone of smart detection, or use a particular crossing line, to trigger a contact sensor opening.  I'm certain that you've set up the feature options for the most flexible and useful experience, and that there are myriad constraints not obvious unless you understand the API.  As a dumb user, I guess it would be nice to be able to specify, for each camera, which named zone (or crossing line) to expose as a contact sensor.  The protect configuration allows multiple zones per camera, each of which has different smart detections enabled or disabled.  However there is nowhere in the browser console (or app) that actually tells you which of those zones has triggered a detection - it just provides the camera and the type.  Crossing lines are called out distinctly from other smart detections, which is confusing since the two are orthogonal (each crossing line can be configured to be triggered either by vehicle or person, but again the name given to the crossing line itself is not exposed in the UI).

I'm curious to know if the API itself exposes the name of the zone/crossing line that generated the detection, since this would correlate very nicely with a contact sensor device in HomeKit.

My ideal usage scenario would definitely be to have a default motion detector per camera (which picks up the settings precisely as defined in Protect for minimum length of motion etc.), but very selectively additionally create contact sensors based on the name of the specific zone or crossing line (which in turn would automatically determine the type of smart detection to consider as an opening).

**Describe alternatives you've considered:**
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
Removing all but the zones I need to trigger my gate from the camera config in Protect is a perfectly decent workaround.

**Additional context:**
<!-- Add any other context or screenshots about the feature request here. -->

<!-- Click the "Preview" tab before you submit to ensure the formatting is correct. -->
