Litmus Edge 4.0.14

release date june 26, 2026 review the current list of limitations docid\ eax yfkpggsv lhc4um5u note for information on updates to apis, see the litmus edge https //api litmus io/view/2s9y5r1rvg#f4804d0e 07a6 4bbc 862e a346cdc53870 and litmus edge manager https //api litmus io/view/2s9y5r1rvg#b7e9be00 4246 4091 8e34 bbe527228b46 change logs new features description devicehub the following new drivers are available in this release automation direct automationdirect productivity series ethernet ge fanuc ge ethernet global data (gen2) experimental idec idec serial yokogawa yokogawa dx ethernet yokogawa mx ethernet integration the new databricks zerobus ingest connector is available in this release enhancements description applications containers page now displays exposed ports in the following format host port → container port , for example 3500 → 3000/tcp devicehub allen bradley compactlogix ethernet advanced and allen bradley logix ethernet renamed the access mode option from compactlogix to logical logical mode now uses id based requests for flexlogix, compactlogix, and controllogix plcs for all firmware versions the global variables folder is now pinned to the top of the browse results improved ab df1 ethernet driver browse and datatype support default datatypes are now correctly assigned during browse for output, input, integer, ascii, and hex/bcd registers added int datatype support for output, input, timer, counter, control, and register data files improved b\&r pvi ethernet driver performance the driver has been optimized to reliably support up to 10,000 tags to enable high density deployments with large b\&r plc installations improved codesys v2 symbolic (gen1 3) driver fixed connectivity issues, added support for browsing devices with or without sym/sdb files, and introduced user configurable options for motorola byte order and protocol settings improved euromap 63 driver session file handling to automatically clean up req files when the controller does not respond to prevent shared folder clutter added float data type support for the ge ethernet absolute driver r , ai , aq , and w registers now support float data types to enable accurate reading of floating point values from ge plcs added password authentication support for the s7commplus driver plcs configured with legacy access control in tia portal can now be connected by specifying a password in the device settings device settings have also been reorganized with advanced options moved to a collapsible section for a cleaner configuration experience improved toyopuc ethernet driver addressing for bit registers bit (boolean) tags now use discontinuous addressing, requiring both a word and bit address component to match plc programming software conventions existing configurations are automatically migrated during upgrade improved other toyopuc ethernet driver issues fixed read/write issues for eb register addresses above 32767, corrected maximum address ranges across multiple register types to align with plc specifications, and added support for jl and js registers (pc10g nano) improved toyopuc ethernet driver file name configuration with updated values (p1, p2, and p3) in the file number dropdown selector added user id configuration to the yokogawa dx ethernet driver to support communication with controllers that require user authentication fixed inconsistent field ordering in driver configuration settings device and tag settings fields across multiple drivers (including allen bradley, siemens, ge, yokogawa, and others) now display in a consistent and predictable order a new count field is available at the tag level for all register types to enable batch reads of consecutive registers as arrays added array read support for the following drivers keyence nano ethernet saia ethernet added data type support for the generator driver the following data types are now available bool , int32 , float32 , uint32 , and json added tag browsing support for the plc5 driver improved automationdirect productivity series ethernet driver polling performance by implementing request grouping, reducing the number of requests needed to read tags the following drivers now display a deprecation warning indicating they will be removed in a future release mitsubishi qj71e71, osi agent, allen bradley compactlogix ethernet freetag, and allen bradley compactlogix ethernet advanced added help text for the name and tag name fields in tag settings to describe their purpose and usage renamed the optional parameters section to advanced parameters in the connect device and edit device dialogs added help text for the following generic device driver tag settings fields to clarify expected values payload , value length , response terminator , and response max length configuration field tooltips are now displayed in the create and edit subscription dialogs events the events list table has been migrated to ag grid for improved performance and responsiveness with large event datasets integration the aws iot sitewise connector now supports high precision timestamps through timestamp timeinseconds and timestamp offsetinnanos fields in devicehub payloads added retain support for mqtt v5 outbound publishing when defining outbound subscriptions in the mqtt v5 cloud connector, a retain option is now available to allow published messages to be retained by the broker for new subscribers the enable and disable buttons for integration connectors are now available during transitional states such as connecting this allows manual recovery when a connector is stuck updated the display name of the aws iot core gen 2 mqtt connector to mqtt aws iot core gen 2 for consistency system improved nats proxy performance and reduced memory usage on edge devices message delivery latency has been reduced and memory buffers have been right sized for constrained edge deployments when you log in to a high availability backup node, a status banner indicates that the node is in standby mode and most features are unavailable if the node is promoted to primary or ha configuration is removed, the page redirects to the dashboard resolved issues description analytics fixed analytics output pane and debug button behavior resolved an issue where the processor output message pane would auto collapse when paused and the debug button was unresponsive this enables you to inspect and debug processor data on the analytics canvas again fixed file permission issue with analytics file writer output files generated by the analytics file writer processor are now accessible to other system components such as flows and the file browser solution this allows you to move, delete, and manage output files without encountering permission errors fixed issue where moving average, moving max, and moving min processors could produce an unexpected error when the data type or window size was not configured the processors now return an error state instead of exiting unexpectedly applications fixed issue with incorrect error message when a non privileged user attempted to launch a privileged application a failed to create an application,undefined error message displayed instead of failed to create an application rejected by administrative policy privileged and some directories require additional permission fixed issue where the template feature was disabled on a licensed litmus edge docker container fixed issue where the docker terminal did not correctly display utf 8 box characters and ui symbols, for example arrows and return symbols fixed issue where text characters in user defined container names were dropped, causing the displayed name to differ from the name the user entered fixed issue where deleting a container image from a browser tab with a stale image id returned an error indicating the image did not exist devicehub fixed issue where the csv export option (dump tag data) in devicehub > devices > data was only available to users in the administrator group now users with read or modify privileges for devicehub can perform a csv export fixed euromap 63 driver compatibility with km mc4 controllers removed special characters (including underscores) from generated job and sess file names to resolve connection failures with controllers that do not accept special characters in file names fixed allen bradley compactlogix driver issue with bad tags disrupting valid tag reads resolved a regression where a single misconfigured or invalid tag in a multiple service request would cause other properly defined tags to fail invalid tags are now isolated so they no longer impact the reading of valid tags fixed issue where the open protocol ethernet driver rejected controller keepalive messages that did not include a revision number the driver now accepts keepalive messages without a revision for pf8 series controllers fixed issue where bulk deleting tags caused the tag count to display a negative value and prevented new tags from being added the tag count now correctly reflects the number of active tags after a bulk delete fixed keyboard navigation issues in the create device dialog pressing enter then tab after selecting a device type no longer causes the device type field to revert and lose focus the down arrow key now moves through device type options one at a time instead of skipping every other option digital twins fixed issue where digital twin dynamic attributes published null values on transformations run after the first transformation this caused the digital twin instance to become inactive integration fixed issue where the insecure skip verify option in rest integration settings was not applied https connections now correctly skip tls certificate verification when this option is enabled this fix also applies to the oauth token fetch step fixed issue where the aws iot sitewise connector forwarded messages with null tag values which caused ingestion errorrs and high log volumes the connector now drops messages where the tag value is null and produces an invalid payload value is required error in the logs fixed issue where influxdb v2 cloud connector failed to automatically reconnect the connector now correctly recovers and resumes data streaming after the influxdb service is restarted, eliminating the need to manually disable and re enable the connector opc ua fixed issue where the opc ua server failed to publish tag values in json format system fixed issue where component names in the template ui were normalized this caused names that differed only by case to appear identical fixed issue where downloading a template before the page finished loading produced an incomplete file the download button is now disabled until configuration data is fully loaded fixed issue where several options (for example dns and ntp ) were missing under dm (device manager) in system > device management > templates fixed issue where templates could not be created or downloaded fixed issue where cloud backup from litmus edge to litmus edge manager failed with a 401 error because an encrypted vault reference was sent as the authentication token fixed issue where the ui could become unresponsive in system > events when the system generated a high volume of events from a single database file additionally, csv files may not have generated and downloaded high availability fixed issue where api keys and activation configuration from litmus edge manager were overwritten during ha synchronization marketplace applications and flows now properly fail over and are migrated to the backup instance when the primary fails fixed issue where ha configuration persisted on the primary node after the backup node was promoted to primary status now the original primary node no longer displays ha configuration after being disconnected and connected again network interface changes are now correctly reflected on backup nodes fixed issue where the primary node incorrectly showed sync status as stopped fixed issue where the backup node was not accessible after deleting a high availability configuration fixed issue where proxy urls configured on the primary node were not copied to the high availability backup node fixed issue where several components including device hub, digital twin, and cloud connectors were not reliably replicated from the primary to the backup node the ha sync mechanism has been redesigned to use each component's own backup and restore apis fixed issue where ha sync timestamps were inconsistent which caused confusion about whether synchronization was working fixed issue where docker images synced from the primary node were not visible on a promoted backup node and a race condition in the ha transport layer could leave the connection broken until a service restart fixed issue where the ha database sync timer ran on all devices including devices where ha was not configured addressed vulnerabilities in third party components