@Phil_Panfili, one common issue is that routines and SHM sometimes tend to timeout especially when the platform is running loaded/slow (are you using Routines or SHM to arm your cameras?). Are you sure the system is being armed? If it isn’t you should use some sort a backup SmartApp like this one here which can detect if things aren’t turned on/off and then do it after it detects a mode change.
If the system is being armed and then it’s turning off that would require some digging to find out which app is sending the disarm command and if it’s disarming the sync module or individual cameras. If it’s individual cameras you can go into the IDE → My Devices → Click on your camera and see the list of Events to track down who send the camera disarm command. If it’s a sync module that would be more difficult to track down, maybe you can go through the list of events on your hub to see who send that one through it will likely be a custom command as by default individual cameras are armed and disarmed.
Other typical issues i’ve come across:
- Do you have CoRE installed, check your pistons - are they sending a disarm command
- Check your Native Blink app, it is configured to have a scheduled to arm/disarm your system creating a scheduling conflict
- Any other scheduling apps you’re using like Smart Lighting
Although the most common issue is the first one if you’re Routines or SHM to arm and disarm your cameras/system. Tracking down random issues can be painful. Hope this helps.