Merge branch 'staging/4.2' into release/4.2

Author: ashvayka

_includes/docs/pe/user-guide/white-labeling.md

@@ -63,13 +63,15 @@ In the "General" tab you can set or change the following options:
 {% endif %}
 
  - Logo height - you can resize the logo;
- - Primary palette - you can customize the background color and font color by choosing one of the suggested UI design options or customizing an existing one;
+ - White labeling allows you to customize the color theme by adjusting the primary and accent palettes to match your desired UI design.
 
-![image](https://img.thingsboard.io/user-guide/white-labeling/primary-palette.png)
+    - Primary palette - you can customize the background color and font color by choosing one of the suggested UI design options or customizing an existing one;
 
- - Accent palette - you can customize the color for some elements, for example for a toggle;
+    ![image](https://img.thingsboard.io/user-guide/white-labeling/primary-palette.png)
 
-![image](https://img.thingsboard.io/user-guide/white-labeling/accent-palette.png)
+    - Accent palette - you can customize the color for some elements, for example for a toggle;
+
+    ![image](https://img.thingsboard.io/user-guide/white-labeling/accent-palette.png)
 
  - Advanced CSS - you can stylize any elements of the ThingsBoard user interface as you wish. We will talk more about this functionality [below](#advanced-css);
  - Show/hide platform name and version - by checking this option, the name of the platform and its current version will be displayed in the lower left corner.

_includes/docs/user-guide/attributes.md

@@ -34,7 +34,8 @@ This make it easy to write custom JS functions for data processing and visualiza
 
 ## Attribute types
 
-There are three types of attributes. Let's review them with examples:
+ThingsBoard supports three types of attributes: **server-side**, **shared**, and **client-side**.
+Each type has a specific purpose, access rules, and use cases, which we explain below.
 
 ### Server-side attributes
 
@@ -108,10 +109,20 @@ As an alternative to curl, you may use [Java](/docs/{{docsPrefix}}reference/rest
 
 ### Shared attributes
 
-This type of attributes is available only for Devices. It is similar to the Server-side attributes but has one important difference. 
-The device firmware/application may request the value of the shared attribute(s) or subscribe to the updates of the attribute(s).
-The devices which communicate over MQTT or other bi-directional communication protocols may subscribe to attribute updates and receive notifications in real-time.
-The devices which communicate over HTTP or other request-response communication protocols may periodically request the value of shared attribute.
+Shared attributes are available only for entities of type Device. It is not available for any other entity types, such as Assets or Customers. They are designed to send configuration or operational parameters such as *thresholds* from the server to the device.
+
+#### How Devices Interact with Shared Attributes
+
+A device cannot publish or change the value of a shared attribute. From the device's perspective, these attributes are read-only. A device's firmware or application can interact with shared attributes in the following ways:
+* Request Current Values: The device can send a request to the server to retrieve the current value(s) of one or more shared attributes.
+* Subscribe to Updates: The device can subscribe to receive notifications whenever a shared attribute's value is changed on the server.
+* Receive Updates via Downlinks: For certain network integrations, shared attribute updates can be pushed to the device as a [downlink message](/docs/user-guide/integrations/#example).
+
+#### Communication Protocol Examples
+
+The method for receiving updates typically depends on the communication protocol used by the device:
+* Real-time Subscriptions (e.g., MQTT): Devices that use bi-directional protocols like [MQTT](/docs/{{docsPrefix}}reference/mqtt-api/#attributes-api) can subscribe to attribute updates and receive notifications in real-time as soon as a value changes.
+* Periodic Polling (e.g., HTTP): Devices that use request-response protocols like [HTTP](/docs/{{docsPrefix}}reference/http-api/#attributes-api) can periodically poll the server to fetch the latest values of their shared attributes.
 
 {:refdef: style="text-align: center;"}
 ![image](https://img.thingsboard.io/user-guide/shared-attributes.svg)
@@ -121,7 +132,7 @@ The most common use case of shared attributes is to store device settings.
 Let's assume the same building monitoring solution and review few examples:
 
 1. The *targetFirmwareVersion* attribute may be used to store the firmware version for particular Device.
-2. The *maxTemperature* attribute may be used to automatically enable HVAC if it is too hot in the room. 
+2. Devices can monitor the *maxTemperatureThreshold* attribute and activate cooling if the temperature exceeds the set limit.
 
 The user may change the attribute via UI. The script or other server-side application may change the attribute value via REST API.
 
@@ -202,7 +213,7 @@ Let's assume the same building monitoring solution and review few examples:
 2. The *currentConfiguration* attribute may be used to report current firmware/application configuration to the platform.
 3. The *currentState* may be used to persist and restore current firmware/application state via network, if device does not have the persistent storage.
 
-The user and server-side applications may browser the client-side attributes via UI/REST API but they are not able to change them. 
+The user and server-side applications may browse the client-side attributes via UI/REST API but they are not able to change them. 
 Basically, the value of the client-side attribute is read-only for the UI/REST API.
 
 #### Fetch client-side attributes via REST API

_includes/docs/user-guide/dashboards.md

@@ -503,7 +503,7 @@ To make a dashboard private again, follow these steps:
 {% capture difference %}
 **Please note:**
 <br>
-that you shouldn't forget to make related devices, assets and entity views public in order to access their data.
+To display data on a public dashboard, the associated entities must also be made public. This can be done by making the device or asset group public for Professional Edition or by making individual devices or assets for Community Edition.
 {% endcapture %}
 {% include templates/info-banner.md content=difference %}
 

_includes/templates/iot-gateway/remote-creating-connector-modbus.md

@@ -56,7 +56,7 @@ This section offers slave adding and detailed connection configuration options t
 | Unit ID           | 1                    |
 | Device name       | Demo Device          |
 | Device profile    | default              |
-| ---               
+| ---               |                      |
 
 {% assign addNewSlave = '
     ===
@@ -76,12 +76,15 @@ Let's configure attribute section using the following steps:
 
 - Click on "**pencil**" icon in the "**Attributes**" section;
 - In the opened window, click on "**Add attribute**" button;
-- Fill in the fields: 
+- Fill in the fields:
   - Fill the "**Key**" field with "**frequency**";
-  - Select the "**Type**" field to "**8int**";
-  - Select the "**Function code**" to "**04 - Read Input Registers**";
+  - Select the "**Type**" field to "**16int**";
+  - Select the "**Function code**" to "**03 - Read Multiple Holding Registers**";
   - Set "**Objects count**" to "**1**";
-  - Set "**Address**" field to "**4**".
+  - Set "**Address**" field to "**3**".
+  - Enable the "**Modifier**" toggle;
+  - In the "**Modifier**" section, set the "**Type**" field to "**divider**";
+  - In the "**Modifier**" section, set the "**Value**" field to "**10**".
 
 {% assign attributeConfiguration1 = '
     ===
@@ -100,21 +103,23 @@ Let's configure attribute section using the following steps:
 
 Let's add another attribute. Collapse the recently added "frequency" attribute, click the "**Add attribute**" button, and fill in the fields with the following values, using the same process as before:
 
-| **Field name** | **Value**   |
-|:---------------|:------------|
-| Key            | power       |
-| Type           | 16float     |
-| Function code  | 4           |
-| Objects count  | 1           |
-| Address        | 8           |
-| ---            
+| **Field name** | **Value** |
+|:---------------|:----------|
+| Key            | power     |
+| Type           | 16int     |
+| Function code  | 3         |
+| Objects count  | 1         |
+| Address        | 2         |
+| Modifier       | Divider   |
+| Modifier Value | 10        |
+| ---            |           |
 
 Click the "**Apply**" button after you've completed the "**Attributes**" section configuration.
 
 {% assign attributeConfiguration2 = '
     ===
         image: https://img.thingsboard.io/gateway/dashboard/slave-configuration-4-ce.png,
-        title: Collapse the recently added "frequency" attribute, and click "**Add attribute**" button to add another attribute;
+        title: Collapse the recently added "**frequency**" attribute, and click "**Add attribute**" button to add another attribute;
     ===
         image: https://img.thingsboard.io/gateway/dashboard/slave-configuration-5-ce.png,
         title: Fill in the fields with values taken from the documentation. Then, click "**Apply**".
@@ -131,10 +136,13 @@ Let's configure time series section using the following steps:
 - In the opened window, click on "**Add time series**" button;
 - Fill in the fields:
   - Fill the "**Key**" field with "**humidity**";
-  - Select the "**Type**" field to "**8uint**"; 
-  - Select the "**Function code**" to "**04 - Read Input Registers**";
+  - Select the "**Type**" field to "**16int**"; 
+  - Select the "**Function code**" to "**03 - Read Multiple Holding Registers**";
   - Set "**Objects count**" to "**1**"; 
-  - Set "**Address**" field to "**4**".
+  - Set "**Address**" field to "**1**".
+  - Enable the "**Modifier**" toggle;
+  - In the "**Modifier**" section, set the "**Type**" field to "**divider**";
+  - In the "**Modifier**" section, set the "**Value**" field to "**10**".
 
 {% assign timeSeriesConfiguration1 = '
     ===
@@ -156,11 +164,13 @@ Let's add another time series. Collapse the recently added "**humidity**" ti
 | **Field name** | **Value**   |
 |:---------------|:------------|
 | Key            | temperature |
-| Type           | 16uint      |
-| Function code  | 4           |
+| Type           | 16int       |
+| Function code  | 3           |
 | Objects count  | 1           |
-| Address        | 8           |
-| ---            
+| Address        | 0           |
+| Modifier       | Divider     |
+| Modifier Value | 10          |
+| ---            |             |
 
 {% assign timeSeriesConfiguration2 = '
     ===
@@ -210,6 +220,9 @@ You can view the synchronization status of the connector configuration in the "*
 
 Also, you can see the connector logs to make sure that the connector works, for this purpose, follow these steps:
 {% assign seeConnectorLogs = '
+    ===
+        image: https://img.thingsboard.io/gateway/dashboard/gateway-getting-started-modbus-logs-14-ce.png,
+        title: In the "**General**" connector tab enable remove logging by turning on the "**Enable remote logging**" toggle. Choose "**DEBUG**" in the "**Log level**" drop-down menu. Click on the "**Save**" button to apply changes;
     ===
         image: https://img.thingsboard.io/gateway/dashboard/gateway-getting-started-modbus-12-ce.png,
         title: Click on "**logs**" icon to open connector logs page;