Home Assistant custom integration that answers a single question: how much energy would a wind turbine have produced at your site?
It takes the wind-speed history of your own anemometer and runs it through the power curve of a chosen turbine model, producing a retrospective estimate of the energy that turbine would have generated — without installing any hardware.
You point the integration at a local wind-speed sensor. The sensor captures the real conditions of your specific site — hub height, nearby obstacles, terrain roughness — and WhatIfWind maps each wind-speed reading onto the selected turbine's power curve to estimate production.
Two ways to build the 365-day series, same end result (daily / monthly / annual production):
- InfluxDB → retrospective analysis. If you already keep a local wind-data history in InfluxDB, the past 365 days are filled backwards and the chart is complete immediately.
- Start now → forward fill. With no prior history, the series is filled forwards from your logger and grows day by day until it covers a full year.
- In HACS, add this repository as a custom repository (category: Integration).
- Install WhatIfWind.
- Restart Home Assistant.
Copy custom_components/whatif_wind into your Home Assistant config/custom_components/
directory and restart.
Add the integration from Settings → Devices & Services → Add Integration → WhatIfWind, then:
- Sensor & environment — pick your wind-speed sensor and the air density for your site. The unit of measurement is auto-detected from the sensor.
- Wind-speed unit — only asked if the sensor doesn't expose a recognized unit.
- Historical data — choose how the 365-day series gets filled (InfluxDB backfill or start now).
- InfluxDB connection — if you chose InfluxDB: read-only access via the native HTTP API (Flux). Credentials are stored in the config entry; no extra libraries are installed.
There is no hardcoded turbine list: you add your own turbines from the UI, no file editing.
Open Settings → Devices & Services → WhatIfWind → Configure, then Add a turbine:
- Name & type — give it a name and pick the rotor type (HAWT 3-blade, or VAWT Savonius / Darrieus / H-rotor). The type sets a default power coefficient (Cp).
- Geometry & nameplate — provide the geometry (blade length for HAWT, or diameter × height
for VAWT) and the rated power. That's all the parametric model needs — it computes production
from the physics (swept area × Cp × air density × wind³), capped at the rated power.
- Advanced (optional): override Cp, cut-in/cut-out speeds.
- Have the manufacturer's power curve? Paste it in the Power curve field (one
speed,powerpair per line, m/s and W) to use the more accurate tabular model instead.
Use Remove a turbine from the same menu to delete custom turbines. Changes apply immediately (the entry reloads). Note: turbines added after the initial InfluxDB backfill are filled forward from that point on, not retroactively.
- Home Assistant
recorder(used for the production history). - Optional: an InfluxDB instance for retrospective backfill.
Issues and pull requests are welcome at github.com/drake69/WhatIfWind.
See the repository for license details.