Based on esphome-p1reader, which is an ESPHome custom component for reading P1 data from electricity meters. Designed for Swedish meters that implements the specification defined in the Swedish Energy Industry Recommendation For Customer Interfaces version 1.3 and above.
Notable differences from esphome-p1reader are:
- More frequent update of sensors with configurable update period (if supported by meter).
- No additional components needed. RJ12 cable connects directly to D1Mini (or equivalent)
- Code rewritten to not spend excessive amounts of time in calls to the
loopfunction. This should ensure stable operation of ESPHome and might help prevent some serial communication issues. - Now (Sep 2022) also supports the binary format used by some meters.
Warning
Custom components, such as this one, are deprecated by ESPHome according to this page and are expected to stop working in future releases of ESPHome. The current version is tested with ESPHome version 2023.9.0.
If anyone has experience converting a custom component into an External component, feel free to contribute!
- Sagemcom T211 / Ellevio, Skånska Energi
- Aidon 6534 with RJ12/P1-port module (not RJ45/NVE module) / SEVAB
- Landis+Gyr E360 / E.ON
- S34U18 (Sanxing SX631) / Vattenfall - But read this
- Kamstrup OMNIPOWER
- Itron A300 / Borås Elnät
- KAIFA MA304H4E / Nacka Energi
- KAIFA CL109 / Öresundskraft
I have used a D1 mini clone, but most ESP-based controllers should work as long as you figure out appropriate pins to use. The P1 port on the meter provides 5V up to 250mA which makes it possible to power the circuit directly from the P1 port.
ESP32 based boards draw more power, which may cause a problem with the supply from the meter and generally offer no advantage over ESP8266 based boards.
If you have pre built hardware which does not connect the RTS signal to a GPIO, read this.
- 1 (Wemos) D1 mini or clone.
- 1 RJ12 cable (6 wires)
- Optionally, hot melt glue and large heat shrink tubing.
Wiring is simple. Five of the pins from the connector (one pin is not used)...
... are connected to four of the pads on the D1Mini.
And that is it. The result could look something like this:
Some hot-melt glue and heat shrink tubing will make it more robust though.
It is possible to attach another P1 reading device in case you need to connect a car charger (or a second p1-mini...) etc. If you have no need for this, you can skip this section and continue with "Installation" below.
- Female connector for the RJ12 cable.
- White (or blue) LED
- Resistor 1 - 3 kΩ
The LED will, in addition to providing visual indication that updates are beeing requested on the port, ensure that the voltage on D0 will not get high enough to damage the D1mini. The LED needs to have a high enough voltage drop for it to work and some colors may not work.
The value of the resistor is not very critical. I have tested with 3 kΩ and anything down to 1 kΩ should be fine.
A p1mini wired up with a secondary port (unpowered) on an experimental board:
Power to the secondary port needs to be supplied from a secondary source (Like an USB charger). Unless the secondary device is already powered (like a car charger etc) in which case it may not be necessary to supply any power at all to the secondary port.
Updates are only sent to the secondary port right after they have been received and processed (if the secondary device is requesting updates via the RTS signal). That means that if the d1mini is set to only update every 15 seconds, the secondary device can not get updates more frequently than that.
Clone the repository and create a companion secrets.yaml file with the following fields:
wifi_ssid: <your wifi SSID>
wifi_password: <your wifi password>
p1mini_password: <Your p1mini password (for OTA, etc)>
p1mini_api_key: <Home Assistant API key>
Make sure to place the secrets.yaml file in the root path of the cloned project. The p1mini_password field can be set to any password before doing the initial upload of the firmware.
Flash ESPHome as usual, just keep the p1mini.h file in the same location as p1mini.yaml (and secrets.yaml). Don't connect USB and the P1 port at the same time! If everything works, Home Assistant will autodetect the new integration after you plug it into the P1 port.
If you do not receive any data, make sure that the P1 port is enabled on your meter and try setting the log level to DEBUG in ESPHome for more feedback.
Specification overview: https://www.tekniskaverken.se/siteassets/tekniska-verken/elnat/aidonfd-rj12-han-interface-se-v13a.cleaned.pdf
OBIS codes: https://tech.enectiva.cz/en/installation-instructions/others/obis-codes-meaning/
P1 hardware info (in Dutch): http://domoticx.com/p1-poort-slimme-meter-hardware/