What infrastructure change do you think might be required to be able to arm/disarm individual cameras on a schedule, if that’s what we are discussing here. The original post is not entirely clear, but the thread certainly moves in the direction of that, and chosen groupings, etc.
Whilst I most definitely agree with you it’s an enhancement, I see no requirement for a change to the infrastructure. The guys who coded the scheduler, per sync module, could easily provide the same, per camera.
In my opinion it is nothing more than a relatively simple change to the app. Indeed, I know this to be the case, because I can already do the things required in the thread by utilising a series of PowerShell scripts, on my windows 10 PC.
The disable motion command, per camera, looks like this, for example.
‘https://rest-’+ $region +".immedia-semi.com/network/$NetworkId/camera/$CameraId/disable"
The disable motion command, per sync module, looks like this
‘https://rest-’+ $region +".immedia-semi.com/network/$NetworkId/disarm"
Enable uses, enable and arm respectively, at the end of each line of code.
With the rest of the script detail, and some careful use of the task scheduler, a whole bunch of timed scenarios can be created, enabling or disabling, different camera selections, or sync modules, as required.
If you can do it by nothing more than a script, from a Windows PC, I’m pretty sure it could be done much better in the app. Not exactly a dramatic difference in the line of code between the two.