DroneForge Nimbus App v2.1.4 ships one of our most requested features: the Python Library.
Builders can now write Python code with access to telemetry, video, and the DroneForge autonomy stack. The goal is simple: make programming FPV drones feel straightforward without hiding the parts developers actually need.
Python Library
v2.1.4 opens up a direct Python Library workflow for building with Nimbus.
Instead of forcing every idea through a custom interface, developers can write Python code and connect it to the drone systems that matter: live telemetry, camera video, and autonomy tools.
That makes Nimbus easier to use for AI drone development, FPV drone experimentation, and autonomous drone workflows where developers want to prototype quickly and stay close to the code.
Telemetry access
The Python Library can access telemetry from Nimbus.
Telemetry is the foundation for most useful drone software. It gives developers the information they need to understand attitude, movement, state, and behavior while the drone is running.
Video access
The Python Library also exposes video.
That is critical for builders working on perception, vision models, object detection, navigation, or any agent that needs to react to what the drone sees.
Autonomy stack access
v2.1.4 also exposes access to the DroneForge autonomy stack.
This gives developers a more powerful starting point than raw camera and telemetry data alone. Python programs can now sit closer to the autonomy layer, which makes it easier to experiment with higher-level behavior for FPV drones and development drones.
Why it matters
This update makes Nimbus more programmable.
Python is already where a lot of robotics, AI, computer vision, and autonomy work happens. By bringing the Python Library directly into the DroneForge workflow, v2.1.4 makes it easier to write drone programs, test ideas, and connect real FPV drone hardware to the software developers already know.
Release context
This changelog entry is part of the DroneForge release archive for Nimbus and DF1. The archive helps builders understand how the autonomy stack has changed over time, including updates to setup, Nimbus App behavior, Python Library workflows, documentation, hardware notes, flight workflows, and community-facing product polish.
Older releases are still useful when comparing versions, debugging a local installation, or following the path from early drone connectivity work to current autonomous flight tooling. Use these notes as historical context alongside the current documentation, Nimbus App releases, and Python Library updates.
For current projects, compare these archived notes with the latest release before making setup decisions. DroneForge continues to refine how developers connect hardware, stream telemetry, inspect video, run agents, and build repeatable autonomy workflows.
Community archive
Continue exploring DroneForge changelogs, research notes, and Nimbus examples through the community archive. These internal links help connect related releases, technical notes, and builder resources.
- Version 2.0.0 - Changelog
- Version 1.0.10 - Changelog
- Version 1.0.9 - Changelog
- Version 1.0.8 - Changelog
- Version 1.0.7 - Changelog
- Version 1.0.6 - Changelog
- Version 1.0.4 - Changelog
- Version 1.0.3 - Changelog
- Version 1.0.2 - Changelog
- Version 1.0.1 - Changelog
- Version 1.0.0 - Changelog
- Version 0.2.0 - Changelog
- Version 0.1.0 - Changelog
- Version 0.0.1 - Changelog
- Version 0.0.0 - Changelog
- Drone Autonomy Research Notes - Research
- Nimbus App and Python Library Examples - Examples