The following are known issues in our latest release
Unexpected crashes and rendering are noticed on Firefox.
Chrome is the currently recommended browser. We will bring support to Firefox in one of the future releases.
The README.md in the <install_dir>/deploy/
has outdated instructions.
Please ignore this README file and follow the MEGH documentation page for information on installation instead.
Online/Offline connection status on stream window is not updated immediately.
Wait for 30 sec or refresh the page.
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.
When use case commissioning errors out, please delete the errored out use case and re-deploy manually with the error rectified.
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.
Update the environment section of the docker-compose.yaml file to specify the following variable:
environment: - NIMBLE_EXECUTION_QUEUE_SIZE=5 |
Setting 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.
Scheduler calendar event on click is displaying nimble threshold keys instead of the keys that shown in the portal.
No workaround, will be fixed in next release.
On click on edit button in the device list of camera view page the edit form is populating incorrect device details.
Device edits can be made from the site view page or device view page.
In the event history, the count seen in table is not the exactly same when the images are retrieved.
No workaround, will be fixed in next release.
Triggering storage purge of a particular channel is not deactivating the activated alert of that channel.
No workaround, will be fixed in the upcoming release.
In the notification history when clicked on the notifications some will not be loading.
Close the notification which was not loading and open the same notification.