
* 2025.3: Beta release notes * 2025.3: Sync with codebase * 2025.3: Tweaks * tiny tweaks * tweaks * some more tweaks * Update 2025-03-05-release-20253.markdown * update * missing breaking change --------- Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Co-authored-by: Bram Kragten <mail@bramkragten.nl>
1.9 KiB
title | description | ha_release | ha_category | ha_codeowners | ha_quality_scale | ha_domain | ha_integration_type | ha_iot_class | ha_config_flow | ha_zeroconf | ha_platforms | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
IOmeter | Instructions on how to integrate IOmeter within Home Assistant. | 2025.3 |
|
|
bronze | iometer | device | Local Polling | true | true |
|
The IOmeter {% term integration %} fetches data from your IOmeter device, by using the local HTTP API.
IOmeter is a German company that provides the IOmeter device for reading electricity meters.
{% important %} In order for the IOmeter to be used by Home Assistant, the Core/Bridge firmware version should be at least 62/69. {% endimportant %}
{% include integrations/config_flow.md %}
Configuration parameters
{% configuration_basic %} IP address: description: The IP address of your IOmeter. {% endconfiguration_basic %}
Data updates
The integration will update its sensors by polling the IOmeter Bridge every ten seconds for new values. We recommend using USB-C power for the IOmeter Core instead of batteries.
Available sensors
The following sensors are supported:
- Power (W): Active power
- Total energy usage (kWh): How much energy the meter used
- Total energy returned (kWh): How much energy the meter returned to the grid
- Meter number: Electricity meter number
- Pin status: Electricity meter pin status
- Core battery level: Battery level of the IOmeter Core in percent
- Core power status: Battery or USB-C power for the IOmeter Core
- Signal strength WiFi: WiFi connection strength of the Bridge
- Signal strength Core/Bridge: Sub-GHz connection strength between Core and Bridge
Troubleshooting
There are no commonly known issues with this integration.
Remove integration
This integration follows standard integration removal. No extra steps are required.
{% include integrations/remove_device_service.md %}