Environment
- Home Assistant Core: 2026.8.2 (Supervised, Raspberry Pi 4, aarch64)
- ring-doorbell: 0.9.14
- firebase-messaging: 0.4.5
Describe the problem
I have a Ring "Peephole / Door View Cam" — a physical device I've owned for 4+ years, not new hardware — that now returns kind: stickup_cam_mini_v3. This value doesn't appear in const.py's kind lists (INDOOR_CAM_KINDS, INDOOR_CAM_GEN2_KINDS, INDOOR_CAM_PTZ_KINDS, STICKUP_CAM_KINDS, etc.).
The diagnostics created_at timestamp (2026-06-25) is recent, but the physical camera itself is not — this timestamp likely reflects a re-pairing or backend reclassification event on Ring's side (possibly a firmware update changing the reported kind string), rather than new hardware. This may mean Ring has started reporting a different kind value for existing camera models, not just released a genuinely new product line.
This looks related to #484 (stickup_cam_mini_ptz_v1), which showed the same "Unknown kind" pattern, though the underlying cause here may be different (existing hardware reclassified vs. genuinely new hardware).
Steps to reproduce
- Own a Ring Peephole / Door View Cam (reports
kind: stickup_cam_mini_v3)
- Set the device up in Home Assistant via the Ring integration
- Observe repeated log entries:
ERROR (MainThread) [ring_doorbell.stickup_cam] Unknown kind: stickup_cam_mini_v3
Expected behavior
The device should be recognized under its correct family without the "Unknown kind" error.
Diagnostics
Relevant device entry from Home Assistant's Ring diagnostics export (personal identifiers redacted by HA's own export tool):
{
"kind": "stickup_cam_mini_v3",
"created_at": "2026-06-25T09:43:56Z",
"device_resource_id": "rduri:dr.prod:0:device.ring|730638642",
"schema_id": "8afb992c2685fe991df449bb1dbfdaa73b2019ad32abd1fb33d8839deed82cea",
"camera_location_indoor": true,
"facing_window": false,
"is_sidewalk_gateway": false,
"battery_life": 100
}(Ring's own app labels this device model "Peephole / Door View Cam.")
Environment
Describe the problem
I have a Ring "Peephole / Door View Cam" — a physical device I've owned for 4+ years, not new hardware — that now returns
kind: stickup_cam_mini_v3. This value doesn't appear inconst.py's kind lists (INDOOR_CAM_KINDS,INDOOR_CAM_GEN2_KINDS,INDOOR_CAM_PTZ_KINDS,STICKUP_CAM_KINDS, etc.).The diagnostics
created_attimestamp (2026-06-25) is recent, but the physical camera itself is not — this timestamp likely reflects a re-pairing or backend reclassification event on Ring's side (possibly a firmware update changing the reportedkindstring), rather than new hardware. This may mean Ring has started reporting a differentkindvalue for existing camera models, not just released a genuinely new product line.This looks related to #484 (
stickup_cam_mini_ptz_v1), which showed the same "Unknown kind" pattern, though the underlying cause here may be different (existing hardware reclassified vs. genuinely new hardware).Steps to reproduce
kind: stickup_cam_mini_v3)ERROR (MainThread) [ring_doorbell.stickup_cam] Unknown kind: stickup_cam_mini_v3Expected behavior
The device should be recognized under its correct family without the "Unknown kind" error.
Diagnostics
Relevant device entry from Home Assistant's Ring diagnostics export (personal identifiers redacted by HA's own export tool):
{ "kind": "stickup_cam_mini_v3", "created_at": "2026-06-25T09:43:56Z", "device_resource_id": "rduri:dr.prod:0:device.ring|730638642", "schema_id": "8afb992c2685fe991df449bb1dbfdaa73b2019ad32abd1fb33d8839deed82cea", "camera_location_indoor": true, "facing_window": false, "is_sidewalk_gateway": false, "battery_life": 100 }(Ring's own app labels this device model "Peephole / Door View Cam.")