Merge branch 'staging/4.2' into release/4.2

Author: ashvayka

_includes/docs/user-guide/attributes.md

@@ -138,7 +138,7 @@ The user may change the attribute via UI. The script or other server-side applic
 
 #### Administration UI
 
-{% include images-gallery.html imageCollection="shared-attrs-ui" %}
+{% include images-gallery.html imageCollection="shared-attrs-ui" showListImageTitles="true" %}
 
 {% include templates/info-banner.md content=bulk_provisioning %}
 

_includes/docs/user-guide/ui/devices.md

@@ -36,12 +36,17 @@ Tenant administrators and users with appropriate permissions can create, edit, o
 ### Adding new device
 
 To add a new device:
-- Navigate to **Entities** ⟶ **Devices**. {% unless docsPrefix == null %}By default, you will see the "**All**" asset group.{% endunless %}
+- Navigate to **Entities** ⟶ **Devices**. {% unless docsPrefix == null %}By default, you will see the "**All**" device group.{% endunless %}
 - Click the "**+**" icon in the upper-right corner and select "**Add new device**" from drop-down menu.
 - In the device creation form, fill in the required fields:
     - **Name** – a unique name for the device.
     - **[Device profile](/docs/{{docsPrefix}}user-guide/device-profiles/){:target="_blank"}** – by default, the profile is set to "**default**", but you can choose a different profile if needed.
-- Optional fields such as label or description can be filled in if needed.
+    {% if (docsPrefix == "pe/") or (docsPrefix == "paas/") or (docsPrefix == "paas/eu/") %}
+    - **Owner and groups:** Helps with organization and access control.
+      - **Owner**: Select the owner from the dropdown list. The device will be created at that owner’s level. By default, the field is pre-filled with the Customer or Tenant name based on where you add the device. You can change it before confirming adding.
+      - **Groups**: Optional field. Add the device to existing device groups or create a new one at the selected owner level. Note: every device is automatically added to the "**All**" group of that owner.      
+    {% endif %}
+- Optional fields such as **Label** or **Description** can be filled in if needed.
 - Click "**Add**".
 
 Device successfully created and is now available in the list.
@@ -162,6 +167,11 @@ On the "<b>Devices</b>" page there is an option "<b>Include customer entities</b
 
 {% include images-gallery.html imageCollection="include-customer-entities" showListImageTitles="true" %}
 
