Litmus Edge 3.2.8

3 min

Release Date: June 23, 2022

Enhancements and Improvements

Description
DeviceHub: OPCUA-subscribe gen2 driver now offers a new topic in the format devicehub.batch_write.${DeviceID} for supporting batch writes.
System: Editing Marketplace Catalog will now hide Client Secret values

Resolved Issues

Description
DeviceHub: Observer-role users will no longer be able to delete devices in Show devices table view. Developer-role users can now successfully update devices in Device Details mode When Emerson driver ROC800 ethernet Polling Interval is updated with a new value, it might stop polling. Polling now continues at the rate of the specified new value.
Flows Manager: Multiple attempts to start flow now correctly shows 400 Bad Request status code accompanied by message flow is starting, please wait... Depreciation message for DataHub Subscribe node has been removed. The node will not be removed in the future.
Applications: Intermittent catalog synchronization issues (with a 502 Error) for the Container Registry table has been resolved.
Integration: Google Cloud Pub/Sub Connector will now display DISCONNECTED status for unauthorized users
System: Memory leaks (leading to massive memory utilization) associated with excessive event traffic (>5 events per second) has been fixed. Device Management: Fixed issues with upgrade between 3.2.3 to 3.2.5 Data store settings are preserved now during software upgrade. Events: Integration Connectors events are now successfully generated. LDAP/AD Auth: After Adding a Provider, groups are now saved with the associated Provider ID. (Previously stuck on loading the groups screen without saving the Provider ID). System > WiFi now successfully displays/hides depended on whether the Litmus Edge device contains a WiFi card or not.
Licensing: Litmus Licensing Server connected to a Litmus Edge instance will now have a more reliable and smoother connection.

Known Issues

Description
Applications: An unavailable Container Registry may lead to a failed deployment attempt of the respective Catalog App. Workaround: Perform a catalog Sync Marketplace operation to refresh the Container Registry table.

Docs powered by Archbee