3
Nest camera.snapshot returns placeholder image instead of real frame for WebRTC-only devices
Source: home-assistant/core#176807 · opened by @johnmhedge
The problem For Nest cameras/doorbells whose CameraLiveStream trait reports supportedProtocols: ["WEB_RTC"] only (i.e. devices migrated to the Google Home app, no RTSP support), any request for a still frame — via camera.snapshot, /api/camera_proxy/<entity>, or /api/camera_proxy_stream/<entity> — returns a static placeholder image, not a real frame from the camera. This fails silently: • HTTP status is 200 OK • Content-Type header says image/jpeg • The entity state is idle/streaming (not unavailable), so nothing looks wrong at a glance • The response is always the exact same byte size regardless of what the camera is actually pointed at, or what time of day it is Inspecting the actual response bytes shows it isn't a JPEG at all — it's a PNG (\x89PNG\r\n\x1a\n magic number) mislabeled with a Content-Type: image/jpeg header. This looks like a generic "no signal"/placeholder graphic being returned instead of a real deco…
No pledges yet. Be the first to back this.
Comments
Similar requests
[BUG] RING Last_Recording entity not created for Doorbell 2K or 4K cameras (tested multiple, with Protect subscription)
0 votes · 0 comments
Mill integration, not exposing Mill Heatpump
0 votes · 0 comments
USL-GlassBreak only shows motion
0 votes · 0 comments
Unifi Protect USL Environmental Moisture sensor marked as unavailable
2 votes · 0 comments
Uploading backup TAR archive not possible when file is above 16MB - 'Maximum request body size 16777216 exceeded.'
0 votes · 0 comments
No comments yet.