Error after latest 0.16 dev build #176
Comments
|
here is a example of a event from homeassistant {
"before": {
"id": "1733532391.455171-ntqkc9",
"camera": "driveway",
"frame_time": 1733534054.463705,
"snapshot": {
"frame_time": 1733532403.072841,
"box": [
39,
104,
355,
344
],
"area": 75840,
"region": [
0,
0,
452,
452
],
"score": 0.9921875,
"attributes": [
{
"label": "license_plate",
"score": 0.62109375,
"box": [
40,
294,
68,
322
]
}
]
},
"label": "car",
"sub_label": null,
"top_score": 0.99609375,
"false_positive": false,
"start_time": 1733532391.455171,
"end_time": null,
"score": 0.97265625,
"box": [
41,
103,
358,
343
],
"area": 76080,
"ratio": 1.3208333333333333,
"region": [
0,
9,
428,
437
],
"active": false,
"stationary": true,
"motionless_count": 8308,
"position_changes": 0,
"current_zones": [
"parking"
],
"entered_zones": [
"parking"
],
"has_clip": false,
"has_snapshot": false,
"attributes": {
"license_plate": 0.83984375
},
"current_attributes": [
{
"label": "license_plate",
"score": 0.6796875,
"box": [
49,
298,
69,
318
]
}
],
"pending_loitering": false
},
"after": {
"id": "1733532391.455171-ntqkc9",
"camera": "driveway",
"frame_time": 1733534054.662122,
"snapshot": {
"frame_time": 1733532403.072841,
"box": [
39,
104,
355,
344
],
"area": 75840,
"region": [
0,
0,
452,
452
],
"score": 0.9921875,
"attributes": [
{
"label": "license_plate",
"score": 0.62109375,
"box": [
40,
294,
68,
322
]
}
]
},
"label": "car",
"sub_label": null,
"top_score": 0.99609375,
"false_positive": false,
"start_time": 1733532391.455171,
"end_time": null,
"score": 0.97265625,
"box": [
41,
103,
358,
343
],
"area": 76080,
"ratio": 1.3208333333333333,
"region": [
0,
9,
428,
437
],
"active": false,
"stationary": true,
"motionless_count": 8309,
"position_changes": 0,
"current_zones": [
"parking"
],
"entered_zones": [
"parking"
],
"has_clip": false,
"has_snapshot": false,
"attributes": {
"license_plate": 0.83984375
},
"current_attributes": [],
"pending_loitering": false
},
"type": "update"
}``` |
|
Looks like frigate-notify is getting a 500 error when querying the event info from Frigate. Are you able to manually grab that event from Also, you can enable trace logging to get additional stuff like MQTT messages & HTTP requests/responses. |
|
I'm having it get messages from mqtt? And it's hitting port 5000 so there shouldn't be any auth errors. Will enabled trace and report back |
|
Yeah we'll receive the review message via MQTT - but in order to look up details of the events within the review, we still have to hit the Frigate API. |
|
The frigate connection looks fine gets a 200 return. Waiting for the next review will send the startup trace that shows connectivity to frigate once I can get to my laptop and sanitize it |
|
|
looks like something broke in the dev on frigate with the api updates. |
|
Ahh, okay. Good to know. Yeah then it's probably worth reverting to an earlier build until that's fixed and/or open an issue with them. For what it's worth, I only run & develop against the latest Frigate beta. |
|
Why does it need to make an api call? If it's set to mqtt, can't it just get everything from mqtt? |
|
Frigate reviews are a collection of one or more detections / events. When we get the review MQTT message, it gives us the list of event IDs that are part of the review item. The review MQTT message doesn't contain all the same information as the event messages - so we make an API call at this point to look up some of those additional details from the event IDs in the review. |
|
im reverting to a older commit, but its likley one of these two commits blakeblackshear/frigate@d3b631a i dunno if its a bug or just a change in how the api is handling things, but i figured i would send it over in-case its a intended change and any code change here would be needed. |
what things are you looking for that are not within the mqtt message? i know labels and image urls should be in there |
|
A few that I'm using are |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using your dev build as well that supports reviews. Updated to latest build and notifications stopped having labels in it, turned on debugging and only see this
2024/12/06 19:53:57 -0500 ERR events/reviews.go:51 > Unable to retrieve detection information error=500 detection_id=1733532835.988643-wmuxqn review_id=1733532837.240501-cfxmw9
Is there a way to capture everything to see the mqtt payload in here too?
The text was updated successfully, but these errors were encountered: