Please stick with the one I linked directly
Okay. I upgraded, but I will overwrite the file again.
By the way, did the naming change of the files saved?
It adds the name value in front of the deepstack_latest_object / car whatever is chosen.
I might have missed it somewhere, but I just want to make sure I didnāt screw anything up here.
Will get back to you when tested.
I donāt know what version you were on before. All changes are in release notes.
However I am beginning to suspect this is not an issue with the deepstack integration but actually from the camera
I try to be on the latest release at all times. Now I run the latest with your modified file you provided me with.
I added the time stamped feature and I do see the files coming in just fine. Every single one of them is ādifferentā.
When I monitor the cameras in āreal timeā I see the exact same thing being snapped and saved as a deepstack file.
I donāt see how this could be a camera problem?
Iāve added a lot of delay, so when the image_processing feature is fired, itās more than 10 seconds after the latest processing.
I need to test it fully today and get back to you.
I am using Blink cameras, and sometimes the updated image is actually still the last image
Arh okay!
Hmm, but when you say updated. Are you then referring to the image saved in the library?
IE the same image is being processed at 2 different times. I am saving all images so can review the history and see that is the case
Hey Rob,
Maybe this is just a coincidence, but for the last two days I havenāt got a notification with the same picture.
Not even when triggering all 4 cameras at the same time, running around the house like a mad man
So something seems to have been improved?
OK well sounds like the changes I made in that file have worked
@robmarkcole using the latest and works fine as well. Small note for your consideration in future changes. You changed the timestamp in the .py like so ā%Y-%m-%d %H:%M:%Sā leaving a gap between date and time.
This provides an incomplete link and some messanger services (Gotify) cant complete and the picture doesnt pull through.
In your future release please add it back if possible.
Thank you.
Done, thank you very much
I really like deepstack, @robmarkcole thanks for the component!
I just want to ask if there is a way to reduce CPU usage in any way: i have a vps and a local nuc without avx and 3 of 4 /app/intelligence.py processes are always using between 8 to 15% CPU.
Other than this i find deepstack very strong as an object detection.
Iām a bit OT but: i wish @robmarkcole could port to HA Azure vision intelligence ( not face ) as another object detection service, since there is a free tier
Hi,
For some reason I no longer seem to get anything fired on the event bus under image_processing.file_saved when deepstack runs. I do get a file createdā¦ This happened after one of the latest upgrades. Anyone else see this?
Figured it out. Without the new(?) āsave_timestamped_file: Trueā nothing fires on image_processing.file_saved. I mistakenly thought the overwrite of the last file would suffice.
Thanks man! Your hard work is much appreciated!!!
Is there any reason behind this suggestion, e.g. you have experience with it or it has some unique functionality? Iāve also published custom components for google vision and AWS rekognition, also have a PR open adding sighthound
well, i tried a bit azure intelligence and for my test cases itās really really good.
Beside that, google vision has 1000 calls while azure raise up to 5000, like sighthound, but i donāt find the last one ( sighthound ) reliable ( often sent me message for a person while it was an hangerā¦ ).
I didnāt tested rekognition BTW, apart from the tier that is not so great and i didnāt found if the picture frame is saved or not after detection.
Since you are the object detection master of HA, i just gave you an hint
Hey Rob, I was too fast. I updated the Deepstack integration a few hours ago and now I see the same images being firesd again.
Should I try copying the image_processing file from your previously mentioned post into the library again?
Those changes are merged into the latest release. If this issue still persists then I think it is an issue with the camera