daedalus
An epidemic-economic model teaching its interventions to react to the outbreak itself.
A side-by-side editorial comparison of ESPHome and profoc — release velocity, themes, recent moves, and the top alternatives to consider.
ESPHome ships on a calendar, and the August beta train is now four builds deep.
ESPHome runs a monthly release train with a beta series ahead of each version. The 2026.7 line closed out with four patch releases covering sensor correctness and build-system behaviour — a device adoption failure caused by concurrent clone cache resolution, ESP-IDF honouring compile process limits, wider C++ source globbing and a lock on WiFi scan results shared with the captive portal. The 2026.8 cycle is now at its fourth beta, with the substance still behind the beta changelog site rather than in the feed.
A forecast combination package that spun its profiler out into its own project
profoc combines probabilistic forecasts online, using the Bernstein online aggregation family with B-spline smoothing over quantiles and time. The recent releases are infrastructure rather than method: 1.3.4 removed a using namespace arma directive for CRAN compliance and closed a timer edge case, 1.3.3 adjusted the integration with rcpptimer against its now-stable 1.2.0 API. The last release to change what users can do was 1.3.0, which exposed the conline C++ class to R and exported init_experts_list(), make_basis_mats(), make_hat_mats() and post_process_model() so the engine can be driven directly.
ESPHome runs a monthly release train with a beta series ahead of each version. The 2026.7 line closed out with four patch releases covering sensor correctness and build-system behaviour — a device adoption failure caused by concurrent clone cache resolution, ESP-IDF honouring compile process limits, wider C++ source globbing and a lock on WiFi scan results shared with the captive portal. The 2026.8 cycle is now at its fourth beta, with the substance still behind the beta changelog site rather than in the feed.
The cadence is the product. Betas arrive every day or two as bump merges carrying no notes, the final release points at a changelog URL, and the real detail lands in the patch releases that follow it. That makes the feed a poor guide to what actually changed in any given month — the 2026.7 patches are the only entries here with readable content, and they are dominated by per-component fixes from a wide set of outside contributors plus automated dependency and device-builder bumps.
Expect 2026.8.0 to go final within days of the beta series ending, followed by the usual run of patch releases carrying the per-component fixes that the beta entries never described.
profoc combines probabilistic forecasts online, using the Bernstein online aggregation family with B-spline smoothing over quantiles and time. The recent releases are infrastructure rather than method: 1.3.4 removed a using namespace arma directive for CRAN compliance and closed a timer edge case, 1.3.3 adjusted the integration with rcpptimer against its now-stable 1.2.0 API. The last release to change what users can do was 1.3.0, which exposed the conline C++ class to R and exported init_experts_list(), make_basis_mats(), make_hat_mats() and post_process_model() so the engine can be driven directly.
The direction is toward a reusable C++ core with thin language bindings. The timing code that lived inside profoc was extracted into the standalone rcpptimer package in 1.3.2, deliberately so other R packages and Python projects could use it through cpptimer and cppytimer, and the clock header was reworked in 1.3.1 to maximise the code shared between the R and Python versions. Method work sits earlier in the history - periodic splines and penalties in 1.2.0, the penalty() function in 1.1.0 - while the recent cadence, a single release in the last sixteen months, points at a package the maintainer considers finished.
The repeated references to future Python use suggest the next significant work happens outside this package, in the shared C++ components, rather than in profoc's R surface.
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 profoc.
An epidemic-economic model teaching its interventions to react to the outbreak itself.
A parallel-chain helper for bkmr that has settled into pure upkeep.
A cancer driver prioritization package that ships rarely and mostly to stay installable
A meteorology ggplot2 extension where the netCDF reader became the main event
An isotope geolocation package still recovering from the r-spatial retirement
Functional data clustering grew from one algorithm into a comparable suite
See all ESPHome alternatives → · See all profoc alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. 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 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 profoc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "profoc alternatives" section above for the current picks, or visit /alternatives/profoc for the full list with editorial commentary on each.