Firmware varies a lot
Paths and codecs change by model and firmware. That is why we check your exact model before you pay.
Dahua NVRs and XVRs are first at launch, and the same driver covers the brands Dahua builds for, like Lorex and Amcrest. The Bridge uses Dahua's CGI command URLs and RTSP.
We test on used recorders in our lab before writing support claims. White labels on the Dahua family share this page's method.
| model line | type | live frame | recorded clips | status |
|---|---|---|---|---|
| NVR4100 series | NVR, IP cameras | Planned | Planned | Planned |
| XVR5100 series | XVR, analog and IP | In testing | In testing | Testing in our lab |
| Lorex, Amcrest (Dahua built) | NVR and DVR | Planned | Planned | Planned |
A frame comes from snapshot.cgi. Recordings are found with mediaFileFind.cgi and fetched with loadfile.cgi, after the Bridge strips a small binary header. Live and playback also run over RTSP.
The Bridge sits on the store network and calls these on the recorder. Nothing reaches the recorder from the internet.
During the private demo we do this with you on a video call. It takes about ten minutes.
Paths and codecs change by model and firmware. That is why we check your exact model before you pay.
One or two playbacks at a time per recorder. Rikuy queues requests and keeps clips short, up to 120 seconds.
Recorders on store networks have known flaws. The Bridge only dials out and only talks to the recorder's address and ports.
In June 2026 the FCC stopped new Hikvision and Dahua imports. Recorders already in stores keep working and Rikuy keeps supporting them.
Other brand on your recorder? See the full list.