Relations. Updated docs

_data/docs-home.yml

@@ -9,6 +9,8 @@ toc:
   path: /docs/getting-started-guides/connectivity/
 - title: Key concepts
   section:
+  - title: Key Concepts and Architecture
+    path: /docs/user-guide/entities-and-relations/
   - title: Alarms
     path: /docs/user-guide/alarms/
   - title: Alarm rules
@@ -19,8 +21,8 @@ toc:
     new: true
   - title: Notification center
     path: /docs/user-guide/notifications/
-  - title: Entities and Relations
-    path: /docs/user-guide/entities-and-relations/
+  - title: Relations
+    path: /docs/key-concepts/relations/
   - title: Device profiles
     path: /docs/user-guide/device-profiles/
   - title: Asset profiles

_data/host-constant.yml

@@ -3,15 +3,15 @@
   hostName: localhost
   mqttHostName: localhost
   coapHostName: localhost
-  httpsUrl: https://localhost
+  httpsUrl: http(s)://localhost
   lwm2mHostName: localhost
   apiHostName: localhost
 - tag: pe
   hostLabel: localhost
   hostName: localhost
   mqttHostName: localhost
   coapHostName: localhost
-  httpsUrl: https://thingsboard.cloud
+  httpsUrl: http(s)://localhost
   lwm2mHostName: lwm2m.thingsboard.cloud
   apiHostName: YOUR_SERVER_HOSTNAME
 - tag: paas

_data/paas-eu/docs-home.yml

@@ -43,6 +43,8 @@ toc:
       path: /docs/paas/eu/solution-templates/waste-management/
 - title: Key concepts
   section:
+    - title: Key Concepts and Architecture
+      path: /docs/paas/eu/user-guide/entities-and-relations/
     - title: Alarms
       path: /docs/paas/eu/user-guide/alarms/
     - title: Alarm rules
@@ -53,8 +55,8 @@ toc:
       new: true
     - title: Notification center
       path: /docs/paas/eu/user-guide/notifications/
-    - title: Entities and Relations
-      path: /docs/paas/eu/user-guide/entities-and-relations/
+    - title: Relations
+      path: /docs/paas/eu/key-concepts/relations/
     - title: Device profiles
       path: /docs/paas/eu/user-guide/device-profiles/
     - title: Asset profiles

_data/paas/docs-home.yml

@@ -43,18 +43,19 @@ toc:
       path: /docs/paas/solution-templates/waste-management/
 - title: Key concepts
   section:
+  - title: Key Concepts and Architecture
+    path: /docs/paas/user-guide/entities-and-relations/
   - title: Alarms
     path: /docs/paas/user-guide/alarms/
   - title: Alarm rules
     path: /docs/paas/user-guide/alarm-rules/
   - title: Calculated fields
-    new: true
     path: /docs/paas/user-guide/calculated-fields/
     new: true
   - title: Notification center
     path: /docs/paas/user-guide/notifications/
-  - title: Entities and Relations
-    path: /docs/paas/user-guide/entities-and-relations/
+  - title: Relations
+    path: /docs/paas/key-concepts/relations/
   - title: Device profiles
     path: /docs/paas/user-guide/device-profiles/
   - title: Asset profiles

_data/pages_info.yml

@@ -771,6 +771,9 @@
 "/docs/iot-gateway/what-is-iot-gateway/":
   url: "/docs/iot-gateway/what-is-iot-gateway/"
   redirect_from: []
+"/docs/key-concepts/relations/":
+  url: "/docs/key-concepts/relations/"
+  redirect_from: []
 "/docs/license/search/":
   url: "/docs/license/search/"
   redirect_from: []
@@ -1842,6 +1845,9 @@
 "/docs/paas/eu/":
   url: "/docs/paas/eu/"
   redirect_from: []
+"/docs/paas/eu/key-concepts/relations/":
+  url: "/docs/paas/eu/key-concepts/relations/"
+  redirect_from: []
 "/docs/paas/eu/legacy-subscriptions/":
   url: "/docs/paas/eu/legacy-subscriptions/"
   redirect_from:
@@ -1898,6 +1904,9 @@
   url: "/docs/paas/eu/reference/snmp-api/"
   redirect_from:
   - "/docs/paas/eu/reference/snmp-api"
+"/docs/paas/eu/samples/abeeway/tracker/":
+  url: "/docs/paas/eu/samples/abeeway/tracker/"
+  redirect_from: []
 "/docs/paas/eu/samples/analytics/ai-models/":
   url: "/docs/paas/eu/samples/analytics/ai-models/"
   redirect_from: []
@@ -2407,6 +2416,9 @@
 "/docs/paas/":
   url: "/docs/paas/"
   redirect_from: []
+"/docs/paas/key-concepts/relations/":
+  url: "/docs/paas/key-concepts/relations/"
+  redirect_from: []
 "/docs/paas/legacy-subscriptions/":
   url: "/docs/paas/legacy-subscriptions/"
   redirect_from:
@@ -2463,6 +2475,9 @@
   url: "/docs/paas/reference/snmp-api/"
   redirect_from:
   - "/docs/paas/reference/snmp-api"
+"/docs/paas/samples/abeeway/tracker/":
+  url: "/docs/paas/samples/abeeway/tracker/"
+  redirect_from: []
 "/docs/paas/samples/analytics/ai-models/":
   url: "/docs/paas/samples/analytics/ai-models/"
   redirect_from: []
@@ -3562,6 +3577,9 @@
 "/docs/pe/":
   url: "/docs/pe/"
   redirect_from: []
+"/docs/pe/key-concepts/relations/":
+  url: "/docs/pe/key-concepts/relations/"
+  redirect_from: []
 "/docs/pe/mobile/alarm-dashboard/":
   url: "/docs/pe/mobile/alarm-dashboard/"
   redirect_from: []
@@ -4002,6 +4020,9 @@
 "/docs/pe/releases/roadmap/":
   url: "/docs/pe/releases/roadmap/"
   redirect_from: []
+"/docs/pe/samples/abeeway/tracker/":
+  url: "/docs/pe/samples/abeeway/tracker/"
+  redirect_from: []
 "/docs/pe/samples/analytics/ai-models/":
   url: "/docs/pe/samples/analytics/ai-models/"
   redirect_from: []

_data/pe/docs-home.yml

@@ -41,6 +41,8 @@ toc:
     path: /docs/pe/solution-templates/waste-management/
 - title: Key concepts
   section:
+  - title: Key Concepts and Architecture
+    path: /docs/pe/user-guide/entities-and-relations/
   - title: Alarms
     path: /docs/pe/user-guide/alarms/
   - title: Alarm rules
@@ -51,8 +53,8 @@ toc:
     new: true
   - title: Notification center
     path: /docs/pe/user-guide/notifications/
-  - title: Entities and Relations
-    path: /docs/pe/user-guide/entities-and-relations/
+  - title: Relations
+    path: /docs/pe/key-concepts/relations/
   - title: Device profiles
     path: /docs/pe/user-guide/device-profiles/
   - title: Asset profiles

_includes/docs/key-concepts/relations.md

