Describe the bug
On startup, the Ring integration logs repeated errors for one of my devices:
ERROR (MainThread) [ring_doorbell.stickup_cam] Unknown kind: cocoa_camera_v2
This fires 7 times per Home Assistant restart. Checked ring_doorbell/const.py on master and the closest match is STICKUP_CAM_GEN3_KINDS = ["cocoa_camera"] — there is no cocoa_camera_v2 entry anywhere in the file, so this kind isn't mapped to any device class.
EDIT: I previously misattributed this to a Ring Video Doorbell Pro 2 in my own household — that was incorrect on my part (I have multiple Ring devices and misidentified which one was throwing the error). Corrected details below, confirmed via the integration's own diagnostics export.
Device details
- Reported kind:
cocoa_camera_v2
- This is a Stick Up Cam, a sibling of the already-recognized
cocoa_camera (STICKUP_CAM_GEN3_KINDS), not a doorbell. Home Assistant's device registry labels it "Unknown Stickup Cam" as a result.
- From the integration diagnostics export, this device's data includes
camera_location_indoor, facing_window, siren_status fields (consistent with the Stick Up Cam family) and ext_power_state set (i.e. externally/plug powered — battery_life is null), so likely a plug-in or wired Stick Up Cam variant, probably a newer hardware revision than the plain cocoa_camera.
- Entities created by Home Assistant for this device still mostly work (camera, motion detection, volume, last-activity sensor) despite the unknown-kind error, but two diagnostic entities (wifi signal category/strength) end up disabled by the integration itself — possibly related to the unrecognized kind limiting capability detection.
Environment
- Home Assistant Core: 2026.7.2
- Integration: built-in
ring (not a custom fork)
To reproduce
Set up the Ring integration against an account with a device reporting kind: cocoa_camera_v2. Error appears in the log at integration setup / reload.
Additional context
Similar unmapped-kind reports exist for other newer Stick Up Cam hardware (e.g. #135388 Stickup_cam_medusa, #141538 Stick Up Cam Pro shown as "Unknown Stickup Cam" in home-assistant/core), so this looks like an ongoing pattern of Ring shipping new internal kind strings for hardware revisions faster than the library adds mappings.
Describe the bug
On startup, the Ring integration logs repeated errors for one of my devices:
This fires 7 times per Home Assistant restart. Checked
ring_doorbell/const.pyonmasterand the closest match isSTICKUP_CAM_GEN3_KINDS = ["cocoa_camera"]— there is nococoa_camera_v2entry anywhere in the file, so this kind isn't mapped to any device class.EDIT: I previously misattributed this to a Ring Video Doorbell Pro 2 in my own household — that was incorrect on my part (I have multiple Ring devices and misidentified which one was throwing the error). Corrected details below, confirmed via the integration's own diagnostics export.
Device details
cocoa_camera_v2cocoa_camera(STICKUP_CAM_GEN3_KINDS), not a doorbell. Home Assistant's device registry labels it "Unknown Stickup Cam" as a result.camera_location_indoor,facing_window,siren_statusfields (consistent with the Stick Up Cam family) andext_power_stateset (i.e. externally/plug powered —battery_lifeisnull), so likely a plug-in or wired Stick Up Cam variant, probably a newer hardware revision than the plaincocoa_camera.Environment
ring(not a custom fork)To reproduce
Set up the Ring integration against an account with a device reporting
kind: cocoa_camera_v2. Error appears in the log at integration setup / reload.Additional context
Similar unmapped-kind reports exist for other newer Stick Up Cam hardware (e.g. #135388
Stickup_cam_medusa, #141538 Stick Up Cam Pro shown as "Unknown Stickup Cam" in home-assistant/core), so this looks like an ongoing pattern of Ring shipping new internalkindstrings for hardware revisions faster than the library adds mappings.