...
| Expand |
|---|
| title | v4.0.11 June 1, 2022 |
|---|
|
| Expand |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| |
| Expand |
|---|
| - Fixed Python Scripting API bug around updating Users
|
|
| Expand |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| |
| Expand |
|---|
| - Added NPE protection when handling Aliases
- Fixed Elecsys namespace Edge Node ID filtering
- Fixed handling of Custom Namespace JSON tags to prevent unnecessary/improper reconfiguration of tags
- Added NPE protection to aliased metrics when handling tag writes
- Added NPE protection when 're-ordering messages' that could prevent Edge Nodes from showing as online
- Fixed issue with property updating in UDT members that are in member UDTs and folders
- Fixed Elecsys namespace handling of SINT16 data types
|
|
| Expand |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| - Added a 'Friendly Name' configuration option for File Records
- Added a 'File Scan Rate Time Unit' configuration option for File Records to allow for faster scans
- Added additional info tags for File publishing including 'Files to Auto-Publish', 'Remaining Retries', and 'Reset'
- Improved thread naming for File Publishers to make them more identifiable
- Added Tag Path validation to configuration
- Added support for treating 'Device level UDTs' as devices when converting UDTs
- Improved Birth caching to increase performance
- Optimized caching to reduce overall memory footprint
- Removed excessive calls to 'getTagConfigsAsync' to increase performance
|
| Expand |
|---|
| - Fixed retry logic when publishing files
- Added NPE protection when handling Aliases
- Fixed an issue where updating a File Configuration could result in removing or resetting file info tags
- Fixed issue with birth caching logic that produced failures in flushing history when flushing in-order
- Added NPE protection when updating Transmission Info tags
- Fixed issue that could result in DATA messages being published before the BIRTH sequence when flushing history in-order
- Fixed startup/shutdown synchronization that could result in thread leaks
- Fixed issue when flushing in-order that could result in an endless loop with many devices
- Fixes to Edge Node discovery to ensure discovery and status flags update properly
- Fixed issue with Transmission publishing incorrect (newer) metric timestamp in Birth message when using in-order/RAM store and forward
- Added NPE check when shutting down Transmission clients
- Fixed RejectedExecutionException that could occur when deleting tags Transmission was publishing
- Fixed potential double DEATH publishes that could occur on device folder removal
|
|
| Expand |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| - Added Python scripting API for scripted configuration
|
|
| Expand |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| - Improved Birth caching to increase performance
- Removed excessive calls to 'getTagConfigsAsync' to increase performance
|
| Expand |
|---|
| - Fixed startup/shutdown synchronization that could result in thread leaks
- Fixed issue that could result in the Push Policy reverting back to 'Push to All'
|
|
| Expand |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| - Improved Birth caching to increase performance
- Removed excessive calls to 'getTagConfigsAsync' to increase performance
|
| Expand |
|---|
| - Fixed startup/shutdown synchronization that could result in thread leaks
- Fixed issue that could result in the Push Policy reverting back to 'Push to All'
- Modified scripting API to use 'AzureSetId' instead of 'AzureSet' for Set key names
|
|
| Expand |
|---|
| title | Google Cloud Injector |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| - Added TCP port number configuration option for connecting to Google IoT Core
- Improved Birth caching to increase performance
- Added Python scripting API for scripted configuration
- Removed excessive calls to 'getTagConfigsAsync' to increase performance
- Added a 'max throughput' configuration option to throttle data flowing to Google IoT Core
|
| Expand |
|---|
| - Fixed startup/shutdown synchronization that could result in thread leaks
- Fixed issue that could result in the Push Policy reverting back to 'Push to All'
|
|
| Expand |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| - Improved Birth caching to increase performance
- Added Python scripting API for scripted configuration
- Removed excessive calls to 'getTagConfigsAsync' to increase performance
|
| Expand |
|---|
| - Fixed startup/shutdown synchronization that could result in thread leaks
- Fixed issue that could result in the Push Policy reverting back to 'Push to All'
|
|
| Expand |
|---|
| title | EFM ABB Totalflow Module |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| - Added Tag Path validation to configuration
|
| Expand |
|---|
| - Fixed meter type handling during auto-discovery when using applications other than AGA3, SUAGA3, AGA7, and SUAGA7
|
|
| Expand |
|---|
| title | EFM Emerson ROC Module |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| - Added Tag Path validation to configuration
|
|
| Expand |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| |
|
| Expand |
|---|
| title | Opto22 groov EPIC and SNAPPAC Driver |
|---|
|
| Expand |
|---|
| title | What's New or Improved |
|---|
| |
|
|
Release notes for earlier module versions available here
