DSMR Slimme Meter


A sensor platform for Dutch Smart Meters which comply to DSMR (Dutch Smart Meter Requirements), also known as ‘Slimme meter’ or ‘P1 poort’.

  • Currently support DSMR V2.2, V3, V4, V5 and V5 Belgian 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

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

USB serial converters:

Serial to network proxies:

DIY solutions (ESP8266 based):

# Example configuration.yaml entry
sensor:
  - platform: dsmr

Configuration Variables

port string (Optional, default: /dev/ttyUSB0)

Serial port to which Smartmeter is connected via USB. For remote (i.e., ser2net) connections, use TCP port number to connect to (i.e., 2001).

host string (Optional)

Host to which Smartmeter is connected via serial or USB, see port. For remote connections, use IP address of host to connect to (i.e., 192.168.1.13).

dsmr_version string (Optional, default: 2.2)

Version of DSMR used by meter. Choices: 2.2, 4, 5, 5B (For Belgian Meter).

reconnect_interval integer (Optional, default: 30)

The reconnect interval in seconds when the connection is lost with the Smartmeter.

precision integer (Optional, default: 3)

Defines the precision of the calculated values, through the argument of round().

Full configuration examples can be found below:

# Example configuration.yaml entry for USB/serial connected Smartmeter
sensor:
  - platform: dsmr
    port: /dev/ttyUSB1
    dsmr_version: 5

group:
  meter_readings:
    name: Meter readings
    entities:
      - sensor.energy_consumption_tarif_1
      - sensor.energy_consumption_tarif_2
      - sensor.energy_production_tarif_1
      - sensor.energy_production_tarif_2
      - sensor.gas_consumption
# Example configuration.yaml entry for remote (TCP/IP, i.e., via ser2net) connection to host which is connected to Smartmeter
sensor:
  - platform: dsmr
    host: 192.168.1.13
    port: 2001
    dsmr_version: 5

group:
  meter_readings:
    name: Meter readings
    entities:
      - sensor.energy_consumption_tarif_1
      - sensor.energy_consumption_tarif_2
      - sensor.energy_production_tarif_1
      - sensor.energy_production_tarif_2
      - sensor.gas_consumption

Optional configuration example for ser2net:

# 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

or

# 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

Docker users have to allow Docker access to the device 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 homeassistant/home-assistant

Options

To configure options for DSMR integration go to Configuration >> Integrations and press Options on the DSMR card.

Time between updates

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.

Reducing the default time between updates will increase the amount of events generated and can potentially flood the system with events.

Technical overview

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.

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.