-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[FR] Detection Short Clip Option for Notification Service #307
Comments
Thanks for describing your use case. I will be looking at post processing for clips in a future release as some other users have requested similar functionality. In addition, the next version will have the ability to do full HD recording from a separate stream, so you won't need to use Blue Iris for that. |
This would be a great feature to have. It looks like HomeAssistant supports MP4s in notifications: https://companion.home-assistant.io/docs/notifications/notification-attachments/ It would be great to include a small clip (maybe 2 seconds before the object is detected) as part of the Events HTTP endpoint that currently provides the object screenshot in the latest beta. On my Nest for example, a very short looped clip is presented in the iOS notification. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is still something I am considering |
Still would love this feature. I do this manually right now and it works ok, but I would think if it would get integrated into Frigate, the clip could be generated much faster, like in real time which would be much nicer and useful, instead of having to wait until the end of a detection event. |
I am looking for something similar and have failed to get it working. I wrote it up in the Home Assistant community (https://community.home-assistant.io/t/frigate-video-via-telegram/286852) but I am not getting any response, so I apologise for putting the same query in 2 different places.
This gives the following errors:
Help would be greatly appreciated. |
@HSB-collab your comment isn't really related to this feature request. Your url is wrong for the notification. Please see the notification docs again. The host should be your homeassistant address, not the frigate address. Please open a new issue rather than replying here if you are not able to resolve it. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I also cannot get the thumbnail from URL: https://kilaku.duckdns.org/api/frigate/notifications/1617859519.848163-9kas2f/floor_1/thumbnail.jpg Error: |
For snapshots and thumbnails, remove the camera name from the path. It would be https://kilaku.duckdns.org/api/frigate/notifications/1617859519.848163-9kas2f/thumbnail.jpg |
* adding face detector * added face detector * feat: added test case for face detector udf * fix: update transformation * feat: added ocr extractor (based on easyocr) * fix: requirements * fix file copying -- ocr makes more sense for mnist * fix: file name * checkpoint * feat: added feature extractor
Would be nice to have an option to output just the first 10 seconds (or definable duration) (plus some prerecord) of video from a detection of an object to send to a notification service.
I think currently we have prerecord option, it looks like you are going to implement a postrecord option, but this is a bit different.
My use case is: currently I have the best image sent to telegram after detection of an object, then I tell Blue Iris to record the event in HD until detection is complete. Then I use ffmpeg to cut the first 10s and optimize for sending over telegram. This works relatively well as I get a short video of the start of each detection over telegram which is much more useful than a static image. However it seems like this could be easily and better implemented in Frigate vs doing it through a Node Red flow and shell commands.
The text was updated successfully, but these errors were encountered: