deviceWISE IoT Gateway 25.03 Release Notes
A number of improvements and fixes were added to the IoT Gateway 25.03 release.
Summary:
The 25.03 release includes improvements made to the Workbench, deviceWISE View, Transaction Server and multiple drivers.
Production Release Date: October 2025
As of Release 24.01 the Technical Support License (TSL) is required to enable updates to new version. The absence of a TSL will prevent the update of installed software. If you do not have a current Technical Support License do not attempt to update your version of deviceWISE.
To ensure you are receiving genuine Telit Cinterion services and updates, all deviceWISE software as of Release 24.01 requires a Technical Support License (TSL) to be installed. The TSL acts as a reminder of the status of your Support subscription. At select periods prior to the expiration of the subscription, a notification on your deviceWISE Workbench will provide a clear visual notification. If you are missing a license or if the license is expired/expiring there will be a visual notice.
New features and enhancements to existing features
Workbench
- [MAP-23198] -Persist in disk Local DB queries
Description: Added persistence for local db sql queries with option to clear history. - [MAP-23338] -Implement generic dual column admin widget
Description: Added general dual selection list for generic panels. - [MAP-23442] -Allow checkboxGroup generic widget to support dynamic checkboxes
Description: Added option for checkboxGroup generic field dynamic checkboxes. - [MAP-23516] -Enable customization of trigger editor layout and action list display
Description: Expanded configuration options for trigger canvas editor. - [MAP-23666] -Create/enable new themes for workbench (macOS and web themes)
Description: Added new theme options to Workbench. - [MAP-23642] -Add Filter to Packages tab
Description: Added filter to package management panel. - [MAP-23631] -Allow custom message returns for Generic admin set/exec
Description: Added ability for generic panels to add custom return messages. - [MAP-23560] -Consolidate docking mechanism for action list/editor in trigger editor
Description: Modified options for pinning action list and action editor in trigger canvas editor. - [MAP-23559] -Enhance admin panel tabs to make most recent selections highlighted
Description: Made titles for recent tabs in admin panel slightly bolder/larger. - [MAP-23926] -Create Entra ID Transport Security Option
Description: Added Certificate Authentication for HTTP/SOAP transport definitions.
deviceWISE View
- [MAP-23348] -Write value widget date - support timestamp for local variables
Description: Add configuration to support write for local variables in date string and timestamp format. - [MAP-23369] -Create SPC Average(XBAR) widget
Description: Added SPC Average(XBAR) widget. - [MAP-22285] -Introduce Ability to Paste at Cursor
Description: Added the ability to paste items at the cursor location in dwView, if space is available for the widget. If not, the default editor layout management policy is applied. - [MAP-23776] -dw View - Image widget and Visual Inspection widget - Invalid data
Description: Removed formatting for Visual Inspection widget.
Transaction Server
- [MAP-21995] -Encrypt SQLITE Databases -- Transaction Server
Description: The deviceWise components i.e CORE and Transaction Server are enabled to encrypt the SQLite Database present under C:\Program Files\deviceWISE\Gateway\db. However, the feature is not enabled on its own and needs to be enabled by adding following attribute in dwcore/dwcore.proprerties. database.encryption_on=true - Once this feature is turned on then the databases will be permanently encrypted and cannot be access with any SQL third party browser.
- [MAP-23830] -Update Third Party Libray for org.eclipse.paho.client.mqttv3-1.2.1.jar
Description: The MQTT connectivity library to IBM Watson IoT Platform is upgraded. - [MAP-23285] -Update Third Party Libray for sqljdbc_auth.dll
Description: The Microsoft Server SQL native auth dll is upgraded to support all recent authentication mechanism. - [MAP-23824] -Update Third Party Libray for MSSQL mssql-jdbc-6.2.0.jre8.jar
Description: The connectivity library to Microsoft SQL Server is upgraded. - [MAP-23823] -Update Third Party Libray for postgresql-42.5.3.jar
Description: The connectivity library to Postgresql SQL is upgraded.
Visual Inspection
- [MAP-23897] -VI Inference action should support bitmaps
Description: Visual Inspection extension now supports running inference on bitmap (BMP) files.
deviceWISE Runtime
- [MAP-23484] -Update jQuery Version to 3.5 or Newer
Description: jquery.js shipped with deviceWISE was updated from ver 3.1 to 3.7.1. - [MAP-23270] -Add protection to prevent bruteforce password attack
Description: Implemented protection to prevent bruteforce password attack. devicewise system will go into a lockout period of 5 minutes if it detects more than 10 consecutive login failures from anywhere (Workbench, dwView, peerlink, sdk clients, etc). During the login period, all login attempts will result in error "Too many attempts, please try again later". The failure count is reset when lockout period ends or after a successful login. - [MAP-23455] -License Server - Duplicate Client entries in License server for a Client
Description: User is able to change the hardware id used by the license pool client now instead of always picking the first hardware id. - [MAP-23885] -Timers. Allow suspend/resume even after the timer has crossed the preset
Description: Revised the global timer to allow suspend/resume even after the timer has crossed the preset. - [MAP-23849] -deviceWISE Crash - Peerlink
Description: The null pointer access window has been closed ensuring that device rendering and connection replacement no longer trigger unexpected crashes. - [MAP-23841] -Can't insert a BINARY into a BLOB in the Local DB
Description: The Local DB Insert action now fully supports the BLOB data type, allowing binary values to be inserted correctly without errors.
Drivers and Extensions
- [MAP-23530] -Multitech Rcell 300 : we need to convert the Bearing into Heading If bearing is greater than or equal to 0, then heading = bearing; otherwise, heading = bearing + 360.
Description: Added 1 extra device variable "Heading" next to "Bearing". - [MAP-23800] -Apple Device --- inference should also have device All or Specific
Description: Added a new option called Device Select to the inference event. - [MAP-23799] -Apple IOS Capture Event -- should only be Memory, not Memory or File
Description: Removed Output Mode from the capture image event. - [MAP-23798] -Apple IOS Driver -- device definition. Use mode instead of capture
Description: Changed the label in the device edit screen from Capture Image to Mode. - [MAP-23536] -Harmonize IOS Apple Event Variables
Description: The events for Capture, Inference and Health have been updated to include the IOS Device Name, Friendly Name and IP Address. - [MAP-23432] -Need to update name for ffmpeg driver
Description: The capture action for all cameras have been updated. Now, all work the same way. The output format can be either file or memory, and the location can be staging or an absolute path. - [MAP-23992] -Add app version to the Health message from App to DW
Description: Added the IOS app version to the Health event message. - [MAP-23884] -MQTT internal enhancements
Description: Added additional error handling to prevent a possible crash when messages are published.
Issues Fixed on the 25.01 Release
Workbench
- [MAP-23528] -Workbench failed to change node successfully
Description: Fixed issue where the Workbench would sometimes not change selected node. - [MAP-23551] -Diagnostics File Panel Unknown Command -1102
Description: Removed obsolete switch toggle setting. - [MAP-23805] -Data Trending is deleting variables without asking for confirmation
Description: Added confirmation dialog to trend delete. - [MAP-23704] -CSV import type failure for http action
Description: Corrected failure to recognize type for csv import in non-json multiline parameter actions. - [MAP-23936] -Some buttons not properly adjusting to theme mode
Description: Fixed icon color on refresh button in dark mode. - [MAP-23916] -Trigger search not finding action ID or allow direct edit of comments
Description: Fixed trigger text search matching for action index. Fixed search result panel direct selection of comment entries. - [MAP-24069] -Validating a trigger with a bad variable in a lazy enum device causes that device to lose variable listing
Description: Correct issue with lazy enumeration devices losing tag list in selection tree. - [MAP-23446] -Modify SUP builder to allow setting of package type and use pkg extension
Description: Added ability in Software Update Package wizard to label the update type.
Transaction Server
- [MAP-23347] -Transaction Server [SOAP Transport]: Message not sent to SAF on SOAP request error
Description: Transport of type SOAP when enabled with SAF were not able to move message to store and forward queue. The fix resolves this problem. - [MAP-23483] -Reconnect issue in Transport and Listener still occurs in v25.01 when using Load Balancer URL
Description: Fix resolve issue when the transport and listener fail to reconnect to IBM JMS Cluster upon failover of JMS Node. - [MAP-23385] -Transaction engine not available when JMS remains disconnected
Description: A component responsible for communication setup with IBM SIB JMS was not releasing memory correctly. The fix ensures more efficient resource usage during application runtime.
Visual Inspection
- [MAP-23428] -VI Action - Dataset image upload crashes dw when there is no connection to studio or edge
Description: Fixed issue in Visual Inspection's image upload action when connection has not been validated when upload is performed.
deviceWISE View
- [MAP-23331] -Page refresh jumps the change password prompt
Description: When the user logs in with the default password, it is correctly prompted with the popup to change the password. However, it is enough to simply refresh the page to bypass this check. - [MAP-23482] -Editing gauge label breaks the UI
Description: Add null validation when editing gauge label. - [MAP-23456] -dwView automatically assigns a variable on second widget
Description: Selection of update rate made mandatory when assigning variable to the widget. - [MAP-23668] -SPC Widget Trim leading trailing blanks for dynamic variables index
Description: SPC Widget Trim leading and trailing blanks for dynamic variables index. - [MAP-23656] -Self-inflicting DOS attack by dwview
Description: Fixed issue that happened when deviceWISE was restarted for any reason, which caused dwView to try, reconnect and resubscribe with 0 delay. - [MAP-23626] -SPC Widgets not supporting dynamic variables
Description: Added support of dynamic variables in the variables picker of the SPC Widgets. - [MAP-23563] -Issue with Missing Widget in deviceWISE VIEW
Description: Fixed issue with widget not appearing in deviceWISE View. - [MAP-23465] -dW View Button widget ignores Font Color
Description: Added Font Color to the properties tab named Button. - [MAP-23891] -UI error when trying to drag and drop a widget
Description: Fixed UI error when trying to drag and drop a widget. - [MAP-23890] -UI overflow errors after going live
Description: Fixed errors when switching from build to live mode.
deviceWISE Runtime
- [MAP-23496] -License Acquire multiple not working. Acquires only one.
Description: Driver that consumes multi-count at once will work properly now. - [MAP-23512] -Generate Random Number Action FLOAT4 type disables trigger
Description: An invalid check was being done with Max value, it only exhibits the problem if this optional parameter is used. Fixed it with a correct range change logic. - [MAP-22863] -Rockwell Variables not Populating
Description: Fixed issue with lazy enumeration variables not populating. - [MAP-22168] -deviceWISE: Hardware ID Mismatch
Description: Fixed a startup issue that caused a hardware ID mismatch. The system now caches the MAC address at startup for consistent operation. - [MAP-23550] -Global Variable with peristed large string gets exported with entire string padded out to length
Description: Runtime used to write the entire memory(max) of a string/binary into the database, making the dwcore.db become unnecessarily large. Now, only the actual data is written into the database, but this only happen if the variable is a scalar type, not in an array of string. - [MAP-22720] -HTTP Server (LWS) locks up after running a VI test for some time
Description: Resolved an issue that caused the server to stop updating variables after a timeout. Connections are now closed and restarted as needed for consistent updates. - [MAP-23773] -Writing to Alias Device Always Results in Error
Description: The return code is now correctly handled, and writing to Alias devices works as expected across all supported data types. - [MAP-23669] -Core crash in image_base64
Description: Internal storage has been updated to use Size_T before multiplication, ensuring that variable sizes are handled correctly without overflow or buffer mismatch. - [MAP-23647] -Hardware ID Mismatch using System Serial Number
Description: The hardware ID module now strips all dashes from the serial number before returning it, ensuring a valid identifier is always provided. (Exception: MAC address). - [MAP-23903] -HTTP client action block cuts the header field content when using libucurl
Description: The 1024-byte header limit has been removed, allowing full header content to be transmitted without truncation. - [MAP-24004] -deviceWISE Core Not Listening on Expected Ports (4011/4012)
Description: Fixed an issue where the deviceWISE core failed to listen on ports 4011 and 4012 due to API signature incompatibility between new drivers and older runtime builds. The runtime and API versions were updated to ensure compatibility and correct port binding. - [MAP-24065] -Getting REJECTED, could not acquire a license - Siemens Listener
Description: Fixed a race condition causing intermittent "cannot acquire license" errors when license pooling was enabled. - [MAP-23370] -HMI Node Crash with Runtime Exception [0xC0000005]
Description: Fixed a crash occuring when an HMI view subscribed to variables before the device was started or after restart, causing the core to reference an invalid object ID during data flow resumption. - [MAP-22569] -Azure IoT Hub Cloud services connector stopping
Description: Azure Device Provisioning Service connection will try to connect automatically when deviceWISE starts and the network is unavailable after previously being connected. - [MAP-22759] -dwnachi Connection Issue
Description: Nachi driver now sends a configurable keep alive so connection is not terminated by robot controller. - [MAP-23137] -Frequent node crash on 25.01.11 version when using the JQ query triggere
Description: Fixed an issue with JQ library releasing local buffer incorrectly. - [MAP-23335] -Investigating Crash Help and SPC package
Description: Resolved crashes related to outdated SPC packages. Deprecated components and associated with communication protocols were removed and updates were merged into main core.
Drivers and Extensions
- [MAP-23546] -Invalid read on _dwappleiosvi_websockets_thread_handler when changing Capture mode
Description: Revised the websocket worker thread to fix valgrind warnings. - [MAP-23545] -Capture Image action from dwappleiosvi returns Unexpected NULL error with bad file path
Description: Changed the error code when the action to save to a file fails. - [MAP-23544] -Valgrind leak on dwappleiosvi_admin_module_init
Description: Fixed memory leak that happened when the driver admin panel was loaded. - [MAP-23515] -Node crash while executing performance tests on dwTrending API
Description: Fixed a bug in a time conversion function that caused invalid memory writes, affecting all trending activity. This issue impacted performance and could lead to crashes. The bug has been resolved to ensure stable operation. - [MAP-23435] -Trending is causing deviceWISE core to crash
Description: When the retention date was null in the trending table it caused an issue. A null check was inserted to prevent the crash, but if a null value is inserted there, it will no longer honor the retention policy. - [MAP-23628] -Okuma driver seems to cause device to indefinitely stay in a Stopping state
Description: The Okuma driver was crashing when the demand write/read was used to a variable that didn't exist. Now the demand is being handled correctly even if the variable doesn't exist. - [MAP-23427] -IFM has two loggers
Description: Only one IFM logger will appear in Workbench when configuring logging under Diagnostics, Logging. - [MAP-23648] -Issue with a new OPC UA Server/FLOAT4 array
Description: Added a new property to the device called Deep Browse Arrays. When selected, an additional folder will be inserted, and the entire array will be read during the browse to determine it's array size. - [MAP-23525] -Atlas Copco and derivatives: Crane Tool Mid61 not firing when using ESTIC driver
Description: dwestic: Added support for revision-1 in mid61 event processing. - [MAP-23472] -node crash in 25.01.11 due to mqtt driver
Description: Added additional error handling to prevent a possible crash when messages are published.
Supported Driver Versions
| Generally Available | |
|---|---|
| Device Driver | Version |
| AcraDyne driver | 1.1.3 |
| Advanced Display Protocol | 1.0.2 |
| Apex Cleco driver | 1.9.4 |
| Atlas Copco driver | 3.10 |
| AWS | 1.0 |
| Azure | 2.1.13 |
| Beckhoff driver | 2.1.9 |
| Bosch Rexroth driver | 1.8.4 |
| Danlaw | 2.12.3 |
| Estic driver | 1.2.0 |
| FANUC CNC Driver | 2.0.4 |
| Fanuc driver | 2.3.3 |
| GPS | 1.0.4 |
| Industrial driver | Updated with each release |
| Ingersoll Rand driver | 1.4.0 |
| Kawasaki | 1.4.0 |
| Keyence | 1.0.6 |
| LDAP – do not use with Linux X86 in versions 21.10 and later | 1.1.2 |
| Lua | 1.1.4 |
| IBM Maximo | 1.1.4 |
| IFM IO-Link | 1.0.1 |
| Melsec | 3.5.7 |
| Mitsubishi driver | 3.3.7 |
| Modbus driver | 2.11.7 |
| Modbus Server driver | 1.1.8 |
| Modem | 1.5.1 |
| MQTT driver | 2.1.11 |
| MTConnect driver | 1.3.3 |
| NMEA GPS | 1.0.4 |
| OAuth2 | 2.3.2 |
| Omron driver | 3.8.2 |
| OPC-UA Client driver | 3.1.26 |
| ROC Plus driver | 2.0.3 |
| Rockwell ControlLogix driver | Updated with each release |
| Schneider Electric | 2.9.0 |
| Siemens S7 driver | 3.0.7 |
| SNMP driver | 1.1.1 |
| Sparkplug B | Included and Updated as part of MQTT |
| Stanley Tools driver | 1.3.0 |
| Sturtevant Richmont driver | 1.8.4 |
| Sysmon | 1.0.2 |
| TCP Listener | 2.4.0 |
| Toyopuc | 1.0.5 |
| TR50 | 2.6.2 |
| deviceWISE View | 2.4.6 |
| Technology Preview | |
|---|---|
| Device Driver | Version |
| Amcrest | 1.0.1 |
| AWS SiteWise | 1.0.3 |
| BACnet / IP driver | 3.2.12 |
| Barcode Scanner | 1.1.1 |
| CODESYS driver | 1.0.0 |
| CTI (Control Technologies Inc.) driver | 2.1.5 |
| EDU (not built for Windows 64-bit) | 1.0.1 |
| E-Sensors | 1.0.1 |
| File Watcher - Updated with 23.04 | 1.0.8 |
| Google Cloud Platform (GCP) | 1.0.0 |
| HAAS | 1.0.2 |
| GrovePi driver(Only in Raspbian directory) | 1.0.2 |
| HTTP Server | 1.0.1 |
| J1939 IXXAT device Driver | 1.1.1 |
| JSON | 1.0.0 |
| Melsec | 1.0.1 |
| Nachi – (Windows Only - Win32 and Win64) | 1.0.0 |
| 1.0.1 | |
| OPTO22 | 1.0.0 |
| Sandbox | 1.3.2 |
| Serial | 1.3.0 |
| SICK CLV Scanner | 1.1.7 |
| Simulation | 1.0.0 |
| Telit SmartIO | 2.2.1 |
| Trending | 1.3.14 |
| Visual Inspection | 1.0.16 |
| Virtual | 1.3.0 |
| Xirgo | 1.3.0 |
| Zaxis (only built for Windows products) | 1.0 |
Upgrading from previous versions
Backup before upgrading! You should do a Backing up and Restoring a node's configuration of your configuration from the Workbench prior to upgrading to a new version of deviceWISE.
Updating from an earlier release level of an Enterprise Gateway to 25.02
Customers updating from 21.05 or earlier release, will need to update both the deviceWISE runtime and the package files to the 25.02 build level before starting their deviceWISE application.
For Windows Enterprise Gateway products:
Upgrading a Windows Enterprise Gateway product from a version before 19.1.6 to 25.02
We moved to a new installation architecture for Windows Asset Gateway and Enterprise Gateway products with version 19.1.6. These Special Notes apply to a one-time transition from a Windows Gateway version before 19.1.6 to a Windows Gateway version after 19.1.6.
If you are upgrading a Gateway for Windows product to version 19.1.6 or later, you must do the following:
- Perform a node backup of deviceWISE
- Backup all files used in the Staging Browser folders or properties files that were added outside of the original deviceWISE installation. (For example: C:\deviceWISE\Runtime\staging and C:\deviceWISE\Runtime\dwcore)
- Uninstall the (pre-19.1.6) version of the Enterprise Gateway for Windows product
- Install deviceWISE Enterprise Gateway for Windows or deviceWISE Asset Gateway for Windows using the given installers.
- Copy the files backed up from step #2 contained in the Staging Browser folders or properties files to the new installation folder. (For example: C:\Program Files (x86)\deviceWISE\Gateway\staging and C:\Program Files (x86)\deviceWISE\Gateway\dwcore)
- Restart deviceWISE.
- After updating to 25.02, you will need to add all device drivers and extensions from the new 25.02 release level.
- Restore your node.
Upgrading a Windows Enterprise Gateway product from 19.1.6 or later to 25.02
A firmware update from a release for Enterprise Gateway for Windows before version 19.1.6 to 25.02 is not supported. You must do a complete product installation as noted in the previous section.
If you are updating an Enterprise Gateway for Windows 64-bit products from the 19.1.6 release or later, then you can use the firmware update option.
After updating to 25.02, you will need to add all device drivers and extensions from the new 25.02 release level.
After updating the runtime and the package files, you may restore your node from a backup if you did a node backup before installing the new version of runtime and packages.
For AIX, Linux, or WinCPU Enterprise Gateway products:
If you are updating an Enterprise Gateway from a 17.2.3 through 25.02 (inclusive) release, then you can use the firmware update option. A firmware update from a release before 17.2.3 is not supported.
If you are updating an Enterprise Gateway from a 17.1.14 or earlier release to 25.02, you must do a complete product installation. This is required to install the supporting libraries and 3rd party support files. These supporting files are not included in a firmware update for an Enterprise Gateway, however they are included in a complete install.
After updating to 25.02, you will need to add all device drivers and extensions from the new 25.02 release level.
After updating the runtime and the package files, you may restore your node from a backup if you did a node backup before installing the new version of runtime and packages.
A firmware update from 16.1.8 or earlier to 25.02 is not supported for CentOS 7 or systemd installations. A full installation is required.
20.1.9 is the final release for VxWorks-based gateways and got removed from builds beginning with the 20.1.10 release. If you need assistance, please contact us here.
Updating from an earlier release of an Asset Gateway to 25.02
Customers updating from 21.05 or earlier release, will need to update both the deviceWISE runtime and the package files to the 25.02 build level before starting their deviceWISE application.
For Windows Asset Gateway products:
Upgrading a Windows Asset Gateway product from a version before 19.1.6 to 25.02
We moved to a new installation architecture for Windows Asset Gateway and Asset Gateway products with version 19.1.6. These Special Notes apply to a one-time transition from a Windows Gateway version before 19.1.6 to a Windows Gateway version after 19.1.6.
If you are upgrading a Gateway for Windows product to version 19.1.6 or later, you must do the following:
- Perform a node backup of deviceWISE
- Backup all files used in the Staging Browser folders or properties files that were added outside of the original deviceWISE installation. (For example: C:\deviceWISE\Runtime\staging and C:\deviceWISE\Runtime\dwcore)
- Uninstall the (pre-19.1.6) version of the Asset Gateway for Windows product
- Install deviceWISE Enterprise Gateway for Windows or deviceWISE Asset Gateway for Windows using the given installers.
- After updating to 25.02, you will need to add all device drivers and extensions from the new 25.02 release level.
- Copy the files backed up from step #2 contained in the Staging Browser folders or properties files to the new installation folder. (For example: C:\Program Files (x86)\deviceWISE\Gateway\staging and C:\Program Files (x86)\deviceWISE\Gateway\dwcore)
- Restore your node.
Upgrading a Windows Asset Gateway product from 19.1.6 or later to 25.02
A firmware update from a release for Asset Gateway for Windows before version 19.1.6 is not supported. You must do a complete product installation as noted in the previous section.
If you are updating an Asset Gateway for Windows 64-bit products from the 19.1.6 release or later, then you can use the firmware update option.
After updating to 25.02, you will need to add all device drivers and extensions from the new 25.02 release level.
After updating the runtime and the package files, you may restore your node from a backup if you did a node backup before installing the new version of runtime and packages.
For AIX, Linux, or WinCPU Asset Gateway products:
If you are updating an Asset Gateway from a 17.2.3 through 22.02 (inclusive) release, then you can use the firmware update option. A firmware update from a release before 17.2.3 is not supported.
If you are updating an Asset Gateway from a 17.1.14 or earlier release to 25.02, you must do a complete product installation. This is required to install the supporting libraries and 3rd party support files. These supporting files are not included in a firmware update for an Asset Gateway, however they are included in a complete install.
After updating to 25.02, you will need to add all device drivers and extensions from the new 25.02 release level.
A firmware update from 16.1.8 or earlier to 25.02 is not supported for CentOS 7 or systemd installations. A full installation is required.
For more information about upgrading your software, see Updating products.
20.1.9 is the final release for VxWorks-based gateways and got removed from builds beginning with the 20.1.10 release. If you need assistance, please contact us here.