Hi @matteius
like you know:
I'm using 7/24 without any detection model and triggering the motion via API from Home assistant. My idea was to send a motion start when Home assistant is firing the "person detected" event from my cameras (or car, animal, whatever)
This is working fine but the object is only set for the current stream file. My expectation was that until the next stop, all subsequent files also are getting the motion recognition object. otherwise the stop command makes no sense for this combination, or?
My idea was wo send a start when HA is switching the entity to "detected" and a stop when HA is switching back to "not detected".
Otherwise the action itself makes no sense in the request.
I could check in Home-Assistant very few seconds if the detection is still valid but this would result in several objects at a stream file in lightnvr.
Hi @matteius
like you know:
I'm using 7/24 without any detection model and triggering the motion via API from Home assistant. My idea was to send a motion start when Home assistant is firing the "person detected" event from my cameras (or car, animal, whatever)
This is working fine but the object is only set for the current stream file. My expectation was that until the next stop, all subsequent files also are getting the motion recognition object. otherwise the stop command makes no sense for this combination, or?
My idea was wo send a start when HA is switching the entity to "detected" and a stop when HA is switching back to "not detected".
Otherwise the action itself makes no sense in the request.
I could check in Home-Assistant very few seconds if the detection is still valid but this would result in several objects at a stream file in lightnvr.