Feature request: add SDM72D-M #10862

TomaszSz7 · 2021-02-07T01:36:18Z

TomaszSz7
Feb 7, 2021

Hi I would like to rise a request for add the function of reading parameters from SDM72D-M energy meter.
Maybe someone has already done it? The official code has only supports for SDM 120 and SDM630.The library is rather the same but the protocal seems to be different.
I would be grateful for the information.
Br!
Tom

barbudor · 2021-02-07T08:34:33Z

barbudor
Feb 7, 2021

Can you provide a PR ?

5 replies

TomaszSz7 Feb 7, 2021
Author

Sure. What do you mean PR ? ;-)

sfromis Feb 7, 2021

Pull Request in Github. Basically it means the relevant working changes to the source code of Tasmota.

barbudor Feb 7, 2021

a PullRequest means that you have to:

Fork Tasmota into you own GitHub account
Download you fork to your PC
Make the relevant changes and addition, test
Push back the changes to your own account
Request Tasmota to pull the new code from your account (the Pull Request)

Let's face that only someone that has the device can write the code and test it.
You have the device, so it's up to you to add the feature in Tasmota.

Now, if the above is overcomplicated for you, but you have all the relevant information, publish all details here and may be someone will pair with you to do the coding and let you do the testing.

curzon01 Feb 8, 2021

I wrote a driver for SDM72D-M it last year, but didn't find it very interesting because this energy meter doesn't seem very common and doesn't provide any other data other than consumption.

If you want I can add it

TomaszSz7 Feb 8, 2021
Author

@curzon01
I basically don't need any other data:-) Would you be so kind and you share the code with me ?

curzon01 · 2021-02-08T15:51:15Z

curzon01
Feb 8, 2021

saw I have to adapt it to the current dev so will do a PR for all next days, pls give some time...

2 replies

curzon01 Feb 10, 2021

@TomaszSz7 - it's in (PR #10892), you can use tasmota-sensor, it's included - give it a try

TomaszSz7 Feb 10, 2021
Author

@curzon01 Thank you very much! I have already tested. Works great!
This is exactly what I was looking for.
Indeed, this meter doesn't provide much information but I don't need this information either.
I wanted to thank you once again. You saved my meter. :-) I already thought it is total c**p. ;-)

kugelkopf123 · 2021-02-10T22:19:05Z

kugelkopf123
Feb 10, 2021

Or just Simply use the sml/scripting driver. https://tasmota.github.io/docs/Smart-Meter-Interface/

0 replies

TomaszSz7 · 2022-10-22T18:44:47Z

TomaszSz7
Oct 22, 2022
Author

Hello!
I don't know do you guys know but a new model of SDM72D-M. meter has been released. It has much more functions than the previous one
SDM72D-M. Link to https://xn--stromzhler-v5a.eu/media/pdf/93/17/d7/SDM72DM-V2.pdf
I accidentally got the second version. ;-) Question for you guys. Would it be a lot of effort to modify the configuration for SDM630 to work for SDM72D-M v2 ?

For many values addresses are the same as with SDM630 but after changing to sdm630 ex/tx there is no communication with the meter.. The SDM72 profile also no longer communicates with this meter.
@curzon01 also this time I count on your help .

Br
Thomas

15 replies

curzon01 Oct 24, 2022

I have a issue when I compile the build...

Which way? VSC? Clear cache, search for issue using VSC when compiling or simply use the online compiling tools way like Gitpod

this rule should look like this ? on the command line yes ?
10:06:48.456 CMD: Rule3 1

