Home Assistant puts every connected thing into a hierarchy. Once you know how that hierarchy works, adding, renaming, removing and cleaning up devices gets much easier, and the device class settings that confuse many new users start to make sense.
How integrations, devices and entities fit together
Home Assistant organizes hardware in four layers:
- Integration: the connection to a brand, service or protocol, such as TP-Link Smart Home or Zigbee Home Automation (ZHA).
- Config entry: one set-up instance of an integration, such as one bridge, account or hub.
- Device: the physical product, or logical unit, that a config entry creates.
- Entity: one thing you can read or control, such as a light’s switch, its brightness or a temperature reading.
Entity IDs follow the pattern domain.object_id, for example light.kitchen_ceiling. A single device usually has several entities, so “device” and “entity” are not interchangeable. Deleting one entity does not delete the device it belongs to.
Adding an integration
Go to Settings > Devices & services > Add integration and search for the brand or protocol you want. Home Assistant also finds some devices on its own. Those appear under Discovered when they announce themselves on your network, through methods such as zeroconf, SSDP, DHCP, Bluetooth or USB.
If you don’t want a discovered device, you can select Ignore. Ignoring is not deletion, and you can un-ignore the device later to set it up.
Renaming a device can also rename its entity IDs. Read the prompt before you confirm, and check any automations and dashboards that use those entities. If an automation stops firing after a rename, see why your Home Assistant automation isn’t triggering.
How do I remove a device from my devices?
- Go to Settings > Devices & services and select the Devices tab.
- Open the device.
- Under Device info, select the three-dot menu and choose Delete.
- Confirm.
The Delete option only appears when the integration supports removing devices. If it’s missing, work through these options in order:
- Remove the integration entry. For a device that belongs to a standalone integration or hub, removing that entry can clear its devices.
- Use the integration’s own removal tool. ZHA has its own Remove action for Zigbee devices. For Z-Wave, deleting a device in Home Assistant does not exclude it from the network, so you still need an exclusion on the Z-Wave side.
- Clean up orphaned entities. Entities marked as “no longer being provided” can be deleted from their entity settings. Entities without a
unique_idhave to be removed from the YAML that defines them.
Two limits are worth knowing before you start:
- A cloud device you delete in Home Assistant stays in the vendor’s account, and it may reappear when the integration reloads.
- Deleting a Matter device has its own steps and fabric behavior. See how to delete a Matter device from Home Assistant.
Disable or delete?
Disabling an entity stops it from polling and hides it. Re-enabling it reloads the integration entry, which can take about 30 seconds. Disabling is the better choice when you might want the entity back later.
Community members disagree on the habit. Some disable unwanted entities to hide them. Others delete them, because disabled entities remain in the storage files. If you’re sure you’ll never need an entity again, deleting it removes it fully.
What device classes do
A device class (device_class) tells Home Assistant what an entity measures or represents. It sets the default icon, the wording of the state, the units and how dashboards treat the entity. It does not change how the device behaves, and it does not convert or correct readings.
Some examples:
- A
binary_sensorwith thedoorclass shows open or closed. With themotionclass it shows detected or clear. Underneath, the state is stillonoroff. - A
sensorwith thepowerclass uses watts (W), and theenergyclass uses kWh or Wh. - A
coverwith thegarageclass is treated as a garage door.
Other common classes include window, garage_door, moisture, smoke, gas and battery for binary sensors; temperature, humidity, illuminance (lx), voltage and current for sensors; and gate, shade, blind and awning for covers.
Change a device class
- In the UI: open the entity’s settings (the cog icon) and use Show as. Not every entity offers this option.
- In YAML or templates: set
device_class:on the entity or template definition.
Changing a device class does not convert units or fix a wrong reading. If a sensor reports a bad value, check the device and its integration first.
Energy dashboard requirements
The Energy dashboard needs a sensor with the energy device class, a state_class of total or total_increasing, and a unit of kWh or Wh. A power sensor in watts won’t provide the energy totals the dashboard needs. To split those totals into daily or monthly figures, see how to track energy use with the Home Assistant utility meter.
Where to go next
Each brand or protocol has its own guide in this cluster:
- Thermostats and climate devices for ecobee, Nest, Carrier and Dreo.
- Lighting, switches and buttons for Kasa, Govee, Zigbee and Thread.
- Appliances for Roborock, myQ, B-hyve and Bambu Lab.
- TV and wearables for LG webOS, Roku and Fitbit.
- Philips Hue, ZHA vs Zigbee2MQTT, Shelly and Matter pairing.
If you’re shopping for a garage door, start with what garage door opener works with Home Assistant. If a brand has no core integration, a custom integration from HACS, the Home Assistant Community Store may cover it. If you’re moving to new hardware, see how to transfer Home Assistant to a new device.