[Support]: frigate/<camera_name>/<object_name>/snapshot MQTT trigger payload decoding error #14462
-
Describe the problem you are havingThe events published on frigate/<camera_name>/<object_name>/snapshot can't be used as MQTT trigger on automations, causing a Automation yaml:
Frigate: v5.4.0 Versionv5.4.0 What browser(s) are you using?Google Chrome 126.0.6478.185 Frigate config filecameras:
doorbell:
enabled: true
ffmpeg:
inputs:
- path: rtsp://admin:[email protected]/Preview_01_sub
roles:
- detect
- record
detect:
enabled: true
width: 640
height: 480
fps: 5
objects:
track:
- person Relevant Frigate log output2024-10-20 17:10:40.538 WARNING (MainThread) [homeassistant.components.mqtt.client] Can't decode payload
b'\xff\xd8\xff\xe0\x00\x10JFIF\x00\x01\x01\x00\x00\x01\x00\x01\x00\x00\xff
...(many lines of binary data output)
on frigate/doorbell/person/snapshot with encoding utf-8 (for <Job None HassJobType.Callback <function async_attach_trigger.<locals>.mqtt_automation_listener at 0x7f4546de40>>) Relevant go2rtc log outputn/a FFprobe output from your cameran/a Frigate statsn/a Install methodHassOS Addon docker-compose file or Docker CLI commandn/a Object DetectorCoral Network connectionWired Camera make and modelDahua (IMOU) Screenshots of the Frigate UI's System metrics pagesNo response Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Answered by
hawkeye217
Oct 20, 2024
Replies: 1 comment 2 replies
-
The MQTT payload is base64 image data, so you'd need to use a
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes, because what's being sent on the
/snapshot
topic is binary image data.You should trigger based on the
/events
or/reviews
topic instead. See the docs.