SoftEther VPN
Post-quantum key exchange landed, then the release train went quiet.
A side-by-side editorial comparison of Tasmota and ESPHome — 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.
ESPHome's July line is all maintenance: bot bumps, build fixes, one breaking ethernet change.
ESPHome is four patches into the 2026.7 cycle, and the patch content is dominated by bundled esphome-device-builder bumps, dependabot updates, and toolchain fixes on the ESP-IDF and Zephyr build paths. The user-visible fixes are narrow and hardware-specific: sensor readings on emc2101, haier and as3935, epaper init defaults, and device adoption failing on first attempt because the git clone cache was unlocked. 2026.7.3 carried an explicitly flagged breaking change to ENC28J60 SPI chip-select hold time.
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.
ESPHome is four patches into the 2026.7 cycle, and the patch content is dominated by bundled esphome-device-builder bumps, dependabot updates, and toolchain fixes on the ESP-IDF and Zephyr build paths. The user-visible fixes are narrow and hardware-specific: sensor readings on emc2101, haier and as3935, epaper init defaults, and device adoption failing on first attempt because the git clone cache was unlocked. 2026.7.3 carried an explicitly flagged breaking change to ENC28J60 SPI chip-select hold time.
The July line is stabilisation rather than expansion — the feature content lives in the 2026.7.0 release the beta tags led up to, and everything since has been build-system and per-component correction. Automated bumps now make up a large share of each patch note, which makes the changelog a poor read on what actually changed for users. The through-line is a build toolchain ESPHome increasingly owns end to end, via the bundled device-builder it keeps rev-ing.
Expect the 2026.8.0 betas to open shortly and reset the cycle, with one or two more bump-heavy patches closing out the 2026.7 line first.
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 ESPHome.
Post-quantum key exchange landed, then the release train went quiet.
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.
See all Tasmota alternatives → · See all ESPHome alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — esp32, home-automation — within Infra & APIs. ESPHome is currently shipping more aggressively (velocity 5.0 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. ESPHome is currently shipping more aggressively (velocity 5.0 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 ESPHome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ESPHome alternatives" section above for the current picks, or visit /alternatives/esphome for the full list with editorial commentary on each.