Smart Meter Interface: Script for NZR EcoCount SL 85 with M-Bus

[aja1909]

Since I didn't find any script for the NZR EcoCount SL 85 with M-Bus Interface I tried to figure it out by myself.

Script
The primary M-Bus address is configured to 9, change the 3rd byte '09' within the cmdTelegrams (2) of the meter definition to the primary address of your smart meter - or set your address to 9 as well.

; NZR EcoCount SL 85 M-Bus
>D
>B
=>sensor53 r
>M 1
+1,3,rE1,0,2400,SL85,1,10,1040094916,105B096416
1,042AssSSssSSs@10,Wirkleistung ges.,W,P_ges,1
1,04AAFC01ssSSssSSs@10,Wirkleistung P1,W,P_P1,1
1,04AAFC02ssSSssSSs@10,Wirkleistung P2,W,P_P2,1
1,04AAFC03ssSSssSSs@10,Wirkleistung P3,W,P_P3,1
1,04FB9475ssSSssSSs@10,Blindleistung ges.,var,Q_ges,1
1,04FBD475ssSSssSSs@10,Scheinleistung ges.,VA,S-ges,1
1,=h<hr/>
; Energie: nur die unteren 32 Bit von 48 Bit ausgewertet
; reicht bis 4 GWh 
1,861003uuUUuuUUs@1000,Wirkenergie Bezug T1,kWh,E_Bezug_T1,3 
1,862003uuUUuuUUs@1000,Wirkenergie Bezug T2,kWh,E_Bezug_T2,3
1,8610833CuuUUuuUUs@1000,Wirkenergie Liefer T1,kWh,E_Liefer_T1,3
1,8620833CuuUUuuUUs@1000,Wirkenergie Liefer T2,kWh,E_Liefer_T2,3
1,=h<hr/>
1,02FDC8FC01uuUU@10,Spannung P1,V,U_P1,1
1,02FDC8FC02uuUU@10,Spannung P2,V,U_P2,1
1,02FDC8FC03uuUU@10,Spannung P3,V,U_P3,1
1,02FB2EuuUU@10,Frequenz,Hz,f,1
1,=h<hr/>
; Strom: nur die unteren 16 Bit von 24 Bit ausgewertet
; reicht bis 65A
1,03FD59uuUU@1,Strom ges.,mA,I_ges,0
1,03FDD9FC01uuUU@1,Strom P1,mA,I_P1,0
1,03FDD9FC02uuUU@1,Strom P2,mA,I_P2,0
1,03FDD9FC03uuUU@1,Strom P3,mA,I_P3,0
1,03FDD9FC04uuUU@1,Strom N,mA,I_N,0
1,=h<hr/>
1,01FF61ss@1,Leistungsfaktor ges.,\%,Lambda_ges,0
1,01FFE101ss@1,Leistungsfaktor P1,\%,Lambda_P1,0
1,01FFE102ss@1,Leistungsfaktor P2,\%,Lambda_P2,0
1,01FFE103s@1,Leistungsfaktor P3,\%,Lambda_P3,0
1,=h<hr/>
1,01FF13uu@1,Tarif,,Tarif,0
1,080972bcd8@1,Meter ID,,ID,0
# 

The smart meter uses 24 bit integers for I and 48 bit integers for E. I didn't find a quick way to decode it so I decided to use just the lower 16/32 bits. I guess I won't see more than 4GWh or more than 65A on the meter. But if anyone of you has a solution for it I would be happy to integrate it.

Hardware
D1 Mini + TTL to MBUS Master Converter
VIN <-> 5V
GND <-> GND
TTLVCC <-> 3.3V
RXD <-> RX (GPIO3)
TXD <-> (GPIO1)
M+ <-> SL 85 Terminal 23
M- <-> SL 85 Terminal 24

[Bremml]

Hey @aja1909!
I really like your idea using a d1 mini for m-bus communication. i also tried your script aswell as i also have a ecocount85 m-bus counter. I use Tasmota 14.4.1.2 (aafe528-scripting) and first configured rx serial and tx serial via Configuration>Module but got the error, that these pins are already in use, so i set rx and tx to default 'none' to be configured using your script. The script works and i get the sensors shown in the main page but all the values are 0.0. Does the script still run on your setup reliable?

[aja1909]

In my setup the module configuration is set to Sonoff Basic (1) (unchanged).
Do you see any I/O activity on the smart meter display (icon next to setup icon)?
Idea: see above. Install a WiFi to serial bridge.

[Bremml]

Hey @aja1909,
i spend the weekend trying esp-iot-mbus. I got it work so far that the connection between wemos d1 and ecocount was established. I was able to send several commands (initialisation, address change, acquiring data) and always got an confirmation (E5)
M-Bus.pdf. But the problem is that also with the command for getting data (105B096416) I only got the confirmation E5 but no data. Also on the control page it just said “Ok” but no data.
Next step is to install the serial bridge. I guess you mean the Serial to TCP Bridge?

[Bremml]

Today I set up the Serial to TCP Bridge and it works so far. Can you give me some hints or commands I could sent over the bridge for debugging the connection?

[aja1909]

You have to send the sync command/"SND_NKE" (0x1040094916), wait for the answer (0xE5) and then the request/"REQ_UD2" (0x105B096416). The slave answers with "RSP_UD2" (hex datagram) which - in my case - includes all data.
If this doesn't work I am running out of ideas. If it answers with E5 only maybe the smart meter is locked. I don't remember unlocking mine but I played around with it quite a while before using this setup.
Go through NZR's manual and M-Bus documentation (request by mail). Ask them for support. We have different types and different FW-Versions (F1.05 vs. F1.12) , maybe they changed something.
If you find a solution please let us know.

[aja1909]

One more idea: try a different power supply an power cable.