From c04eea9889df665ad54f14ad69ccbd04ee58e914 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Tue, 1 Oct 2024 09:48:00 +0200 Subject: [PATCH] Terminology: move devices before entities (#34995) * Terminology: mave devices before entities * Apply suggestions from code review --- source/getting-started/concepts-terminology.markdown | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/getting-started/concepts-terminology.markdown b/source/getting-started/concepts-terminology.markdown index 965c545a48a..56d073be7bb 100644 --- a/source/getting-started/concepts-terminology.markdown +++ b/source/getting-started/concepts-terminology.markdown @@ -20,12 +20,6 @@ For a full list of compatible {% term integrations %}, refer to the [integration Once an {% term integration %} has been added, the hardware and/or data are represented in Home Assistant as [devices and entities](#devices). -## Entities - -Entities are the basic building blocks to hold data in Home Assistant. An {% term entity %} represents a {% term sensor %}, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other {% term entities %}. An {% term entity %} is usually part of a {% term device %} or a {% term service %}. Entities have {% term states %}. - -
Screenshot of the Entities table. Each line represents an entity.
Screenshot of the Entities table. Each line represents an entity.