Serve up previous best_person images too. about frigate

[miikkajo]

Added, tested, fixed... should be working now ;)

[miikkajo]

i created new repo for this example
for simplicity it's in package format

https://github.com/miikkajo/frigate-history

edit: i got swiper card working too and i'm loving it :)

[wills106]

Thanks a lot @miikkajo for the examples. I have 3 cameras running at the moment.
Is the setup something that could be templated? To save on copy and paste with a few changes.
It would be easier to expand in the future that way.
I just can't quite get my head round templating yet :(

My config is:
https://github.com/wills106/homeassistant-config/blob/master/packages/frigate.yaml

[miikkajo]

sorry, i'm been pretty busy latelty...
i actually moved to using addon myself,
i try to document it as soon as i got time for it.

here is project for it
https://github.com/miikkajo/ha-addon_frigate-history

you can add my addon repository to hassio, https://github.com/miikkajo/hassio_addons

of course if you are not using hassio, it does not help much...
as for order of cards, i remember i have seen something like that,
not sure what is causing it...

[miikkajo]

how about doing this on hass side?
you could create automation for saving snapshot images to disk
i'm currently pushing images to telegram on detection so i have history there

but i'm liking this swiper card idea, it should not be too hard to do :)

[scstraus]

I haven't upgraded to the new MQTT image push yet, and don't know how this would be done, to keep only a certain amount of images and expose to the UI but if you know how to do this, please share :-). I can imagine how to do it with multiple cameras, but I bet there are many ways to skin this cat.

[scstraus]

Nicely done! Time for me to upgrade!

[miikkajo]

just moved images out of /tmp/ to /config/www , /tmp/ is stupid place to keep them, as you lose them :)
i'm actually not using mqtt images for this, but surely one can do it

[scstraus]

Does anyone know how this would work with MQTT? I'm thinking to try jumping to the new version as it looks like my sensors are triggering at very low thresholds for some reason, I'm hoping MQTT solves this, but would also like to know how to do this "look back" with MQTT images.. I don't have any idea how MQTT handles images..

[miikkajo]

i'll update example to use MQTT images

[scstraus]

Wow you're on top of things!! Thanks!

[miikkajo]

i just realized that my approach with MQTT trigger with camera topic just wont work,
as image is persistent message, on hass restart automation will trigger on it
and fill history with old image

but i would really like to use mqtt image, as it's been selected for best person image :)
it just select first on motion, likely it wont be the best one.

i need to clear retained message on automation after it's been prosessed

@wills106: i did take different approach on configuration
/packages/
frigate_cam1_history.yaml
frigate_cam2_history.yaml
frigate_cam3_history.yaml

i have file for each camera, it's easy to just search & replace cam1 -> cam2

this whole automation with camera snapshots is just silly hack,
i just hoped it would be easier to configure as yaml package than custom_component.

but it's process of fail and success that may lead to something usefull :)

[miikkajo]

ok, i took another take on this.
moved fifo logic from automation to bash script, added check for duplicates and size of history
no need to script_component and automation is simpler now

config is now for 2 cameras and history_size is 10 frames.

what is bugging me is using local_image camera entities,
i tried to use directly lovelace picture entity, but as /local is cached
i did not manage to get updated images...

[miikkajo]

i was thinking of custom_component but this last version is working so fine that
i'm going to just use it for now :)
10 frames of history is great, seems to be enough for quick view of past detections.

[scstraus]

Hi @miikkajo, I finally got up on the MQTT version and was thinking to try this. In the repo, you reference the file frigate_history_mqtt.yaml, but I can't find it in the repo. Is frigate_history.yaml working with the MQTT version?

[scstraus]

Finally got it working.. Strange though, it seems to randomly reverse the order of the cards so that sometimes it starts with the tenth from the last instead of last.. Did you ever have that issue?

[niemyjski]

@miikkajo your fork is now out of date, I got write access to the parent and merged in a ton of changes, e.g., please use the parent one

[JonGilmore]

@miikkajo is your addon still working for the 0.8.0 release?

[miikkajo]

well, it should, it only listens for mqtt snapshot message and dumps snapshot images to disk.
personally i'm using clips and events from 0.8.x release, and i'm pretty pleased with it

[stale]

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.