You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, I just added Compreface to my setup. I think DS has been doing this the entire time but I am not sure.
I am using HAOS Generic x86 on an older HP Min w/i7 along with Frigate, Double-Take, MQTT, and Deepstack.
I have tried DS CPU also, but after 4 or so image register calls it starts to 500 and won't respond anymore until restarted.
It would stop responding at times previous to adding Compreface. Maybe I just noticed now, but in the UI deepstack is red for these images vs compreface being all green. (list at bottom in log)
Clicking Sync in Double Take, I can watch as the progress bar goes across when it starts failing. Takes exactly 15 seconds to move on, then it quickly reads one, then 15 seconds again and it see-saws between compreface and DS.
So, I just added Compreface to my setup. I think DS has been doing this the entire time but I am not sure.
I am using HAOS Generic x86 on an older HP Min w/i7 along with Frigate, Double-Take, MQTT, and Deepstack.
I have tried DS CPU also, but after 4 or so image register calls it starts to 500 and won't respond anymore until restarted.
It would stop responding at times previous to adding Compreface. Maybe I just noticed now, but in the UI deepstack is red for these images vs compreface being all green. (list at bottom in log)
Clicking Sync in Double Take, I can watch as the progress bar goes across when it starts failing. Takes exactly 15 seconds to move on, then it quickly reads one, then 15 seconds again and it see-saws between compreface and DS.
Here's part of the double take config:
detectors:
deepstack:
url: "http://192.168.134.250:5001"
key: ""
opencv_face_required: true
compreface:
url: "http://192.168.134.250:8000"
key: "KEY"
confidence: 75 # Confidence threshold for recognition
save_unknown: true # Optional: Save unrecognized faces for later review
save_matches: true # Save recognized faces
And here's the logs in Deepstack: (you can see the response time getting longer until the 500s start)
1/restore
[GIN] 2024/12/04 - 12:52:11 | 200 | 16.739199ms | 172.30.32.1 | POST "/v1/vision/face/delete"
[GIN] 2024/12/04 - 12:52:13 | 200 | 851.071821ms | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:52:16 | 200 | 966.53666ms | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:52:20 | 200 | 1.317585424s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:53:23 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:53:39 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:53:57 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:54:13 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:54:30 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:54:46 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:55:03 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:55:19 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:55:35 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:55:51 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:56:07 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
[GIN] 2024/12/04 - 12:56:23 | 500 | 1m0s | 172.30.32.1 | POST "/v1/vision/face/register"
The text was updated successfully, but these errors were encountered: