You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The {cam_name} format isn't being parsed when sending a motion webhook. I'm seeing this in the logs for motion events:
[WyzeBridge] [MOTION] Motion detected on porch at 17:04:35
[WEBHOOKS] 500 Server Error: Internal Server Error for url: http://localhost:8555/motion?%7Bcam_name%7D
[WyzeBridge] ☁️ Pulling "porch" thumbnail to /img/porch.jpg
Back in 2.8.3, get_http_webhooks(url.format(cam_name=uri, img=str(img)), msg, img) handled the cam_name format. In 2.9.x+ there doesn't appear to be a url.format(cam_name=...) call anywhere so this is going unhandled.
adding url = url.format(cam_name=camera, img=str(img)) to webhooks.send_webhook seems to fix it, but that might not be the optimal solution.
The formatting of the {cam_name} and {img} tokens in webhooks URLs worked in 2.8.x but has not worked in newer versions. See mrlt8#1378
This patch adds formatting of those tokens in send_webhooks
traviswparker
added a commit
to traviswparker/docker-wyze-bridge
that referenced
this issue
Oct 31, 2024
Describe the bug
The {cam_name} format isn't being parsed when sending a motion webhook. I'm seeing this in the logs for motion events:
Back in 2.8.3,
get_http_webhooks(url.format(cam_name=uri, img=str(img)), msg, img)
handled the cam_name format. In 2.9.x+ there doesn't appear to be a url.format(cam_name=...) call anywhere so this is going unhandled.adding
url = url.format(cam_name=camera, img=str(img))
to webhooks.send_webhook seems to fix it, but that might not be the optimal solution.Affected Bridge Version
2.9.x to main
Bridge type
Docker Run/Compose
Affected Camera(s)
all
Affected Camera Firmware
all
docker-compose or config (if applicable)
The text was updated successfully, but these errors were encountered: