Thanks for adding this Loki. I’ll try to expand on the use of profiles. Having the camera settings saved off in an SD file (Profile) would or could eliminate the need for development to create more “actions” for every setting that comes up. Profiles, or a set of different camera settings, could be saved for when camera owners are at work vs a different set of settings when they are home, not simply turn the camera off or on. Profiles could have different settings for vacation vs a normal in and out week, daytime/sunlight vs night time, etc. Also, if your camera isn’t permanently mounted, like if you moved it to different locations for special projects, you could have a profile for each location and load them as needed.
I’m not sure how drawing different detection zones would ever be accomplished by an action. But, loading that from a file? Sure. I don’t see re-configuring a camera as a series of actions unless you have a really robust set of actions and you would still be missing different detection zones. Actions, to me, are more like a macro or script of things I do, like turn on time lapse for the next 3 hours, save a short video, etc. Things that aren’t settings. Changing profiles could be added as an action and even better if they could be scheduled to load. I don’t have a long list of cryptically named shortcuts changing various settings, nor do I want them.