-
-
Notifications
You must be signed in to change notification settings - Fork 95
Crashing Deepstack Processing? #169
Comments
Well it does sound like something odd is going on either accessing the images or with the actual images themselves. Please put logger in debug mode and try find some relevant error messages |
I had a go at getting logs with debug, but all I'm getting is:
Should I be looking somewhere else? My HA config is:
And in Docker I get this, with the first one being from AI Tool with a test image, the second an attempt via HA using a camera.
|
It is a timeout error, increase to 30 seconds, but if that doesn't solve it I am out of ideas and we should take this issue to the Deepstack repo |
Just tried 30 seconds, same thing, looks like it might work if I set it to 10 minutes. Thanks, I'll have a look at raising it over there tomorrow, do you know if there's any debug logging I can look for on the Deepstack side of things? |
Playing around with this a little further, I have tried pointing different cameras at Deepstack and it's still taking 4-10 minutes to process them. I even tried setting up Deepstack on another device and am getting the same problem. Are the images cached from the Home Assistant side of things? Just wondering if it's trying to send a corrupt image file or something like that which I can clear. |
We need to determine if this is related to the HA integration or Deepstack. Can you pull some images from your camera and see if you can reproduce the issue just directly posting the images using curl? |
Just tried that using some images downloaded using the camera.snapshot service (from the same camera). They process fine (250ms). Setting that same image as a Local File camera in Home Assistant and running the image processing on it is back to 5+ minutes. |
My guess is it's a periodically corrupted image. Saving using snapshot might be transforming it. Another guess is there is something funny about the way you are triggering the scan. Can you share config and the image? |
We have an issue on Deepstack repo to create a logger so we can see all images and responses etc, but it is not started yet. I might begin with this soon. It looks like a good quality, high resolution image. Another guess is that the large size of the image might be overloading Deepstack somehow. I think you can use the proxy camera to downsize it, so that is worth a try. Also can you try posting the full high res image via curl? |
I just noticed you set confidence 0, and remember there is a Deepstack bug for that value. Please increase it and try again |
Thank you! Just changed from 0 to 1 and it's working! Weird... I hadn't changed that part of the config in ages and was using 0 in AI Tool too. |
The Deepstack-python dependency changed its bahaviour, as previously only confidences above 0.45 were allowed, all though this was not clear |
A bit of a weird one, I've broken my previously working setup, and haven't been able to get it working again.
I've gone from 200ms processing, to pretty much timing out, Docker console seems to indicate things are taking between 5 and 15 minutes to process (but not sure it's actually doing anything at that point). I am also getting the same issue using the AI tool talking to Deepstack separately (see below).
The biggest thing I did was change the snapshot path to instead be a mounted share from my NAS, that side of things seems to work for everything else (can access via HA media browser and camera entities), but suspect it's causing issues with this integration.
I did also update to the latest version of this integration and the 2021.1.0b0 HA version recently, but I 'think' it was working briefly after that, although not 100%.
So I tried reverting things to use the old home assistant file locations under config, didn't help, deleted the Deepstack Docker container and recreated, no change. But what I did notice, is if I delete the Docker container and recreate it, and use the AI tool before HA tries, I'm back to 200ms processing and that works continuously, UNTIL I run a request from HA, in which both AI Tool and HA aren't able to have anything processed until I restart the Docker container.
That's where I'm up to, any ideas?
The text was updated successfully, but these errors were encountered: