Devices & Services

Configuration > Devices & Services is the hub every integration below hangs off. A card only shows up once that integration actually has a configured device - a fresh install starts with the page empty, not ten cards to dismiss.

Adding an integration

"+ Add integration" opens a searchable catalog of everything that isn't configured yet - brand icon, name, chevron, one row per integration. Picking a row takes you straight to that integration's own page, where its real connect flow lives; an integration only becomes "configured" once that flow actually succeeds; backing out part-way through leaves it right where it was, still listed in the catalog.

Adding a device manually

Most integrations find devices themselves (mDNS, a local network scan, a cloud account lookup) and let you connect straight from a Discovered row. Every integration's own "Configured" page also has a "+ Add device" item in its header menu for typing a device's name, address, and port in by hand instead - useful when discovery doesn't (or can't) find something on your network, or you'd rather skip scanning entirely and connect directly.

Correcting an address

Every device-type detail page shows its own Edit button right next to the Address field. Most integrations that use network discovery try to keep a device's stored address current automatically as it changes - but a device's own discovery responder isn't always reliable (a real case: a device stayed reachable fine by its plain IP address the entire time, while its own mDNS responder simply stopped answering queries). When that happens, nothing automatic can fix it, since there's nothing left to resolve to - Edit lets you type the correct address in directly, and saving it also triggers an immediate reconnect attempt wherever that's safe to do (a TV's own webOS/Tizen page saves the address only, since forcing a reconnect there can pop an on-screen pairing prompt on the TV itself).

What's available today

• ESPHome - live device connections over mDNS/API. Config-file management and dashboard compiles live under their own separate ESPHome builder tile instead (see ESPHome builder) - the two used to share one always-visible sidebar entry; now both are ordinary opt-in integrations here, each hidden until it actually has something configured.
• Presence detection - attach any entity from any integration as an extra occupancy signal for an Area.
• Shelly - Gen2/Gen3 devices over their own local JSON-RPC API.
• MOS - a self-hosted homelab/server OS.
• Unraid - via the Unraid Connect plugin's GraphQL API.
• iRobot - Wi-Fi Connected Roomba vacuums.
• Tuya - Tuya-protocol smart devices, paired via a one-time cloud setup.
• IKEA - DIRIGERA hub, SYMFONISK speakers, and the IDÅSEN desk.
• TVs - LG (webOS), Samsung (Tizen), and Android TV.
• MQTT auto-discovery - any device already speaking the standard MQTT discovery convention.

Every integration here gets the same treatment once connected: entities selectable in Dashboard cards, plots on the History page, and triggers/conditions/actions in Automations - one shared addressing scheme, not a special case per integration. Every device page also gives you a quick look without leaving it: click any entity's own name for a popup showing its current value and a 24h/7d/30d chart, no need to add it to a Dashboard first. Opened from a device's own page, the popup also shows "Area > Device" under the title, and clicking the title bar toggles a wider view of the graph.

The cog-wheel button next to that popup's title opens a small settings screen for that one entity: a custom Name (used everywhere that entity's name is shown - Dashboard cards, History graphs, pickers - once set, falling back to the entity's own real name otherwise), an Icon (stored for future use, not yet shown anywhere), and a Display precision that overrides the app-wide decimal-places default for that one entity, including as the new default the first time you add it to a Dashboard card.

Devices and Entities tabs

Alongside the Integrations catalog above, this page's header also has Devices and Entities tabs, centered the same way the Dashboard page's own tab bar is. Both are built on the same generic entity registry the History page already uses, so every integration shows up automatically with no per-integration setup. Devices lists every device across every integration, alphabetically - clicking one goes straight to its own detail page (or, for the rare source with no per-device page of its own, e.g. MQTT, to that integration's own list page instead). Entities groups the same devices' own entities into an expandable list (expanded by default, one device per section) - clicking an entity opens the exact same quick-history popup described above. Each tab has its own search box (no view toggle or filter on these two - there's nothing to switch or filter on a read-only browse list); every search box on this page, Integrations included, shows how many rows it's searching right in its placeholder, e.g. "Search 20 devices…".

Reordering cards

"Edit mode" (the header's three-dot menu) shows a banner and lets you drag cards into whatever order you'd rather see them in - saved to your own account, not shared with other users signed in to the same install. Any integration can also be pinned straight to the sidebar for one-click access, from the sidebar's own cog-icon edit mode - see Interface overview.

Removing one

Deleting an integration's last configured device removes its real configuration and credentials the same way its own list page's per-row delete always has - the card then disappears from this page the next time it loads, since there's nothing left to consider it configured by.