energieleser
energieleser
The energieleser integration fetches real-time consumption data reported by energieleser devices, such as stromleser.one, gasleser, gasleser.pulse, wasserleser, and wärmeleser, using local HTTP API.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
sensor | Sensor (air quality, temperature) |
What people report
Energieleser meter readers are supported, but the hard-coded 10 second polling can overwhelm the Stromleser One.
- Works4
- Partly works1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| gasleser gas meter reader | Works | Listed as supported in the docsSaved copySupported devices: stromleser.one (electricity meter reader); gasleser (gas meter reader); gasleser.pulse (gas meter reader, pulse-counting variant); wasserleser (water meter reader); wärmeleser (heat meter reader). Limitations: Rate limits: The energieleser devices can be overwhelmed by excessive HTTP requests. If you configure multiple apps or integrations to poll the same device simultaneously, the device may reach a rate limit or become temporarily unresponsive. Excerpt saved from home-assistant.io on 2026-10-23. | Docs | |
| gasleser.pulse gas meter reader | Works | Pulse-counting variant addedSaved copyProposed change Added a new device type for energieleser intergration. ## Type of change <!-- What type of change does your PR introduce to Home Assistant? NOTE: Please, check only 1! box! If your PR requires multiple boxes to be checked, you'll most likely need to split Excerpt saved from GitHub on 2026-10-23. | PR #180167 · 2026-08 | |
| wasserleser water meter reader | Works | Listed as supported in the docsSaved copySupported devices: stromleser.one (electricity meter reader); gasleser (gas meter reader); gasleser.pulse (gas meter reader, pulse-counting variant); wasserleser (water meter reader); wärmeleser (heat meter reader). Limitations: Rate limits: The energieleser devices can be overwhelmed by excessive HTTP requests. If you configure multiple apps or integrations to poll the same device simultaneously, the device may reach a rate limit or become temporarily unresponsive. Excerpt saved from home-assistant.io on 2026-10-23. | Docs | |
| wärmeleser heat meter reader | Works | Listed as supported in the docsSaved copySupported devices: stromleser.one (electricity meter reader); gasleser (gas meter reader); gasleser.pulse (gas meter reader, pulse-counting variant); wasserleser (water meter reader); wärmeleser (heat meter reader). Limitations: Rate limits: The energieleser devices can be overwhelmed by excessive HTTP requests. If you configure multiple apps or integrations to poll the same device simultaneously, the device may reach a rate limit or become temporarily unresponsive. Excerpt saved from home-assistant.io on 2026-10-23. | Docs | |
| stromleser.one electricity meter reader | Partly works Local | Polling every 10s causes intermittent 429 Too Many Requests errorsSaved copyThe problem The `energieleser` integration polls the device every 10 seconds (`SCAN_INTERVAL = timedelta(seconds=10)`, hardcoded in `coordinator.py`, no options flow to change it). My "Stromleser One" device can't sustain that request rate and intermittently replies `429 Too Many Requests`, which surfaces as recurring `UpdateFailed` errors in the log, roughly once every 5–30 minutes over many hours, e.g.: [code] No data is lost (the coordinator just retries on the next 10s cycle), but the log is spammed and the entity briefly goes `unavailable` on every hit. Since there's no `OptionsFlow` … Excerpt saved from GitHub on 2026-10-23. | Issue #177848 · 2026-07 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Found automatically over
- Bonjour (zeroconf)
Details
| Installs (analytics) | 1,056 (0.15%) |
|---|---|
| Quality scale | Platinum |
| Added in | Home Assistant 2026.7 |
| Set up in the UI | Yes |
| Maintainers | @AjinkyaGokhale, @NiccoFink |
Devices listed in its documentation
- stromleser.one (electricity meter reader)
- gasleser (gas meter reader)
- gasleser.pulse (gas meter reader, pulse-counting variant)
- wasserleser (water meter reader)
- wärmeleser (heat meter reader)
Limitations from the docs
- Rate limits: The energieleser devices can be overwhelmed by excessive HTTP requests. If you configure multiple apps or integrations to poll the same device simultaneously, the device may reach a rate limit or become temporarily unresponsive.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
