Errata
The following are known issues in our latest release
- 1 Firefox browser compatibility
- 1.1 Current Behavior
- 1.2 Workaround
- 2 Package README
- 2.1 Observation
- 2.2 Workaround
- 3 Analytics Screen Refresh
- 3.1 Current Behavior
- 3.2 Workaround
- 4 Use Case Commissioning Error
- 4.1 Current Behavior
- 4.2 Workaround
- 5 High Latency During Network Congestion
- 5.1 Current Behavior
- 5.2 Workaround
- 6 Schedule event on click is showing wrong threshold keys
- 6.1 Current Behavior
- 6.2 Workaround
- 7 Camera view device edit is not populating correct details
- 7.1 Current Behavior
- 7.2 Workaround
- 8 Mismatch in analytics count for most of the use-cases
- 8.1 Current Behavior
- 8.2 Workaround
- 9 Storage Purge trigger is not deactivating the alert
- 9.1 Current Behavior
- 9.2 Workaround
- 10 Some of the Notifications in Notification history is not loading
- 10.1 Current Behavior
- 10.2 Workaround
Firefox browser compatibility
Current Behavior
Unexpected crashes and rendering are noticed on Firefox.
Workaround
Chrome is the currently recommended browser. We will bring support to Firefox in one of the future releases.
Package README
Observation
The README.md in the <install_dir>/deploy/ has outdated instructions.
Workaround
Please ignore this README file and follow the MEGH documentation page for information on installation instead.
Analytics Screen Refresh
Current Behavior
Online/Offline connection status on stream window is not updated immediately.
Workaround
Wait for 30 sec or refresh the page.
Use Case Commissioning Error
Current Behavior
When a use case commissioning action errors out, the program currently tries indefinitely to auto-restore it. This might lead Nimble to end up in an unfavorable state.
Workaround
When use case commissioning errors out, please delete the errored out use case and re-deploy manually with the error rectified.
High Latency During Network Congestion
Current Behavior
Nimble may buffer up to, by default, 30 frames per channel before dropping data. When the network is congested these buffers may fill up causing high latency.
Workaround
Update the environment section of the docker-compose.yaml file to specify the following variable:
environment:
- NIMBLE_EXECUTION_QUEUE_SIZE=5Setting the queue size to 30 will add a maximum of 1 second of latency for a 30fps channel or 6 seconds of latency for a 5fps channel during network congestion. For sites with network congestion it is recommended to set this value to 5.
Schedule event on click is showing wrong threshold keys
Current Behavior
Scheduler calendar event on click is displaying nimble threshold keys instead of the keys that shown in the portal.
Workaround
No workaround, will be fixed in next release.
Camera view device edit is not populating correct details
Current Behavior
On click on edit button in the device list of camera view page the edit form is populating incorrect device details.
Workaround
Device edits can be made from the site view page or device view page.
Mismatch in analytics count for most of the use-cases
Current Behavior
In the event history, the count seen in table is not the exactly same when the images are retrieved.
Workaround
No workaround, will be fixed in next release.
Storage Purge trigger is not deactivating the alert
Current Behavior
Triggering storage purge of a particular channel is not deactivating the activated alert of that channel.
Workaround
No workaround, will be fixed in the upcoming release.
Some of the Notifications in Notification history is not loading
Current Behavior
In the notification history when clicked on the notifications some will not be loading.
Workaround
Close the notification which was not loading and open the same notification.