Release 10.16.0.483
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | An old data model migration mechanism was erroneously removing installed software information from devices when the Advanced Software Management microservice was resubscribed or restarted. This mechanism has entirely been removed so that existing data is no longer modified. | DM-3475 |
Release 10.16.0.476
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.16.0.461
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.16.0.438
Improvements
| Component | Description | Issue |
|---|---|---|
| LWM2M | The LWM2M agent realtime subscription for device operations now has a configurable limited time-to-live (TTL). The default TTL duration is 3 minutes. This setting may be configured on platform level. | DM-3067 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | In Chrome, custom event and operation fields having 0 or '0' as a value were incorrectly parsed and displayed as date. This is now fixed. | DM-3098 |
Release 10.16.0.458
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | Sorting and filtering by creationTime and lastUpdated is no longer supported by the Inventory API, therefore it has been replaced by sorting and filtering on creationTime.date and lastUpdated.date properties only. |
DM-3112 |
Release 10.16.0.446
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.16.0.415
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | Under certain rare conditions LWM2M devices were not able to connect due to an internal 409 conflict. The LWM2M agent is now more robust for such scenarios. | DM-3044 |
Release 10.16.0.405
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.16.0.396
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.16.0.383
Fixes
| Component | Description | Issue |
|---|---|---|
| Device management | The availability calculations in the "Availability" overview and for individual devices were not correct. Percentages were calculated for the respective time (24 hours, last 7 days and last 30 days) plus an additional 24 hours. The time interval has now been corrected. | DM-2737 |
| Device management | After editing a device protocol details page and leaving the page, a confirmation pop-up is now always properly shown. | DM-2700 |
Release 10.16.0.376
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | Fixed an issue in the data grid and device grid components where specific string, Boolean, and numeric cell values were wrongly formatted as dates. | DM-2746 |
Release 10.16.0.369
Fixes
| Component | Description | Issue |
|---|---|---|
| Cloud Fieldbus | Previously, the CAN bus protocol limited the representation of numeric values in the maximum value field, which posed limitations when dealing with exceptionally large numbers. To address this limitation, we have implemented a transformation mechanism that allows numeric fields to be defined using textual representations. | DM-2691 |
| Device management | The Copy dashboard button is now disabled when the user does not have the correct permissions. | MTM-53334 |
| LWM2M | A fail-safe mechanism to regularly get pending LWM2M device connector operations from the platform has been added in addition to the real-time mechanism in the LWM2M agent. This mechanism is beneficial when real-time connections between the LWM2M agent and the platform are unstable. | DM-2652 |
| LWM2M | Setting up LWM2M agent DTLS connections by DTLS Connection IDs (CID) is now supported. By default this functionality is enabled. If you use LWM2M devices that support connection IDs, contact your platform administrator to apply additional settings or check if this feature is enabled. | DM-2701 |
Release 10.16.0.327
Fixes
| Component | Description | Issue |
|---|---|---|
| Device management | In the Device profiles page, when adding a repository item (software, firmware, configuration) if the device profile has a device type defined, the items shown either correspond to this device type or they don't have a device type specified. In some cases, repository items without a filter were not visualized in the window for adding an item. These items are now correctly shown. | DM-2547 |
| LWM2M | When reading an entire LWM2M object which contains multiple object instances in a simple read, observer or send operation, the LWM2M agent processed and stored only one of the resources of these object instances. This is now resolved and the LWM2M agent processes and stores all resource data from multiple object instances correctly. | DM-2426 |
| LWM2M | During a large number of parallel LWM2M DTLS device connection requests, used for devices using PSK secured mode, the LWM2M agent was not able to handle all connections at the same time. This caused platform connection failures for the devices. In the LWM2M agent, the default settings for this part have been adjusted and made configurable to serve large parallel connections. | DM-2651 |
| LWM2M | If thousands of decoder events were pending to be processed, the LWM2M agent tried to process the same event twice in certain cases. As a result, the log file showed confusing SDK exceptions. This has now been fixed. | DM-2659 |
| OPC UA | The application of OPC UA device protocols was unreliable when there were more than 1000 protocols. This is now fixed. | DM-2634 |
Release 10.16.0.316
Fixes
| Component | Description | Issue |
|---|---|---|
| Device management | On the Measurements tab in the device details, a tooltip has been added which shows the complete values in case of truncated values in the Y-axis. Moreover, the information is provided that you can see the complete values by hovering over the axis. | MTM-48603 |
| LWM2M | If the LWM2M device observation frequency is high, for example, a few milliseconds, the LWM2M agent processed the same message multiple times, occupying a lot of resources. This is now resolved. The LWM2M agent no longer reprocesses the same observation request. | DM-1823 |
Release 10.16.0.302
Fixes
| Component | Description | Issue |
|---|---|---|
| Connectivity | The performance of MQTT connections has been improved. MQTT devices can now connect or reconnect faster, especially if the platform already has a large number of MQTT devices connected. | MTM-53819 |
| Device management | The device list now shows complex columns like c8y_SoftwareList correctly after converting them to strings. |
DM-2410 |
| LWM2M | The LWM2M agent now correctly persists all registration update parameters. Previously, the LWM2M agent did not store changes of registration parameters, for example, updated registration lifetimes. This is now fixed. | DM-2503 |
| OPC UA | In OPC UA device gateway nodes, expected but missing information prevented the completion of the address space scan operation. This is now fixed by skipping these nodes and adding an error message in the opcua-device-gateway log files. Additionally, the overall scanning speed has been improved for the full and partial address space scan operations. | DM-2365 |
Release 10.16.0.282
Fixes
| Component | Description | Issue |
|---|---|---|
| Device management | In smart groups which are configured with sorting but without a filter, devices were not shown correctly. This has been addressed by correctly generating the required query. | DM-2243 |
| Device management | In the Trusted certificates page, an issue with the tooltip for the Signed verification code field has been fixed. | MTM-53813 |
Release 10.16.0.264
Improvements
| Component | Description | Issue |
|---|---|---|
| LWM2M | The performance of the migrateLwm2mDevices operation has been improved. New command line arguments have been introduced with the operation. A list of legacy LWM2M devices can be specified directly from the shell command. Moreover, the migration of the LWM2M client registration objects can be skipped by using an argument. For details, refer to LWM2M > LWM2M connector device > Migration of the LWM2M devices in the Protocol integration guide. |
DM-1866 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Device management | Issues with flashing the device availability connection status have been fixed. | MTM-51541 |
| Loriot | The memory limit for the Loriot microservice has been increased to 2Gi. | DM-2427 |
Release 10.16.0.259
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.16.0.256
Fixes
| Component | Description | Issue |
|---|---|---|
| Device management | In the device grid, issues with applying filters have been fixed. | DM-2321 |
| LWM2M | Custom actions were not always executed if a LWM2M device used a SEND operation to report the whole LWM2M object data. This issue is now resolved and the custom actions are always executed for the resource instances for which they are defined. | DM-2188 |
| LWM2M | The LWM2M agent now ignores trailing commas at the end of object links in the registration request of a LWM2M client. | DM-2342 |
| LWM2M | In certain cases, the registration couldn't be associated with a LWM2M 1.1 SEND request, leading to a 4.04 CoAP response. This is now fixed. | DM-2270 |
| LWM2M | The LWM2M agent is now able to properly convert the timestamps from the SenML data reported by the LWM2M client to a platform compatible date-time format for performing respective resource actions. | DM-2150 |
| OPC UA | In case of bad connectivity or network delay gateway devices could go to a state where they were disconnected. This resulted in operation execution being suspended. This issue is now resolved. | DM-2037 |
| OPC UA | If the namespace is not defined for a specific node, a missing error handler in the past prevented completion of the scan operation. This is now fixed by skipping nodes that cannot be read. The opcua-device-gateway logs include further details in such cases. The log level INFO contains the failure message and the log level DEBUG contains the stacktrace. | DM-1920 |
Release 10.16.0.214
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | Multi-line LWM2M post-operations were not executed right after the LWM2M device's new registration when realtime was disabled for the tenant who owns the device. As a result the device might not receive these operations until the next LWM2M device's registration update. This issue is now resolved and LWM2M post-operations are executed right after the LWM2M device's new registration, no matter whether realtime is enabled or not for this kind of devices. | DM-2100 |
Release 10.16.0.205
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | Two new LWM2M shell commands have been added.
- The new executelegacy command allows LWM2M execute requests with non-standard LWM2M parameters. The behavior of this operation resembles the semantics of the existing execute operation until version 10.15.
- The new coap shell command enables making raw CoAP requests to devices to facilitate non-standard communication in exceptional cases.
For details, refer to LWM2M > Handling LWM2M shell commands in the Protocol integration guide. |
DM-2153 |
Release 10.16.0.200
Fixes
| Component | Description | Issue |
|---|---|---|
| Connectivity | Due to compatibility issues of the connectivity microservice with the Kite provider, an error occurred on the metrics page, when the monthly consumption data was an out-of-scope integer. This has been fixed by changing the data type. | DM-1566 |
| Device management | SmartREST Inventory GET templates created in the UI did not generate responses when there was no external ID type declared in the template. This issue has been addressed for both existing and newly created templates. | DM-2126 |
| Device management | When removing a device which has child devices, users can now choose either to remove a device user or to remove all child devices. Prior to this change, it was possible to choose both options in the UI, but such an action is not supported by the backend. | MTM-45277 |
| Device management | On bulk device registration views, the Upload button now stays disabled if there is no file selected or if the selected file is invalid. | DM-1641 |
| Device management | On the Services tab in the device details, the filter for the "Status" column did not work properly and didn't return results when a filter was applied. This is now fixed. | DM-2002 |
| LWM2M | During the LWM2M client registration, if the agent failed to find the registered device from the database due to a communication problem, an internal object related to the device managed object was automatically removed by the agent. Afterwards, LWM2M clients always failed to connect. This is now fixed and the internal object is only removed if the actual device managed object does not exist in the database. | DM-2131 |
| LWM2M | Due to a limitation of the Leshan library used by the LWM2M agent, only device registration messages were supported where the LWM2M version is attached to the LWM2M object. The LWM2M agent has now been extended to also accept LWM2M registration messages where the LWM2M version is attached to the LWM2M object instance. | DM-1893 |
| Loriot | Events created by the Loriot agent when sending uplink requests are now considered device requests, providing connectivity status and availability monitoring. | DM-2139 |
Release 10.16.0.163
Fixes
| Component | Description | Issue |
|---|---|---|
| Device management | On the Shell tab in the device details, when a shell command operation is created, its name now corresponds to the command text if available. If no command text is available then it displays the operation description. | DM-2069 |
| Device management | In device list views, when a device was deleted, any related child devices were deleted as well. This functionality has now been enhanced. On device deletion, any existing child hierarchy types, that is, not only devices but also additions and assets are deleted accordingly. | DM-2003 |
| Device management | In events and alarms views, custom properties with numeric values were incorrectly parsed and displayed as dates in the Chrome browser. This is now fixed. | DM-1999 |
| Device management | On the Software tab in the device details, the Reload button now correctly updates the Installed software list. | DM-2005 |
| LWM2M | In the older Leshan demo client, the device registration requests for the Cumulocity IoT LWM2M demo device and possibly also some other devices could contain spaces between the core link separators. This was successfully handled by the LWM2M agent 10.14 and below but caused the LWM2M agent 10.15 and above to reject these device requests. Now, the LWM2M server accepts these requests again. The older device registration requests can be processed again. | DM-2070 |
| LWM2M | In certain cases the migration of LWM2M devices registered on versions before 10.15 reported "Unable to process device" for certain devices. This happened due to adjustments to the device configuration, for example when editing the registration lifetime. With this fix, the migration logic robustness has been improved. | DM-2022 |
Release 10.16.0.121
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.16.0.117
Improvements
| Component | Description | Issue |
|---|---|---|
| Actility | Users can now configure the application server key, application server ID, core API version and admin API version in the UI while creating an Actility connection instead of configuring these values in the properties file. | DM-1142; DM-1171 |
| Actility | The Actility agent now accepts both XML and JSON uplink messages from Thingpark Actility. Prior to this change, JSON messages had been denied. | DM-1255 |
| Actility | The Cumulocity IoT Actility agent is now able to register devices on Actility ThingPark Enterprise in addition to the registration via Actility Thingpark Wireless. | DM-1102 |
| Actility | The LPWAN device managed object now has a c8y_Agent fragment which contains information about the name, version, URL, and maintainer of the agent. |
DM-906 |
| Actility | For devices registered with the Loriot agent, downlink operations can now be sent from the Shell tab. | DM-1176 |
| Advanced Software Management | The performance of the advanced-software-mgmt microservice has been improved. | DM-1251 |
| Device Management | Filtering by groups in the device grid component is now enhanced by a search. Users can now search and select assets through the hierarchy. | DM-1406 |
| Device Management | The c8y-data-grid component now offers a simpler mechanism for persisting grid configuration and enabling user-defined columns. By providing a "DataGridConfigurationStrategy" developers can enable user-defined columns for a given c8y-data-grid instance and define how and where the grid configuration is stored. In the @c8y/ngx-component a "UserPreferencesConfigurationStrategy" service is implemented that stores the grid configuration in form of user preferences. Additionally, custom columns have been enabled for sub assets and search results grids. |
DM-1024 |
| Device Management | Core re-usable data-grid related components and services have been moved to the @c8y/ngx-components packages for easier use in components based on the c8y-data-grid component without the need to create dependencies to the @c8y/ngx-components/device-grid. |
DM-1023 |
| LWM2M | When the client sent data to the LWM2M agent for an unmapped event the agent triggered an alarm instead of creating an event. Now the LWM2M agent creates a c8y_lwm2m_sendData event. Otherwise, if there is already a mapping uploaded to the agent, the data is processed by the mapping engine. |
DM-373 |
| LWM2M | The LWM2M agent now provides two operations on the connector device for manually invalidating LWM2M registrations. | DM-1336 |
| LWM2M | LWM2M 1.1 allows direct writing to a resource instance. That means if you have a resource, which has some resource instances (for example, /3/0/11/0) and these resource instances allow direct writing, it's possible to write values to any of the resource instances. | DM-371 |
| LWM2M | The LWM2M bulk registration now also supports the creation of external IDs and extra fragments in managed objects like it is supported in the general bulk registration. Furthermore, it is now possible to assign LWM2M devices to groups as part of the LWM2M bulk registration process. | DM-1544 |
| OPC UA | DeviceTypeMappings of a managed object are now stored beside the device gateway to reduce the size of the managed object stored in the inventory. | DM-304 |
| OPC UA | The usage of Prometheus via JMX has been enabled to provide additional metrics of the current count of alarms and measurements. For details, see OPCUA > Troubleshooting in the Protocol integration guide. The JAR file can be downloaded from the prometheus.io web page. | DM-317 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Cloud Fieldbus | The Offset property field in the register configuration now accepts all values. | MTM-48256 |
| Cloud Remote Access | The behavior of the Cloud Remote Access UI functionality has been improved. The microservice subscription is now checked before the microservice health check, in order to prevent unnecessary delays on loading device details within the Device Management application for tenants which are not using this feature. | MTM-44680 |
| Device Management | In the device list view, when a custom column is added it is always positioned after all default columns. | DM-1309 |
| Device Management | On a device grid, when applying filters to columns, this is now saved to the configuration for the grid, and when users returns to the same page the filters will be visualized and applied. | DM-1228 |
| Device Management | When deleting devices in the device list view, the options to delete child devices and device owners are again available in the confirmation window. | DM-1319 |
| Device Management | Misleading tooltips in the Groups page have been removed. | MTM-47241 |
| Device Management | In the Device Management application, for example in the Info tab or the Location tab, the latitude position is now consistently displayed as first position value, followed by longitude. | MTM-41052 |
| Device Management | The data type mapping of the "Asset properties" widget has been improved to ignore null values for properties created by default when using MQTT templates, which prevented user from saving widget data unless the mentioned properties were fixed manually. Affected properties: c8y_Firmware.url, c8y_Software.url, c8y_Mobile.imei, c8y_Mobile.imsi, c8y_Mobile.cellId, c8y_Mobile.lac, c8y_Mobile.mcc, c8y_Mobile.mnc. | MTM-44294 |
| Device Management | The device registration wizard had several layout and functionality issues which were fixed by aligning them to the default platform user experience. | DM-1335 |
| Device Management | In the Device protocols page, filtering for specific device protocols using a search term is now more efficient. The list is filled and displayed faster with the desired search results. | DM-912 |
| Device Management | The Create smart group button in the All devices list is clickable again when all column filters are cleared. | DM-1541 |
| Device Management | When removing a device with child devices, users can now choose either to remove a device user or to remove all child devices. Prior to this change, it was possible to choose both options in the UI, but such an action is not supported by the backend. | MTM-45277 |
| Device Management | On the Location tab in the device details, you can now again change the location of the device on the map by dragging the position marker. | DM-1565 |
| 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 |
| Device Management | The Submit button in the "Device data" widgets editor is now always enabled. The validation on fields is still present, but validation errors no longer prevent users from committing manual changes. | DM-1623 |
| Device Management | In the Software repository page, the Add software dialog accepted a software without software type although the field Software type is mandatory. This has been fixed and the Add software button is now active only when the mandatory Software type field is filled. | DM-1713 |
| Device Management | In the Software repository page, sorting for the column "Device type" did not function properly. This issue is now fixed. | DM-1712 |
| Device Management | The option to copy the home page dashboard has been removed since it didn't provide useful functionality. | DM-1869 |
| Device Management | The groups list in the Groups page now allows to filter by the grid's columns. | DM-1836 |
| Device Management | The "Groups" column in the device list formerly displayed all groups higher in the hierarchy to which the device belonged directly or transitively. This has been fixed and now only direct parent groups are displayed. | DM-1870 |
| Device Management | An issue with the filter functionality on the Groups page for smart groups has been fixed. Results now include devices belonging to the selected smart groups. | DM-1872 |
| Device Management | By adding or removing an external identifier of type c8y_Serial to/from the monitored device, the device connection monitoring is notified accordingly to start or stop with the specified external identifier. |
MTM-50025 |
| Device Management | The Assign devices button is now disabled for users without the required permissions. | MTM-50928 |
| LWM2M | The LWM2M agent now fetches a limited number of pending operations if an LWM2M device sends a registration or a registration update. | DM-1474 |
| LWM2M |
- The LWM2M agent always retrieved the external decoder events from one month back only. So if an event remained unprocessed over a month, then it wasn't processed anymore. The time period is now configurable from the agent's configuration.
- Events, measurements, and alarms created by the LWM2M agent are flushed every 10 mins. If a high number of devices connects concurrently or in a short time period, the size of the queue can increase significantly, which in turn leads to high memory usage until all elements are flushed. The flush time interval can now be configured from the agent's properties. |
DM-1602 |
| LWM2M | The external decoder service was using a single thread per event to parallelize the decoder event processing. Those threads were created from another execution thread which can lead to a deadlock on a tenant. To avoid such deadlocks, the processing of the decoder events is done in batches for each tenant. Additionally, a fail-safe mechanism has been introduced, so that the agent is able to release a tenant after a certain period of a deadlock. | DM-1519 |
| LWM2M | A security vulnerability CVE-2022-39368 was found in Leshan 2.0.0-M8 and Californium 3.6.0. The dependencies were updated to the latest versions Leshan 2.0.0-M9 and Californium 3.7.0. | DM-1734 |
| LWM2M | The LWM2M agent now fetches a limited number of pending operations if a LWM2M device sends a registration or a registration update. | DM-1474 |
| LWM2M | On the Objects tab in the device details, if you select an object containing a timestamp resource, the text box which displays the timestamp now receives the correct timestamp data type and no error message is displayed. | DM-1673 |
| LWM2M | By default, the LWM2M object-resource mappings of the Management tenant that are configured using the LWM2M device protocols were not inherited by the subtenants. With this change, the LWM2M object-resource mappings defined in the Management tenant are applied to all its subtenants by default. The default mappings from the Management tenant can also be overwritten by uploading the LWM2M device protocol for the LWM2M object on the subtenant level as described in LWM2M > LWM2M device protocols in the Protocol integration guide. | DM-1778 |
| LWM2M | While updating the security info for PSK devices in the database, the LWM2M agent internally deleted the old security managed object and created a new one. Due to the asynchronous deletion of managed objects in the Cumulocity IoT platform, the agent intermittently failed to update the security info. With the current changes, the LWM2M agent updates the required security details in the same managed object instead of removing it first. | DM-1671 |
| LWM2M | The LWM2M agent now allows users to write binary data to a resource on a device using a shell operation. For more details about the shell command, refer to LWM2M > Handling LWM2M shell commands in the Protocol integration guide. | DM-1241 |
| MQTT | The MQTT storage is now properly cleared by removing not needed data after device disconnection. This may result in performance improvements, especially in terms of MQTT connect and subscribe operations. | MTM-49888 |
| 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 |
| OPC UA | The OPC UA artefacts on Edge have the JVM heap size defined relative to the defined memory limit for the container. Security improvements have been added to limit the Docker capabilities. | DM-1327 |
| OPC UA | The OPCUA device gateway creates an application identity certificate to identify itself with the OPCUA server. During the upgrade of the OPCUA gateway from version 10.11 or earlier to 10.13 and later, the private key of this application identity is encrypted internally and saved. The encryption of the old identity was faulty in the earlier releases of 10.13 and later, which led to issues with the server connection using Sign or SignAndEncrypt security mode after the upgrade. This issue is now resolved. Users who configured the OPCUA server after the upgrade, or did a new configuration with 10.13 or later versions are unaffected by the issue. The issue was only during the encryption of old identities. | DM-1246 |
| OPCUA | In previous versions of the OPCUA management service users were allowed to save the OPCUA device protocols with invalid node IDs in the Limit device protocol to specific root nodes ID field while applying constraints. This led to an error during retrieval of the whole device protocols list. With the current release the node IDs are now validated before saving the device protocol. Wrong values will be shown in a popup. | DM-822 |
| OPC UA | Due to a change introduced in 10.14, the opcua-device-gateway on OPC UA server connects or reconnects did a full device type matching with a comparison of device types to the server's address space to find matched nodes and the application of these matched nodes. With this fix, the opcua-device-gateway directly applies the matched nodes settings if there was a matching done previously and no more recent updates to the device types were done. | DM-1651 |
| OPC UA | Previously, when the autoReconnect property was enabled in the OPC UA server's client configuration, then on server connection drop, in addition to the Prosys client SDK auto-reconnect mechanism, the OPCUA device gateway did an additional reconnect. This led to issues with re-creating subscriptions to the server.
Now with autoReconnect enabled, only the Prosys client SDK does the auto-reconnect. If the autoReconnect property is disabled in the OPC UA server's client configuration, the OPCUA device gateway will do the reconnection itself by default. This OPC UA device gateway reconnect can also be disabled by setting the gateway configuration property triggerManualReconnectOnConnectionDrop to false. For details on the property, see OPCUA > Gateway configuration and registration in the Protocol integration guide. |
DM-1078 |