Short answer
Wind is not a replacement for solar but a complement. HUBCORE does not recommend a turbine based on catalogue data or a map — it requires on-site wind measurement, a turbulence assessment and clarity on noise, icing, maintenance and planning.
Measured resource first
Turbine output scales with the cube of wind speed — a small error in the speed estimate becomes a large error in yield. The basis must therefore be on-site measurement at the planned rotor height over a sufficient period, not a general wind atlas.
- Measurement height and duration must match the project scale
- Buildings and trees create turbulence that wears the machine
- Roof mounting is usually the worst option for both yield and vibration
Noise, vibration and icing
In residential settings, noise and vibration are the most common source of conflict. Winter adds icing, which reduces output, unbalances the rotor and creates an ice-throw risk — requiring a safety zone and, where needed, shutdown logic.
Noise limits, setback requirements and planning permission are decided by the local authority. HUBCORE does not confirm the permissibility of any location.
Maintenance and availability
A turbine has moving parts requiring regular maintenance, access and spare parts. Before deciding, it must be clear who services the machine locally, what the response time is and what happens if the manufacturer leaves the market.
Integration with HUBCORE
For HUBCORE, a turbine is like any other generator: it needs metering, state readback and the ability to curtail output or safely stop the machine. Without those it cannot participate in the site's energy balance or in future flexibility.
- On-site wind measurement completed and documented
- Noise and setback requirements checked with the municipality
- Service agreement and spare part availability agreed
- Documented interface for metering and curtailment
HUBCORE fit filter
- Controllability — Can the device be safely limited, started and stopped through a documented interface?
- Measurability — Do we get trustworthy measurements (power, energy, phases, state, faults) at sufficient resolution?
- Integrability — Is the interface publicly documented (e.g. Modbus, SunSpec, REST, MQTT, OCPP) and versioned?
- Local operation — Do critical control and safety keep working when the vendor cloud or internet is down?
- Security — Is access authenticated, are rights scoped, is traffic encrypted and firmware updatable?
- Serviceability — Is it clear who owns maintenance, spare parts, firmware and fault resolution?
- Scalability — Can the solution grow (more points, kWh, sites) without redesigning the architecture?
HUBCORE's position
HUBCORE treats wind as a complementary source only on sites where the measured resource, location and serviceability are evidenced. By default we focus on solar, storage and load management.
Not yet verified
- Is there enough service capability for small wind turbines in Estonia?
- In which rural areas does wind genuinely anti-correlate with solar?