If you’re lucky enough to have a camera which SS fully supports (including motion detection) or you are willing to use SS’s motion detection, that’s exactly what happens when use motion detection mode. Whenever a trigger is received (either from SS or the camera’s own software), SS dumps its buffer into a new file and continues recording. I’ve seen this function called “timewarp” in other contexts.
SS does not recognize my camera as a motion trigger source, so I’m trying to find a workaround. The camera’s trigger state is getting as far as an OH item, so the part I’m missing is getting that into SS to be treated as a motion detection event. Even if it was picked up as a tampering event, I think it would would work just as well.
Binding to the Camera Recording channel is close, although it has these disadvantages:
- No timewarp.
- Does not show up in the SS timeline as motion.
- I’m not sure how well it would work with the “low quality continuous, high quality on motion” strategy.
Another approach is using OH rules to map my booleans to the external triggers channel, then SS rules to use that number to stop and start recordings. That is more complicated and it appears to get me to the same place as directly mapping to the Camera Record channel.