Direct answer
For the Ring Chime Pro (2nd Gen), controller eligibility, setup code, prior fabric, Thread/Wi-Fi and multi-admin support should be resolved. First, identify the exact protocol/controller and confirm active hub eligibility.
What this covers
- Ring Chime Pro (2nd Gen) (2nd generation — the model number is on the label beside the plug)
- Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.
- The specific fault this record addresses: will not connect through Matter, HomeKit or another platform
What it does not cover
- ×The same symptom on a different Ring product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
The device is still commissioned to a fabric it can no longer reach
What separates it It appears in the old controller and works in none, or joins a new controller and drops out within minutes. A reset clears local settings on several implementations without clearing commissioning data.
How to confirm Remove it from every previous controller BEFORE resetting the hardware. Doing it in the other order is the single most common way this ends up unrecoverable without support.
- 2
The platform does not support this device type
What separates it The device commissions successfully and some capabilities are missing on one platform. Standards cover a defined set of device types and attributes, and manufacturer-specific features fall outside them.
How to confirm Compare the capability list against what the standard defines for that device type. Missing extras is expected behaviour, not a fault.
- 3
The controller's own version is too old
What separates it Commissioning fails on one controller and succeeds on another. Support arrives in controller software releases, and an older hub simply does not know the device type.
How to confirm Check the controller's version against the manufacturer's stated requirement before changing anything on the device.
- 4
The device is on a network segment the controller cannot reach
What separates it Both are online and cannot find each other. IoT VLANs, guest networks and client isolation all break local discovery, which these protocols depend on.
How to confirm Put both on the same segment with isolation off for the test. Discovery here is local, not cloud-mediated.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- Every controller and platform this device has ever been commissioned to, including ones no longer in use.
- The exact protocol involved and the exact controller version, both read rather than assumed.
- Whether the device commissions and then drops, or never commissions at all — these are different failures.
- Which network segment each of the device and the controller is on, and whether client isolation is enabled.
Remove it from every previous controller before touching the hardware
Reset / data riskThis order is the whole game. A reset clears local settings without clearing commissioning data on several implementations, and a device that still believes it belongs to an unreachable fabric will keep trying to rejoin it rather than accepting a new one — a state that frequently needs manufacturer support to clear.
Check the controller's version against the requirement
ReversibleSupport for a device type arrives in controller software, not in the accessory. Commissioning that fails on one controller and succeeds on another is a version gap, and nothing done to the device will close it.
Put the device and the controller on the same network segment
ReversibleDiscovery here is local rather than cloud-mediated, so IoT VLANs, guest networks and client isolation all break it while leaving both devices apparently online. Test with isolation off before concluding anything.
Confirm control from both platforms before finishing
ReversibleA device that works on the new platform and has silently dropped off the old one is a half-completed job. Test both, and test one of them away from the home network.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- 2nd generation — the model number is on the label beside the plug. Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.
- What it is
- An audible chime and a Wi-Fi extender for Ring devices in one plug-in unit. It is not a camera and has no battery, so most camera-shaped troubleshooting does not apply to it — but a fault here presents as a fault on every Ring device that connects through it.
- Power
- Plugs into a standard power outlet, with US, CA, UK, EU and ANZ plug adapters depending on destination country. There is no battery, so it has no independent state to preserve across a power cut.
- Wi-Fi
- 802.11 a/b/g/n/ac dual-band at 2.4 GHz and 5 GHz. Ring states a setup requirement of a router operating at both 2.4 GHz and 5 GHz — this device is one of the few in the range that genuinely needs the 5 GHz band present.
- Compatibility
- Ring states it works with all Ring Video Doorbells and Security Cameras.
- Placement
- As an extender it has to sit between the router and the device that needs help — roughly halfway, in range of both. Plugged in beside the device it is meant to assist, it has the same poor signal that device has and improves nothing.
- Power path
- Mains adapter into a standard outlet. Switched outlets and outlets on a circuit that trips are the two failure modes that present as device faults. Use the supplied adapter — third-party adapters that supply the right voltage at the wrong current are a common cause of intermittent restarts.
- Symptom boundary
- This record covers Ring Chime Pro (2nd Gen) when it will not connect through Matter, HomeKit or another platform. A different symptom on the same hardware, or this symptom on a different Ring product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !The device is locked to a fabric that no longer exists and will not accept a new commissioning after a documented reset. This generally needs the manufacturer.
- !The capability you need is not defined by the standard for this device type, which no configuration will produce.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Ring publishes this as "Works With Ring". Ring's own statement of which third-party platforms and devices it integrates with. Probed 2026-08-21: title-verified. What that article does not carry is the model boundary — it is written for a product line, and 2nd generation — the model number is on the label beside the plug is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
Does the Chime Pro need a 5 GHz router?+
Ring states the setup requirement as a router operating at both 2.4 GHz and 5 GHz, and the device itself is 802.11 a/b/g/n/ac dual-band. That makes it one of the few products in the Ring range where a 2.4-GHz-only network is genuinely insufficient — the opposite of the usual smart-home constraint.
Where should the Chime Pro be plugged in?+
Roughly halfway between the router and the device that needs help, in usable range of both. Plugged in next to the camera it is meant to assist, it receives the same weak signal that camera does and has nothing better to relay. This is the most common reason an extender changes nothing.
All my Ring devices went offline at once.+
If they connect through the Chime Pro, check it first. It is an extender as well as a chime, so a fault here takes out everything downstream of it simultaneously — which reads as a catastrophic account or provider failure and is usually one unplugged extender.
Does the Chime Pro work with every Ring device?+
Ring states that it works with all Ring Video Doorbells and Security Cameras. Where a specific device is not chiming, that is a per-device setting in the app rather than a compatibility limit.
Does it keep working in a power cut?+
No. It plugs into a standard outlet and has no battery, so it stops with the power and comes back with it. Anything connecting through it stops too — which is why devices that do have batteries can still appear offline after an outage.
I reset it and now nothing can add it.+
That is the order problem, and it is the most common serious mistake on this symptom. A reset clears local settings without clearing commissioning data on several implementations, so the device still believes it belongs to a fabric it cannot reach and keeps trying to rejoin it. Removing it from the old controller first is what avoids this.
It joins and then disappears within minutes.+
That is the same disagreement seen from the other side — the device is being pulled back toward a fabric it still holds credentials for. It is not a signal problem, and improving the network will not change it.
Some features are missing on one platform.+
Standards define a fixed set of device types and attributes, and manufacturer-specific extras fall outside them. Missing extras on a cross-platform integration is expected rather than broken, and the manufacturer's own app remains the place those features live.
Both devices are online and cannot find each other.+
Discovery here is local rather than cloud-mediated, so an IoT VLAN, a guest network or client isolation will break it while leaving both perfectly online. Put both on the same segment with isolation off before investigating anything else.
Is it worth using the manufacturer's app as well?+
Usually yes. The standard covers the common capabilities; the manufacturer's app covers everything else, including firmware updates and the settings that are not in the standard. Treating cross-platform control as a replacement rather than an addition is what produces most of the missing-feature complaints.
Does this answer apply to every Ring model?+
No. It is scoped to 2nd generation — the model number is on the label beside the plug. Ring device; wired/battery power, Chime/Alarm integration, subscription and Wi-Fi band vary.
What should I record before troubleshooting Matter or HomeKit?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing Matter, HomeKit. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Keep setup codes private and do not reset locks/alarms casually.
Answer for the exact device and software version shown above.