Triggering the image_processing.scan service does not always update in home assistant

[blackgold9]

Im running into the issue where triggering a scan does not always update the hass state, or save a new image to the specified folder. Sometimes it works, sometimes it doesn't, without any pattern i've been able to spot.

I have deepstack object 3.1 configured talking to deepstack running on linux like so:

image_processing:
  - platform: deepstack_object
    ip_address: <IP Address>
    port: 5000
    api_key: !secret deepstack_key
    save_file_folder: /config/snapshots/
    # save_timestamped_file: True
    # roi_x_min: 0.35
    # roi_x_max: 0.8
    #roi_y_min: 0.4
    # roi_y_max: 0.8
    targets:
      - person
    source:
      - entity_id: camera.loft

I've noticed in the debug logs the webhook being called with data at the right timestamp, but then it appears to reference the timestamp of the old state in home assitant, and when i check the UI the state in the UI is still from the old timestamp in the log line.

[robmarkcole]

please increase the timeout in config, sometimes deepstack is slow, particularly on first processing. This is not an issue with the code so closing, thanks

[blackgold9]

I upped my timeout to 30 seconds and still not getting results. Expected?

…

On Mon, May 18, 2020, 11:39 PM Robin ***@***.***> wrote: Closed #124 <#124>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABUILMRPKZ4JSNYMV5XIN3RSISTJANCNFSM4NDGMSZQ> .

[blackgold9]

These logs show results coming back in a second or so:
https://pastebin.com/yC2Z1w4U

Yet I don't see the latest snapshot image updated on the filesystem, nor the actual readings updated. So, to me it looks like something other than timeout. Misconfiguration?

[blackgold9]

I have 2 camera set up for processing (2 separate deepstack_object entitites). One of them updates most of the time, and saves a timestamped file. The latest file often doesn't update even when a new timestamp file is written. The other entity almost never writes any images or updates.

[robmarkcole]

My guess is that the images may be corrupted somehow. Unless we can reproduce this reliably we are just guessing

[blackgold9]

Yeah. I got the GPU version of deepstack going, and now the results update relatively quickly, but the files only sometimes do.

…

On Mon, May 25, 2020 at 11:39 AM Robin ***@***.***> wrote: My guess is that the images may be corrupted somehow. Unless we can reproduce this reliably we are just guessing — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABUILMDOALMZQGDUPBEGRLRTK3N5ANCNFSM4NDGMSZQ> .

[fgonza2]

i see the same issue on 0.155.3