No, do not enable the rule (that's not a normal rule):

compile tasmota with USE_MODBUS_ENERGY enabled.
disable the rule Rule3 0
reenter the rule as shown above Rule3 on file#modbus do {"Name":"SDM72V2","B...
reboot device (!)

How do you think ,SDM72V2 will be added to the master build ?

Why? the generic driver was written for this purpose

TomaszSz7 Oct 24, 2022
Author

compile tasmota with USE_MODBUS_ENERGY enabled. -> done

disable the rule Rule3 0 -> done

reenter the rule as shown above Rule3 on file#modbus do {"Name":"SDM72V2","B... - > done

reboot device (!) -> done

console message

19:44:47.040 CMD: Rule3 on file#modbus do {"Name":"SDM72V2","....
19:44:47.067 RUL: Stored uncompressed, would compress from 455 to 351 (-23%)
19:44:47.072 RSL: RESULT = {"Rule3":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":455,"Free":56,"Rules":"on file#modbus do {"Name":"SDM72V2","Baud":9600,"Config":"8N1","Address":1,"Function":4,"Voltage":[0,2,4],"Current":[6,8,10],"Power":[12,14,16],"ApparentPower":[18,20,22],"ReactivePower":[24,26,28],"Factor":[30,32,34],"Frequency":70,"Total":342,"User":[{"R":0x48,"J":"ImportActive","G":"Import Active","U":"kWh","D":24},{"R":0x502,"J":"ExportPower","G":"Export Power","U":"W","D":23},{"R":0x500,"J":"ImportPower","G":"Import Power","U":"W","D":23}]} endon"}}

what should happen ?
on the list of components for GPIO I should see SDM72V2 ?

Why? the generic driver was written for this purpose

ok

curzon01 Oct 25, 2022

what should happen ? on the list of components for GPIO I should see SDM72V2 ?

No, it's an generic driver so configure your Modbus GPIO using NrgModbus Tx/Rx, for example:

After that rule3 gets its functionality

TomaszSz7 Oct 25, 2022
Author

Do you have a repo or builds with active NrgModbus ?
I cannot assign a component to the GPIO. In the dropdown list for GPIO1, I don't have NrgModbus.

what should I do ?
I know Python and SQL. I do not know C...

GPIO CONF (GPIOs ALL)
14:29:30.806 RSL: RESULT = {"GPIOs2":{"6656":"TM1637 DIO","6688":"DLP Tx","6720":"DLP Rx","6752":"SSD1351 DC","6784":"XPT2046 CS","6816":"CSE7761 Tx","6848":"CSE7761 Rx","6880":"VL53LXX XSHUT","6912":"MAX7219 CLK","6944":"MAX7219 DIN","6976":"MAX7219 CS","7008":"TFmini+ TX","7040":"TFmini+ RX","7072":"ZC Pulse","7104":"Input","7136":"I2S DOUT","7168":"I2S BCLK","7200":"I2S WS","7232":"I2S DIN","7264":"I2S WS IN","7296":"I2S BCLK IN","7328":"Interrupt","7360":"MCP2515 CS","7392":"HRG15 Tx","7424":"HRG15 Rx","7456":"VINDRIKTNING","7488":"BL0939 Rx","7520":"BL0942 Rx","7552":"HM330X SET","7584":"Heartbeat","7616":"Heartbeat_i","7648":"74x595 SRCLK","7680":"74x595 RCLK","7712":"74x595 OE","7744":"74x595 SER","7776":"SolaxX1 RTS","7808":"Option E","7840":"SDM230 Tx","7872":"SDM230 Rx","7904":"ADC MQ","7936":"CM110x TX","7968":"CM110x RX","8000":"BL6523 Tx","8032":"BL6523 Rx","8064":"ADE7880 IRQ","8096":"Reset","8128":"MS01","8160":"SDIO CMD","8192":"SDIO CLK","8224":"SDIO D0","8256":"SDIO D1","8288":"SDIO D2","8320":"SDIO D3","8352":"Flowrate","8384":"BP5758D Clk","8416":"BP5758D Dat","8448":"SM2335 Clk","8480":"SM2335 Dat","8512":"MP3 Busy","8544":"TM1621 CS","8576":"TM1621 WR","8608":"TM1621 RD","8640":"TM1621 DAT","8672":"Relay_b","8704":"Relay_bi","8736":"I2S MCLK","8768":"ModBr Tx","8800":"ModBr Rx","8832":"ADE7953 RST","8864":"NrgModbus Tx","8896":"NrgModbus Rx"}}

sfromis Oct 25, 2022

Seeing "8864":"NrgModbus Tx","8896":"NrgModbus Rx" in your output of the gpios command indicates that you have NrgModbus included in the binary you're using, those are the two gpios you need to config.

TomaszSz7 · 2022-10-22T21:51:30Z

TomaszSz7
Oct 22, 2022
Author

Thanks for your insights!
I've tested this change. Unfortunately, it still doesn't work....
UART for ESPHome is working. Maybe something is with the protocol for MODbus.
i don't get it.
The port settings should be the same in the driver for sdm630.

2 replies

barbudor Oct 22, 2022

It's not expected to work better but to provide more logs that can help debugging
So please provide the updated logs

What is the esp home config that you are using?
Does that provides energy like tasmota?

Thanks

TomaszSz7 Oct 25, 2022
Author

`uart:
id: mod_bus
rx_pin: 3
tx_pin: 1
baud_rate: 9600
stop_bits: 1

modbus:
uart_id: mod_bus
flow_control_pin: 5
id: modbus1
modbus_controller:

id: sdm
address: 0x0001
modbus_id: modbus1
update_interval: 1s
sensor:
############# SDM #############
platform: modbus_controller
modbus_controller_id: sdm
name: "Phase 1 line to neutral volts"
id: "Phase_1_line_to_neutral_volts"
register_type: read
device_class: energy
unit_of_measurement: "W"
address: 0x0000
value_type: FP32
accuracy_decimals: 0
filters:
- multiply: 1.0
platform: modbus_controller
modbus_controller_id: sdm
name: "Phase 2 line to neutral volts"
id: "Phase_2_line_to_neutral_volts"
register_type: read
device_class: energy
unit_of_measurement: "W"
address: 0x0002
value_type: FP32
accuracy_decimals: 1
filters:
- multiply: 1.0
platform: modbus_controller
modbus_controller_id: sdm
name: "Phase 3 line to neutral volts"
id: "Phase_3_line_to_neutral_volts"
register_type: read
device_class: energy
unit_of_measurement: "W"
address: 0x0004
value_type: FP32
accuracy_decimals: 1
filters:
- multiply: 1.0

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Feature request: add SDM72D-M #10862

{{title}}

Replies: 5 comments 24 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Feature request: add SDM72D-M #10862

Replies: 5 comments · 24 replies

TomaszSz7 Feb 7, 2021 Author

TomaszSz7 Feb 8, 2021 Author

TomaszSz7 Feb 10, 2021 Author

TomaszSz7 Oct 22, 2022 Author

TomaszSz7 Oct 24, 2022 Author

TomaszSz7 Oct 25, 2022 Author

TomaszSz7 Oct 22, 2022 Author

TomaszSz7 Oct 25, 2022 Author

Replies: 5 comments 24 replies

TomaszSz7 Feb 7, 2021
Author

TomaszSz7 Feb 8, 2021
Author

TomaszSz7 Feb 10, 2021
Author

TomaszSz7
Oct 22, 2022
Author

TomaszSz7 Oct 24, 2022
Author

TomaszSz7 Oct 25, 2022
Author

TomaszSz7
Oct 22, 2022
Author

TomaszSz7 Oct 25, 2022
Author