Yeah, no issues here:
It uses a webhook from Motion eye

The automation is a bit messy, as it originally used to be a blueprint, which I adapted to an automation.
For clarification, the first device is a Android phone, the 2nd device an IOS; they differ a bit as they use a different URL for the message ![]()
alias: Warehouse Notify when camera detects motion
description: ""
trigger:
- platform: webhook
webhook_id: warehouseipc
allowed_methods:
- POST
local_only: true
condition: []
action:
- service: camera.snapshot
entity_id: camera.warehouse
data:
filename: "{{ snapshot_create_file_path }}"
- device_id: 12341234123412341234123412344321
domain: mobile_app
type: notify
title: "{{ notification_title }}"
message: "{{ notification_message }}"
data: >-
{% set android_data = {"image": "%s"} | format(snapshot_access_file_path)
%} {% set ios_data = {"attachment": {"url": "%s", "content_type": "JPEG"}}
| format(snapshot_access_file_path) %} {{ android_data }}
- device_id: 12341234123412341234123412344321
domain: mobile_app
type: notify
title: "{{ notification_title }}"
message: "{{ notification_message }}"
data: >-
{% set android_data = {"image": "%s"} | format(snapshot_access_file_path)
%} {% set ios_data = {"attachment": {"url": "%s", "content_type": "JPEG"}}
| format(snapshot_access_file_path) %} {{ ios_data }}
variables:
notification_title: Warehouse
notification_message: Motion detected in warehouse
delay: 0
snapshot_create_file_path: /config/www/tmp/snapshot_{{ states[camera].object_id }}.jpg
snapshot_access_file_path: "{{ snapshot_create_file_path | replace('/config/www','/local') }}"
oh.it seems i already opted that solution in the link…![]()