Support for reading Dutch Smart Meter (electricity/gas) (P1 port)

All will do the job. It mainly depends on the level of DIY and customization you want. A ready-to-run all-in-one solution can bring you to a running environment with minimal manual steps, but you lack the control to tweak it, and troubleshooting becomes more difficult.
Personally, I like to use Linux distributions as standard as they come, but to each its own… ;o)

Thanks @justClouds & @phsdv for the response im going to look into this when i have some more time!
Don’t really know of my usb cable had the FTDI chip inside…

Can you point us to the website of the seller? That should give enough clues.

sorry for late response this is the link https://www.allekabels.nl/searchresult.php?keyword=1215232

Hi all,

today I’ve received a new ‘smart meter’ because the other one died… Now they installed a Sagemcom T210-D, I plugged in the P1-cable and HASS is showing me the data, but… the component updates every second(!) instead of 10 seconds. This causes high CPU on my VM.

Can I configure the interval/poll time?

Changed already the DSMR version from 4 to 5, no difference

There is no polling for the DSMR component, it just parses the data as it comes in. It’s strange it would cause a very high load if it sends every second, since it’s a trivial amount of data that is to be parsed. Maybe HA is causing the load because of updating the states associated? Do you have any automations bound to the DSMR states? Maybe try with a clean HA configuration with only DSMR to see if it causes the same load? Otherwise we have to look into throttling in to dsmr-parser library https://github.com/ndokter/dsmr_parser/

Thanks for your reply! I don’t have any automations based on the states of the DSMR sensors, but I’ve got a template-sensor that will bound the low and high tariff together, but with or without this template the CPU climbs to 17-20% and after a couple of hours it’ll climb to +/- 70-80%!

After enabling the DSMR component at 18:15:

Got the right cable now and its just plug and play with the dsmr platform!!! Nice :slight_smile:
I dont have any experience with influxdb and grafana but is it possible to set this on the same raspberry pi install with hassio?
Or is it better to set it on a synology nas? my nas is’nt online all the time now so hope its possible to set it along side hassio…

Probably buying solar panels soon so want to check the possibilities of making my own monitor system…

I have done both :slightly_smiling_face:

  • first I had the cable plugged into the PI and ran InfluxDB and Grafana Addons from: https://github.com/bestlibre/hassio-addons
    Worked great.
    After that I plugged the cable into my Synology NAS and used Domoticz to publish the values to MQTT. Changed the sensors to MQTT sensor with the same name, influxdb and grafana continued working perfectly.

So, yes it is possible to run it on your Pi

HI,

i am running the DSMR component. Alle working fine and i can now see the Smart meter values. Only those are total stand. I would really like to see the current energy and gas usage of today and perhaps this week/month/year.

How could this be achieved?
I have already Influxdb and Grafana running, but it did not get the right code.

1 Like

Anyone perhaps an idea how to send this P1 data to PVOutput. Home Assistan does support the PVOutput sensor to pickup the data, but cannot find anything about sending it to pvoutput.

Wouldn’t it be possible to publish the values to MQTT and then use a script like: https://github.com/jkairys/mqtt-pvoutput-bridge to read the values into pvoutput?

You could also use dsmrreader

http://dsmr-reader.readthedocs.io/nl/latest/intro.html

It supports uploading to pvoutput and MinderGas and supports MQTT to get your readings in Home Assistant. You can even run dsmrreader inside an iframe in Home Assistant. Both work fine together on a Rpi3 here.

Does anyone know if it is possible to increase the reading frequency of the gasmeter? Data is currently coming in every 50 mins, but would like to increase that (maybe by reading the gasometer directly?)

Just increasing the reading frequency won’t do you any good as you would get the same readings over and over again… ;o|
The gas meter readings are transmitted wireless to the ‘Smart Meter’ (the one with the P1 port). And as you can see, there are no wires connected to the gas meter (for safety reasons), so it’s battery operated. To ensure approx. 15 years lifespan, they reduced the data transmit frequency as specified in the DSMR standard, allowing the battery to last long enough.

Do you guys know if this also works? https://www.p1connector.nl/

Worked great in Domoticz, but HASS doesn’t show anything.

Yes, it also works with a Rapsberry Pi P1 Connector from https://www.p1connector.nl/.
But it is possible that you have to take some actions.

I have it running on a Raspberry Pi 3 with Hassbian, but I had to make some changes:

sudo nano /boot/config.txt
Add at the end of the file
dtoverlay=pi3-disable-bt

sudo nano /boot/cmdline.txt
remove the word phase “console=serial0,115200” or “console=ttyAMA0,115200”

sudo reboot

Than follow the instructions at https://home-assistant.io/components/sensor.dsmr/
Use /dev/ttyAMA0 for the port.

It will look something like this:

sensor:

  • platform: dsmr
    port: /dev/ttyAMA0

group:
meter_readings:
name: Meter readings
entities:
- sensor.power_consumption_low
- sensor.power_consumption_normal
- sensor.power_production_low
- sensor.power_production_normal
- sensor.gas_consumption

Thanks. I’m on Hassio, that doesn’t work. Any idea if that’s possible?

Edited both files on the SD card according to your post. But nothing in HASS… :frowning:

This has been working well for quite a while, but I recently had to move to opening up home-assistant so I could use Google Home voice control (with ssl and duckdns) but now the script has stopped working. I tried modifying the script, but my Python skills are not that great. Could you help me out on getting the script to work with SSL enabled?

Managed to get the mindergas script working by using the duckdns domain name and setting the port to 443. Not ideal as I want to keep things local as much as possible, but ok for now.