Product Updates
2020

Litmus Edge 3.0.0.0

3min

Release Date: October 16, 2020

Enhancements and New Features

Description

DeviceHub 2.0

  • Added performance improvements for DeviceHub. With these improvements system consumes less CPU/RAM resources.
  • Added Advanced Drivers
  • Added support for TagName Aliasing
  • Start/Stop individual driver communication
  • Legacy drivers are suffixed with Gen 1 for identification

IMPORTANT:

  • Deprecated BACnet Driver in 3.0.0.0 image. It is still available on 2.x versions. Upcoming release of 3.x will have an advance BACnet driver with performance improvements.
  • Special characters in device and TagName are converted to underscore in alias topic

Flows Manager

  • Start/Stop/Delete multiple instances (up to 4) of flows
  • User can add new flows with maximum allowed RAM
  • Added support to download flows.json file
  • Added support to upload custom node modules
  • Added support to download the logs
  • Upgraded with node-red backend (1.0.6)
  • Included new nodes
  • Included Access Subscribe and Access Publish which restricts direct access to message broker to improve security
  • Access Publish and Subscribe can search through list of topics
  • Flows are included as part of backup/restore and template
  • Flows permission fixes for Admin and Observer Edge users

INFO:

  • To show all topics allowed by Access API in Access Publish/Subscribe node, you need to start typing the name in the topic name field.
  • Search will work after adding the Access API Token and saving the flows.
  • Flows backup from previous system won't be restored automatically with 3.x, however a user can manually export the flows json configuration from 2.x flows and import it to 3.x flows

New and improved Integration Connectors

  • Added support for CA signed certificate with Azure IoT hub
  • Added connector for Oracle DB
  • Integration connectors list with search functionality
  • Added Access Connector
  • Updated libraries for Kafka connectors
  • Improvements for database connectors
  • Integration Logs are available to user. This logging is disabled by default. User can click the CC card and enable the log to have it appear on the CC dashboard.
  • Bug fixes and general UI enhancements

INFO:

  • Database Schema has the field value type changed from NUMERIC to VARCHAR

Enhancements to Analytics

  • Ability to run TensorFlow and TensorFlow lite models natively
  • Import and export ability for Analytics
  • Live data debug support
  • Tengo scripting engine to perform a variety of changes on metadata

INFO:

  • CPU must support AVX to run TensorFlow models with Analytics. More Information available on TensorFlow website.

Enhancements to Marketplace

  • Additional registry login support (AWS, Azure, GCR)
  • Catalog V2 added as a default catalog
  • Improved UI and UX
  • Improved application launch progress with providing more information to user through informative UI messages
  • Marketplace permission fixes for Admin and Observer Edge users

Enhancements to OPC UA Server

  • Added OPC UA Client Certificate Authentication
  • Added update for easy import/export of OPC UA Server configuration
  • OPUCA Server configurations are included with backup/template
  • Various bug fixes and UI improvements

Device Management improvements

  • WiFi and LTE support for EL300
    • Kernel Upgrade to provide Wifi Support for HPE Edgeline EL300 (Intel Wireless-AC 9260 Module)
    • Added support for EL300 LTE module
  • Redesign Network page
  • Redesign Services page
  • Enhancements to Support page
  • Enhancements to Edge events
  • Improvements to Backup/Restore and Template
    • Backup file encryption
    • Changed backup format from JSON to ZIP file
    • Implemented mechanism to import 2.6.x configurations
    • UI improvements

Improved DeviceHub Agent:

  • Upgraded DeviceHub Agent 3.2.2.0. It can be found in System > Support > File Downloads
  • Default port is changed to 41250
  • Enhanced DeviceHub agent to allow sending csv files to Edge
  • Added columns Type and Value into the tags table
  • Amended CSV generation in accordance with FreeTag changes
  • Shows the type number if the type is unknown
  • Added statistic info section with total count of tags sent, server connection state, OPCDA connection state.
  • Performance improvements
  • UI improvements

INFO:

  • Keep network ID : 0.0.0.0 to monitor network traffic across all the IP addresses

General UI & UX Improvements

  • Icons changed for Datahub, Analytics
  • Improved on authorization access for developer and observer user permissions throughout web UI
  • Manage identity certificates and CSRs from web UI
  • Improved error handling and error messages
  • Configurable column in Devicehub tag page
  • Web UI Idle time out extended to 24 hrs
  • Introduced progress bar to show cloud activation end point update progress
  • Implemented select all/none functionality for browse tags window

Miscellaneous

  • Implemented CSRF protection. Cross-Site Request Forgery (CSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they are currently authenticated.
  • Implemented Self Signed Certificate generation upon adding a new device
  • Users can manage identity certificates and CSRs from web UI
  • System is accessible from browser by host name if their computer supports mDNS. This is a convenient feature if device uses DHCP for address allocation and the address may change time to time. The host name is static and it never changes.

Known Issues

Description

  • Running Marketplace Application configuration are not added to template
  • Backup from previous system with same TagName may show an error upon restore
  • Backup/Restore from previous system may fail for some cases
  • PLC Status tag may show an error of “unexpected token” in flows

Important Information

Description

Deprecated Components

  • Deprecated LWM2M
  • Deprecated Flows, which is replaced with advanced Flows Manager
  • Deprecated BACnet driver
  • Deprecated BACnet Service Management from UI
  • Deprecated Git based Marketplace Catalog (V1), replaced with Marketplace Catalog (V2)
  • Deprecated Reinitialize button in DeviceHub. It isn't needed for DeviceHub 2.0 and start / stop drivers has the same process.

IMPORTANT:

  • Software update through UPD is not compatible for updating systems from 2.x to 3.x. Fresh installation of LE is required to launch 3.0.0.0
  • BalenaEtcher v1.5.109 can be used to create bootable USB drive from ISO file
  • Default password for first time login has changed to “litmusedge”
  • Clear browser cache after performing a software upgrade
  • Always make sure supported browsers are updated to the latest version
  • DeviceHub service stops if minimum disk space requirement isn't met. Please make sure to have minimum 1 GB disk space while deploying applications.
  • LEM 1.9.x is compatible with both LE 2.x and LE 3.x
  • Edge FTP server listens to port 21
  • Auto-provision of device from Litmus Edge Manager-1.7.2 is supported starting 2.6.1 LE
  • Valid production licenses are expected to work even after clean installation of 3.0.0.0 on the same device
  • Duplicate Tags prevent restoration of a 2.6.x backup to a newly installed 3.0.0.0 instance. Remove duplicate Tags prior to backup.

System Migration from 2.x to 3.x

Litmus Edge migration refers to taking backup from 2.6.x version and restoring it on 3.x, transferring all configurations in the process. Production deployments running on 2.x doesn't have to migrate to 3.x, as migration process may not be successful depending upon the environment. Software update through UPD is not compatible for updating systems from 2.x to 3.x. Fresh installation of LE is required to launch 3.0.0.0

What does success look like?

Successfully performed migration means that all configurations has successfully restored and that the new system has no incompatibility with previously accessible functionality, except for those that are deprecated.

Deployment Environments

Users can install ISO directly on the following environments:

  • Hyper-V
  • KVM
  • VMware ESXi

Additional information can be found in documentation.