OpenMQTTGateway
OpenMQTTGateway spent three years shedding its dependencies, then stopped shipping entirely.
A side-by-side editorial comparison of Tasmota and Dashy — 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.
Dashy ships a release per merged PR — the real 4.5 features are already scrolling off the feed.
The self-hosted dashboard cuts a version for essentially every merged pull request, so the recent window is a mix of dependabot bumps, German translations, an out-of-memory fix from unclosed secureConnect listeners, OIDC post-logout redirect support, and new sorting by provider and item ID. The 4.5.0 release that carries the substance — drag-and-drop editing of sections, items and widgets, a rebuilt GitHub stats widget on the official API, and number formatting in the custom-api widget — sits just outside this window.
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 self-hosted dashboard cuts a version for essentially every merged pull request, so the recent window is a mix of dependabot bumps, German translations, an out-of-memory fix from unclosed secureConnect listeners, OIDC post-logout redirect support, and new sorting by provider and item ID. The 4.5.0 release that carries the substance — drag-and-drop editing of sections, items and widgets, a rebuilt GitHub stats widget on the official API, and number formatting in the custom-api widget — sits just outside this window.
Development is steady and community-driven, with a maintainer handling auth and stability while contributors add widgets, sorting and translations. The direction after 4.5.0 is refinement rather than expansion: fix what the new editing surface exposed, round out OIDC, keep dependencies current. The per-PR release cadence makes the feed noisy relative to how much actually changes.
Expect the 4.5.x patch stream to continue at roughly a release every few days, dominated by dependency bumps and follow-up fixes to the drag-and-drop editor. Larger features will land in a 4.6 cut rather than trickling through patches.
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 Dashy.
OpenMQTTGateway spent three years shedding its dependencies, then stopped shipping entirely.
umbrelOS now pins any Docker container to the home screen — the app store stopped being the boundary.
ZoneMinder 1.38 finally split capturing from analysing — and added roles to a system that had none.
YARA ships bounds checks, not features — three patch releases published thirteen minutes apart.
Dokku ships patches weekly, and quietly grows a Kubernetes backend under its single-host roots.
Fail2Ban's last release was an interim beta 14 months ago; the feed spans eight years in six entries.
See all Tasmota alternatives → · See all Dashy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dashy is currently shipping more aggressively (velocity 6.3 vs 0.0), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dashy is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 Dashy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dashy alternatives" section above for the current picks, or visit /alternatives/dashy for the full list with editorial commentary on each.