NEBLI
DJI live streaming

Stream your DJI drone to your VMS or command center

Quick answer. A DJI drone does not stream into a VMS on its own, but it can get there in two hops. The pilot sends the live feed from DJI Fly or DJI Pilot 2 to Nebli; nothing is installed on the aircraft. On Enterprise, your VMS then adds each drone as one more RTSP camera and pulls its live video over RTSPS (RTSP over TLS). That works with any VMS or player able to pull RTSPS over the internet.

Who this is for

This page is for the person who adds cameras to the wall: the real-time crime center or control-room admin, or the integrator who runs the VMS. The goal is a drone's live picture sitting next to the fixed cameras your room already watches, inside the system you already run. Nebli adds the drone feed; it does not replace your VMS.

How the video gets from the drone to your wall

The path has three legs.

  1. From the controller to Nebli. The pilot sets up the stream in DJI Fly or DJI Pilot 2, using the app's custom RTMP option. Nothing is installed on the aircraft. The connection is outbound from the app, so it works from the field over a hotspot, LTE or Starlink.
  2. Across the network. Nebli carries the video over whatever connection the pilot has. Small gaps are filled so the picture keeps flowing. If the connection drops completely, the video comes back on its own, with no reload and no new link.
  3. From Nebli into your VMS. Your VMS pulls the drone's live video from Nebli over RTSPS, with one address and one credential per drone.

That is how a DJI drone ends up as an RTSP camera: the DJI app sends RTMP to Nebli, and your VMS pulls RTSPS from Nebli.

What your VMS needs

SettingValue
AddressThe full RTSPS address from Nebli: rtsps://rtsp.nebli.ai:8554/egress/<id>. Enter it whole; the server address alone returns 404.
Port8554, already in the address
TransportRTSP over TCP. UDP is refused.
EncryptionTLS 1.2 or later, publicly trusted certificate. No SRTP.
VideoH.264
Sign-inBasic, one username and password per drone

Your VMS needs to open an RTSPS address (RTSP over TLS), or to tunnel RTSP over HTTPS. Nebli does not serve plain RTSP.

Set it up in three steps

  1. Get the drone's credential. In the Nebli dashboard, open VMS in the sidebar, find the drone and click Connect. A card shows the address, username and password. The password is shown once; Nebli does not keep it, so copy it now. It works as soon as it is shown.
  2. Add the drone in your VMS. Add a generic RTSP camera, not a vendor-specific driver. Enter the full RTSPS address with TLS on, the username and password, TCP transport and H.264 video. Repeat for each drone.
  3. Check that it is pulling. The VMS page in Nebli shows each drone's state: pulling now, the last pull, or not pulled yet. Its status is true to within 6 minutes.

To test from a computer before you touch the VMS:

ffmpeg -rtsp_transport tcp -i "rtsps://<username>:<password>@rtsp.nebli.ai:8554/egress/<id>" -f null -

A wrong or missing credential returns 401. An unknown drone returns 404.

Which VMS works

Any VMS or player able to pull RTSPS over the internet can add a Nebli drone feed as a generic RTSP camera. Nebli does not use a vendor plug-in or a driver for your VMS, so the test is the protocol: can your system open an RTSPS address, with TCP transport and H.264, from an address on the internet?

Between flights

When the drone lands or the stream stops, your VMS keeps showing the last frame for up to five minutes. If the video comes back in that time, it carries on in the same session. After that the session ends, and the VMS reconnects when the drone streams again.

What the VMS does not get

  • Recordings. Only live video goes to the VMS. Record in your VMS. Flights recorded in Nebli stay on its Flights page.
  • Telemetry and control. The VMS gets video only.

People who are not at the VMS can watch the same flight on a private link that opens in any browser, with a PIN. And a pilot always flies the aircraft. Nebli never flies on its own.

Credentials and access

Each drone has its own credential. Replace password issues a new one, and the old one stops working at once. Disconnect ends the drone's credential, so the VMS can no longer pull it. Archiving or suspending a drone, or deactivating the organization, ends its credential too.

Plan

Connecting a VMS needs the Enterprise plan or the video-egress trial. The video your VMS pulls is counted each month; nothing stops or caps it.

FAQ

Can a DJI drone stream RTSP to my VMS?

Not by itself. The DJI app streams to Nebli using its custom RTMP option, and your VMS pulls the drone's live video from Nebli over RTSPS (RTSP over TLS). On Enterprise, each drone appears in your VMS as one more RTSP camera.

Do I need a plug-in or a vendor driver for my VMS?

No. The drone is added as a generic RTSP camera. Any VMS or player able to pull RTSPS over the internet can add it.

Does it work from the field over cellular?

Yes. The DJI app's connection is outbound, so it works over a hotspot, LTE or Starlink. Nebli fills small gaps and recovers on its own after a full drop.

How much upstream bandwidth does the pilot need?

More than the app's label suggests. On our Matrice 4E bench test, the "1.5M" setting sustained 9.5 to 14 Mbps of real upstream traffic, H.264 at 720p.

Does the VMS get recordings or telemetry?

No. It gets live video only. Record in your VMS; flights recorded in Nebli stay on its Flights page.

Can someone outside the command center watch?

Yes. A private link opens in any browser, with a PIN, and there is nothing to install.

Does it have to be a DJI drone?

No. PX4 and ArduPilot aircraft, and any RTSP or RTMP camera, connect to Nebli too. This page covers DJI.

Who flies the drone?

A pilot always flies the aircraft. Nebli never flies on its own.