REST API v4 /devices/{id}/footage - motion parameter not filtering results (v6.1.0 ~ v6.1.2)

Hello everyone,

I am developing a VMS agent that integrates with Nx Witness via the REST API, and I have encountered an issue with the motion parameter in the footage endpoint.

---

Environment

- Nx Witness Version: v6.1.0.42176, v6.1.1.42624, v6.1.2.42921 (reproduced on all three)
- OS: Ubuntu 24.04 (ARM64)

---

Issue Description

The motion parameter in GET /rest/v4/devices/{id}/footage appears to be completely ignored. Regardless of the coordinates specified, the response is identical to a full-frame request.

Steps to reproduce:

1. Full-frame request (motion=0,0,1x1):

curl -sk -u "admin:password" \
 "https://localhost:7001/rest/v4/devices/{id}/footage?periodType=motion&motion=0,0,1x1&startTimeMs=X&endTimeMs=Y"

→ Returns N chunks

2. Specific area request (motion=0.674,0.226,0.209x0.258):

curl -sk -u "admin:password" \
 "https://localhost:7001/rest/v4/devices/{id}/footage?periodType=motion&motion=0.674,0.226,0.209x0.258&startTimeMs=X&endTimeMs=Y"

→ Returns exactly the same N chunks

I also tried the following variations with no difference in results:
- motion[]=0.674,0.226,0.209x0.258
- URL-encoded: motion=0.674%2C0.226%2C0.209x0.258
- Rounded values: motion=0.67,0.23,0.21x0.26

---

Expected Behavior

Only the time periods where motion was detected in the specified area should be returned.

---

Comparison with Legacy API

The equivalent legacy API works correctly with the same camera and time range:

curl -sk -u "admin:password" \
 "https://localhost:7001/ec2/recordedTimePeriods?cameraId={id}&periodsType=1&filter=[[{\"x\":29,\"y\":7,\"width\":9,\"height\":8}]]&startTime=X&endTime=Y"

→ Returns 0 chunks (correctly filtered - no motion in that area)

Note: The legacy API /ec2/recordedTimePeriods was marked as Deprecated in v6.1.0 with the message "Use GET /rest/v4/devices/{id}/footage instead", so we are trying to migrate to the new API.

---

Questions

1. Is this a known bug?
2. Is there a correct way to use the motion parameter that we might be missing?
3. If this is a bug, is there a planned fix or a target version?

Any guidance would be greatly appreciated. Thank you!