Direct answer
For the Ring Chime Pro (2nd Gen), invitation/account, home membership, role/permission and platform region should be separated. First, verify the invite was accepted by the intended account.
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: shared users or family members cannot control it
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 invitation was accepted by a different account
What separates it The person appears as a member but cannot control anything, or sees an empty home. An invitation sent to one address and accepted while signed in as another produces exactly this.
How to confirm Compare the address the invitation was sent to against the address the member is actually signed in as, on their phone. These differ far more often than anyone expects.
- 2
The role granted does not include the capability
What separates it The member can do some things and not others — view but not unlock, control but not change settings, see live view but not recordings. Roles are tiered and the tiers are not obvious from their names.
How to confirm Compare the role's documented capabilities against what the member is trying to do. This is usually working exactly as designed.
- 3
The invitation expired or was never delivered
What separates it The member never received anything. Invitations time out, and they land in spam filters reliably enough that it should be the first thing checked.
How to confirm Resend and have the member check spam while you watch. Do not send a second invitation to a different address in the meantime — that creates the mismatched-account problem above.
- 4
The member's app or account region does not match
What separates it The member can sign in but the home does not appear at all. Regional account separation means two accounts in different regions cannot share a home on some platforms.
How to confirm Compare the account regions. This is not configurable from either phone.
- 5
The device was added to a personal account rather than the home
What separates it One device is missing from the member's view while everything else works. A device set up outside the shared structure is owned individually and is not covered by home membership.
How to confirm Check where that specific device lives in the account structure rather than what the member's role is.
- 6
Remote access is granted but local access is not, or the reverse
What separates it The member can control the device at home and not away, or vice versa. These are separate permissions on several platforms.
How to confirm Test as the member both on the home network and on cellular. A difference between the two identifies which permission is missing.
- 7
The member is on an outdated app version
What separates it Newly shared device types do not appear for one person. Sharing capabilities are added in app releases, and an old client cannot render what it does not know about.
How to confirm Compare app versions between the owner's phone and the member's before changing any permission.
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.
- The exact address the invitation was sent to, and the exact address the member is signed in as on their own phone — written down side by side.
- Whether the member sees the home and cannot control it, or does not see the home at all. These are two different failures.
- Precisely what the member can and cannot do, rather than a general report that it does not work.
- The role or permission level assigned, and what that role documents as including.
- Whether the difference appears only away from home, only at home, or in both.
- The app version on the owner's phone and on the member's.
- Whether the missing device was set up inside the shared home or on someone's personal account.
Confirm which account actually accepted the invitation
ReversibleRead the signed-in address on the member's own phone rather than trusting the address the invitation was sent to. Accepting while signed in as a different account is the single most common cause here and is invisible from the owner's side.
Establish whether they see the home at all
ReversibleSeeing the home but being unable to control it is a role problem. Not seeing it at all is an account, region or invitation problem. These share no steps, and one question separates them.
Compare one specific action, owner against member
ReversibleHave both try the same action on the same device at the same time. A general report that sharing is broken cannot be acted on; a specific capability that one has and the other does not points directly at a role tier.
Test the member both at home and on cellular
ReversibleLocal control and remote control are separate permissions on several platforms. A member who can operate the device in the house and not from work is missing one specific grant, not the whole share.
Compare app versions before changing permissions
ReversibleSharing support for newer device types arrives in app releases. An outdated client cannot display a device it does not know about, which looks exactly like a permission that was never granted.
Confirm the device belongs to the home, not to a person
ReversibleA device set up on someone's personal account sits outside the shared structure entirely. Home membership does not reach it, and the fix is to move the device rather than to widen anyone's role.
Resend only the invitation that failed
Signs you outDo not remove the member and rebuild the home. Removing a member discards their per-device settings and any automations they own, and rebuilding a home to fix one invitation is the most expensive possible response to it.
Verify as the member, on the member's phone
ReversibleConfirming from the owner's phone proves nothing about the member's experience — the owner has capabilities the member does not. The test has to be run on the member's device, signed in as the member.
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 shared users or family members cannot control it. 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.
- !Account regions differ and cannot be reconciled — this is not configurable from either phone.
- !The owner account is inaccessible and ownership needs transferring, which requires the provider and proof of purchase.
- !A shared security device is behaving inconsistently between users in a way that affects whether the property is actually protected.
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 "Troubleshooting Shared User invites". Ring's article for shared users who cannot accept or use access. 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 invited them and they still cannot control anything.+
Check which account accepted. An invitation sent to one address and accepted while signed in as a different one produces exactly this: they appear as a member and can do nothing. Read the signed-in address on their phone rather than the address you sent to.
They cannot see the home at all.+
That is a different failure from seeing it and being unable to act. Not seeing the home points at the invitation never being accepted by that account, an expired invitation, or mismatched account regions — none of which are role problems.
It works at home but not when they are out.+
Local control and remote control are separate permissions on several platforms. A member who can operate the device in the house and not from work is missing one specific grant, and widening their whole role is the wrong fix.
One device is missing from their view and the rest are fine.+
That device was probably set up on someone's personal account rather than inside the shared home. Home membership does not reach it. The fix is to move the device into the home, not to change anyone's permissions.
Should I delete the home and start again?+
No — that is the most expensive possible response. Rebuilding a home discards every automation, every share and every per-device setting attached to it, to fix an invitation that could be resent in ten seconds.
The invitation never arrived.+
Check spam, and check that it has not expired — invitations time out. Resend to the same address rather than trying a different one, because a second invitation to a different address creates the mismatched-account problem that is much harder to diagnose afterwards.
Their app looks different from mine.+
Compare versions. Sharing support for newer device types arrives in app releases, and an outdated client cannot render a device it does not know about — which is indistinguishable from a permission that was never granted.
Can I share my password instead of inviting them?+
Never. A shared owner password gives full control including the ability to remove you, and it defeats the per-user history that tells you who did what. Every platform's invitation flow exists specifically to avoid this.
How should I test that sharing works?+
On the member's phone, signed in as the member, doing the exact action they need — both at home and on cellular. Testing from the owner's phone proves nothing, because the owner has capabilities the member does not.
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 shared access or family?+
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 shared access, family. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not share owner passwords, codes or unnecessary security access.
Answer for the exact device and software version shown above.