Manage TR-069 CPE devices via the GenieACS REST API

Steps

1. Reach the GenieACS North Bound Interface (NBI), which listens on port 7557 by default and has no built-in auth shown in the API reference examples — secure it via a reverse proxy or VPN, and separately configure CPE authentication and NBI roles/permissions per GenieACS's security docs.
2. Query devices, tasks, presets, or objects with GET /<collection>/?query=<MongoDB-style JSON filter>, optionally trimming fields with projection=.
3. Enqueue a parameter change by POSTing a task to /devices/<device_id>/tasks, e.g. a setParameterValues task with a parameterValues array of [path, value, xsd-type] triples, or read values with a getParameterValues task.
4. Add ?connection_request to the POST to force an immediate connection request to the CPE instead of waiting for its next periodic inform; a 200 response means the task executed immediately, 202 means it was only queued.
5. Percent-encode device IDs carefully in URLs — GenieACS's own docs warn that device IDs can contain characters needing double-encoding in edge cases.