Release 10.7.0.49
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.7.0.47
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.7.0.46
Fixes
| Component | Description | Issue | |
|---|---|---|---|
| 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 Handling LWM2M shell commands in the Protocol integration guide. |
MTM-40674 |
Release 10.7.0.44
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.7.0.42
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 |
Release 10.7.0.38
Info
There are no significant improvements or fixes related to this component in this Maintenance release.
Release 10.7.0.37
Fixes
| Component | Description | Issue |
|---|---|---|
| Bulk operations | In the operations section of the bulk operation details, long descriptions broke the correct formatting and visibility of table elements. This has been fixed by limiting/truncating the description text. | MTM-38433 |
Release 10.7.0.36
Improvements
| Component | Description | Issue |
|---|---|---|
| LWM2M | The description of the dynamic client awake time has been added to the LWM2M documentation, see <a href="https://cumulocity.com/guides/10.7.0/protocol-integration/lwm2m/#register-device" class="no-ajaxy">LWM2M > Registering LWM2M devices</a>in the <i>Protocol integration guide</i>. | MTM-34195 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | The sorting of groups and devices has been changed to be consistent in all places. Previously the sorting of groups and devices in the navigator was not consistent with the sorting in the **Subassets** tab. Now the sorting will be case-sensitive in both cases, for example "AAA BBB CCC aaa bbb..." instead of "aaa AAA bbb CCC ccc...". | MTM-36844 |
| 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 |
| Web SDK | Improved app subscription to avoid a race condition bug when applying branding to an application. This was often leading to not/wrong applied branding when creating a new branding. | MTM-37276 |
Release 10.7.0.32
Improvements
| Component | Description | Issue |
|---|---|---|
| Device Management | Bulk operations can now be filtered by date or date ranges. | MTM-34921 |
| 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 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Device monitoring | Improved the performance of device availability monitoring when monitoring a large number of devices. | MTM-36213 |
| Device monitoring | Under certain circumstances, the availability status of devices could show wrong information. This has been fixed so the availability status now is always accurate. The availability calculation now also takes into account correctly the setting for "0" as documented. | MTM-36103 |
Release 10.7.0.31
Improvements
| Component | Description | Issue |
|---|---|---|
| LWM2M | Added support for old content format codes: TLV (1542) and JSON (1543). | MTM-36250 |
Fixes
| Component | Description | Issue |
|---|---|---|
| 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 |
| Sigfox | The list of available contracts displayed in the Sigfox device registration now includes contracts with activationEndTime = 0 and maxTokens=0. According to the Sigfox documentation, 0 should be considered as unlimited. | MTM-36756 |
Release 10.7.0.24
Improvements
| Component | Description | Issue |
|---|---|---|
| Actility | New advanced settings have been introduced for the Java Microservice SDK that allow the developer to alter the connection pool settings.
These settings can be considered to be used if the request/connection times out or no route to host exceptions are being experienced for the requests to the microservice. These settings should only be altered where the network environment is fully understood.
The following properties, which can be specified in the microservice's property file, are available: "C8Y.httpClient.httpReadTimeout" (default: 180000 in ms) "C8Y.httpClient.pool.enabled" (default: true) "C8Y.httpClient.pool.perHost" (default: 50) "C8Y.httpClient.pool.max" (default: 100) "C8Y.httpClient.pool.awaitTimeout" (default: 10000 in ms)
|
MTM-32602 |
| Actility | Optimized indices containing time data to improve the performance of operations such as query and insert. | MTM-30879 |
| Cloud Remote Access | When trying to connect to a WebSocket and the WebSocket connection is closed, more meaningful code is provided now, including the reason why the connection was closed. | MTM-32632 |
| Cloud Remote Access | Cloud Remote Access now works with SSO. | MTM-31978 |
| Cockpit & Device Management | Performance has been improved by making breadcrumbs on devices and groups configurable. Per default, breadcrumbs on devices and groups are now turned off. They can be turned on by setting the breadcrumbs application option, see http://resources.cumulocity.com/documentation/websdk/ngx-components/classes/ApplicationOptions.html#breadcrumbs. All other breadcrumbs are still displayed. |
MTM-29924 |
| Cockpit & Device Management | To improve performance, in the sub-assets view of group details, the objects are now fetched from inventory using the childAssets endpoint instead of advanced querying (in-group). | MTM-32441 |
| Cockpit & Device Management | To improve performance, the group assignment widget now uses the "withChildren:false" parameter in calls to inventory. | MTM-32032 |
| Cockpit & Device Management | Improved the performance of the navigator groups items by changing how the inventory API is called to fetch managed objects. | MTM-32870 |
| Cockpit & Device Management | In the view for root level groups the number of children for a group is no longer displayed by default but only shown on mouseover. | MTM-32452 |
| Cockpit & Device Management | On the root groups views, the query to inventory uses the flags onlyRoots=true and withChildren=false. This results in improved performance. | MTM-32450 |
| Device Management | In the device registration wizard, the label has been changed from "LoRa" to "Actility LoRa". The label "LoRa provider settings" has been changed to "Actility LoRa provider settings". | MTM-33061 |
| Device Management | The configuration repository functionality has been enhanced. It is now possible to specify a configuration type. Moreover, the configuration repository now provides a list view, which shows the new configuration type and also allows the user to filter for configurations. If a device has the "c8y_SupportedConfigurations" fragment with a list of supported configuration types, it can have multiple configurations. For details, see Device Management > Managing device data > Managing configurations in the User guide. |
MTM-32117 |
| Device Management | Dynamic groups that are in fact just managed objects with the fragment "c8y_IsDynamicGroup" can now get extended to be invisible in the UI.
To do so, the "c8y_IsDynamicGroup" object within the JSON must look like this: "c8y_IsDynamicGroup": { "invisible": {} }. If the managed object includes the fragment like this it won't be rendered within the navigator and also not in the groups' view. |
MTM-32643 |
| Device Management | In the group assignment widget under device details, the list of available groups is now only retrieved when the user expands the dropdown. | MTM-32462 |
| Device Management | The default page size for the device list is now 40. | MTM-32458 |
| Device Management | The legacy configuration view has been migrated into the new configuration feature. | MTM-33296 |
| Device Management | The firmware and software update functionality has been enhanced. You can now manage versions for software items, and versions and patches for firmware items. Moreover, you can install multiple software items on a device, and update or remove them separately from the Software tab of a device. For details, see Device Management > Managing device data in the User guide. | MTM-30314 |
| Device Management | The bulk operations functionality has been significantly enhanced. Details on bulk operations and their status can now be viewed in the Bulk operations tab on the Device control page. A new wizard has been implemented to add bulk operations of various types. For details, see Device Management > Monitoring and controlling devices > Working with operations in the User guide. | MTM-30318 |
| Device Management | It is now possible to set up device profiles that contain a set of firmware, software packages and configuration files. If a profile is applied to a device the respective items will be installed on the device. For details, see Device Management > Managing device data > Managing device profiles in the User guide. | MTM-33621 |
| Device Management | Cumulocity IoT allows devices to connect via MQTT protocol using a X.509 certificate for authentication. To do so, a certificate must be trusted by Cumulocity IoT. For details on how to manage trusted certificates in the UI refer to Device Management > Managing device data > Managing trusted certificates in the User guide. | MTM-33621 |
| Device Management | Improved loading time for the service monitoring view, when managing a large number of devices. | MTM-32460 |
| 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. For details, see 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 | 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 groups and subgroups via checkboxes. 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 |
| LWM2M | The Leshan Demo client version has been updated from 1.0.0-M13 to 1.0.1. | MTM-32930 |
| LWM2M | The pmax attribute has been removed so that devices are no longer forced to send a notification (observe response) every 10 seconds on firmware update. | MTM-32979 |
| LWM2M | It is now possible to map object No. 4 into a measurement with c8y_SignalStrength. | MTM-32929 |
| LWM2M | The IntegrationResource shell in the LWM2M agent has been removed. | MTM-29243 |
| LWM2M | Boolean values are mapped to measurements (false as 0 and true as 1). | MTM-32379 |
| LWM2M | LWM2M now uses the latest Microservice SDK. The agent framework has completely been removed. Verify if the firmware update object mapping exists before executing Firmware Over The Air (FOTA). If it does not exist, the operation will fail. |
MTM-31461 |
| 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 firmware update delivery method (push/pull), the reset mechanism (write \0 to package URI vs. null to package or both), the image delivery protocol (coap/coaps/http/https) and the firmware update URL can now be configured as part of the optional fragment. | MTM-33386 |
| MQTT | New static MQTT operation response templates have been added:
- Firmware with patch (525) - Software update (528) - Configuration download with type (524) - Configuration upload with type (526) - Data profile (527) |
MTM-31466 |
| MQTT | MQTT queues are purged when an MQTT device or tenant is deleted. | MTM-31469 |
| MQTT | A new MQTT static template has been added: "Set currently installed configuration" (120), see Device integration using MQTT > MQTT static templates in the Device SDK guide. | MTM-33618 |
| Netcomm Agent | NetComm Agent Version 1.1.0 has been released, including the following updates: - The device type has been renamed to NTC-220 Agent (previously POSIX Agent). - Predefined commands are now available on the Shell tab (requires version 10.6.6 or later). The following fixes have been made: - Allow Ethernet WAN and USB WAN connection as well as cellular WAN. - Fixed the issue that the agent updates its position with different intervals from the configured ones. - Fixed a Modbus plugin issue that the agent continues to send measurements after slaves are unavailable. |
MTM-33746 |
| OPC UA | Updated text from "device type" to "device protocol" in auto-apply constraints fields and description. | MTM-32633 |
| OPC UA | The OPC UA device protocol plugin implicitly sets the measurement mappings' fragment name with the user-given measurement type which makes opcua-device-gateway to use this value as the measurement fragment name instead of auto-generating the name based on the node ID. The Measurement tab of the device displays the fragment name as the title for the measurement. | MTM-32635 |
| OPC UA | To facilitate the processing of OPC UA values transmitted as events, a new fragment containing the value has been added to the event: c8y_ua_DataValue. | MTM-29823 |
| OPC UA | Alarms produced by failed HTTP post actions can now be aggregated and sent to the Cumulocity IoT platform in a configurable fixed delay. | MTM-32596 |
| OPC UA | It is now possible to map a UA alarm severity into a Cumulocity IoT alarm severity. | MTM-31147 |
| OPC UA | For OPC UA mappings, the alarm and event type can now have placeholders for selected attributes by using their index. | MTM-31146 |
| OPC UA | The default configuration file packaged in the JAR is now fully commented. | MTM-33266 |
| OPC UA | Processing mode support has been added for the OPC UA device protocol event, alarm and measurement value mappings. It is possible to define one processing mode for the device protocol and also override the processing mode for any event, alarm, measurement value mapping. If the processing mode is not defined then all the mappings will be saved in regular persistent mode. At the moment, the feature is only available via Rest API by using device protocol endpoints. Supported processing modes are PERSISTENT, TRANSIENT, QUIESCENT, CEP for measurement and event and only PERSISTENT for alarm mappings. If the given processing mode is not supported for the mapping then a warning log is given in the opcua-device-gateway logs when the device type is being applied and the default mode (PERSISTENT) is selected for those mappings. |
MTM-30895 |
| OPC UA | UA alarm severity mappings can be configured in the OPC UA server managed object. | MTM-35656 |
| Sensor app | The sensor app wizard has been updated with new links for Google Play Store and Apple App Store. Moreover, the paragraph on data-capturing has been updated. | MTM-32956 |
| Sigfox | The monitoring alarm message in case of missing credentials now contains informative text. | MTM-22454 |
| Sigfox | Hex-string validation has been added in the microservice for ID and PAC. The hex-string value of the device ID from the device registration form is saved in uppercase to avoid being considered as 2 different devices for the microservice. |
MTM-20893 |
| Sigfox | Null value properties have been removed from unprocessed Sigfox data events. | MTM-31809 |
| Sigfox | The error message upon unauthorized access to the Sigfox platform shows more meaningful content now. | MTM-22451 |
| 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 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Actility | Improved HAProxy configuration to allow more concurrent connections. | MTM-31229 |
| Cloud Remote Access | The websocket connection URL has been fixed. It now uses the domain name instead of the tenant ID. | MTM-33062 |
| Cockpit & Device Management | Adding a new group will now be reflected in the groups detail view without further need to reload. | MTM-31157 |
| Cockpit & Device Management | The title on the child devices tab is now displayed correctly. | MTM-32769 |
| Device Management | The CSV file for bulk device registration cannot have duplicated standard (not custom) columns. In that case an error will be returned. | MTM-31884 |
| Device Management | The calendar is no longer cut when the browser's window height is small. | MTM-31424 |
| Device Management | There is no longer an error when unsubscribing a device from a group. | MTM-32211 |
| Device Management | Device permissions are now correctly resolved after changing the device owner. | MTM-30410 |
| Device Management | A Load more button has been added to the child devices view for displaying larger numbers of devices. | MTM-34473 |
| Device Management | Fixed an issue where the Measurement tab in the device details sometimes was not shown. | MTM-35140 |
| Device Simulator | The Simulator menu item is now only shown in the navigator if the "Device-simulator" application is subscribed. | MTM-31872 |
| Impact | The Impact resource subscription mechanism has been adjusted to only subscribe for device resources if they are valid and match a configured auto-observe device protocol resource mapping. | MTM-33845 |
| Jasper | Fixed issue where SMS details in the Connectivity tab of a device did not expand. | MTM-31295 |
| LWM2M | The LWM2M object details page now displays the correct content when navigating between instances of the same object. | MTM-32220 |
| LWM2M | An error when reading LWM2M connectivity monitoring /4 has been resolved. | MTM-32831 |
| LWM2M | LWM2M bootstrap parameters can now be seen on the device details page. | MTM-32654 |
| LWM2M | Removed placeholder 'seconds' as the values are referring to the actual measurement values and not to a timespan. Disabled HTML default validation (not required) due to which data entered by the user was saved even though error messages were shown. | MTM-33108 |
| LWM2M | An error when reading LWM2M connectivity monitoring /4 has been resolved. | MTM-32831 |
| 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 | The number of pending operation executions in the post-registration process can now be limited. For details, see LightweightM2M > Handling LWM2M post registration actions in the Protocol integration guide. | MTM-36082 |
| MQTT | Requests made with JSON via MQTT are counted to the tenant statistics. For details see, Tenants > Tenant usage statistics in the Reference guide. | MTM-34123 |
| MQTT | The creation of subscriptions to MQTT topics has been changed to prevent subscriptions of unverified devices. A device is called unverified if the device definition (managed object) doesn’t include the "com_cumulocity_model_Agent" fragment. When trying to do so the client now gets an exception on one of the following topics: "s/e" for errors, "s/dl" for SmartREST 1.0 over MQTT and "s/dcr" for credentials for device registration.
Note that this change might lead to a situation where existing device registration processes no longer work if they so far did not comply with the device integration process. The basic life cycle for integrating devices into Cumulocity IoT using the MQTT implementation is described in Device integration using MQTT > Device integration in the Device SDK guide. In case of any issues, ensure that the order of commands complies with the order described in this description. |
MTM-31300 |
| OPC UA | The measurement and alarm timestamp is now taken from the first non-empty value of the following timestamps in the respective order: source timestamp, server timestamp and current timestamp. | MTM-33648 |
| OPC UA | The light scan process for the opcua-device-gateway's address space now skips traversing non-browsable nodes. Null checks have been improved for the internal server mappings update process. | MTM-33995 |
| 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 device type mappings matching time has been significantly improved for huge address space and device type. | MTM-35019 |
| OPC UA | The HTTP POST action request body is now UTF-8 encoded. | MTM-34487 |