You do not need the hub that originally added a Z-Wave device in order to remove it from that device’s memory. Z-Wave includes a “general exclusion” command that any Z-Wave controller can issue, and it works regardless of which controller the device was previously paired to.
Why exclusion is two separate steps, and why that matters here
Z-Wave exclusion is not a single action performed by the controller alone. It is a two-part process: the controller broadcasts an exclusion command, and then you perform a physical action on the device itself to confirm it. The device does not check “is this the controller that added me” before accepting the exclusion: it accepts the command from whatever controller sent it, and then clears its own network membership.
That structure is exactly why this works when the old controller is gone. Exclusion was never designed to require the original hub’s cooperation. It was designed as an operation any Z-Wave controller can perform, paired with a physical confirmation on the device that proves you have hands-on access to it: not proof that you have the original network.
The general exclusion command, in plain terms
Every Z-Wave controller (whatever hub or app you’re currently using) has some form of an exclusion or “remove device” mode. Putting your current controller into that mode issues a general exclusion broadcast that any Z-Wave device in range is listening for.
The steps, at the level every Z-Wave controller shares:
- Put your current controller into exclusion mode. This is usually a clearly labeled button (“Remove Device,” “Exclude,” or similar) in the network management section of your controller’s app.
- Perform the device’s confirmation action while the controller is listening. This is where it becomes device-specific, covered below.
- Wait for confirmation. A successful exclusion is normally acknowledged by the controller app, and the device’s own status light or behavior may also change to indicate it’s no longer joined to a network.
This works even if the hub that originally added the device has been sold, factory reset, or thrown away. The command comes from your current controller; the device does not need to remember or verify the old one.
What still requires the device’s own manual
The controller side of this is generic: any Z-Wave controller can send the broadcast. The device side is not. The specific physical action that confirms an exclusion (a button press, a particular number of taps, holding something for a set number of seconds) is set by the device’s manufacturer and varies by model. [FIRST-PARTY-REQUIRED] We have not tested every device this applies to, so the confirmation gesture for your specific switch, lock, or sensor is something to check in that device’s own manual or the manufacturer’s support page rather than guess at.
If the manual is genuinely unavailable (a common problem with a device bought secondhand with no paperwork), searching the model number alongside “Z-Wave exclusion” or “factory reset” usually surfaces the manufacturer’s own instructions, since the confirmation gesture is public information the manufacturer publishes, not something tied to any particular account or hub.
Some devices also support a full factory reset as a separate, more drastic option, which clears the device’s network membership from the device side without any controller involvement at all. That’s a fallback worth checking if the general exclusion process above doesn’t confirm successfully: some devices are more reliably reset than excluded via broadcast.
What a second-hand device inherits from its previous owner
A device bought used and still showing as joined to a network is the single most common reason to need this process. The device itself doesn’t know or care who owns it; it only knows it currently believes itself to be part of a Z-Wave network, and it will refuse to join a new one until that membership is cleared.
This is a genuinely different situation from a device that’s locked to a cloud account tied to the previous owner’s login, which is a separate app-level problem the exclusion process above does not touch. Exclusion clears the device’s local Z-Wave network membership; it has no effect on any manufacturer account the device might also be registered to. Whether the specific device you have used cloud accounts at all is worth checking before you assume exclusion alone will finish the job.
If excluding the device doesn’t resolve the underlying symptom, or you’re not certain a stale network membership is actually the problem, the device, radio, router or cloud test is the faster way to confirm what’s actually wrong before you spend more time on exclusion specifically.
For the wider question of what to check first when a device that used to work stops cooperating with your network, see why a smart device that was working starts dropping off. And if the device you’re excluding is being replaced because its routing has become unreliable rather than because you’re switching hubs, a network heal may be the thing you actually need instead.
FAQ
Do I need the previous owner’s app or account to exclude a device?
No. Exclusion is a network-layer command issued by your own current controller. It does not require the previous owner’s app, login, or cooperation.
What if the device won’t respond to the exclusion confirmation gesture?
Double-check you’re using the correct gesture for that specific model: this is the step manufacturers vary on most. If it genuinely doesn’t respond, a full factory reset (if the device supports one) is the next thing to try.
Can I exclude a device that isn’t currently working at all?
Only if it can still receive the physical confirmation action and has power. A device that’s completely dead (no power, no response to any button) generally can’t be excluded through the normal process, since it needs to actively participate in the exchange.
Will excluding a device erase any automations built around it?
Automations live in your controller’s software, not on the device. Excluding the device will typically leave references to it as broken or missing in any automation that used it, which you’ll need to clean up separately.
Is general exclusion the same thing as a factory reset?
No. General exclusion is a controller-issued command that clears network membership. A factory reset is performed on the device itself and typically clears more: network membership plus any other stored configuration, depending on the device.
Sources referenced in this article
- Home Assistant Community, How to exclude Z-Wave devices from old controller.
https://community.home-assistant.io/t/how-to-exclude-z-wave-devices-from-old-controller/125805(accessed 2026-08-06). Source of the general exclusion command behavior and the two-step (controller command, device confirmation) structure. - SmartThings Support, Z-Wave General Info.
https://support.smartthings.com/hc/en-us/articles/204392790-Z-Wave-General-Info(accessed 2026-08-06). Source confirming general exclusion is a standard Z-Wave protocol capability available across controllers.
Review interval: 12 months (controller app terminology and menu structure can shift).