Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Additional Features #2

Open
liljenstolpe opened this issue May 16, 2020 · 0 comments
Open

Additional Features #2

liljenstolpe opened this issue May 16, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@liljenstolpe
Copy link

Greetings,

I just saw that Noonlight has opened their API. I was playing with it a bit today, and had some thoughts about other things that could be done in this switch:

  1. I see that you already are thinking about deciding what service (fire/le/medical) to post true on based on what sensor(s) have fired. Maybe do it off of a group (i.e. put sensors in dispatchFire, dispatchLE, dispatchMedical groups).

  2. Add person entities to the alarm based on a config entry. That way any household member or your neighbor can turn off the alarm without knowing your pin. Not sure if noonlight calls them all or not.

  3. It would be really interesting to also call the verification API with video or snapshots from cameras asking if there is a person in the image.

I'm thinking of implementing a two-hit / one-hit verified, dispatch, to reduce false alarms:

  1. a sensor gets tripped
    a) notify everyone on the notification list
    b) grab some images and send them for verification with a short (30 sec) timeout
    c) send everyone on the notification list the images
    d) if the verification task comes back as conclusively verified, treat that as a second sensor tripping.
  2. dispatch on two sensor trips
@snicker snicker added the enhancement New feature or request label Jun 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants