werf
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
A side-by-side editorial comparison of Tasmota and OpenMQTTGateway — release velocity, themes, recent moves, and the top alternatives to consider.
Tasmota's release train is a hardware-support treadmill — new silicon, new sensors, every two months
Tasmota ships a named minor roughly every two months, and each one is a long list of newly supported devices: CO2 and air-quality sensors, RTCs, I/O expanders, display controllers, energy monitors and board templates. The platform work underneath tracks Espressif's silicon closely, with ESP32-P4 and ESP32-C5 support arriving and an ARCH template key now covering eleven ESP32 variants.
OpenMQTTGateway spent three years shedding its dependencies, then stopped shipping entirely.
The last release was January 2025, a single bug fix for adaptive scanning restarting the gateway. Before that, the project moved steadily toward standing alone: 1.8.0 embedded an MQTT broker via PicoMQTT so a gateway no longer needs an external server, 1.6.0 added a web interface so it no longer needs a home automation controller to configure, and 1.5.0 brought device trackers for presence detection with over-the-air updates from the controller. Hardware arrived alongside software, with the Theengs Bridge in 1.7.0 and the Theengs Plug in 1.3.0.
Tasmota ships a named minor roughly every two months, and each one is a long list of newly supported devices: CO2 and air-quality sensors, RTCs, I/O expanders, display controllers, energy monitors and board templates. The platform work underneath tracks Espressif's silicon closely, with ESP32-P4 and ESP32-C5 support arriving and an ARCH template key now covering eleven ESP32 variants.
The direction is breadth, not depth — Tasmota's value is that whatever ESP-based device someone buys, a driver already exists. The infrastructure work serves that goal: the redesigned ESP8266 I2C driver enabling a second bus, multi-bus support for existing expanders, and an Extension Manager replacing the older partition tooling all exist to fit more drivers onto constrained hardware.
Expect the next minor to follow the same shape — another codenamed release adding sensor and board support, tracking whichever ESP32 variants Espressif ships next.
The last release was January 2025, a single bug fix for adaptive scanning restarting the gateway. Before that, the project moved steadily toward standing alone: 1.8.0 embedded an MQTT broker via PicoMQTT so a gateway no longer needs an external server, 1.6.0 added a web interface so it no longer needs a home automation controller to configure, and 1.5.0 brought device trackers for presence detection with over-the-air updates from the controller. Hardware arrived alongside software, with the Theengs Bridge in 1.7.0 and the Theengs Plug in 1.3.0.
The arc through 1.2 to 1.8 is one of progressive independence — first from a controller for configuration, then from a broker for messaging — turning a bridge component into a self-contained device. Release intervals widened throughout: monthly in early 2023, then annual, then nothing for nineteen months. Whatever the roadmap was, the feed has not recorded activity since.
The evidence here does not support a confident prediction about what ships next; the project has published nothing in nineteen months. If it resumes, the unfinished thread is the embedded broker, which shipped in 1.8.0 and received only a scanning bug fix afterward.
Other Infra & APIs 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 Tasmota or OpenMQTTGateway.
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
Volatility 3 caught up with Volatility 2, then started reorganising itself.
A small LDAP server that grew OpenTelemetry tracing, embedded plugins and RISC-V builds.
OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.
Patch tags land monthly with release notes that itemize nothing.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
See all Tasmota alternatives → · See all OpenMQTTGateway alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — esp32 — within Infra & APIs. Tasmota and OpenMQTTGateway are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Tasmota and OpenMQTTGateway are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Tasmota alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Tasmota alternatives" section above for the current picks, or visit /alternatives/tasmota for the full list with editorial commentary on each.
Top OpenMQTTGateway alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "OpenMQTTGateway alternatives" section above for the current picks, or visit /alternatives/openmqttgateway for the full list with editorial commentary on each.