A sensor platform for Belgian, Dutch, Luxembourg and Swedish Smart Meters which comply to DSMR (Dutch Smart Meter Requirements), also known as ‘Slimme meter’ or ‘P1 poort’. Swedish meters with a ‘HAN port’ are not supported by this integration.
- Currently support DSMR V2.2, V3, V4, V5, Belgian V5 variant, Luxembourg V5 variant (Smarty), Swedish V5 variant and the EasyMeter Q3D (Germany) through the dsmr_parser module by Nigel Dokter.
- For official information about DSMR refer to: DSMR Document
- For official information about the P1 port refer to: P1 Companion Standard
- For unofficial hardware connection examples refer to: Domoticx
- For official information about the Swedish variant refer to: Swedish specification.
- Supports P1 cables integrated in a RFXtrx device.
- For Belgian meters, choose DSMR version
- For Dutch meters, choose DSMR version
- For Luxembourg meters, choose DSMR version
- For Swedish meters, choose DSMR version
- For EasyMeter Q3D, choose DSMR version
To configure options for DSMR integration go to Settings -> Devices & Services and press Options on the DSMR card.
Typically the smart meter sends new data every 5-10 seconds. This value defines the minimum time between entity updates in seconds. Setting this value to 0 will update entities each time data is received from the smart meter.
This integration is known to work for:
- Iskra ME382 / MT382 (DSMR 2.2)
- ISKRA AM550 (DSMR 5.0)
- Landis+Gyr E350 (DMSR 4)
- Landis+Gyr ZCF110 / ZM F110 (DSMR 4.2)
- Kaifa E0026
- Kamstrup 382JxC (DSMR 2.2)
- Sagemcom XS210 ESMR5
- Sagemcom T211
- Ziv E0058 ESMR5
- EasyMeter Q3D
Docker users have to allow Docker access to the USB to serial converter by adding
--device /dev/ttyUSB21:/dev/ttyUSB21 to the run command:
$ docker run --device /dev/ttyUSB0:/dev/ttyUSB0 -d --name="home-assistant" -v /home/USERNAME/hass:/config -v /etc/localtime:/etc/localtime:ro --net=host ghcr.io/home-assistant/home-assistant
DIY solutions (ESP8266 based):
Adding DSMR Slimme Meter to your Home Assistant instance can be done via the user interface, by using this My button:
If the above My button doesn’t work, you can also perform the following steps manually:
Optional configuration example for ser2net 3.x.x:
# Example /etc/ser2net.conf for proxying USB/serial connections to DSMRv4 smart meters 2001:raw:600:/dev/ttyUSB0:115200 NONE 1STOPBIT 8DATABITS XONXOFF LOCAL -RTSCTS
# Example /etc/ser2net.conf for proxying USB/serial connections to DSMRv2.2 smart meters 2001:raw:600:/dev/ttyUSB0:9600 EVEN 1STOPBIT 7DATABITS XONXOFF LOCAL -RTSCTS
Optional configuration example for ser2net 4.x.x:
# Example /etc/ser2net.yaml for proxying USB/serial connections to DSMRv4 smart meters connection: &con0096 accepter: tcp,2001 enable: on options: banner: *banner kickolduser: true telnet-brk-on-sync: true connector: serialdev, /dev/ttyUSB0, 115200n81,local
DSMR is a standard to which Dutch smartmeters must comply. It specifies that the smartmeter must send out a ‘telegram’ every 10 seconds (every second for DSMR 5.0 devices) over a serial port.
The contents of this telegram differ between version but they generally consist of lines with ‘obis’ (Object Identification System, a numerical ID for a value) followed with the value and unit.
Smart meters in Belgium, Luxembourg and Sweden provided telegrams with largely the same contents.
This module sets up an asynchronous reading loop using the
dsmr_parser module which waits for a complete telegram, parser it and puts it on an async queue as a dictionary of
obis/object mapping. The numeric value and unit of each value can be read from the objects attributes. Because the
obis are know for each DSMR version the Entities for this integration are create during bootstrap.
Another loop (DSMR class) is setup which reads the telegram queue, stores/caches the latest telegram and notifies the Entities that the telegram has been updated.