Undertow
Undertow 2.4.0 clears three CVEs and finally lands long-open HTTP/2 and timeout requests
Comparison · DevOps
QGroundControl vs Z-Wave JS
A side-by-side editorial comparison of QGroundControl and Z-Wave JS — release velocity, themes, recent moves, and the top alternatives to consider.
QGroundControl vs Z-Wave JS: at a glance
What is QGroundControl?
QGroundControl rebuilt its flight UI around touch screens, then went quiet for ten months
QGroundControl shipped v5.0 in July 2025 after five release candidates, patched it through 5.0.8 in October, and then published nothing until a v5.1 release candidate at the end of July 2026. The v5.0 release was the substantive event: the Fly View toolbar, instrument selection, multi-vehicle telemetry and application settings were reworked, MAVLink 2 signing arrived, and the build system was converted entirely to cmake with qmake dropped. The patch line that followed was almost purely crash and platform fixes — Mac notarization, Android SD-card permissions for API 30+, parameter-loading crashes.
What is Z-Wave JS?
Z-Wave driver where the hard problems are now smart locks and device quirks.
Z-Wave JS is the driver layer underneath most open-source Z-Wave integrations, and its releases follow a tight weekly-to-fortnightly rhythm mixing three things: protocol correctness, device config files, and developer surface. The current focus is clearly credential handling on smart locks — several consecutive releases fix stale cached credentials, bulk user deletion timeouts, and locks misreporting progress during credential learning. Alongside that, inclusion reliability got direct attention, with ongoing interviews now paused during inclusion and security bootstrapping.
QGroundControl vs Z-Wave JS: editorial side-by-side
QGroundControl
2.5DEVOPS
QGroundControl rebuilt its flight UI around touch screens, then went quiet for ten months
◆ Current state
QGroundControl shipped v5.0 in July 2025 after five release candidates, patched it through 5.0.8 in October, and then published nothing until a v5.1 release candidate at the end of July 2026. The v5.0 release was the substantive event: the Fly View toolbar, instrument selection, multi-vehicle telemetry and application settings were reworked, MAVLink 2 signing arrived, and the build system was converted entirely to cmake with qmake dropped. The patch line that followed was almost purely crash and platform fixes — Mac notarization, Android SD-card permissions for API 30+, parameter-loading crashes.
◆ Where it's heading
The ten-month gap between 5.0.8 and the 5.1 candidate is the clearest signal in these entries: development moved off the release feed rather than stopping, since 5.1 arrives as an RC rather than a patch. The stated design intent from v5.0 — pushing flight-to-flight settings into the toolbar and reserving Vehicle Configuration for initial setup — is a durable direction, and the touch-screen focus points at integrated controllers like Herelink as the target hardware. The RC itself carries no changelog, deferring to an external What's New page.
◆ Prediction
A v5.1 stable release should follow within weeks of the candidate, and on the v5.0 precedent it will be followed by a run of 5.1.x patches concentrated on platform packaging and crash fixes rather than features.
Z-Wave JS
5.0DEVOPS
Z-Wave driver where the hard problems are now smart locks and device quirks.
◆ Current state
Z-Wave JS is the driver layer underneath most open-source Z-Wave integrations, and its releases follow a tight weekly-to-fortnightly rhythm mixing three things: protocol correctness, device config files, and developer surface. The current focus is clearly credential handling on smart locks — several consecutive releases fix stale cached credentials, bulk user deletion timeouts, and locks misreporting progress during credential learning. Alongside that, inclusion reliability got direct attention, with ongoing interviews now paused during inclusion and security bootstrapping.
◆ Where it's heading
The protocol work is moving from getting commands through to getting them right under adversarial timing — S2 delivery verification, split multi-frame reports, and optimistic value updates now distinguishing actuator from non-actuator command classes. The other steady stream is the device database, which absorbs manufacturer inconsistencies so integrations above it do not have to.
◆ Prediction
User Code and User Credential handling should keep generating fixes, since each release surfaces another lock firmware that deviates from the spec in a new way.
Alternatives to QGroundControl and Z-Wave JS
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either QGroundControl or Z-Wave JS.
Betaflight
Betaflight grew a real autopilot: waypoint missions, geofence RTH and MAVLink ground control
OceanBase
OceanBase is rebuilding itself as a RAG backend without giving up the HTAP story
Pelican
Pelican now ships roughly once a year, and 4.12 is theme housekeeping
WildFly
WildFly's quarterly train is really a stability ladder, and OIDC keeps climbing it
RESTEasy
Jakarta REST implementation in pure maintenance across two parallel branches.
See all QGroundControl alternatives → · See all Z-Wave JS alternatives →
Recent activity from QGroundControl and Z-Wave JS
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4d agoZ-Wave JSPTI Zniffer trace support and a value-DB race condition fix
- 11d agoQGroundControlQGroundControl v5.1 - Release Candidate 1
- 25d agoZ-Wave JSInterviews pause during inclusion; proprietary Aeotec and Z-Wave.me commands
- 1mo agoZ-Wave JSMissing type exports and command class metadata corrections
- 1mo agoZ-Wave JSS2 delivery verification via sequence number; User Code cache sync fix
- 1mo agoZ-Wave JSDevice config corrections for Zooz, SimonTech and MCOHome
- 1mo agoZ-Wave JSGranular interview progress reporting via a new event
- 10mo agoQGroundControlQGroundControl v5.0.8 - Stable
- 10mo agoQGroundControlQGroundControl v5.0.7- Stable
- 1y agoQGroundControlQGroundControl V5.0 - Stable ⚡
- 1y agoQGroundControlQGroundControl v5.0 - Release Candidate 5
- 1y agoQGroundControlQGroundControl v5.0 - Release Candidate 4
Frequently asked questions
What is the difference between QGroundControl and Z-Wave JS?
They serve adjacent needs but don't currently overlap on shipped themes. Z-Wave JS is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is QGroundControl better than Z-Wave JS?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Z-Wave JS is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
What are the best alternatives to QGroundControl?
Top QGroundControl alternatives in DevOps are ranked by recent ship velocity. Browse the "QGroundControl alternatives" section above for the current picks, or visit /alternatives/qgroundcontrol for the full list with editorial commentary on each.
What are the best alternatives to Z-Wave JS?
Top Z-Wave JS alternatives in DevOps are ranked by recent ship velocity. Browse the "Z-Wave JS alternatives" section above for the current picks, or visit /alternatives/zwave-js for the full list with editorial commentary on each.