Skipper
Skipper adds RFC 9421 HTTP Message Signatures and delivers 21% RouteGroup load time improvement
A side-by-side editorial comparison of ESPHome and Home Assistant — release velocity, themes, recent moves, and the top alternatives to consider.
ESPHome 2026.9.0 ships template climate component, OTA encryption with API key, and ESP-NOW for ESP32-P4
ESPHome 2026.9.0 is out, capping a beta cycle that added a template climate component (a long-requested flexible HVAC control primitive), OTA encryption keyed to the device's API key (hardening the update path), and ESP-NOW over hosted shim for the ESP32-P4. The beta cycle also included a systematic RAM allocation safety pass across the codebase — heap exhaustion now returns an error instead of panicking. Monthly releases continue landing at a consistent pace.
Home Assistant is systematically dismantling its YAML walls, one device category per month.
Home Assistant ships monthly releases on a reliable cadence, each tackling a specific technical friction point. The 2026.x series has focused on making previously expert-only features — Modbus configuration, infrared control, complex automation triggers — accessible through UI and intent-based interfaces rather than YAML hand-coding. With 2026.7, purpose-specific automation triggers graduated from Labs to become the default for all users, a genuine UX architecture shift.
ESPHome 2026.9.0 is out, capping a beta cycle that added a template climate component (a long-requested flexible HVAC control primitive), OTA encryption keyed to the device's API key (hardening the update path), and ESP-NOW over hosted shim for the ESP32-P4. The beta cycle also included a systematic RAM allocation safety pass across the codebase — heap exhaustion now returns an error instead of panicking. Monthly releases continue landing at a consistent pace.
ESPHome is expanding in two directions simultaneously: broader hardware support (ESP32-P4, BK72xx BLE, new platform components) and more robust runtime behavior (RAMAllocator pattern, use-after-free fixes, better BLE-WiFi coexistence). The template climate component is the most user-visible addition — it brings custom HVAC logic into ESPHome's declarative model, reducing the need for external Home Assistant automations. Audio stack (i2s, resampler, mixer) reliability is also a consistent focus.
The 2026.10.0 cycle will likely continue the RAMAllocator pattern across remaining allocating code paths and add more ESP32-P4-specific features. Audio (voice assistants, speakers) will stay a top area given the ongoing i2s reliability work.
Home Assistant ships monthly releases on a reliable cadence, each tackling a specific technical friction point. The 2026.x series has focused on making previously expert-only features — Modbus configuration, infrared control, complex automation triggers — accessible through UI and intent-based interfaces rather than YAML hand-coding. With 2026.7, purpose-specific automation triggers graduated from Labs to become the default for all users, a genuine UX architecture shift.
The arc is consistent: reduce reliance on YAML and internal-system knowledge while broadening the hardware ecosystem. Each release chips away at a specific category of device or workflow that previously required expert configuration. The open development commitment announced at State of the Open Home 2026 adds transparency to roadmap planning, which may accelerate community contributions to hardware integrations.
The next likely move is further automation simplification — possibly natural-language rule description or voice-driven automation authoring — building on the purpose-specific trigger foundation. Hardware expansion (Matter/Thread, radio, legacy IR) will continue on the monthly release cadence.
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 ESPHome or Home Assistant.
Skipper adds RFC 9421 HTTP Message Signatures and delivers 21% RouteGroup load time improvement
ToolJet bundles MCP, multi-LLM switching, and PATs in a single beta — shifting from app builder to AI development platform
GitHub Copilot tightens enterprise governance while AI security scanning drops its CodeQL prerequisite
Redocly ships a built-in MCP server page across its entire docs platform, with public and authenticated endpoints
Expo kills its AI agent, SDK 58 beta arrives as EAS observability stack hits GA
Jackett in pure tracker-maintenance mode, daily domain and category updates only
See all ESPHome alternatives → · See all Home Assistant alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — iot, home-automation — within Infra & APIs. ESPHome is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 6.3 vs 2.5), with 1 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 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.
Top Home Assistant alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Home Assistant alternatives" section above for the current picks, or visit /alternatives/home-assistant for the full list with editorial commentary on each.