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 Mismatch in analytics count for most of the use-cases
- 6.1 Current Behavior
- 6.2 Workaround
- 7 Storage Purge trigger is not deactivating the alert
- 7.1 Current Behavior
- 7.2 Workaround
- 8 Site Reports Notifications list shows notification count as 0
- 8.1 Current Behavior
- 8.2 Workaround
- 9 Alert Edit from Rule preview is not working.
- 9.1 Current Behavior
- 9.2 Workaround
- 10 Missing Post usecase is not supported with On demand feature.
- 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.
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.
Site Reports Notifications list shows notification count as 0
Current Behavior
Site Reports table shows the total notifications count as 0 even though there are notifications that are being sent.
Workaround
No workaround, will be fixed in the upcoming release.
Alert Edit from Rule preview is not working.
Current Behavior
When you click edit on a particular rule alert sometimes the alert edit page is not loading properly.
Workaround
Please refresh the alert edit page this will give you an option to edit the alert again.
Missing Post usecase is not supported with On demand feature.
Current Behavior
Missing Post will only receive one notification when there is switch from having detections to a blank frame with no bounding boxes in the video stream. Repeated notifications don’t get sent as long as video frames are empty when on demand feature is on.
Workaround
No workaround, will be fixed in the upcoming release.