Error 404 setting sublabel

[dmnscn]

Hi team, all is working without problem but i can't get working the sublabel insert:

2024-05-08 05:52:03,330 - main - INFO - Recognised plate is a Watched Plate: XXXX
2024-05-08 05:52:03,330 - main - INFO - Storing plate number in database: XXXX with score: 0.852
2024-05-08 05:52:03,355 - main - ERROR - Failed to set sublabel. Status code: 404

some special config to add to frigate conf for sublabel set?

[ljmerza]

whats your config

[mrlindstrom]

I'm getting this as well, but I am also on the new beta3 so I'm curious if they changed something about sublabels in this version that will need to be taken into account.

[mrlindstrom]

I'm getting this as well, but I am also on the new beta3 so I'm curious if they changed something about sublabels in this version that will need to be taken into account.

Actually scratch that, it looks like I only saw one 404, but it says the other sublabels were set successfully. Now to just figure out how to see them in this beta...

2024-06-19 10:17:06,959 - __main__ - INFO - Storing plate number in database: KZN 5302 with score: 0.9811196327209473 2024-06-19 10:17:06,979 - __main__ - ERROR - Failed to set sublabel. Status code: 404 2024-06-19 10:17:26,269 - __main__ - INFO - Storing plate number in database: PYN 4842 with score: 0.8880830407142639 2024-06-19 10:17:26,283 - __main__ - INFO - Sublabel set successfully to: PYN 4842 with 88.8% confidence 2024-06-19 10:18:01,051 - __main__ - INFO - Storing plate number in database: LXT 3255 with score: 0.9847781658172607 2024-06-19 10:18:01,066 - __main__ - INFO - Sublabel set successfully to: LXT 3255 with 98.5% confidence

[yannpub]

Having the same issue here. Plate is recognised, but when it goes to add the sublabel, I get the 404 error.
Running Frigate beta4 as an HA addon.

Edit: For some unknown reasons, sometimes it works, but I get the 404 more often than proper results.

[ljmerza]

Looking at the docs for the latest beta, it doesnt look like this API has changed so it may be beta issue on frigate. now that i think about it, it may be a race condition where the event has been set to mqtt and picked up by this app but hasnt been saved to frigate's db yet

[kyle4269]

Looking at the docs for the latest beta, it doesnt look like this API has changed so it may be beta issue on frigate. now that i think about it, it may be a race condition where the event has been set to mqtt and picked up by this app but hasnt been saved to frigate's db yet

That's what I found also, the event isn't saved in frigate db yet.