thingsboard · ViacheslavKlimov · Aug 6, 2026 · Aug 6, 2026 · Aug 6, 2026
diff --git a/pe/docs/AiChatControllerApi.md b/pe/docs/AiChatControllerApi.md
@@ -7,7 +7,7 @@ object client.create_chat(body: object)  # createChat
 None client.delete_chat(chat_id: UUID)  # deleteChat
 object client.get_chat_messages(chat_id: UUID)  # getChatMessages
 object client.list_chats(chat_type: ChatType)  # listChats
-List[object] client.send_chat_message(chat_id: UUID, x_authorization: str, body: str, accept_language: Optional[str] = None)  # sendChatMessage
+List[object] client.send_chat_message(chat_id: UUID, x_authorization: str, body: object, accept_language: Optional[str] = None)  # sendChatMessage
 None client.update_chat(chat_id: UUID, body: object)  # updateChat
 ```
 
@@ -103,7 +103,7 @@ listChats
 ## send_chat_message
 
 ```python
-List[object] client.send_chat_message(chat_id: UUID, x_authorization: str, body: str, accept_language: Optional[str] = None)
+List[object] client.send_chat_message(chat_id: UUID, x_authorization: str, body: object, accept_language: Optional[str] = None)
 ```
 
 **POST** `/api/ai/chats/{chatId}/messages`
@@ -117,7 +117,7 @@ sendChatMessage
 |------------- | ------------- | ------------- | -------------|
 | **chat_id** | **UUID** |  | |
 | **x_authorization** | **str** |  | |
-| **body** | **str** |  | |
+| **body** | **object** |  | |
 | **accept_language** | **str** |  | [optional] |
 
 ### Return type

diff --git a/pe/docs/AlarmControllerApi.md b/pe/docs/AlarmControllerApi.md
@@ -370,7 +370,7 @@ Alarm client.save_alarm(alarm: Alarm)
 
 Create or Update Alarm (saveAlarm)
 
-Creates or Updates the Alarm. When creating alarm, platform generates Alarm Id as [time-based UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier#Version_1_(date-time_and_MAC_address)). The newly created Alarm id will be present in the response. Specify existing Alarm id to update the alarm. Referencing non-existing Alarm Id will cause 'Not Found' error.   Platform also deduplicate the alarms based on the entity id of originator and alarm 'type'. For example, if the user or system component create the alarm with the type 'HighTemperature' for device 'Device A' the new active alarm is created. If the user tries to create 'HighTemperature' alarm for the same device again, the previous alarm will be updated (the 'end_ts' will be set to current timestamp). If the user clears the alarm (see 'Clear Alarm(clearAlarm)'), than new alarm with the same type and same device may be created. Remove 'id', 'tenantId' and optionally 'customerId' from the request body example (below) to create new Alarm entity.   Available for users with 'TENANT_ADMIN' or 'CUSTOMER_USER' authority. Security check is performed to verify that the user has 'WRITE' permission for the entity (entities).
+Creates or Updates the Alarm. When creating alarm, platform generates Alarm Id as [time-based UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier#Version_1_(date-time_and_MAC_address)). The newly created Alarm id will be present in the response. Specify existing Alarm id to update the alarm. Referencing non-existing Alarm Id will cause 'Not Found' error.   Platform also deduplicate the alarms based on the entity id of originator and alarm 'type'. For example, if the user or system component create the alarm with the type 'HighTemperature' for device 'Device A' the new active alarm is created. If the user tries to create 'HighTemperature' alarm for the same device again, the previous alarm will be updated (the 'end_ts' will be set to current timestamp). If the user clears the alarm (see 'Clear Alarm(clearAlarm)'), than new alarm with the same type and same device may be created. Remove 'id', 'tenantId' and optionally 'customerId' from the request body example (below) to create new Alarm entity.   The alarm originator is an immutable routing key: when updating an existing alarm, the 'originator' in the request body must match the stored alarm's originator. A request that references an existing alarm id but carries a different originator is treated as a lookup miss and causes a 'Not Found' error.   Available for users with 'TENANT_ADMIN' or 'CUSTOMER_USER' authority. Security check is performed to verify that the user has 'WRITE' permission for the entity (entities).
 
 
 ### Parameters

diff --git a/pe/docs/Dashboard.md b/pe/docs/Dashboard.md
@@ -18,7 +18,7 @@
 | **assigned_customers** | [**List[ShortCustomerInfo]**](ShortCustomerInfo.md) | List of assigned customers with their info. | [optional] |
 | **mobile_hide** | **bool** | Hide dashboard from mobile devices. Useful if the dashboard is not designed for small screens. | [optional] [readonly] |
 | **mobile_order** | **int** | Order on mobile devices. Useful to adjust sorting of the dashboards for mobile applications | [optional] [readonly] |
-| **configuration** | **object** |  | [optional] |
+| **configuration** | **object** | JSON object with main configuration of the dashboard: layouts, widgets, aliases, etc. The JSON structure of the dashboard configuration is quite complex. The easiest way to learn it is to export existing dashboard to JSON. | [optional] |
 | **resources** | [**List[ResourceExportData]**](ResourceExportData.md) |  | [optional] |
 | **version** | **int** |  | [optional] |
 

diff --git a/pe/docs/DashboardInfo.md b/pe/docs/DashboardInfo.md
@@ -18,7 +18,7 @@
 | **assigned_customers** | [**List[ShortCustomerInfo]**](ShortCustomerInfo.md) | List of assigned customers with their info. | [optional] |
 | **mobile_hide** | **bool** | Hide dashboard from mobile devices. Useful if the dashboard is not designed for small screens. | [optional] [readonly] |
 | **mobile_order** | **int** | Order on mobile devices. Useful to adjust sorting of the dashboards for mobile applications | [optional] [readonly] |
-| **configuration** | **object** |  | [optional] |
+| **configuration** | **object** | JSON object with main configuration of the dashboard: layouts, widgets, aliases, etc. The JSON structure of the dashboard configuration is quite complex. The easiest way to learn it is to export existing dashboard to JSON. | [optional] |
 | **resources** | [**List[ResourceExportData]**](ResourceExportData.md) |  | [optional] |
 | **version** | **int** |  | [optional] |
 | **groups** | [**List[EntityInfo]**](EntityInfo.md) | Groups | [optional] |

diff --git a/pe/docs/DeviceProfile.md b/pe/docs/DeviceProfile.md
@@ -242,7 +242,7 @@ A JSON value representing the device profile.
 | epmax | int |  | [optional] |
 
 #### TelemetryObserveStrategy (enum)
-`SINGLE_LEFT_PARENTHESIS_0_RIGHT_PARENTHESIS_COLON__ONE_RESOURCE_EQUALS_ONE_SINGLE_OBSERVE_REQUEST` | `COMPOSITE_ALL_LEFT_PARENTHESIS_1_RIGHT_PARENTHESIS_COLON__ALL_RESOURCES_IN_ONE_COMPOSITE_OBSERVE_REQUEST` | `COMPOSITE_BY_OBJECT_LEFT_PARENTHESIS_2_RIGHT_PARENTHESIS_COLON__GROUPED_COMPOSITE_OBSERVE_REQUESTS_BY_OBJECT`
+`SINGLE` | `COMPOSITE_ALL` | `COMPOSITE_BY_OBJECT`
 
 #### PowerMode (enum)
 `PSM` | `DRX` | `E_DRX`

diff --git a/pe/docs/DeviceProfileData.md b/pe/docs/DeviceProfileData.md
@@ -203,7 +203,7 @@
 | epmax | int |  | [optional] |
 
 #### TelemetryObserveStrategy (enum)
-`SINGLE_LEFT_PARENTHESIS_0_RIGHT_PARENTHESIS_COLON__ONE_RESOURCE_EQUALS_ONE_SINGLE_OBSERVE_REQUEST` | `COMPOSITE_ALL_LEFT_PARENTHESIS_1_RIGHT_PARENTHESIS_COLON__ALL_RESOURCES_IN_ONE_COMPOSITE_OBSERVE_REQUEST` | `COMPOSITE_BY_OBJECT_LEFT_PARENTHESIS_2_RIGHT_PARENTHESIS_COLON__GROUPED_COMPOSITE_OBSERVE_REQUESTS_BY_OBJECT`
+`SINGLE` | `COMPOSITE_ALL` | `COMPOSITE_BY_OBJECT`
 
 #### PowerMode (enum)
 `PSM` | `DRX` | `E_DRX`

diff --git a/pe/docs/DeviceProfileTransportConfiguration.md b/pe/docs/DeviceProfileTransportConfiguration.md
@@ -174,7 +174,7 @@ Configuration for device profile transport
 | epmax | int |  | [optional] |
 
 #### TelemetryObserveStrategy (enum)
-`SINGLE_LEFT_PARENTHESIS_0_RIGHT_PARENTHESIS_COLON__ONE_RESOURCE_EQUALS_ONE_SINGLE_OBSERVE_REQUEST` | `COMPOSITE_ALL_LEFT_PARENTHESIS_1_RIGHT_PARENTHESIS_COLON__ALL_RESOURCES_IN_ONE_COMPOSITE_OBSERVE_REQUEST` | `COMPOSITE_BY_OBJECT_LEFT_PARENTHESIS_2_RIGHT_PARENTHESIS_COLON__GROUPED_COMPOSITE_OBSERVE_REQUESTS_BY_OBJECT`
+`SINGLE` | `COMPOSITE_ALL` | `COMPOSITE_BY_OBJECT`
 
 #### SnmpCommunicationSpec (enum)
 `TELEMETRY_QUERYING` | `CLIENT_ATTRIBUTES_QUERYING` | `SHARED_ATTRIBUTES_SETTING` | `TO_DEVICE_RPC_REQUEST` | `TO_SERVER_RPC_REQUEST`

diff --git a/pe/docs/EntityGroupControllerApi.md b/pe/docs/EntityGroupControllerApi.md
@@ -929,16 +929,16 @@ None client.share_entity_group_to_child_owner_user_group(entity_group_id: str, u
 
 Share the Entity Group with User group (shareEntityGroupToChildOwnerUserGroup)
 
-Share the entity group with specified user group using specified role.   Available for users with 'TENANT_ADMIN' or 'CUSTOMER_USER' authority. Security check is performed to verify that the user has 'WRITE' permission for specified group.
+Share the entity group with the specified user group using the specified role. Unlike the 'shareEntityGroup' API method, this method is designed for sharing 'down' the owner hierarchy and does not require 'WRITE' permission for the shared entity group or the target user group. In particular, it allows the current user to re-share an entity group that was shared with them by the parent owner: for example, a customer user may re-share a tenant-owned dashboard group with a user group of their sub-customer.  The following security checks are performed:  * the target user group must belong to the current user's owner or to one of its sub-customers; * the current user must have the 'SHARE_GROUP' operation granted for the shared entity group: either as a generic permission for the corresponding entity group resource (applies only if the shared entity group belongs to the current user's owner hierarchy), or as a group permission created when the entity group was shared with the current user's user group using a group role that includes the 'SHARE_GROUP' operation; * the specified role must be a group role that is readable by the current user, so it must belong to the current user's owner or to one of its sub-customers; * the operations of the specified role must be a subset of the operations the current user was granted for the shared entity group (always passes if the current user was granted the 'ALL' operation).  If the specified role also includes the 'SHARE_GROUP' operation, the members of the target user group will be able to re-share the entity group further down their own owner hierarchy in the same way.  Available for users with 'TENANT_ADMIN' or 'CUSTOMER_USER' authority.
 
 
 ### Parameters
 
 | Name | Type | Description  | Notes |
 |------------- | ------------- | ------------- | -------------|
-| **entity_group_id** | **str** | A string value representing the Entity Group Id that you would like to share. For example, '784f394c-42b6-435a-983c-b7beff2784f9' | |
-| **user_group_id** | **str** | A string value representing the Entity(User) Group Id that you would like to share with. For example, '784f394c-42b6-435a-983c-b7beff2784f9' | |
-| **role_id** | **str** | A string value representing the Role Id that describes set of permissions you would like to share (read, write, etc). For example, '784f394c-42b6-435a-983c-b7beff2784f9' | |
+| **entity_group_id** | **str** | ID of the entity group to share | |
+| **user_group_id** | **str** | ID of the user group to share the entity group with. The user group must belong to the current user's owner or to one of its sub-customers | |
+| **role_id** | **str** | ID of the group role that defines the set of operations to grant to the target user group | |
 
 ### Return type
 

diff --git a/pe/docs/HomeDashboard.md b/pe/docs/HomeDashboard.md
@@ -18,7 +18,7 @@
 | **assigned_customers** | [**List[ShortCustomerInfo]**](ShortCustomerInfo.md) | List of assigned customers with their info. | [optional] |
 | **mobile_hide** | **bool** | Hide dashboard from mobile devices. Useful if the dashboard is not designed for small screens. | [optional] [readonly] |
 | **mobile_order** | **int** | Order on mobile devices. Useful to adjust sorting of the dashboards for mobile applications | [optional] [readonly] |
-| **configuration** | **object** |  | [optional] |
+| **configuration** | **object** | JSON object with main configuration of the dashboard: layouts, widgets, aliases, etc. The JSON structure of the dashboard configuration is quite complex. The easiest way to learn it is to export existing dashboard to JSON. | [optional] |
 | **resources** | [**List[ResourceExportData]**](ResourceExportData.md) |  | [optional] |
 | **version** | **int** |  | [optional] |
 | **hide_dashboard_toolbar** | **bool** | Hide dashboard toolbar flag. Useful for rendering dashboards on mobile. | [optional] |

diff --git a/pe/docs/Lwm2mDeviceProfileTransportConfiguration.md b/pe/docs/Lwm2mDeviceProfileTransportConfiguration.md
@@ -71,7 +71,7 @@
 | epmax | int |  | [optional] |
 
 #### TelemetryObserveStrategy (enum)
-`SINGLE_LEFT_PARENTHESIS_0_RIGHT_PARENTHESIS_COLON__ONE_RESOURCE_EQUALS_ONE_SINGLE_OBSERVE_REQUEST` | `COMPOSITE_ALL_LEFT_PARENTHESIS_1_RIGHT_PARENTHESIS_COLON__ALL_RESOURCES_IN_ONE_COMPOSITE_OBSERVE_REQUEST` | `COMPOSITE_BY_OBJECT_LEFT_PARENTHESIS_2_RIGHT_PARENTHESIS_COLON__GROUPED_COMPOSITE_OBSERVE_REQUESTS_BY_OBJECT`
+`SINGLE` | `COMPOSITE_ALL` | `COMPOSITE_BY_OBJECT`
 
 #### PowerMode (enum)
 `PSM` | `DRX` | `E_DRX`

diff --git a/pe/docs/PageDataDashboardInfo.md b/pe/docs/PageDataDashboardInfo.md
@@ -32,7 +32,7 @@
 | assigned_customers | List[ShortCustomerInfo] | List of assigned customers with their info. | [optional] |
 | mobile_hide | bool | Hide dashboard from mobile devices. Useful if the dashboard is not designed for small screens. | [optional] [readonly] |
 | mobile_order | int | Order on mobile devices. Useful to adjust sorting of the dashboards for mobile applications | [optional] [readonly] |
-| configuration | object |  | [optional] |
+| configuration | object | JSON object with main configuration of the dashboard: layouts, widgets, aliases, etc. The JSON structure of the dashboard configuration is quite complex. The easiest way to learn it is to export existing dashboard to JSON. | [optional] |
 | resources | List[ResourceExportData] |  | [optional] |
 | version | int |  | [optional] |
 | groups | List[EntityInfo] | Groups | [optional] |

diff --git a/pe/docs/PageDataDeviceProfile.md b/pe/docs/PageDataDeviceProfile.md
@@ -248,7 +248,7 @@
 | epmax | int |  | [optional] |
 
 #### TelemetryObserveStrategy (enum)
-`SINGLE_LEFT_PARENTHESIS_0_RIGHT_PARENTHESIS_COLON__ONE_RESOURCE_EQUALS_ONE_SINGLE_OBSERVE_REQUEST` | `COMPOSITE_ALL_LEFT_PARENTHESIS_1_RIGHT_PARENTHESIS_COLON__ALL_RESOURCES_IN_ONE_COMPOSITE_OBSERVE_REQUEST` | `COMPOSITE_BY_OBJECT_LEFT_PARENTHESIS_2_RIGHT_PARENTHESIS_COLON__GROUPED_COMPOSITE_OBSERVE_REQUESTS_BY_OBJECT`
+`SINGLE` | `COMPOSITE_ALL` | `COMPOSITE_BY_OBJECT`
 
 #### PowerMode (enum)
 `PSM` | `DRX` | `E_DRX`

diff --git a/pe/docs/TelemetryMappingConfiguration.md b/pe/docs/TelemetryMappingConfiguration.md
@@ -36,7 +36,7 @@
 | epmax | int |  | [optional] |
 
 #### TelemetryObserveStrategy (enum)
-`SINGLE_LEFT_PARENTHESIS_0_RIGHT_PARENTHESIS_COLON__ONE_RESOURCE_EQUALS_ONE_SINGLE_OBSERVE_REQUEST` | `COMPOSITE_ALL_LEFT_PARENTHESIS_1_RIGHT_PARENTHESIS_COLON__ALL_RESOURCES_IN_ONE_COMPOSITE_OBSERVE_REQUEST` | `COMPOSITE_BY_OBJECT_LEFT_PARENTHESIS_2_RIGHT_PARENTHESIS_COLON__GROUPED_COMPOSITE_OBSERVE_REQUESTS_BY_OBJECT`
+`SINGLE` | `COMPOSITE_ALL` | `COMPOSITE_BY_OBJECT`
 
 #### LwM2mVersion
 | Name | Type | Description | Notes |

diff --git a/pe/docs/TelemetryObserveStrategy.md b/pe/docs/TelemetryObserveStrategy.md
@@ -3,14 +3,16 @@
 
 `tb_pe_client.models.TelemetryObserveStrategy`
 
+Observation strategy for telemetry. SINGLE (0): one resource equals one single observe request. COMPOSITE_ALL (1): all resources in one composite observe request. COMPOSITE_BY_OBJECT (2): grouped composite observe requests by object.
+
 ## Enum Values
 
 
-* `SINGLE_LEFT_PARENTHESIS_0_RIGHT_PARENTHESIS_COLON__ONE_RESOURCE_EQUALS_ONE_SINGLE_OBSERVE_REQUEST` (value: `'SINGLE (0): One resource equals one single observe request'`)
+* `SINGLE` (value: `'SINGLE'`)
 
-* `COMPOSITE_ALL_LEFT_PARENTHESIS_1_RIGHT_PARENTHESIS_COLON__ALL_RESOURCES_IN_ONE_COMPOSITE_OBSERVE_REQUEST` (value: `'COMPOSITE_ALL (1): All resources in one composite observe request'`)
+* `COMPOSITE_ALL` (value: `'COMPOSITE_ALL'`)
 
-* `COMPOSITE_BY_OBJECT_LEFT_PARENTHESIS_2_RIGHT_PARENTHESIS_COLON__GROUPED_COMPOSITE_OBSERVE_REQUESTS_BY_OBJECT` (value: `'COMPOSITE_BY_OBJECT (2): Grouped composite observe requests by object'`)
+* `COMPOSITE_BY_OBJECT` (value: `'COMPOSITE_BY_OBJECT'`)