Remove a device or a bridge
Remove devices first, while the bridge is still connected, then disable the bridge, then uninstall it.
Remove a device
Section titled “Remove a device”On the bridge’s machine, with the bridge connected:
nodelets thing listnodelets thing remove nl_5c0e8a2f-7d41-4b9e-a3c6-2f8d1e4b7a90The command asks you to confirm, then removes the Thing from the bridge and its Nodelet from your account. After that:
- Calls to the Nodelet answer
NOT_FOUND, and keys and connections no longer list it. - Its saved readings are deleted. Reads stop at once, and the stored readings are deleted shortly after.
- Its record stays. The Devices section of the Account page lists it as Removed, and only you can open its record.
A removed Nodelet cannot return. To connect the same device again, add it as a new Thing, which gets a new ID.
If the connection drops during a removal, the Thing shows removing, and the bridge finishes the removal when it next connects.
Disable the bridge
Section titled “Disable the bridge”- Open Account on the dashboard.
- Under Bridges, choose the disable button beside the bridge, and confirm Disable bridge.
The bridge is disconnected and cannot reconnect, and its devices stop responding. Disabling cannot be undone, and a disabled bridge cannot be recovered. The bridge stays listed as Disabled. To stop a bridge only for now, use Stop key instead; see Recover a bridge.
Uninstall the bridge service
Section titled “Uninstall the bridge service”On the bridge’s machine, first remove the CLI’s saved session:
nodelets logoutThen uninstall:
sudo nodelets bridge uninstallThis removes the service and the nodelets executable, and keeps the state directory, with the bridge’s identity and Things, so a reinstall picks up where it left off. To delete the state as well:
sudo nodelets bridge uninstall --purgeAfter --purge the machine has no bridge identity. Running the installer and nodelets bridge register makes it a new bridge with a new ID.