If a device is deleted, the device may not be removed from Litmus Edge processes. The vertical scroll bar in the CSV Upload for tags Error dialog does not scale correctly, limiting visibility to only 4 errors.
|
After editing the Digital Twin model, the updated version does not appear automatically and requires a manual page refresh to see the changes. After stopping the instances, message transmission unexpectedly increases and persists for hours. Restarting the service resolves the issue. The Hierarchy items do not retain the second modification and are reverted to their original positions after saving the model. Setting an Instance interval to a high-value results in a complete crash. Long model and instance names may cause UI buttons (Upgrade Instance, Reload, Save Model) to break. There will be no error encountered when creating a model or instance with the same name. The thumbnail for the cloned model is not displaying correctly. Long instance names (over 200 characters) may not display properly in the templates view, requiring screen resizing for full visibility.
|
|
Flows may reach a Maximum restart threshold reached status, resulting in a RUNNING status with inaccessible flow and an error message when attempting to edit. When copying an Analytics flow in the same or a different group, all connection names revert to default values (value and event). In the Add Processor dialog box, user input is hidden by drop-down menu list. The Expression Processor function will display an error regardless of its connection status.
|
There is no notification to the user if you delete a container that is in running or paused state. When running a command, the Hide button may not display correctly. You may not be able to disconnect a running container from the Docker network when using ipvlan driver. The MS SQL Server and Elastic Server applications may not successfully deploy from Applications > Marketplace. Launching applications from Litmus Edge Manager to Litmus Edge may result in a 400 Bad Request error. Networks and volumes created from compose apps have a tmp_ prefix, which affects their naming convention. Adding invalid credentials in Add a Marketplace Catalog dialog box results in a generic internal error instead of a specific error message. After upgrading from Litmus Edge Manager 2.16.4 to 2.16.7, registry values are displayed as undefined in the components list, leading to application launch failures on all Litmus Edge instances.
|
There may be issues trying to send max batch values with the AWS SiteWise connector. The edit feature is unavailable for non-UNS metadata fields in Device details of Litmus UNS connector. External timeseries DB for Influx v.1.0 shows a persistent successful connection status, but users may encounter various error messages on the analytics page. You can create blank local topic for an inbound subscription. This will be removed in future releases. Fields for the AWS SiteWise connector may not have the correct input validation. You may not be able to delete a password for the NATS connector if a password was configured when the connector was created. The MSSQL connector does not transition to a Failed state when disconnected from the database. The Kafka connector continues transmitting data even after disabling subscriptions. The high CPU consumption and writer for topic is not found error occurs when all subscriptions are disabled in Kafka connector. The Kafka connector has memory leaks when the payloads exceed the limit.
|
|
You may not be able to download support bundles successfully. If you create a template and then delete DeviceHub devices from Litmus Edge, the deleted devices may not be successfully uploaded from the template that contains the deleted devices. When attempting to add a mount point for FTP server, you will run into an Internal Server Error. If you deactivate Litmus Edge, you may get an error message in Litmus Edge but a success message in Litmus Edge Manager. Analytics events on the Events page may incorrectly display as Group Locked. Tag names in the Events page may incorrectly display as nil. You may run into an activation error message Last error: "Not found" during activation that may not clear from the UI. Clearing permissions for DeviceHub may not fully eliminate them as expected. Access control edit page displays OPC UA errors when modifying user roles. When activating Litmus Edge Manager with an invalid activation code, two different error pop-ups may be produced. Users with insufficient RBAC permissions are unable to add cloud connectors, as the Edit role details button is greyed out. Templates may generate a Failed Template Error with incorrect event details.
|
Terminal User Interface (TUI): |