Release 10.11.0.38
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | Fixed an issue where users could not find a location on the map based on the address they entered. | MTM-49644 |
| Device Management | In case of many active alarms of different severities, in the "Active critical alarms" widget users might have needed to press the Load more button several times on an empty list in order to see their active critical alarms. This is now fixed - the widget always initially shows active critical alarms if available and the Load more button does not load empty pages. | DM-1646 |
Release 10.11.0.37
Fixes
| Component | Description | Issue |
|---|---|---|
| Cloud Remote Access | Fixed an issue that prevented copying the Cloud Remote Access credentials when the Management tenant was not subscribed to the microservice. | MTM-46818 |
Release 10.11.0.36
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.11.0.33
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.11.0.32
Fixes
| Component | Description | Issue |
|---|---|---|
| OPC UA | The nodes of the OPC UA server address space contain hierarchical references that are used by the opcua-device-gateway to traverse the address space tree during the address space scans. The partial address space scans used to require the inverse hierarchical direction for the start node and its parent nodes. Now partial scan also works when the start node or its parent nodes do not contain the inverse hierarchical references.
Moreover, for better troubleshooting during scans debug/trace logs have been added to all opcua-device-gateway address space scanners. For more details on how to enable them, see OPCUA > Troubleshooting in the Protocol integration guide. |
DM-1008 |
Release 10.11.0.31
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | Fixed an issue with saving data in the "Device data" widget where the LPWAN device > Provisioned item was rendered as a text field. Now it is rendered as a checkbox and the data can be saved correctly. | MTM-45040 |
Release 10.11.0.28
Improvements
| Component | Description | Issue |
|---|---|---|
| Cloud Remote Access | The configuration of the Cloud Remote Access password and salt has been moved to the per tenant microservice settings credentials.encryption.password and credentials.encryption.salt. If Cloud Remote Access has been used before on the tenant and the tenant has devices with Cloud Remote Access configuration, these settings will be added automatically. |
MTM-45176 |
| MQTT | The performance of the MQTT subscribe and unsubscribe operations has been significantly improved. This will improve the device reconnection performance for all MQTT devices and will have a particular impact where a large number of devices are re-connecting at the same time. | MTM-44939 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Cloud Remote Access | Fixed an issue that prevented copying the Cloud Remote Access credentials when the Management tenant was not subscribed to the microservice. | MTM-46115|
| LWM2M | Cumulocity IoT LWM2M now ignores invalid FOTA status reports when they're not expected to be sent by the device. Corresponding FOTA operations are not failed anymore. | DM-939 |
| LWM2M | The LWM2M agent now accepts the resources of type TIME for creating measurements if the resource's value can be converted to an integer value. | DM-913 |
Release 10.11.0.26
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.11.0.25
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | For devices having the c8y_Firmware, c8y_Software/c8y_SoftwareList, or c8y_Configuration fragment the device details tabs Firmware, Software, or Configuration are now displayed even if devices do not support the respective operations. In this case creating install/update operations is not possible via UI. |
MTM-45139 |
| LWM2M | A subscribed LWM2M decoder microservice was still visible under LWM2M Resource > Custom actions after the microservice had been unsubscribed but not deleted. This issue is now resolved. When you unsubscribe the LWM2M decoder microservice, it is no longer accessible as a custom action until you subscribe to this service again. | MTM-41435 |
| SmartREST | In custom SmartREST 2.0 response templates that parse array parameters, only the first element was escaped when control characters were used. We now ensure that all returned array elements are escaped when necessary. | MTM-44498 |
Release 10.11.0.24
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | In the Logs tab of the device details, operations are now sorted descending by creation date, displaying newest operations on top. Scrolling down through the list allows to load and see older operations. | MTM-44461 |
Release 10.11.0.23
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | An issue has been fixed which had the same devices show up repeatedly in the search result view. Now the results are correctly paged. | MTM-44398 |
| Device Management | A missing tooltip has been added with information on how to provide a file path when adding a new configuration object to the configuration repository. | MTM-44752 |
Release 10.11.0.22
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | When searching matches for all device types for a server address space, the opcua-device-gateway used to iterate if multiple device types existed that returned the same result. This situation is prevented now to run only once for the server. | MTM-43595 |
| Device Management | An issue with the Connectivity tab has been fixed, which prevented that users with read-only access to a given device could load the device details. | DM-627 |
Release 10.11.0.19
Improvements
| Component | Description | Issue |
|---|---|---|
| MQTT | The processing of the MQTT "last will" message is now done asynchronously. This improves the performance of "device disconnected" events and the concurrency of handling new MQTT connections. | MTM-44058 |
Release 10.11.0.17
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | The LWM2M agent operation handler now handles a Californium library's connector error by setting the operation back to pending state to process the operation later on. This kind of error can happen when sending an operation to a device and there is no longer a DTLS connection with the URI that is used. | MTM-43663 |
| LWM2M | String resources can now again be mapped into measurement values, that is the LWM2M agent accepts numeric (integer and float) values sent as a string. In addition also the following strings will be treated as numeric values:
- Any positive or negative numeric sequence with leading 0 (zero) will be interpreted as octal value, but will be transformed and stored as a decimal number - Any positive or negative alphanumeric sequence containing letters from A to F, starting with 0x will be interpreted as hex value, but will be transformed and stored as a decimal number Strings which do not meet these requirement won't be processed and an error message will be logged. See also LWM2M > Overview in the Protocol integration guide. |
MTM-43661 |
Release 10.11.0.16
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | On smaller screens, the configuration preview box was hiding the Save to repository and Download buttons on the Configuration tab of the device details view. The layout of the view has been adjusted so that the preview box does not extend too much on smaller screens. | MTM-42949 |
Release 10.11.0.12
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | When a LWM2M device registration update comes with a different port or address than the previous registration, for example the LWM2M registration update comes with a new COAP port due to the load balancer's idle timeout being exceeded, all ongoing operations that are not finished meanwhile will be set back to PENDING state, instead of directly canceling them. | MTM-41981 |
| LWM2M | The resourceValue fragment added to events and alarms now works with opaque resources. Measurements cannot be created with opaque resource values. If enabled, it will create a warning alarm if non-numeric/non-Boolean values are received. Additionally, the type for no-mapping-known alarms has been improved by including the object ID. See also LWM2M > LWM2M device protocols in the Protocol integration guide. | MTM-41682 |
Release 10.11.0.8
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.11.0.4
Improvements
| Component | Description | Issue |
|---|---|---|
| Actility LoRa | Information has been added to the documentation on the significance of device profiles in the Device registration screen. See Actility LoRa > Registering LoRa devices in the Protocol integration guide. | MTM-39119 |
| Connectivity | The Connectivity microservice has been extended with a cache for data from the configured connectivity provider to prevent timeout issues. The cache duration can be configured in seconds along with the regular SIM provider settings in the Administration application under Settings > Connectivity. | MTM-38819 |
| Device Management | The Info tab for groups has been removed. Its content is now available in the Subassets tab. | MTM-39743 |
| Device Management | To improve usability, a tooltip has been added with information on how to provide a file path when adding a new firmware, software or configuration object to the corresponding repositories. | MTM-39747 |
| LWM2M | If a device is not connected/offline or an execution fails, a log entry in the event stream will be created now. | MTM-33372 |
| OPC UA | Improved the handling of device types for subscriptions: An unnecessary check against the value attribute was removed. | MTM-40447 |
| OPC UA | The OPC UA device gateway now correctly handles updates to the alarm status mapping information persisted in the managed object in the platform at the time of reconnect. | MTM-39955 |
| OPC UA | Prosys Client SDK dependency has been upgraded to version 4.5.8.
To avoid conflicts due to the dependency change, the opcua-device-gateway process creates the address space local db files with a new filename cumulocity-opcua-server-.
The legacy address space local db files are cleaned up at the start of the opcua-device-gateway process automatically by default. Deletion of the legacy files can be turned off by setting the "gateway.db.addressSpace.legacyCleanup" to false in the .yaml configuration file. |
MTM-39401 |
| Sigfox | The LPWAN tab will now also be shown for Sigfox devices in the device details. This allows a user to change the associated device protocol even after the device registration. | MTM-35234 |
| Sigfox | The generation of the user password for Sigfox callbacks has been improved to align with the Cumulocity IoT password policy guidelines. | MTM-26010 |
| Sigfox | Due to a request limit in the Sigfox platform, the number of health check calls to the Sigfox platform must be optimized. This is addressed by increasing the health check call frequency from 2 mins to 1 hour. When the health is down, the health check frequency is reduced to 5 mins to avoid the waiting period of 1 hour. When the health is up again, then the scheduler is reset to 1 hour again. | MTM-30409 |
| Sigfox | The Sigfox device can now be assigned/transferred to another device type from the LPWAN tab. | MTM-39442 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | Fixed a layout issue in the Firmware/Software pages where text consisting of a single word was not truncated properly. | MTM-39110 |
| LWM2M | LWM2M bootstrap via PSK requires the existence of an external ID, namely c8y_BootstrapPskId. Before, there was an undocumented fallback behavior that allowed for bootstrapping LWM2M devices without this external ID if the device could be found using a corresponding fragment. If bootstrap is now carried out using bootstrap in PSK and the external ID is missing, the external ID is automatically recreated if the device can be found in the inventory. Note that this is a temporary and deprecated reestablishment of the fallback behavior which does not remove the need of the external ID c8y_BootstrapPskId. | MTM-39371 |
| LWM2M | In order to update the values of an attribute associated with any object, instance, or resource, the write attribute command must be used along with attribute nomenclature as specified in the LWM2M 1.0 specification. For example: writeattr /{Object ID}/{ObjectInstance ID}/{ResourceID}?pmin={minimum period}&pmax={maximum period}>={greater than}<={less than}&st={step}. See also LWM2M > Handling LWM2M shell commands in the Protocol integration guide. |
MTM-40674 |
| LWM2M | The attribute C8Y.lwm2m.enableBootstrapPSKFragmentFallback has been added to the agent's default configuration. If enabled, the LWM2M agent will find the bootstrap PSK ID from the fragments ("bootstrap psk_id") if it cannot be found from the external IDs. See LWM2M > Registration of PSK-secured devices in the Protocol integration guide for more information on the fields required for a bootstrap PSK connection. |
MTM-40632 |
| OPC UA | The processing mode set in the OPC UA device protocol is now also applied for the mappings created due to historic read operations with tag type TAG. | MTM-40524 |
| Sigfox | The credentials for the Sigfox integration do no longer expire. To achieve this, a device user credential is now used for the Sigfox callback APIs as passwords for device users do not expire. | MTM-39467 |