Release 10.9.0.35
Fixes
| Component | Description | Issue |
|---|---|---|
| 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.9.0.33
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.9.0.31
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.9.0.28
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 |
Release 10.9.0.27
Info
There have been no significant improvements or fixes related to this component since the last Maintenance release.
Release 10.9.0.26
Info
There have been no significant improvements or fixes related to this component since the last Maintenance release.
Release 10.9.0.25
Info
There have been no significant improvements or fixes related to this component since the last Maintenance release.
Release 10.9.0.24
Info
There have been no significant improvements or fixes related to this component since the last Maintenance release.
Release 10.9.0.23
Improvements
| Component | Description | Issue |
|---|---|---|
| LWM2M | The firmware update process will now be automatically cancelled when the firmware update operation is deleted. | MTM-38583 |
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | In order to update the value of attributes associated with any object, instance, or resource, the write attribute command must be used with the desired values. The attributes nomenclature for the shell command has been updated as per the LWM2M 1.0 specification. The attribute greater than must be written as gt instead of greater; less than must be written as lt instead of less, and step as st instead of step. 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 |
Release 10.9.0.21
Info
There have been no significant improvements or fixes related to this component since the last Maintenance release.
Release 10.9.0.20
Info
There have been no significant improvements or fixes related to this component since the last Maintenance release.
Release 10.9.0.18
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | LWM2M bootstrap via PSK requires the existence of an external ID, namely c8y_BootstrapPskId. Before, there was an undocumented fall-back 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 |
Release 10.9.0.17
Info
There have been no significant improvements or fixes related to this component since the last Maintenance release.
Release 10.9.0.16
Improvements
| Component | Description | Issue |
|---|---|---|
| Sigfox | The generation of the user password for Sigfox callbacks has been improved to align with the Cumulocity IoT password policy guidelines. | MTM-26010 |
Release 10.9.0.12
Improvements
| Component | Description | Issue |
|---|---|---|
| Cloud Remote Access | Cloud Remote Access now also works for users that are signed in using single sign-on or two-factor authentication. | MTM-31977 |
| Cloud Remote Access | For Cloud Remote Access connections via SSH, in addition to public/private key pairs, SSH certificates (with DSA and RSA algorithms) can now be provided to authenticate against the target device. | MTM-36001 |
| Device Management | The Configuration tab within the device details for devices that do support simple text-based configuration has been improved. | MTM-33294 |
| Device Management | Improved loading time for the service monitoring view, when managing a large number of devices. | MTM-32460 |
| Device Management | An endpoint has been added to allow filtering of bulk operations by time. For details, see Device control > Bulk operations in the Cumulocity IoT OpenAPI Specification. | MTM-32397 |
| Device Management | In the bulk operation creation dialog, a Title field has been implemented to change the name of the bulk operation. Moreover, a Description field has been added to provide additional information on the bulk operation. See also Device Management > Monitoring and controlling devices > Working with operations in the User guide. | MTM-34920 |
| Device Management | Bulk operations now generate a real-time notification (WebSocket notification) similar to real-time notifications generated for the individual operations. | MTM-33725 |
| Device Management | Bulk operations have been extended with a new property "generalStatus". Possible values for general status are: SCHEDULED, CANCELED, EXECUTING, EXECUTING_WITH_ERROR, FAILED and SUCCESSFUL. For details, see Device control > Bulk operations in the Cumulocity IoT OpenAPI Specification. | MTM-33724 |
| Device Management | An endpoint has been added to allow filtering by one or more bulk operation general statuses. For details, see Device control > Bulk operations in the Cumulocity IoT OpenAPI Specification. | MTM-35298 |
| Device Management | In the Bulk operations tab, the details view of bulk operations now shows the audit log. Moreover, the Audit logs page in the Administration application has a filter type for bulk operations. For details, see Device Management > Monitoring and controlling devices > Working with operations in the User guide. | MTM-34957 |
| Device Management | The Bulk operations tab is now updated in realtime. The Refresh button has been removed. | MTM-34922 |
| Device Management | Devices for bulk operations can now be filtered by group. For details, see Device Management > Monitoring and controlling devices > Working with operations in the User guide. | MTM-31154 |
| Device Management | If a bulk operations fails, the user can now manually set the status to successful. | MTM-35729 |
| Device Management | Devices for bulk operations can now be filtered by groups and subgroups via checkboxes. For details, see Device Management > Monitoring and controlling devices > Working with operations in the User guide. | MTM-34916 |
| Device Management | In the bulk operation creation dialog the link to the documentation has been changed to the User guide which provides the relevant information. | MTM-37221 |
| Device Management | The user experience of the Firmware/Software/Configuration repositories has been improved. It is now possible
- to add a device type on software or firmware creation. - to filter not only by name but also by description or device type. - to install multiple software items at once on a device. Moreover, Firmware/software operation details are displayed in the Software/Firmware tab instead of redirecting to the Control tab. |
MTM-33664 |
| Device Management | To improve performance, the sorting of groups and devices has been changed. The sorting will now be case-sensitive, like for example "AAA BBB CCC aaa bbb..." instead of "aaa AAA bbb CCC ccc...". | MTM-36844 |
| Device monitoring | Devices are now immediately marked as unavailable when the response interval expires. Alarms will be raised after 3 minutes delay to be sure that the state of the devices is synchronized within the database. | MTM-34737 |
| LWM2M | A new parameter, C8Y.lwm2mMaxRequestTimeout, has been introduced to allow the request timeout to be set at the individual device. The default value is 10 minutes. The lwm2mRequestTimeout specified at the device managed object and the global C8Y.lwm2mRequestTimeout should always be less than the C8Y.lwm2mMaxRequestTimeout value. The order in which these timeouts are used is: first lwm2mRequestTimeout and if that is not defined then the global lwm2mRequestTimeout value is used. | MTM-34081 |
| LWM2M | The LWM2M agent creates events with specific event types during the device bootstrap and registration process. Bootstrap event types: c8y_LWM2MDeviceBootstrapStart c8y_LWM2MDeviceBootstrapEnd c8y_LWM2MDeviceBootstrapFailure Registration event types: c8y_LWM2MDeviceRegistration c8y_LWM2MDeviceDeRegistration c8y_LWM2MDeviceRegistrationUpdate |
MTM-33392 |
| LWM2M | The LWM2M device client awake time can now be defined in the device managed object if the device does not send it during registration. Preference is given to the client awake time (awaketimeRegistrationParameter) defined in the device managed object. | MTM-34152 |
| LWM2M | Only the managed object ID will be logged to the log files instead of the whole managed object. | MTM-34994 |
| LWM2M | A new flag "firmwareDeliveryEncoding" has been implemented whose value can be used as the content format during firmware push. By default the content format is OPAQUE. | MTM-34907 |
| LWM2M | The LWM2M agent fails starved LWM2M operations after a certain age (configurable) using a scheduled job (interval also configurable). The mechanism can be turned on an off in the agent configuration. For detail, see LWM2M > LWM2M device details in the Protocol integration guide. | MTM-34214 |
| LWM2M | Added support for old content format codes: TLV (1542) and JSON (1543). | MTM-36250 |
| LWM2M | Improved the documentation within the cumulocity-examples repositories on how to implement custom LWM2M decoders, see https://bitbucket.org/m2m/cumulocity-examples/src/develop/sample-lwm2m-custom-decoder/. | MTM-36391 |
| LWM2M | To improve the user experience, the information in the LWM2M list of device protocols now shows the object ID as part of the title of the LWM2M device type. | MTM-36545 |
| LWM2M | The LWM2M agent now uses non-blocking coap messaging for delivering operations to devices, resulting in a more efficient use of coap threads and a better scalability. | MTM-36529 |
| MQTT | Requests made with JSON via MQTT are counted to the tenant statistics. For details see, Tenants in the Cumulocity IoT OpenAPI Specification. | MTM-34123 |
| OPC UA | The dry run operation now allows the user to determine the set of nodes to which a device protocol would be applied by the gateway. | MTM-32855 |
| OPC UA | Alarms for bad status codes that are populated by the OPC UA device gateway now contain status code information for the alarm type and a text description. | MTM-30482 |
| OPC UA | The JSON validation for the body template in OPC UA device protocols custom actions has been removed. Below the text area, an information text is now available showing the possible placeholders that can be used to pass data into the body. The body template is marked as "required" which means that this field is mandatory. Any validation errors will replace the information text with the validation error message. After fixing the validation error the information text will pop up again. | MTM-34385 |
| OPC UA | When deleting a server from the OPC UA server tab of the device gateway in the Device Management application, which uses the opcua-mgmt-service REST API endpoint and equivalent to DELETE /service/opcua-mgmt-service/servers/{serverId}, the server and its corresponding address space nodes are deleted. However, with this improvement, the devices associated with the server are no longer deleted automatically. | MTM-32857 |
| OPC UA | Bulk cyclic read support has been added for OPC UA. | MTM-35309 |
| OPC UA | Added support for mapping a Boolean value node to a Cumulocity IoT measurement. | MTM-29922 |
| OPC UA | It is now possible to specify how the alarm status should be mapped from an OPC UA server to Cumulocity IoT by using regular expressions. | MTM-35392 |
| OPC UA | An operation has been added to read a file from the OPC UA server and upload it to Cumulocity IoT. | MTM-24410 |
| OPC UA | A retry mechanism has been implemented for failed custom actions. For details on the configuration, see "Custom action retry mechanism on external server failure" in OPC UA > Device protocols and "Additional customizations" in OPC UA > Gateway configuration and registration in the Protocol integration guide. | MTM-33605 |
| OPC UA | OPC UA history read batch sizes can now be configured in the operations, see "Historic read" in OPC UA > Operations in the Protocol integration guide. | MTM-30364 |
| OPC UA | UA alarm severity mappings can be configured in the OPC UA server managed object. | MTM-35656 |
| OPC UA | Added performance tuning tips for OPC UA, see OPC UA > Running the gateway in the Protocol integration guide. | MTM-35609 |
| OPC UA | Added support for partial address space scan by providing the "nodeId" parameter in the scan address space operation. Model change events from the connected servers are handled and address space node changes are persisted automatically in the local and in the Cumulocity IoT Inventory API. | MTM-32840 |
| OPC UA | Read-, write and method invocation operations can now carry an optional expiration time which prevents the gateway from executing outdated operations. | MTM-35643 |
| OPC UA | To avoid confusion, the OPC UA legacy entry has been removed from the Add device protocols dialog in the Device Management application. | MTM-36251 |
| OPC UA | If the retry mechanism for custom actions is disabled in the configuration the collecting and storing of events will also be disabled. | MTM-37078 |
| Sigfox | For registered Sigfox devices in Cumulocity IoT, the provision status check from Sigfox Cloud is stopped if the corresponding provisioning job is no longer found in Sigfox Cloud. For these devices, the c8y_LpwanDevice fragment contains provision=false and the error message "Provision status check cannot be done because registration job was not found." | MTM-33940 |
| SmartREST | A new MQTT static template has been added: "Set device profile that is being applied" (121), see Device integration using MQTT > MQTT static templates in the Device SDK guide. | MTM-34503 |
| SNMP | Validation error messages are shown as a tool tip on hovering over the element. | MTM-31791 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Bulk operations | Bulk operations with status EXECUTING have a cancel option. When all single operations had been created and the user tried to cancel the bulk operation an error occurred. This has been resolved by removing the option to cancel a bulk operation when all its single operations have already been created. | MTM-38907 |
| Bulk operations | Previously bulk operations that were started but not completed became stuck in platform failover scenarios. A mechanism to resume these bulk operations upon restart has been introduced. | MTM-38171 |
| Cloud Fieldbus | Added validation to prevent defining the same measurement in multiple registers. | MTM-32416 |
| Cloud Remote Access | A new SmartREST template c8y_RemoteAccessConnect has been added to establish tunneling by the Remote Access device agent, see also Device integration using MQTT > MQTT static templates in the Device SDK guide. |
MTM-35819 |
| Device Management | A Load more button has been added to the child devices view for displaying larger numbers of devices. | MTM-34473 |
| Device Management | The performance of the device details page has been improved. | MTM-35544 |
| Device Management | Fixed an issue where the Measurement tab in the device details sometimes was not shown. | MTM-35140 |
| Device Management | In the search result page when users click the Add group link they will now be able to enter a group name and create a group from the listed devices. | MTM-35089 |
| Device Management | In the Device configuration tab, the message informing the user that the configuration file is empty has been improved. | MTM-36366 |
| Device Monitoring | In the case that availability monitoring for a device was deactivated, alarms were still incorrectly being raised to indicate a device was unavailable. This behaviour has now been corrected. | MTM-37863 |
| LWM2M | For push-based FOTA the read to /5/0/8 has been removed. This improves compatibility with LWM2M devices for firmware updates over the air by simplifying one of the internal workflows. | MTM-34178 |
| LWM2M | When upgrading from 10.6.0 to 10.6.6 or later version, the LWM2M observations are preserved. | MTM-35214 |
| LWM2M | LWM2M object models are now stored separately for each tenant and should not get overridden when they are loaded again into the LWM2M agent. | MTM-35000 |
| LWM2M | Improved concurrency robustness for operation execution. | MTM-35070 |
| LWM2M | In certain situation, the repeated upload of a LWM2M DDF object failed with the error "Object mapping for objectId: <Number> already exists in database". This issue has been fixed. | MTM-34271 |
| LWM2M | The number of pending operation executions in the post-registration process can now be limited. | MTM-36082 |
| LWM2M | The description of the write operation has been added to the documentation, see LWM2M > Handling LWM2M shell commands in the Protocol integration guide. | MTM-36488 |
| MQTT | Cumulocity IoT core now monitors the direct memory usage and when it reaches the threshold the platform health check will report the node as down and cut off the traffic. | MTM-35303 |
| MQTT | MQTT now returns bad password return code instead of unauthorized code, when a wrong password has been provided on connection. | MTM-35963 |
| MQTT | The JWT token can now be generated for devices authenticated with certificates regardless of the preferred login mode set (Basic, OAuth Internal). Previously it was only possible when the login mode was set to OAuth Internal. | MTM-35965 |
| OPC UA | The OPC UA gateway now disconnects from an OPC UA server if there are too many outstanding measurements, events or alarms that have not been pushed to the platform yet. This should prevent "out of memory" issues. However, if an out of memory situation happens, the gateway now cleanly disconnects from the server and exits with an exit status of "1". | MTM-32856 |
| OPC UA | The HTTP POST action request body is now UTF-8 encoded. | MTM-34487 |
| OPC UA | The device type mappings matching time has been significantly improved for huge address space and device type. | MTM-35019 |
| OPC UA | JMX and SSH are disabled by default for the OPC UA gateway. | MTM-35178 |
| OPC UA | The history read operation on an OPC UA server will return the status as FAILED, if the provided "NodeId" for the operation is invalid. | MTM-30416 |
| Sigfox | The list of available contracts displayed in the Sigfox device registration now includes contracts with activationEndTime = 0 and maxTokens=0 because, according to the Sigfox documentation, 0 should be considered as unlimited. | MTM-36756 |