Revoke a Former Roommate’s Smart-Home Integrations
Remove an ex-roommate from linked smart-home services, not just the main household app, and test access afterward.
When a roommate leaves, remove their smart-home access from the household platform and every linked service, then change shared credentials and test from outside the home. Deleting a visible “member” is only the first step because voice assistants, lock codes, camera shares, vendor accounts, and automation services can preserve separate paths.
Inventory every route into the home
List connected locks, cameras, doorbells, thermostats, alarms, lights, garage controls, speakers, hubs, and appliance apps. Beside each device, record its primary administrator, invited members, physical codes, linked voice assistants, third-party automations, and recovery email or phone. This integration inventory should describe access paths, not expose passwords in a shared note.
Ask the departing resident to remove personal integrations before the agreed turnover time, but do not make completion depend solely on them. The remaining administrator should review memberships and linked services directly. The FTC’s advice for buying or selling a smart home recommends removing administrative access and personal information, changing account settings and logins, and resetting devices for a transfer.
A roommate move is not exactly a home sale, so choose resets based on ownership and manufacturer instructions. If the departing person owns a device, agree whether it leaves, transfers, or is disconnected. Preserve footage or logs only when there is a legitimate household need and legal basis.
Revoke, rotate, and verify
Remove the former resident from the home account, individual device shares, voice profiles, routines, webhook services, and family groups. Delete door and alarm codes assigned to them. Rotate credentials that were actually shared, including the administrator password and recovery methods. Enable multifactor authentication where supported.
Check automations for names that hide their effect, such as “arrive home” or “night routine.” A third-party service may still issue commands even after its creator disappears from the main app. Revoke tokens or unlink the service, then recreate only the automations the current household understands.
Perform a remote-action test on each security-sensitive device. From cellular data, have the current administrator confirm legitimate remote access, notifications, and live status. Review the member list again and check recent access where the product offers it. Do not ask the former roommate to attempt entry after access is revoked.
If removal could put someone at risk, especially in a coercive or abusive situation, use a safety plan and specialist support rather than sending a confrontation message. Account changes can generate alerts.
Check physical accessories as well. Return spare keys, lock fobs, bridge devices, setup cards, and printed recovery codes to their owner or secure custodian. Update emergency contacts that still point to the departed resident. If a camera covered their private room, agree on deletion and retention before another person occupies it, subject to applicable law.
Questions residents ask
Is changing the Wi-Fi password enough?
No. Cloud accounts and cellular-connected services may work without the home Wi-Fi password. Review memberships, codes, integrations, and recovery settings separately.
Should every device be factory-reset?
Not automatically. Follow manufacturer guidance and the ownership agreement. A reset may erase evidence, settings, or other residents’ access. Use it when transfer instructions require it or when access cannot be reliably removed another way.
What if nobody knows who the administrator is?
Use the vendor’s official recovery process and proof-of-ownership requirements. Do not create a second unmanaged account as a shortcut.
How HomeCo helps
Build the integration inventory in HomeCo with one private task per platform and a named current administrator. Track revoke, rotate, and verify as separate checkboxes. The shared task model keeps device work visible without storing secret values.
Close the project after member lists, physical codes, recovery contacts, and remote tests are complete. Schedule another review after the final device has physically left the home.