You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Evercam use case for ExNVR is to manage large numbers of these NVRs. The easier it is to understand and mass update configs, the better. Also handy for diagnostics. Teltonika routers have this.
This issue is about downloading the current config of the current device, locally.
This is related to the idea of a cloud deployment/commissioning system. A new device (or an existing device if instructed) calls home to see if it has been commissioned. If yes, it is given the config file, a set of instructions to self-configure.
For Evercam , this would mean a freshy installed device polling a cloud endpoint, identifying itself with a unique ID (MAC?) to see if it has been claimed/commissioned.
I suspect there are well thought out ways of doing this that I'm not aware of. Teltonika do it quite well.
The text was updated successfully, but these errors were encountered:
The Evercam use case for ExNVR is to manage large numbers of these NVRs. The easier it is to understand and mass update configs, the better. Also handy for diagnostics. Teltonika routers have this.
This issue is about downloading the current config of the current device, locally.
This is related to the idea of a cloud deployment/commissioning system. A new device (or an existing device if instructed) calls home to see if it has been commissioned. If yes, it is given the config file, a set of instructions to self-configure.
For Evercam , this would mean a freshy installed device polling a cloud endpoint, identifying itself with a unique ID (MAC?) to see if it has been claimed/commissioned.
I suspect there are well thought out ways of doing this that I'm not aware of. Teltonika do it quite well.
The text was updated successfully, but these errors were encountered: