Repository navigation
Add device kinds cocoa_camera_v2, cocoa_camera_v3 and cocoa_doorbell_v3 - #550
yosandan13 wants to merge 2 commits into
Conversation
Ring keeps shipping new internal kind strings for hardware revisions of families that are already mapped. An unmapped kind is not merely a cosmetic naming problem: has_capability() returns False for every capability, so downstream consumers create no motion, siren or ding entities at all, and the device cannot trigger any automation even though it works normally in the Ring app. Both strings belong to families already present here: - cocoa_camera_v2 alongside cocoa_camera in STICKUP_CAM_GEN3_KINDS, restoring BATTERY, SIREN and MOTION_DETECTION/VIDEO - cocoa_doorbell_v3 alongside cocoa_doorbell and cocoa_doorbell_v2 in DOORBELL_GEN2_KINDS, restoring BATTERY and MOTION_DETECTION/VIDEO/DING Refs python-ring-doorbell#535, python-ring-doorbell#549, python-ring-doorbell#543.
|
Same shape, one revision further along. My Ring Outdoor Cam Pro (Plug-In) — a brand-new unit, mains-powered at 230 V, no battery bay, added to the account on 2026-08-19 — reports What actually breaksThe camera entity, volume control and last-activity sensor all come through fine — what's missing is everything gated behind Side-by-side on the same account and integration version: a mapped Diagnostics (redacted)"kind": "cocoa_camera_v3",
"device_type": "cocoa_camera_v3",
"health": {
"ac_power": 1,
"battery_percentage_category": "unknown",
"battery_voltage_category": "unknown"
}Permanently wired to mains, so only Environment: HA core 2026.8.x, ring-doorbell 0.9.14. AskWould you mind folding this string into the PR? It's the same one-line change in the same list. And +1 on the graceful-degradation suggestion at the end of your description. This is now the third suffix in the |
Same shape as cocoa_camera_v2, one hardware revision further along: reported on a Ring Outdoor Cam Pro (Plug-In), mains-powered, no battery bay. Loses the same three capabilities for the same reason - has_capability() gates on membership in these lists, so an unmapped kind creates no motion, siren or motion-detection entity even though motion triggers normally in the Ring app. Folds in the report and diagnostics from @Frone87 on the open PR. Refs python-ring-doorbell#549, python-ring-doorbell#535.
|
Done — Your report made the case stronger than mine did on its own. A mains-powered unit with no battery bay is a useful counterpoint: it shows the breakage is not tied to a power source or a battery-reporting quirk, just to the Noted in the description that On the fallback: three unmapped suffixes in the |
Upstream python-ring-doorbell has had no merges for months; this takes what its open pull requests offer, adapted to this fork: - WebRTC: _close() no longer awaits its own reader task when the stream closes from inside it (upstream python-ring-doorbell#548, python-ring-doorbell#534). - New RingDoorBell.async_take_snapshot(): one request that returns a stored snapshot newer than max_age or captures a fresh one, via the endpoint ring-mqtt uses (upstream python-ring-doorbell#528). Existing snapshot methods are unchanged. - Outdoor Cam Plus reports a battery from its health data when it says either way, so plug-in variants no longer get one; a camera whose battery died reports nothing and keeps it (upstream python-ring-doorbell#538, reworked). - Device kinds: Battery Doorbell Pro 4K, Wired Doorbell Plus (2nd Gen), Wired Doorbell (doorbell_tahoe), Doorbell (2nd Gen) cocoa_doorbell_v3, Indoor Cam Plus, Spotlight Cam Pro 4K, Elite Cam 140/360 4K and Chime (2nd Gen) (upstream python-ring-doorbell#553, python-ring-doorbell#539, python-ring-doorbell#536, python-ring-doorbell#531, python-ring-doorbell#550). Co-authored-by: Niels Haagsman <haagsman@gmail.com> Co-authored-by: Adam Reeve <adam@adamreeve.com> Co-authored-by: danielcolquitt <daniel@colquitt.xyz> Co-authored-by: Tom Roberts <tom@tomroberts.co.uk> Co-authored-by: ben79 <benjaminfearnley@gmail.com> Co-authored-by: Aaron Wolen <aaron@wolen.com> Co-authored-by: Yoan <yoan.cousin@proton.me>
Upstream python-ring-doorbell has had no merges for months; this takes what its open pull requests offer, adapted to this fork: - WebRTC: _close() no longer awaits its own reader task when the stream closes from inside it (upstream python-ring-doorbell#548, python-ring-doorbell#534). - New RingDoorBell.async_take_snapshot(): one request that returns a stored snapshot newer than max_age or captures a fresh one, via the endpoint ring-mqtt uses (upstream python-ring-doorbell#528). Existing snapshot methods are unchanged. - Outdoor Cam Plus reports a battery from its health data when it says either way, so plug-in variants no longer get one; a camera whose battery died reports nothing and keeps it (upstream python-ring-doorbell#538, reworked). - Device kinds: Battery Doorbell Pro 4K, Wired Doorbell Plus (2nd Gen), Wired Doorbell (doorbell_tahoe), Doorbell (2nd Gen) cocoa_doorbell_v3, Indoor Cam Plus, Spotlight Cam Pro 4K, Elite Cam 140/360 4K and Chime (2nd Gen) (upstream python-ring-doorbell#553, python-ring-doorbell#539, python-ring-doorbell#536, python-ring-doorbell#531, python-ring-doorbell#550). Co-authored-by: Niels Haagsman <haagsman@gmail.com> Co-authored-by: Adam Reeve <adam@adamreeve.com> Co-authored-by: danielcolquitt <daniel@colquitt.xyz> Co-authored-by: Tom Roberts <tom@tomroberts.co.uk> Co-authored-by: ben79 <benjaminfearnley@gmail.com> Co-authored-by: Aaron Wolen <aaron@wolen.com> Co-authored-by: Yoan <yoan.cousin@proton.me>
Upstream python-ring-doorbell has had no merges for months; this takes what its open pull requests offer, adapted to this fork: - WebRTC: _close() no longer awaits its own reader task when the stream closes from inside it (upstream python-ring-doorbell#548, python-ring-doorbell#534). - New RingDoorBell.async_take_snapshot(): one request that returns a stored snapshot newer than max_age or captures a fresh one, via the endpoint ring-mqtt uses (upstream python-ring-doorbell#528). Existing snapshot methods are unchanged. - Outdoor Cam Plus reports a battery from its health data when it says either way, so plug-in variants no longer get one; a camera whose battery died reports nothing and keeps it (upstream python-ring-doorbell#538, reworked). - Device kinds: Battery Doorbell Pro 4K, Wired Doorbell Plus (2nd Gen), Wired Doorbell (doorbell_tahoe), Doorbell (2nd Gen) cocoa_doorbell_v3, Indoor Cam Plus, Spotlight Cam Pro 4K, Elite Cam 140/360 4K and Chime (2nd Gen) (upstream python-ring-doorbell#553, python-ring-doorbell#539, python-ring-doorbell#536, python-ring-doorbell#531, python-ring-doorbell#550). Co-authored-by: Niels Haagsman <haagsman@gmail.com> Co-authored-by: Adam Reeve <adam@adamreeve.com> Co-authored-by: danielcolquitt <daniel@colquitt.xyz> Co-authored-by: Tom Roberts <tom@tomroberts.co.uk> Co-authored-by: ben79 <benjaminfearnley@gmail.com> Co-authored-by: Aaron Wolen <aaron@wolen.com> Co-authored-by: Yoan <yoan.cousin@proton.me>
Upstream python-ring-doorbell has had no merges for months; this takes what its open pull requests offer, adapted to this fork: - WebRTC: _close() no longer awaits its own reader task when the stream closes from inside it (upstream python-ring-doorbell#548, python-ring-doorbell#534). - New RingDoorBell.async_take_snapshot(): one request that returns a stored snapshot newer than max_age or captures a fresh one, via the endpoint ring-mqtt uses (upstream python-ring-doorbell#528). Existing snapshot methods are unchanged. - Outdoor Cam Plus reports a battery from its health data when it says either way, so plug-in variants no longer get one; a camera whose battery died reports nothing and keeps it (upstream python-ring-doorbell#538, reworked). - Device kinds: Battery Doorbell Pro 4K, Wired Doorbell Plus (2nd Gen), Wired Doorbell (doorbell_tahoe), Doorbell (2nd Gen) cocoa_doorbell_v3, Indoor Cam Plus, Spotlight Cam Pro 4K, Elite Cam 140/360 4K and Chime (2nd Gen) (upstream python-ring-doorbell#553, python-ring-doorbell#539, python-ring-doorbell#536, python-ring-doorbell#531, python-ring-doorbell#550). Co-authored-by: Niels Haagsman <haagsman@gmail.com> Co-authored-by: Adam Reeve <adam@adamreeve.com> Co-authored-by: danielcolquitt <daniel@colquitt.xyz> Co-authored-by: Tom Roberts <tom@tomroberts.co.uk> Co-authored-by: ben79 <benjaminfearnley@gmail.com> Co-authored-by: Aaron Wolen <aaron@wolen.com> Co-authored-by: Yoan <yoan.cousin@proton.me>
Upstream python-ring-doorbell has had no merges for months; this takes what its open pull requests offer, adapted to this fork: - WebRTC: _close() no longer awaits its own reader task when the stream closes from inside it (upstream python-ring-doorbell#548, python-ring-doorbell#534). - New RingDoorBell.async_take_snapshot(): one request that returns a stored snapshot newer than max_age or captures a fresh one, via the endpoint ring-mqtt uses (upstream python-ring-doorbell#528). Existing snapshot methods are unchanged. - Outdoor Cam Plus reports a battery from its health data when it says either way, so plug-in variants no longer get one; a camera whose battery died reports nothing and keeps it (upstream python-ring-doorbell#538, reworked). - Device kinds: Battery Doorbell Pro 4K, Wired Doorbell Plus (2nd Gen), Wired Doorbell (doorbell_tahoe), Doorbell (2nd Gen) cocoa_doorbell_v3, Indoor Cam Plus, Spotlight Cam Pro 4K, Elite Cam 140/360 4K and Chime (2nd Gen) (upstream python-ring-doorbell#553, python-ring-doorbell#539, python-ring-doorbell#536, python-ring-doorbell#531, python-ring-doorbell#550). Co-authored-by: Niels Haagsman <haagsman@gmail.com> Co-authored-by: Adam Reeve <adam@adamreeve.com> Co-authored-by: danielcolquitt <daniel@colquitt.xyz> Co-authored-by: Tom Roberts <tom@tomroberts.co.uk> Co-authored-by: ben79 <benjaminfearnley@gmail.com> Co-authored-by: Aaron Wolen <aaron@wolen.com> Co-authored-by: Yoan <yoan.cousin@proton.me>
Ring keeps shipping new internal
kindstrings for hardware revisions of families that are already mapped here. Three of them are currently unmapped, and the consequence goes well beyond a cosmetic naming problem.Both
Doorbot.has_capability()andRingStickUpCam.has_capability()resolve capabilities by membership in the*_KINDSlists. An unmapped kind therefore returnsFalsefor every capability, so downstream consumers create no motion, siren or ding entities at all — the device cannot trigger any automation, even though motion and ding work normally in the Ring app.The three kinds
cocoa_camera_v2Unknown Stickup Camcocoa_camerainSTICKUP_CAM_GEN3_KINDScocoa_camera_v3Unknown Stickup Camcocoa_doorbell_v3Unknown Doorbellcocoa_doorbell,cocoa_doorbell_v2inDOORBELL_GEN2_KINDSAdding them restores
BATTERY,SIRENandMOTION_DETECTION/VIDEOfor the camera, andBATTERYandMOTION_DETECTION/VIDEO/DINGfor the doorbell.Evidence
Observed on a single installation with five Ring devices on one account, which gives a clean side-by-side comparison — mapped and unmapped kinds, same account, same integration version:
modelstickup_cam_mini_ptz_v1stickup_cam_mini_v2cocoa_camera_v2cocoa_camera_v2cocoa_doorbell_v3The same physical doorbell had previously registered under an older identity that was mapped, and did get the full entity set — so the loss is purely one of identification, not of hardware capability.
Environment: Home Assistant core 2026.8.1,
ring-doorbell0.9.14.Added after review
@Frone87 reported the same failure on a Ring Outdoor Cam Pro (Plug-In) — a
mains-powered unit with no battery bay, added to their account on 2026-08-19 —
reporting
kind: "cocoa_camera_v3"and registering as "Unknown Stickup Cam".Same three entities missing, same
has_capability()root cause, and the sameclean side-by-side on their account: a mapped
stickup_cam_longfingets themotion event, siren and motion-detection switch; their unmapped
cocoa_camera_v3gets none of the three.Since it belongs in the same list and is the same one-line change, it is folded
into this PR rather than split into a separate one. On that device
BATTERYdegrades harmlessly — the sensor is created but stays Unknown, as
battery_lifeis absent from the attributes.
That makes
cocoa_camera_v2,cocoa_camera_v3andcocoa_doorbell_v3threeunmapped suffixes in the
cocoa_*family within a few months, which is thestrongest argument for the fallback suggestion at the end of this description.
Related issues
Unknown kind: cocoa_camera_v2(Stick Up Cam variant)Unknown kind: cocoa_camera_v2(Ring Outdoor Cam Plus)cocoa_doorbell_v3; KeyError inexisting_doorbell_typeon unmapped chime type 3 #543 —cocoa_doorbell_v3registers as Unknown DoorbellNote that #498 ("Support for cocoa_camera_v2") was closed in April 2026, but the string is absent from
master— it looks like the fix never landed, which would explain why the reports keep recurring.This PR deliberately addresses only the mapping half of #543. The
KeyError: 3onexisting_doorbell_typereported there is independent — it depends on the In-Home Chime Type setting rather than on the device kind — and is better fixed separately, together with the graceful-degradation request from #506.Testing
No existing test references these constants, and the change adds no new behaviour beyond list membership, so no test was added — happy to add fixture-based capability tests if you would prefer that.
I was not able to run
uv run pytestlocally:cffi, pulled in viafirebase-messaging→cryptography, requires MSVC build tools that are unavailable on this machine. I verified instead thatconst.pystill parses, that both strings land in exactly one list each, and that no list contains duplicates. CI will cover the rest.A broader suggestion
This is the third or fourth report of the same shape in a few months, and the pattern is structural: Ring adds revision suffixes faster than mappings can follow. Falling back to the base capability set of the nearest family prefix — rather than to no capabilities at all — would turn each of these from a total loss of function into a cosmetic naming gap. Happy to open a separate issue if that seems worth pursuing.