-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
[FEAT] Add Total Count for Matches, Misses and Unknown To MQTT Payload #223
Comments
Hey @DevTodd, sorry for the delay in responding to this. I should have a new beta build with this added within the next day or two. I refactored a bit during the process so it took a little longer than I wanted. Thank you for the suggestion and the sponsorship. It really means a lot to me! |
## [1.13.0-beta.4](v1.13.0-beta.3...v1.13.0-beta.4) (2022-10-21) ### Features * **mqtt & api:** total count for person, match, miss, and unknown ([#223](#223)) ([2bf4406](2bf4406))
I pushed a beta build to include this feature. I removed the Let me know what you think! {
"id": "ff894ff3-2215-4cea-befa-43fe00898b65",
"duration": 4.25,
"timestamp": "2021-06-17T03:19:55.695Z",
"attempts": 5,
"camera": "back-door",
"zones": [],
"matches": [
{
"name": "david",
"confidence": 100,
"match": true,
"box": { "top": 286, "left": 744, "width": 319, "height": 397 },
"type": "manual",
"duration": 0.8,
"detector": "compreface",
"filename": "dcb772de-d8e8-4074-9bce-15dbba5955c5.jpg",
"base64": null
}
],
"misses": [],
"unknowns": [],
"counts": { "person": 1, "match": 1, "miss": 0, "unknown": 0 }
} |
Thank you for taking the time to do this. It breaks a lot of my automations since I was previously using personCount as it was the only option available that I could use to determine if more than one person was detected. I'm working 18 hour days lately due to some new secops regulations so when I have time I will test. Again, thank you for the work and consideration of my request. |
I will add it back for now as backwards compatibility and make a note that I will remove it in a future release. I don't want to break any of your automations. No rush on testing, sorry to hear about the long days at work! I've been using it over the past day around the house and it seems to be working well, I will probably create a release tonight. Feel free to message me on Discord if you run into any issues and I'll get it fixed right away. |
## [1.13.0](v1.12.1...v1.13.0) (2022-10-21) ### Features * frigate matches below an area target ([3365bc7](3365bc7)) * **mqtt & api:** total count for person, match, miss, and unknown ([#223](#223)) ([2bf4406](2bf4406)) * support for MQTT TLS ([#241](#241)) ([7f37b78](7f37b78)) ### Bug Fixes * remove non alphanumeric characters from MQTT topic names ([#239](#239)) ([885d8a1](885d8a1))
Closing this since |
## [1.13.0](v1.12.1...v1.13.0) (2022-10-21) ### Features * frigate matches below an area target ([3365bc7](3365bc7)) * **mqtt & api:** total count for person, match, miss, and unknown ([#223](#223)) ([2bf4406](2bf4406)) * support for MQTT TLS ([#241](#241)) ([7f37b78](7f37b78)) ### Bug Fixes * remove non alphanumeric characters from MQTT topic names ([#239](#239)) ([885d8a1](885d8a1))
Describe the solution you'd like
For the MQTT Payload published to sensor/double-take/camera name/state it would be nice to get
matchCount
missCount
unknownCount
in addition to the already present
personCount
Thanks!
The text was updated successfully, but these errors were encountered: