New Device: Kidde Ring Smoke + CO Alarm

[Blaster707]

Description

Earlier in 2025, Ring and Kidde released a new device - the Ring Smart Smoke + CO Alarm. This device does not appear to currently be available in homebridge-ring. Requesting this device be added; I did not see any other requests for this device in either Issues or Discussions.

Proposed solution

Device data is used to add this device to the plugin.

Alternatives

No response

Device data

Due to the length of the output of Data Discovery, I am attaching a .txt file with the output.

Ring Data Discovery 11.5.2025.txt

[BrianWhiting]

I would also like to see support for this device, in addition to the Kidde Smoke Alarm (no CO sensor). I have 6 smoke alarms and 4 CO/smoke alarms (these are the only devices in my Ring account) and can provide a JSON file of the devices like OP provided if someone can give me some instructions (I'm a programmer, so I know my way around things like Postman, just don't want to spend an excess amount of time going through the code to find out how to hit the right endpoint).

[jbettcher]

Thanks for looking at this - I'd love to see these working within the homebridge side of things too. Happy to help test or contribute if useful. I have the devices json response saved with the 'sensor_bluejay_ws' and 'sensor_bluejay_wsc' device types (smoke and co/smoke) coming back under the 'other' collection. Right now it doesn't look like anything in that 'other' collection is getting mapped to any kind of custom smoke detector object. I'm guessing there's also some work to do with subscriptions/push notifications for these devices. Anyway, happy to send that over the device json if it's useful but I won't post directly here since there's probably some sensitive IDs/mac addresses/geo coords in it.

[tsightler]

There's nothing that needs to be done other than adding a new device to ring-homebridge (or modifying the existing ones) that supports the new status, I've already added support to ring-mqtt even using the older ring-client-api so I know it works.

However, there are some interesting other changes, for example, every other device currently supported (other than cameras/chimes/intercoms) are Z-wave devices and require a hub. However, these new kiddie devices can work without an alarm or other hub device at all. For that scenario a websocket connection is needed even if there's no base station, which I'm not sure of ring-homebridge can deal with (ring-mqtt definitely cannot today, I need to make some logic changes).

Overall, I'm sure PRs would be welcome.

[dgreif]

I've released 14.3.0 which should theoretically add support for these smoke/co detectors. Thanks for the device logs @Blaster707, those were very helpful!

Since I don't have one of these myself, I can't test that it's set up properly. Would one of you mind verifying:

• That the device shows up
• That a smoke alarm is actually passed through to HomeKit? This one may require you to actually set it off 🤔. I know that's asking a lot, but I would hate for folks to depend on these and then they not actually work in an emergency

[jbettcher]

Thanks for the work on this @dgreif. Unfortunately, I still don't see any of my sensor_bluejay_ws and sensor_bluejay_wsc devices showing up:

homebridge  | [2/8/2026, 12:10:35 PM] [homebridge-ring] Loaded homebridge-ring v14.3.0 child bridge successfully
homebridge  | [2/8/2026, 12:10:36 PM] [homebridge-ring] Found the following locations:
homebridge  | [2/8/2026, 12:10:36 PM] [homebridge-ring]   locationId: xxxxxx
homebridge  | [2/8/2026, 12:10:36 PM] [homebridge-ring] Configuring 0 cameras and 0 devices for location "xxxx" - locationId: xxxxx
homebridge  | [2/8/2026, 12:10:36 PM] [homebridge-ring] Ignoring push notification received in first two seconds after starting up
homebridge  | [2/8/2026, 12:10:36 PM] [homebridge-ring] Ignoring push notification received in first two seconds after starting up

I have 2x of the Kidde/Ring smoke-only detectors (sensor_bluejay_ws) and 2x of the Kidde/Ring CO + smoke detectors (sensor_bluejay_wsc). These come back in as objects in the "other" collection of fetchRingDevices here:

ring/packages/ring-client-api/api.ts

Line 92 in 3bcc624

other: otherDevices,

. However, fetchAndBuildLocations does not seem to do anything with "other" devices here:

ring/packages/ring-client-api/api.ts

Line 427 in 3bcc624

} = await this.fetchRingDevices(),

I wasn't quite following the comments @tsightler made concerning the zwave hub devices. My Kidde/Ring smoke detectors were purchased in the US at a home depot, and are wifi-only. They are set up exclusively in the Ring app. Maybe the CO/smoke and smoke-only detectors I have are different than what others are testing?

I haven't had time to dig in more other than some superficial debugging to understand how best to extend the api and/or homebridge-ring to integrate these new objects, but I may be able to do that in the next few weeks. Happy to test functionality once they start showing up within the homebridge-ring side of things.

[jbettcher]

Not sure if it helps, but I took a stab at creating a type for the Kidde/Ring smoke detectors that I see coming back as part of the 'other' devices on the initial Location query. It may be that my devices are different than what others have; I'm not sure that they are RingDevices, maybe more like third party garage door openers. I don't know enough about the ring API to really go further here, but it may help to see the type of data I get from the initial location fetch.

See the todo comment for where I'm stuck; I'm not sure that these devices can be coerced into a RingDevice type.

main...jbettcher:ring:kidde_ring_support#diff-012c42aa98f8f94008d0765323cf069a15172a05ceed90c37070d5dfd73f706fR125

[Excel1216]

I have 3 of the CO/Smoke detectors and would love if they worked with HomeKit

[mynameisbobwehadababyitsaboy]

I've released 14.3.0 which should theoretically add support for these smoke/co detectors. Thanks for the device logs @Blaster707, those were very helpful!

Since I don't have one of these myself, I can't test that it's set up properly. Would one of you mind verifying:

• That the device shows up
• That a smoke alarm is actually passed through to HomeKit? This one may require you to actually set it off 🤔. I know that's asking a lot, but I would hate for folks to depend on these and then they not actually work in an emergency

I installed one in my home today (to test out as a replacement to the discontinued Nest detect). Unfortunately it doesn't show up for me in 14.3.0.

I'd be happy to set mine off for the greater good once it's able to show up for me in Homekit.

[mynameisbobwehadababyitsaboy]

Oh actually, update. The wired model of the Kidde Ring Smoke/CO alarm is working!

However, the battery version isn't connecting to Homekit yet.