+## Share device
+You can share devices by adding them to a device group and then sharing the group with a customer.
+
+For detailed instructions, please see the section on how to [Share device group](#share-device-group).
+
 {% endif %}
 
 {% unless docsPrefix == null %}
@@ -189,7 +199,7 @@ To make the group private again, follow the same steps using the "**Make private
 
 ## Share device group
 
-You can share an device group with one or more customers. This is useful, for example, when multiple customers need access to the same device.
+You can share a device group with one or more customers. This is useful, for example, when multiple customers need access to the same device.
 
 > You cannot share an individual device — only the device group that contains it.
 
@@ -201,6 +211,23 @@ To share an device group:
 - Confirm the action by clicking "**Share**".
 
 {% include images-gallery.html imageCollection="share-device-group" %}
+
+**Managing and Verifying Permissions**
+
+After a device group has been shared, you can view, edit, or revoke permissions at any time.
+
+1. From the "Device groups" list, click on the pencil button of the desired group to open the "Entity group details".
+
+2. Navigate to the Permissions tab.
+
+3. On this tab, you will see a complete list of all permissions granted for this group. Here you can:
+
+- **Add** a new permission: Click the "+" icon in the top right corner of the panel. A dialog window will appear where you can select a role and a user group to grant access to.
+
+- **Edit** an existing permission: Click the pencil icon next to the permission you want to modify.
+
+- **Delete** a permission: Click the trash can icon to remove access for that user group.
+
 {% endunless %}
 
 ## Device details

_includes/docs/user-guide/widgets.md

@@ -409,19 +409,19 @@ In the legend settings, you can:
 
 The legend displays a label for each [data key](/docs/{{docsPrefix}}user-guide/widgets/#data-keys). When a widget contains data from multiple devices, or when several devices use the same data key name (for example, temperature), it may be difficult to determine which key value corresponds to which device in the legend or tooltip.
 
-To make the legend or tooltip clearer, you should use <b>${entityName}</b> or <b>${entityLabel}</b> in the data key configuration.
+To make the legend clearer, you should use **${entityName}** or **${entityLabel}** in the **Label** field of the data key configuration.
 
-- <b>${entityName}</b> – a variable that automatically inserts the system name of the entity in the legend or tooltip. This helps clearly identify the object, especially when its technical name or unique identifier is important.   
-  Example: If a device has the name <b>sensor-101</b>, then in the field where <b>${entityName}</b> is used, you will see <b>sensor-101</b>.
+- **${entityName}** – a variable that automatically inserts the system name of the entity in the legend. This helps clearly identify the object, especially when its technical name or unique identifier is important.   
+  Example: If a device has the name **sensor-101**, then in the field where **${entityName}** is used, you will see **sensor-101**.
 
 {% include images-gallery.html imageCollection="entity-name-legend" %}
 
-- <b>${entityLabel}</b> – a variable that inserts the entity&#39;s label in the legend or tooltip.. This is often used as a human-readable label and allows you to display a more descriptive name of the device or entity.   
+- **${entityLabel}** – a variable that inserts the entity's label in the legend. This is often used as a human-readable label and allows you to display a more descriptive name of the device or entity.   
    Example: A device has:
-    - <b>Name</b> = <b>sensor-101</b>
-    - <b>Label</b> = <b>Temperature Sensor, Warehouse #1</b>
+    - **Name** = **sensor-101**
+    - **Label** = **Temperature Sensor, Warehouse #1**
 
-    In the field where <b>${entityLabel}</b> is used, the operator will see the more understandable text: <b>Temperature Sensor, Warehouse #1</b>.
+    In the field where **${entityLabel}** is used, the operator will see the more understandable text: **Temperature Sensor, Warehouse #1**.
 
 {% include images-gallery.html imageCollection="entity-label-legend" %}
 
@@ -466,7 +466,23 @@ You can change the appearance of the chart grid: customize the color of the back
 
 - **Show cumulative values in stacking mode**. While stacking mode is on, you can check the box "Cumulative values" to enable your chart to display sum of all entity values.
 
-**Tooltip value format function, f(value, latestData)** is used when you want to manually customize the tooltip.
+Tooltip value format function, **f(value, latestData)** is used when you want to manually customize the tooltip.
+
+To make the tooltip clearer, you should use **${entityName}** or **${entityLabel}** in the **Label** field of the data key configuration.
+
+- **${entityName}** – a variable that automatically inserts the system name of the entity in the tooltip. This helps clearly identify the object, especially when its technical name or unique identifier is important.   
+  Example: If a device has the name **Sensor 1**, then in the field where **${entityName}** is used, you will see **Sensor 1**.
+
+{% include images-gallery.html imageCollection="entity-name-tooltip" %}
+
+- **${entityLabel}** – a variable that inserts the entity's label in the tooltip. This is often used as a human-readable label and allows you to display a more descriptive name of the device or entity.   
+   Example: A device has:
+    - **Name** = **Sensor 1**
+    - **Label** = **Sensor 1 Label**
+
+    In the field where **${entityLabel}** is used, the operator will see the more understandable text: **Sensor 1 Label**.
+
+{% include images-gallery.html imageCollection="entity-label-tooltip" %}
 
 You can customize the values that will be displayed in the tooltip via tooltip settings or
 [Advanced Data key configuration](/docs/{{docsPrefix}}user-guide/ui/advanced-data-key-configuration/#tooltip-settings){:target="_blank"}.

_includes/templates/iot-gateway/bacnet-connector/examples/shared-attributes-and-rpc/attribute-updates.md

@@ -11,22 +11,22 @@ Let’s add an attribute update to our configuration. For this purpose, follow t
 
 {% assign attributeUpdates = '
     ===
-        image: /images/gateway/bacnet-connector/examples/select-created-gateway.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/select-created-gateway.png,
         title: Go to "**Entities**" → "**Gateways**" in the left sidebar and select your gateway.
     ===
-        image: /images/gateway/bacnet-connector/examples/select-connector-configuration.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/select-connector-configuration.png,
         title: Click on the "**Connectors configuration**" button on the right side menu.
     ===
-        image: /images/gateway/bacnet-connector/examples/select-device-configuration.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/select-device-configuration.png,
         title: Select the created BACnet connector and click on the "**Devices**" tab. Make sure you have configured and connected device (if you don’t know how to do it, see [Application settings](/docs/iot-gateway/config/bacnet/#application) and [Data mapping](/docs/iot-gateway/config/bacnet/#data-mapping) sections of this guide). Click on the “**Pencil**” icon on a device you want to configure attribute updates for.
     ===
-        image: /images/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-1.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-1.png,
         title: Scroll down to the “**Attribute updates**” section and click on the “**Pencil**” icon to edit the attribute updates.
     ===
-        image: /images/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-2.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-2.png,
         title: Click on the “**Add attribute update**” button. In our case, we will add `relay` attribute update, so the “**Key**” field, enter `relay`, select the “**Object ID**” as **Analog Input** and "**1**", "**Property ID**" as "**Present Value**".
     ===
-        image: /images/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-3.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-3.png,
         title: Remember to save your changes by clicking the “**Apply**” button and click save connector configuration button.
 '
 %}
@@ -39,9 +39,9 @@ with type "**Boolean**" set it to "**True**".
 
 {% assign attributeUpdates2 = '
     ===
-        image: /images/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-4.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-4.png,
     ===
-        image: /images/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-5.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-5.png,
 '
 %}
 
@@ -50,7 +50,7 @@ with type "**Boolean**" set it to "**True**".
 Now, let’s check the value of the relay Object ID. In the selected device, go to the "**Last telemetry**" tab and 
 check the value of the `relay` telemetry. It should be `true` since we set the shared attribute to `true`.
 
-![image](/images/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-6.png)
+![image](https://img.thingsboard.io/gateway/bacnet-connector/examples/connector-configuration-attribute-updates-6.png)
 
 Try to change the value of the `relay` shared attribute to `false`. After a few seconds, you should see that the
 `relay` telemetry value has changed to `false`, which means that the attribute update worked correctly.

_includes/templates/iot-gateway/bacnet-connector/examples/shared-attributes-and-rpc/reserved-rpc.md

@@ -29,7 +29,7 @@ Response:
 {"result": {"value":  "inactive"}}
 ```
 
-![image](/images/gateway/bacnet-connector/examples/reserved-rpc-result-1.png)
+![image](https://img.thingsboard.io/gateway/bacnet-connector/examples/reserved-rpc-result-1.png)
 
 So, the `GET` method returns the current value of the relay, and we can see that the relay is off.
 
@@ -52,7 +52,7 @@ Response:
 
 And as you can see, from the screenshot below, the relay telemetry value has changed to `1`:
 
-![image](/images/gateway/bacnet-connector/examples/reserved-rpc-result-2.png)
+![image](https://img.thingsboard.io/gateway/bacnet-connector/examples/reserved-rpc-result-2.png)
 
 Also, let’s check the value of the relay telemetry again:
 
@@ -66,7 +66,7 @@ Response:
 {"result": {"value":  "active"}}
 ```
 
-![image](/images/gateway/bacnet-connector/examples/reserved-rpc-result-3.png)
+![image](https://img.thingsboard.io/gateway/bacnet-connector/examples/reserved-rpc-result-3.png)
 
 Full configuration for BACnet connector for the examples above will look like this 
 (**make sure to use the right device host and port**):

_includes/templates/iot-gateway/bacnet-connector/examples/shared-attributes-and-rpc/rpc-to-device.md

@@ -7,22 +7,22 @@ we need to configure the BACnet connector to support RPC calls. For this purpose
 
 {% assign rpcToDevice = '
     ===
-        image: /images/gateway/bacnet-connector/examples/select-created-gateway.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/select-created-gateway.png,
         title: Go to "**Entities**" → "**Gateways**" in the left sidebar and select your gateway.
     ===
-        image: /images/gateway/bacnet-connector/examples/select-connector-configuration.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/select-connector-configuration.png,
         title: Click on the "**Connectors configuration**" button on the right side menu.
     ===
-        image: /images/gateway/bacnet-connector/examples/select-device-configuration.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/select-device-configuration.png,
         title: Select the created BACnet connector and click on the "**Devices**" tab. Make sure you have configured and connected device (if you don’t know how to do it, see [Application settings](/docs/iot-gateway/config/bacnet/#application) and [Data mapping](/docs/iot-gateway/config/bacnet/#data-mapping) sections of this guide). Click on the “**Pencil**” icon on a device you want to configure attribute updates for.
     ===
-        image: /images/gateway/bacnet-connector/examples/rpc-to-device-1.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/rpc-to-device-1.png,
         title: Scroll down to the "**RPC methods**" section and click on the "**Pencil**" icon to edit the RPC methods.
     ===
-        image: /images/gateway/bacnet-connector/examples/rpc-to-device-2.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/rpc-to-device-2.png,
         title: Click on the "**Add method**" button. Fill in the "**Method**" field with `getTemperature`, select the "**Request Type**" as "**Read Property**", "**Object ID**" as "**Analog Value**" and "**1**", and "**Property ID**" as "**Present Value**".
     ===
-        image: /images/gateway/bacnet-connector/examples/rpc-to-device-3.png,
+        image: https://img.thingsboard.io/gateway/bacnet-connector/examples/rpc-to-device-3.png,
         title: Remember to save your changes by clicking the "**Apply**" button and click save connector configuration button.
 '
 %}
@@ -38,7 +38,7 @@ getTemperature
 
 Response:
 
-![image](/images/gateway/bacnet-connector/examples/rpc-to-device-4.png)
+![image](https://img.thingsboard.io/gateway/bacnet-connector/examples/rpc-to-device-4.png)
 
 {% capture difference %}
 The RPC Debug Terminal is used only for example purpose, so you can use any other widget that supports RPC calls.

_includes/templates/iot-gateway/bacnet-connector/examples/time-series-and-attributes/discovering-all-device.md

@@ -92,4 +92,4 @@ messages from all devices. After receiving the IAm message, the connector will a
 device found with the specified templates and start reading data from the objects. The screenshot below shows what the 
 device list looks like after automatic discovery:
 
-![image](/images/gateway/bacnet-connector/examples/discovered-devices-overview.png)
+![image](https://img.thingsboard.io/gateway/bacnet-connector/examples/discovered-devices-overview.png)

_includes/templates/iot-gateway/bacnet-connector/examples/time-series-and-attributes/reading-all-device-objects.md

@@ -50,4 +50,4 @@ be read.
 After saving the changes and starting the connector, you can see that the corresponding device has been added to the 
 platform, and its telemetry has started to fill with all the device objects:
 
-![image](/images/gateway/bacnet-connector/examples/device-objects-overview.png)
+![image](https://img.thingsboard.io/gateway/bacnet-connector/examples/device-objects-overview.png)