Water meter and Home assistant
Guide: Reading Multical 21 & FlowIQ 2200 Water Meters in Home Assistant via ESPHome + MQTT
Introduction
This guide explains how to read Wireless M-Bus (wMBus) data from two types of water meters:
• Kamstrup Multical 21
• Kamstrup FlowIQ 2200
Using:
• ESP32
• CC1101 868 MHz radio module
• ESPHome
• Wmbusmeter add-on
• Mosquitto MQTT broker
You will find two complete YAML configurations included at the end of this guide.
Hardware Required
• ESP32 Dev Board
• CC1101 868 MHz RF module
• Jumper wires
• USB cable for programming
• Home Assistant with Supervisor
Wiring Diagram (ESP32 → CC1101)
Connect the CC1101 to the ESP32 as follows:
CC1101 Pin → ESP32 Pin
• VCC → 3.3V
• GND → GND
• MISO → GPIO19
• MOSI → GPIO23
• SCK → GPIO18
• CS → GPIO5
• GDO0 → GPIO4
• GDO2 → GPIO2
Install Required Home Assistant Add-ons
Install from Add-on Store and HACS (Home Assistant Community Store):
1. Wmbusmeter – decodes Wireless M-Bus telegrams
2. Mosquitto Broker – MQTT transport layer
3. ESPHome – for firmware building and flashing
Make sure these are running after installation.
Extracting the AES Key (KEM Key)
To decode encrypted telegrams, you need the AES key from your water supplier. Ask their customer service.
1. Open Wmbusmeters
2. Go to the “KEM Processing” tab
3. Enter the meter details (meter ID + KEM file)
4. Copy the extracted AES key
This key along with the meter ID will be used inside the YAML file. Meter ID is the same as the meter number printed on the meter.
Preparing the ESP32 Using ESPHome
1. Open ESPHome in Home Assistant
2. Click “New Device” → Continue
3. Select “ESPHome Web” to flash via browser
4. Connect your ESP32
5. Flash minimal base image
6. Adopt the device into Home Assistant
Once adopted, open the device YAML for editing.
Flashing the Final YAML
1. Copy the YAML configuration from this guide
2. Paste it into the ESPHome YAML editor
3. Adjust Wi-Fi, meter ID, keys, and names
4. Click INSTALL → “Plug into this computer”
5. Flash via ESPHome Web
Your water meter should now appear in Home Assistant automatically. Open the ESPHome integration under settings/integrations and check if the meter sends values as intended.
Big thanks to all of you developers, SzczepanLeon and many more for providing this solution.
Multical 21 ESPHome YAML
“`yaml
esphome:
name: wmbusmetertest
friendly_name: watermeter
name_add_mac_suffix: false
esp32:
board: esp32dev
logger:
level: DEBUG
api:
ota:
platform: esphome
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
time:
– platform: sntp
id: sntp_time
external_components:
– source: github://SzczepanLeon/esphome-components@version_4
components: [ wmbus, ethernet ]
wmbus:
mosi_pin: GPIO23
miso_pin: GPIO19
clk_pin: GPIO18
cs_pin: GPIO5
gdo0_pin: GPIO4
gdo2_pin: GPIO2
led_pin: GPIO0
led_blink_time: “1s”
all_drivers: false
log_all: false
sensor:
– platform: wmbus
meter_id: 0x11122233
type: multical21
key: “474079F3DA6C65C717E3ABCB4E8B7951”
sensors:
– name: “RSSI”
field: “rssi”
state_class: “measurement”
accuracy_decimals: 0
unit_of_measurement: “dBm”
– name: “Total Water”
field: “total”
state_class: “total”
accuracy_decimals: 3
unit_of_measurement: “m³”
– name: “Tapwater Target”
field: “target”
state_class: “total”
accuracy_decimals: 3
unit_of_measurement: “m³”
text_sensor:
– platform: wmbus
meter_id: 0x11122233
type: multical21
key: “474079F3DA6C65C717E3ABCB4E8B7951”
sensors:
– name: “Watermeter Status”
field: “status”
– name: “Watermeter Dry Time”
field: “time_dry”
– name: “Watermeter Reverse Time”
field: “time_reversed”
– name: “Watermeter Leak Time”
field: “time_leaking”
– name: “Watermeter Burst Time”
field: “time_bursting”
“`
FlowIQ 2200 ESPHome YAML
“`yaml
esphome:
name: flowiq2200
friendly_name: watermeter
name_add_mac_suffix: false
esp32:
board: esp32dev
framework:
type: arduino
logger:
level: DEBUG
api:
encryption:
key: “y0l5ASpFokJX3jUBY+N6x0etxzcldzLDCyahZbnUdfs=”
ota:
platform: esphome
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
time:
– platform: sntp
id: sntp_time
external_components:
– source: github://SzczepanLeon/esphome-components@version_4
components: [ wmbus, ethernet ]
wmbus:
mosi_pin: GPIO23
miso_pin: GPIO19
clk_pin: GPIO18
cs_pin: GPIO5
gdo0_pin: GPIO4
gdo2_pin: GPIO2
led_pin: GPIO0
led_blink_time: “1s”
all_drivers: False
log_all: False
sensor:
– platform: wmbus
meter_id: 0x23543306
type: flowiq2200
key: “AC51BF6DD0BD0607280D3E78CD89A9EB”
sensors:
– name: “RSSi”
field: “rssi”
state_class: “total”
accuracy_decimals: 0
unit_of_measurement: “dBm”
– name: “Total Water”
field: “total”
state_class: “total”
accuracy_decimals: 3
unit_of_measurement: “m³”
– name: “Watermeter Max Flow”
field: “max_flow”
state_class: “measurement”
unit_of_measurement: “m³/h”
accuracy_decimals: 3
– name: “Watermeter Flow”
field: “flow”
state_class: “measurement”
unit_of_measurement: “m³/h”
accuracy_decimals: 3
– name: “Tapwater Target”
field: “target”
state_class: “total”
accuracy_decimals: 3
unit_of_measurement: “m³”
– name: “Tapwater Temperature”
field: “min_flow_temperature”
state_class: “measurement”
accuracy_decimals: 0
unit_of_measurement: “°C”
– name: “Tapwater External Temperature”
field: “min_external_temperature”
state_class: “measurement”
accuracy_decimals: 0
unit_of_measurement: “°C”
text_sensor:
– platform: wmbus
meter_id: 0x23543306
type: flowiq2200
key: “AC51BF6DD0BD0607280D3E78CD89A9EB”
sensors:
– name: “Watermeter Status”
field: “status”
“`
Recent Comments