Get a DJI Enterprise feed into Hover.

DJI's Enterprise line (flown with the Pilot 2 app on an Enterprise remote) has a built-in custom livestream module that can push video straight to Hover. This guide covers the Pilot 2 menu path, what each protocol tab actually asks for, and how to point it at Hover.

Bench-verified on Matrice 4E

Everything in this guide describing the Matrice 4E and RC Plus 2 is bench-verified: we ran it end to end on our own hardware on 2026-07-14, including a packet-level capture of the actual stream. Other Pilot 2 models share the same livestream module and menu, cited to DJI's own documentation; where DJI's docs are silent on a specific model, that's called out.

Finding the livestream settings

From the camera view, tap back (<) to the Pilot 2 home screen. The Cloud Service tile shows your current livestream configuration once one is set.

If nothing is configured yet, the tile reads "Not Logged In." Tap it to open the Cloud Services menu: FlightHub 2, FlightHub 2 On-Premises, Open Platforms, GB28181, and Customize Live Stream. Tap Customize Live Stream to reach the same editor.

RTSP: the drone's own livestream server

Every Matrice 4-series aircraft on current firmware exposes both an RTMP push and an RTSP pull option from the same Customize Livestream screen. RTSP turns the drone itself into a small RTSP server that a client can connect to and pull video from, no push destination needed.

The RTSP tab asks for an account and password you choose, plus a fixed port (8554, not editable), and a toggle to push MISB-standard metadata for GIS platforms. There is no stream-path field to set; the path is fixed by the aircraft. Saving these credentials starts the RTSP service immediately, without needing to press Start in the camera view, and it stays running across a battery swap.

Bench-measured spec: H.264 High profile, 1280×720, about 30 fps, video only (no audio track), delivered over RTSP.

RTSP is a real, working capability of the aircraft. Whether Hover can pull that RTSP feed directly is a separate question, covered below; do not assume the two are the same thing.

RTMP: custom livestream push

The RTMP tab is what Hover uses. It's a single field: one combined URL that carries both the destination server and your stream key.

There is no separate stream-key field. The key is appended to the URL after a trailing slash, the same way DJI's own consumer-app documentation describes it (see the consumer guide for the verbatim wording): rtmp://host:port/stream-key.

Tap Save, then start the stream from the camera view. The livestream flyout shows the active protocol, the destination, and a live bitrate readout.

Bench-measured spec (Matrice 4E): H.264 High profile, 1280×720, about 30 fps, video only, FLV container. The in-app quality label reads "Adaptive," shown as 720P / 30FPS / 1.5M, but that 1.5 Mbps figure is a floor, not a ceiling: on a healthy connection we measured real throughput of roughly 9.5 to 14 Mbps. On other Pilot 2 models, DJI's own documentation states five selectable quality levels up to 1080p at 3 Mbps; frame rate and codec are not stated in DJI's docs for those models.

Pointing it at Hover

Hover ingests DJI's custom RTMP push directly. In the Hover dashboard: Assets → + Add DJI drone → give it a name and pick the airframe. Hover mints a one-time ingest URL and stream key, shown once. Paste that whole string into the Pilot 2 RTMP URL field above, save, and start the stream. Assign the new asset to a deployment to see it on your live map and dashboard.

This path is shipped and bench-verified end to end: drone → Hover's ingest → live video rendering in the Hover dashboard. It is video only. Gimbal control and flight telemetry are not part of this path, since the drone isn't bound to Hover as a controlled asset, just streaming video to it.

Model coverage

DJI's custom-RTMP livestream module is shared across the Pilot 2 lineup. Coverage below is graded by evidence: bench-verified is our own hardware; DJI-documented is DJI's official enumeration of supported aircraft; DJI-silent means DJI hasn't published a per-model statement, though the aircraft shares the same livestream module.

Dock aircraft have no remote and no Pilot 2 app, so the in-app RTMP menu above doesn't apply to them. They stream through DJI's Cloud API and FlightHub 2, a different integration path this guide doesn't cover.

Common questions

Can I get a live feed from my DJI enterprise drone into Hover today?

Yes, over custom RTMP. Point the Pilot 2 app's custom RTMP livestream field at the ingest URL Hover mints for your deployment. This is shipped and bench-verified end to end on a DJI Matrice 4E. Gimbal control and telemetry are not part of this video-only path.

Does Hover support DJI's RTSP livestream mode?

The drone's RTSP server is real and bench-verified on current Matrice 4-series firmware. Hover pulling that RTSP feed directly is not yet a shippable capability; use the RTMP path today. RTSP-pull support is coming.

Which DJI enterprise drones does this cover?

Any drone that runs DJI Pilot 2 on an Enterprise remote: the Mavic 3 Enterprise series, Matrice 30 series, Matrice 300/350 RTK, and Matrice 4 series. DJI Dock aircraft do not have a Pilot 2 app and are not covered; they stream through DJI's Cloud API and FlightHub 2 instead.