📸 Notification with camera snapshot with blocking condition and clickaction

StanG · July 24, 2023, 5:43pm

I have seen this behavior a couple times myself. But only when there have been multiple notifications sent in somewhat rapid succession. It has nothing to do with paths, that’s a different discussion.

We could change the filename for the image to contain a unique identifier (like datetime) but then we would need to clean-up these photo’s at some point.

It could also just be a race condition, where the photo is not yet overwritten when the notification is send, because the snapshot service takes long to respond. In this last case this could easily be fixed by adding a wait before sending the notification.

I’ll change the template later today.

StanG · July 24, 2023, 5:54pm

I have added a (fixed for now) 2 second delay between creating the snapshot and sending it through notification.
Give that a try.

sirkelsalot · July 25, 2023, 2:07am

Thanks for the prompt reply, Stan. Honestly I’m pretty perplexed by this. The 2 second delay didn’t seem to help (I changed it to 30 seconds also). I also added a 2 second delay per on when to take the snapshot, just to see if I could trace things.

Steps:

manually execute the automation for testing (9:54:54 PM)
through HA File Editor plugin, navigate to /config/www/tmp/ and check the timestamp on the file created (I manually deleted the prior files before the test). verify it is 2 seconds later due to the optional snapshot delay (9:54:56 PM)
check the trace of the automation and verify the new 30 second blueprint delay (I overwrote your 2 second since that didn’t work the first try) is executed (9:54:56 PM)
check the timestamp on when the notification was sent (9:55:26 PM)
check the actual android notificaiton that came in at 9:54:56 PM and observe that the timestamp overlay is Friday at 2:44pm

I really don’t understand where it is pulling that image from. The image literally doesn’t exist in the directory. There have been probably 50+ snapshots since that time on Friday, where could it possibly still pull this one from? It seems to get “stuck” sometimes on various old snapshots. It’s not always 2:44pm Friday, I did get a few Sundays in there. Could it be cached in the app itself somehow?

I did restart HA after making the above changes and before this test. So if something was somehow in memory, I would assume that would have cleared out any 3+ day old snapshots.

maxedmini1 · July 25, 2023, 4:26pm

Yes I got the same problem on iOS with a old snapshot always showing

StanG · July 25, 2023, 8:04pm

Maybe iOS somehow caches the photo because it’s the same filename.
Let’s try with a unique filename.

Can you please try this blueprint. I have not tested it though, let me know how it goes.

gist.github.com

https://gist.github.com/Stan-Gobien/cec44e4217344d8484c856ff1a92e177

CriticalCollapseOptionNotHomeMotionCameraSnapshotWithClickActionUniqueFilename.yaml

blueprint:
  name: Send a notification with camera snapshot when motion is detected with blocking state and URL (or lovelace view) on click, critical or not, collapse or not.
  description: >
    This automation blueprint creates a camera snapshot if motion is detected 
    and sends a notification to your phone with the picture. 
    Optionally you can define a binary sensor that will block the automation from running when state is ON.
    For Example do not run when somebody is home (you can use the people_home template example).
    Furthermore you have the option to make the notification critical or high priority and to collapse/overwrite or not.

This file has been truncated. show original

It should create a file with the datetime stamp at the end.

sirkelsalot · July 26, 2023, 1:55am

FYI, this appears to be working for me now. So based on Maxedmini, it doesn’t appear to be mobile OS specific. I’m running latest Android OS on a Pixel for my testing. I will continue to test it tomorrow and see how it plays out and figure out the cleanup of the old files later.

The most curious thing is that the “old” images it shows are kind of all over the place. Most of the are from Friday, but then I had a few Sunday images in there, and then once or twice it was an actual fresh, new images. That’s the part I don’t quite get is how it’s mostly the same few old images, but it’s not consistent at all. The only thing I can think of is that I’m running on a VM for years now and I know that’s not the preferred installation approach for HA anymore, I just haven’t bother to migrate to docker.

StanG · July 26, 2023, 6:09pm

I’m running a VM with Home Assistant Operating System myself. I think it’s the preferred method next to running Home Assistant Operating System on bare metal.

sirkelsalot · July 26, 2023, 7:45pm

Ya, I could be remembering wrong. I thought I recalled something in recent years about changing the recommended install methods.

Regardless, this does seem to be working well now. For my purposes, I did move the original delay to be ahead of the “condition” check. I did this so I could set the blocking entity state for the “person detected” flag on my reolink camera which is slower to react/update to “on”.

I have two automations now, one triggered by the regular camera motion event, with a 1 second delay, and the condition check to see if a person has been detect. That sends the motion detected notification when there is no person. Then a separate notification triggered by the person detected sensor, with no blocking entity, that can send a different notification for the person.

Next will look at cleaning up old thumbnails.

#condition:
#  - condition: template
#    value_template: >
#      {{ (blocker_entity == none) or (states[blocker_entity].state == 'off') }}
action:
  - delay: "{{ delay }}"

  - condition: template
    value_template: >
      {{ (blocker_entity == none) or (states[blocker_entity].state == 'off') }}

  - service: camera.snapshot
    entity_id: !input camera
    data:
      filename: "{{ snapshot_create_file_path }}"

  - device_id: !input notify_device
    domain: mobile_app
    type: notify

ondrupls · February 5, 2024, 12:55am

Hi, the automation used to work perfectly even when I was connected to an external URL. Now it suddenly stopped sending and image when I am not on local URL. Is there a fix? I went through all the replies and I didnt find any fix

On my iPhone - iOS HA app

StanG · February 5, 2024, 7:29pm

There must be something wrong with your external URL.

Check if you can view the snapshot file in your browser.
The URL is something like below, check with internal URL and external URL.

https://home-assistant-server.domain.tld:8123/local/tmp/snapshot_camera_object_name.jpg

If you have the samba addon, you can use explorer to see the name of the file. It’s in the config/www/tmp folder. You can also use SSH to lookup the name of the file.

ondrupls · February 7, 2024, 6:41pm

thanks for the reply, i appreciate it a lot…

i tried it and it works i tried it on my phone while on my local wifi, on cellular data, and also on my macbook, in all instances it worked fine via the external web adress for my home assistant

https://XXXXXXXXX.XXX/local/tmp/snapshot_192_168_101_33.jpg

StanG · February 8, 2024, 5:09pm

Then I don’t know why it’s not working in the push notification on your iPhone.
Perhaps try a different SmartPhone for testing?