@@ -0,0 +1,149 @@
+* TOC
+{:toc}
+
+**Relations** in ThingsBoard represent **directed connections between two entities**. They allow you to model real-world relationships (like hierarchy, ownership, or control) in your IoT solution.
+
+A relation has the following properties:
+- A relation connects two entities within the same [Tenant](/docs/{{docsPrefix}}user-guide/ui/tenants/){:target="_blank"}.
+- Each relation has a **direction**: _From_ and _To_.
+- Each relation has a **relation type** (string), for example: _Contains_, _Manages_, _Uses_, _Supports_.
+- You can define **custom relation types** depending on your needs.
+
+## Why Use Relations?
+
+Relations help you model logical and physical connections between entities such as:
+- A building (asset) contains multiple devices. 
+- A customer manages assigned assets and devices. 
+- A gateway device is connected to multiple sensors.
+
+Relations are commonly used for:
+- Representing entity hierarchies (e.g., Customer ⇾ Asset ⇾ Device)   
+- Navigating related entities in dashboards
+- Performing relation-based processing in rule chains
+- Filtering, aggregating, and visualizing data across entity groups
+
+## Relation Direction and Types
+
+<b><font size="4">Direction</font></b>   
+Relations in ThingsBoard are **directional**:
+- **From** – the source entity 
+- **To** – the target entity
+
+Direction is important because most API queries and rule engine operations depend on it to determine which entities are considered parent/child.
+The same relation type behaves differently depending on whether you query relations **from** an entity or **to** an entity.
+
+<b><font size="4">Relation Types</font></b>
+
+Relation types define the meaning of the relationship. Common examples:
+- **Contains** - Entity A contains Entity B (hierarchy)
+- **Manages** - Entity A manages Entity B
+- **Uses** - Entity A uses or depends on Entity B
+- **Supports** - abstract dependency or support relationship
+
+You can create **your own relation types** if needed.
+
+## Creating and Managing Relations
+
+Relations are created and managed in the ThingsBoard UI from the **Relations** tab on the entity details page.
+
+To create a relation:
+1. Open the entity details page.
+2. Navigate to the **Relations** tab.
+3. Select the relation **direction** (**From** or **To**). 
+4. Click the "**+**" button to open the **Add relation** dialog. 
+5. In the dialog, specify the **Relation type** (for example, _Contains_). 
+6. Define the **relation type** and select the **related entity**.
+7. (Optional) Fill in the **Additional info (JSON)** field if additional metadata is required. 
+8. lick **Add** to create the relation.
+
+## How Relations Are Used in ThingsBoard
+
+Relations are widely used across the ThingsBoard platform to build hierarchical models, simplify entity navigation, and implement advanced data processing scenarios.
+
+<b><font size="4">In Dashboards</font></b>
+
+Relations enable dashboards to dynamically resolve and display entities without hardcoding identifiers.   
+They are commonly used in:
+- [Entity aliases](/docs/user-guide/ui/aliases/){:target="_blank"}
+- Dashboard states
+- Widgets that display related entity data (for example, Alarms table)
+
+[Widgets](/docs/{{docsPrefix}}user-guide/widgets/){:target="_blank"} can display alarms, telemetry and attributes from related entities, filter entities based on relationships, visualize hierarchical structures (_Customer_ &#8702; _Assets_ &#8702; _Devices_)
+
+This enables reusable dashboards that adapt automatically to different customers and deployments.
+
+<b><font size="4">In Rule Engine</font></b>
+
+Relations are actively used in the ThingsBoard [Rule Engine](/docs/{{docsPrefix}}user-guide/rule-engine-2-0/overview/){:target="_blank"} to route messages, enrich telemetry, and forward data between related entities.
+
+Common relation-based nodes include: [Check relation presence](/docs/user-guide/rule-engine-2-0/nodes/filter/check-relation-presence){:target="_blank"}, [Related device attributes](/docs/user-guide/rule-engine-2-0/nodes/enrichment/related-device-attributes){:target="_blank"}, [Related entity data](/docs/user-guide/rule-engine-2-0/nodes/enrichment/related-entity-data){:target="_blank"}, [Duplicate to related](/docs/user-guide/rule-engine-2-0/nodes/transformation/duplicate-to-related){:target="_blank"}.
+
+These nodes allow rule chains to validate relations, fetch data from related entities, and propagate messages based on relation direction and type.
+
+<b><font size="4">In Calculated fields</font></b>
+
+Relations can also be used in [Calculated fields](/docs/{{docsPrefix}}user-guide/calculated-fields/){:target="_blank"} to dynamically compute values based on related entities.
+
+Typical use cases include:
+- [Propagation](/docs/user-guide/calculated-fields/propagation-calculated-field){:target="_blank"} – transforming or propagating data to related entities
+- [Related entities aggregation](/docs/user-guide/calculated-fields/related-entities-aggregation-calculated-field){:target="_blank"} – aggregating latest data (min, max, avg, sum, count, etc.) from related entities
+- [Geofencing](/docs/user-guide/calculated-fields/geofencing-calculated-field){:target="_blank"} – detecting enter/exit events relative to related geozones and generating notifications
+
+## API and Tools
+
+Relations can also be created, queried, and deleted programmatically using the ThingsBoard [REST API](/docs/{{docsPrefix}}reference/rest-api/){:target="_blank"}.
+
+A relation is represented as a JSON object containing:
+- **from** (entityType + id)
+- **to** (entityType + id)
+- **type** (the relation name)
+- **typeGroup** (optional categorization)
+- optional **additionalInfo** (custom JSON)
+
+**Example:**
+
+```json
+{
+  "from": {
+    "id": "156c853f-89b1-321b-635j-y8febb2784h4",
+    "entityType": "DEVICE"
+  },
+  "to": {
+    "id": "784f394c-42b6-435a-983c-b7beff2784f9",
+    "entityType": "DEVICE"
+  },
+  "type": "Contains",
+  "typeGroup": "COMMON",
+  "version": 0,
+  "additionalInfo": {}
+}
+```
+
+## Example Hierarchy Using Relations
+
+The following example illustrates how the _Contains_ relation can be used to model a hierarchical structure in ThingsBoard.
+
+In this example:
+- **Region A** is defined as an **Asset**.
+- Region A contains two child assets: **Field A** and **Field B**.
+- Each field contains multiple **Devices**, such as moisture sensors and irrigation systems.
+
+This forms the following hierarchy:
+
+{% if docsPrefix == null %}
+![image](/images/key-concepts/relations-ce.svg)
+{% endif %}
+{% if docsPrefix == "pe/" or docsPrefix contains "paas/" %}
+![image](/images/key-concepts/relations-pe.svg)
+{% endif %}
+
+The _Contains_ relation follows the direction:
+**From (Parent) → To (Child)**
+
+In this case:
+- Region A &#8702; Contains &#8702; Field A 
+- Region A &#8702; Contains &#8702; Field B 
+- Field A &#8702; Contains &#8702; Devices 
+- Field B &#8702; Contains &#8702; Devices
+
+This structure demonstrates how relations are used to model real-world physical or logical hierarchies such as geographic regions, production areas, facilities, or equipment groups.