PZEM Driver

[meingraham]

@gemu2015

Some discussion on Discord re: 3-phase power monitoring with Tasmota. In particular, using multiple inexpensive PZEM-004T modules. I suggested that perhaps the smart meter interface you added recently might be a means to achieve that. The main issue that most mentioned is the advanced skill level required. Understanding how to compile all the appropriate features, understanding the meter protocol, coding the appropriate descriptor, etc. Although the smart meter interface provide a great deal of flexibility and expandability, it may be too much for "average" users.

For users who just want a black box solution, the thought of enhancing the current PZEM driver to add addressability of multiple modules was considered. Do you think this is feasible?

ESPHome seems to be supporting more of this type of capability, I don't care for ESPHome, but many high profile users seems to be considering it over Tasmota, especially if they are Home Assistant users. With the advent of more ESP32 based devices (e.g., https://circuitsetup.us/index.php/product/expandable-6-channel-esp32-energy-meter/), ESPHome is making an inroads since they support the ESP32.

Anyway, I thought I'd reach out to get your thoughts about enhancing the PZEM driver for "simple" 3-phase monitors.

Regards.

Mike

P.S. I don't even have a need for a 3-phase monitor 😉 But there have been several threads with this topic so I think it is relevant.

[gemu2015]

@meingraham

multiple PZEM support could be easily added with a few minor modifications to my driver.

according the complexity of coding the descriptors you are true, but once you have a descriptor it is simply a copy and paste operation.

i will think of the 3 module expansion and once ready i will make a pr.
since i don't have any PZEM someone who has should try the driver then.
i can provide a descriptor from the data sheet to start with

Gerhard

[gemu2015]

@meingraham
i have implemented a one phase PZEM decoder now. if you know someone to test it he may download my fork and give it a try. if it works i will implement the 3 phases.

greetings

Gerhard

>D

>B
->sensor53 r

>M 1
+1,3,p,0,9600,PZEM1,1,1,b0c0a8010100,b1c0a8010100,b2c0a8010100,b3c0a8010100

1,a0vvvvvvxx00xx@i0:1,Voltage P1,V,Voltage_P1,2
1,a1ccccccxx00xx@i1:1,Current P1,A,Current_P1,2
1,a2uuuuxxxx00xx@i2:1,active Power P1,W,Power_P1,2
1,a3eeeeeexx00xx@i3:1Energy P1,W,Energy_P1,2
#

[gemu2015]

updated driver available

better descriptor

>D
>B
->sensor53 r

>M 1
+1,3,p,0,9600,PZEM1,1,1,b0,b1,b2,b3

1,a0vvvvvvxx00xx@1,Voltage P1,V,Voltage_P1,2
1,a1ccccccxx00xx@1,Current P1,A,Current_P1,2
1,a2ppppxxxx00xx@1,Active Power P1,W,Power_P1,2
1,a3eeeeeexx00xx@1,Energy P1,kWh,Energy_P1,2
#

[gemu2015]

3 Phase PZEM driver

>D

>B
->sensor53 r

>M 3
+1,3,p,0,9600,PZEM_1,1,2,b0,b1,b2,b3
+2,2,p,0,9600,PZEM_2,4,2,b0,b1,b2,b3
+3,14,p,0,9600,PZEM_3,12,2,b0,b1,b2,b3

1,a0vvvvvvxx00xx@1,Voltage,V,Voltage,2
1,a1ccccccxx00xx@1,Current,A,Current,2
1,a2ppppxxxx00xx@1,Active Power,W,Power,2
1,a3eeeeeexx00xx@1,Energy,kWh,Energy,2
2,a0vvvvvvxx00xx@1,Voltage,V,Voltage,2
2,a1ccccccxx00xx@1,Current,A,Current,2
2,a2ppppxxxx00xx@1,Active Power,W,Power,2
2,a3eeeeeexx00xx@1,Energy,kWh,Energy,2
3,a0vvvvvvxx00xx@1,Voltage,V,Voltage,2
3,a1ccccccxx00xx@1,Current,A,Current,2
3,a2ppppxxxx00xx@1,Active Power,W,Power,2
3,a3eeeeeexx00xx@1,Energy,kWh,Energy,2
#

[meingraham]

@gemu2015

I have made several changes to the smart meter wiki article. Please review.

Sensor53 command has no documentation. I need to add this to the Commands page. What does r mean? Are there other values?

For any of these meters, how are the GPIO specified in the Template/Module? What are the component types to use? For example, typically one would specify the PZEM Tx/Rx in the Tasmota setup. You can only specify one PZEM in this manner and the specific components associates which driver to use. To use this driver (53), one cannot use the Tasmota component definitions; correct?

Have you considered also the Modbus PZEM (v3) so you only need one pair of GPIO and allow all PZEM to be connected to the same GPIO and then specify each by "addressing" it via the serial protocol before requesting data from each PZEM? I'm referring to this post. Or can this already be done using the MODBUS part of your driver?

For the PZEM descriptor, what is b0,b1,b2,b3? What are a0/a1/a2/a3? I can infer that v/c/p/e are for voltage/current/power/energy. Why are these "special" characters required? The other protocols just assume that there are numerals which are then decoded into the specified variable.

Mike

[gemu2015]

@meingraham

i will check your changes tomorrow

sensor53 r resets the driver with the new descriptor
sensor53 cx nnnn presets the counter x (1..4) to the value nnnn (counter mode)

for debugging:
sensor53 dx dumps the meter x (1..5) input to the console for debug purposes (this disables the decoder)
sensor53 d0 is needed to revert to decoding mode

the gpio pins may only be defined in the descriptor, in Tasmota GPIO selector they must be set to "none" otherwise a "double GPIO define error" is emitted in console and the descriptor is ignored

the PZEM support is only for the PZEM-04 (not the MODBUS version)
the a0,a1,a2,a3 transmit block designators define the PZEM registers to access.
this one uses a very special coding which i had to implement with the literals v/c/p/e

the PZEM MODBUS version however is NOT compatible to the standard MODBUS decoder which uses float numbers. the MODBUS PZEM uses half word registers. this device may be probably decoded in RAW mode.

I personally would NEVER use PZEM for 3 phases. there are cheap complete 3 phase meters with MODBUS which provide a lot more functions, are much more precise and support reverse currents (for solar feeds) which is not possible with PZEM

Gerhard

[meingraham]

I'll add the Sensor53 documentation. Thanks

Vital information. I suspected as much. I wanted to confirm -
the gpio pins may only be defined in the descriptor, in Tasmota GPIO selector they must be set to "none" otherwise a "double GPIO define error" is emitted in console and the descriptor is ignored

the PZEM support is only for the PZEM-04 (not the MODBUS version)
the a0,a1,a2,a3 transmit block designators define the PZEM registers to access.
this one uses a very special coding which i had to implement with the literals v/c/p/e

I'll incorporate this into the article after you've had a chance to review my other changes.

I agree that using 3 PZEM-004T for 3-phase is a "kludgy"/"sketchy" solution. I would be interested in what 3-phase MODBUS devices you recommend. I rather steer users toward that and then use the MODBUS feature of your smart meter interface to integrate with Tasmota.

Mike

[gemu2015]

"c = set the driver to counter mode and preset counter (x = 1..5) to value"

cmd sensor95 cx does not switch to counter mode but presets a counter of a meter when in counter mode

=> c = preset a counter in counter mode (x = 1..5) to value

probably we should include the sensor53 cmds also in the sensor description file.

according to PZEM i hesitate to put it into the documentation

1. it is not yet tested and not yet merged
2. Theo has an easy to use PZEM driver for 3 variants and since i would not recommend a 3 phase driver users should use Theos version.

according to the MODBUS driver my solution has the advantage of being adaptable to various meters and indeed addressing more then on device over a single MODBUS is possible.

for 3 phase meters i would use the Eastron sdm530 or sdm630 (about 80-100 Euros)

or

at amazon or eBay there are a lot of 3 phase meters with MODBUS starting from about 50 Euros.

or this very cheap china import (31 Dollars)

https://www.aliexpress.com/item/33039151836.html?mb=mylGLEyZ6gyW6Zg&srcSns=Copy%20to%20Clipboard&tid=white_backgroup_101&tt=sns_Copy&aff_platform=default&cpt=1567930010043&sk=5w4aliIM&aff_trace_key=1c693e1cbd104222922b3295e301f74e-1567930010043-09490-5w4aliIM&businessType=ProductDetail&templateId=white_backgroup_101&platform=AE&terminal_id=3638e64a8cdb478680d9479bb208c39c

[meingraham]

Sensor95? I saw where you changed the descriptors a few days ago from 95 to 53. I have documented Sensor53 and included that in the meter documentation. What is Sensor95?

I don't understand what you mean by this -

"c = set the driver to counter mode and preset counter (x = 1..5) to value"

cmd sensor95 cx does not switch to counter mode but presets a counter of a meter when in counter mode

=> c = preset a counter in counter mode (x = 1..5) to value

probably we should include the sensor53 cmds also in the sensor description file.

[gemu2015]

sorry sensor95 was the name for this driver i used for the last 2 years before merging to tasmota.

you wrote in the wiki "c = set the driver to counter mode and preset counter (x = 1..5) to value"

BUT sensor53 cx does NOT switch to counter mode but presets a counter of a meter WHEN in counter mode

[rt400]

hi..
well i have a 3 PZEM04T v3.0 . i can be your tester if you like
just tell me what to do and i can report back to you the result

[gemu2015]

@rt400
ok then first lets test a single device.
download my fork and compile with
#undef USE_RULES
#define USE_SCRIPTER
#define USE_SML_M

you should see the default OBIS device in WEBUI and in configuration you should see the submenu "edit script"

now copy the above single device descriptor in the edit script edit window, check enable script
and save.
your should now see the PZEM entries on the main page.

the descriptor assumes esp8266 RX and TX , so connect these to the PZEM.

hopefully now you should see the PZEM values in the WEBUI

if this works we may try the 3 phases solution

thanks

[rt400]

got a error :

sonoff:29:143: error: core_version.h: No such file or directory

compilation terminated.

exit status 1
core_version.h: No such file or directory 

i used with 2.5.2 core also downgrade to 2.3.0 and still got this error

[gemu2015]

ok to check i downloaded my own repo and compiled with platformio.
and it worked (select your preferred language version)

if you use Arduino IDE i have no advice whats wrong

but you may use the official Tasmota DEV version and simply replace the sml53 file with the one from my fork.

i meantime realized that you have the PZEM v3 with MODBUS telegram. i have to make a slight change for that and the above descriptors won't work.

try to get scripting to work in the meantime.

i will be back with a MODBUS descriptor later.

[gemu2015]

here is a PZEM v3 descriptor
use the very last sml version from GitHub

D

B
=>sensor53 r

M 1
+1,3,m,0,9600,PZEM3,1,1,01040000,01040001,01040003,01040005

1,010404uuuuxxxxxxxx@i0:10,Voltage,V,voltage,2
1,010404uuuuuuuuxxxx@i1:1000,Current,A,current,4
1,010404uuuuuuuuxxxx@i2:10,Power,W,power,2
1,010404uuuuuuuuxxxx@i3:1000,Energy,kWh,energy,4

[fitim7]

Is „USE_SCRIPT“ already implemented for ESP32?
Getting weird errors here:

.pioenvs/tasmota32-DE/src/tasmota.ino.cpp.o:(.literal._Z6Xdrv10h+0x28): undefined reference to `ScriptWebShow(char)'
.pioenvs/tasmota32-DE/src/tasmota.ino.cpp.o: In function `Xdrv10(unsigned char)':
/Users/fits/Downloads/Sonoff-Tasmota-universal8/tasmota/xdrv_10_scripter.ino:5108: undefined reference to `ScriptWebShow(char)'

Same happening for „USE_LIGHT“

[gemu2015]

yes script works well on ESP32.
you must define both
#define USE_SCRIPT
#define USE_SCRIPT_WEB_DISPLAY

this is due to a bug in scripter
i removed it now.

[fitim7]

You sir saved my day. Thank you.
And yes, I define both, just wanted to show the problem here.
Btw. This also happens with "USE_LIGHT" in ESP32:

.pioenvs/tasmota32-DE/src/tasmota.ino.cpp.o:(.literal._Z6Xdrv10h+0x28): undefined reference to `ScriptWebShow(char)'
.pioenvs/tasmota32-DE/src/tasmota.ino.cpp.o: In function `Xdrv10(unsigned char)':
/Users/fits/Downloads/Sonoff-Tasmota-universal8/tasmota/xdrv_04_light.ino:330: undefined reference to `ScriptWebShow(char)'
collect2: error: ld returned 1 exit status
*** [.pioenvs/tasmota32-DE/firmware.elf] Error 1

[gemu2015]

its not related to ESP32, it happens also with esp8266

strange however that the error is reported for light driver which has no reference to ScriptWebShow

[fitim7]

Hmm, okay that's weird. So the only way to handle this for me is:

#undef USE_LIGHT

Thank you my friend! Script working now btw ! :)

[gemu2015]

#define USE_SCRIPT
#define USE_SCRIPT_WEB_DISPLAY
#define USE_LIGHT

works for me at least with my latest version

[herrfrei]

I have a question that is not specially for the PZEM driver but for scripts in general: I want to compute a load mean value from the measurements when they arrive and transmit this value with >J. Right now I don't know where to get the values from the >M section to compute a variable.

Any ideas?

[kugelkopf123]

@herrfrei
Look at the example in the docs. https://tasmota.github.io/docs/Smart-Meter-Interface/#landis-gyr-zmr120ares2r2sfcs-obis

The >>T section.

_{Sent with GitHawk}

[herrfrei]

Thanks for the hint. The >T section is filled on teleperiod. Not when new data arrive. I get updates every second, but want to sent the MQTT message every 60 seconds. So I need to update the power value when the new data arrive and not when they are published.

[gemu2015]

you may access the >M registers directly with sml[x]
x being the line of definition 1 ... N (html lines not counted)
these are updated when they arrive from serial port
remark:
the SML section works with double, scripter with float. in very rare cases this may cause an accuracy lost.

[gemu2015]

you must compile with #define USE_SML_SCRIPT_CMD

[herrfrei]

Many thanks for the hint!

[onley]

Is this discussion what led to the ModuleAddress command and if so would it be possible to expand this from 3 addresses? I am considering using these PZEM modules to monitor multiple circuits at the service panel and would like to be able to connect multiple modules to a single wemo D1 but the current ModuleAddress command only allows for 3 unique addresses and they seem to be related in a 3 phase arrangement where as I would like the different modules to be completely separate topics.

[gemu2015]

PZEM is no longer officially supported by this driver because the Tasmota standard PZEM driver works for most users.
however the code is still there and might still work
with SML it is possible to have more than 3 devices on the same bus.
i myself prefer MODBUS devices however there is also a new version of the PZEM device that has a MODBUS protocol. i would suggest to take these devices if you prefer clamp meters.
to set the module ID you must connect one module after the other and issue a set module id cmd before you can connect them all in parallel.

[onley]

Thank you, I will pursue the Tasmota PZEM driver, I thought that's what this was. Sorry.

[gemu2015]

yes i know, but this shows that the cmd is correct.

then sml(1 3 "r1542") should also work
you must issue this cmd e.g. in section >B

[onley]

Wouldn't that only execute on boot? I am trying to run it from a sub routine called by mqtt.

[gemu2015]

of course later you can use it anywhere. We just want to prove it works like expected

[onley]

My boot section is

B

->sensor53 r
sml(1 3 "r1542")

and I do not get a reset. Should this work in >B before the meter is defined?

[gemu2015]

the meter is defined by ->sensor53 r

probably try this in >S every second, just to see what happens

[gemu2015]

oh, sorry i forgot that this command only works with stored strings.

D
str="r1542"

B
->sensor53 r
sml(1 3 str)

[onley]

still no reset

D
meterreset="r1542"
B

->sensor53 r
sml(1 3 meterreset)

[gemu2015]

ok, will check tomorrow what is wrong

[onley]

Thank you for your help

[gemu2015]

try one thing,
send the string every second,
and then go to dump mode.
you should then see the string dumped between your normal values

btw this mode only works with a descriptor that has values to send, so use your normal settings,

[onley]

D
P="0404UUuuUUuusxxxx@i"
h="1,=h

---

"
c=""
E=":1000,Energy,kWh,"
W=":2.5,Power,W,"
H="HotTub"
B="Boiler"
D="Dryer"
C="Compressor"
S="Stove"
WH="Waterheater"
num="1"
meterreset="r1542"
B

->sensor53 d1
sml(1 3 meterreset)

M 1
+1,3,m,0,9600,ENERGY,1,1,15040000,15040008,15040003,15040005,01040003,01040005,02040003,02040005,03040003,03040005,04040003,04040005,05040003,05040005,06040003,06040005,07040003,07040005,08040003,08040005,09040003,09040005,0a040003,0a040005,0b040003,0b040005,15040003,15040005,15040003,15040005,15040003,15040005,15040003,15040005,15040003,15040005,15040003,15040005,15040003,15040005,15040003,15040005

1,150404UUuuxxxxxxxx@i0:10,Voltage,V,Boiler-V,2
1,150404UUuuxxxxxxxx@i1:10,Frequency,Hz,Boiler-PF,2

after restart

00:00:00.001 HDW: ESP8266EX
00:00:00.050 CFG: Loaded from flash at F5, Count 84
00:00:00.054 SER: Set to 8N1 9600 bit/s
00:00:00.056 QPC: Count 1
00:00:00.064 Project tasmota - Power Version 10.1.0(tasmota)-2_7_4_9(2022-02-11T14:37:53)
00:00:00.560 WIF: Connecting to AP1 OpenWrt Channel 11 BSSId 94:10:3E:07:63:09 in mode 11n as Wemo-3777...
00:00:03.756 WIF: Connected
00:00:04.009 HTP: Web server active on Wemo-3777 with IP address 192.168.2.107
00:00:04.011 UPP: Multicast (re)joined
12:44:15.034 MQT: Attempting connection...
12:44:15.046 MQT: Connected
12:44:15.048 MQT: tele/Wemo/LWT = Online (retained)
12:44:15.050 MQT: cmnd/Wemo/POWER =
12:44:15.056 MQT: tele/Wemo/INFO1 = {"Info1":{"Module":"Generic","Version":"10.1.0(tasmota)","FallbackTopic":"cmnd/DVES_29EEC1_fb/","GroupTopic":"cmnd/tasmotas/"}}
12:44:15.059 MQT: tele/Wemo/INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"Wemo-3777","IPAddress":"192.168.2.107"}}
12:44:15.061 MQT: tele/Wemo/INFO3 = {"Info3":{"RestartReason":"Power On"}}
12:44:16.036 UPP: Multicast (re)joined
12:44:16.434 QPC: Reset
12:44:19.386 MQT: tele/Wemo/STATE = {"Time":"2022-02-11T12:44:19","Uptime":"0T00:00:11","UptimeSec":11,"Heap":21,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"OpenWrt","BSSId":"94:10:3E:07:63:09","Channel":11,"Mode":"11n","RSSI":64,"Signal":-68,"LinkCount":1,"Downtime":"0T00:00:05"}}
12:44:29.406 MQT: tele/Wemo/STATE = {"Time":"2022-02-11T12:44:29","Uptime":"0T00:00:21","UptimeSec":21,"Heap":20,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"OpenWrt","BSSId":"94:10:3E:07:63:09","Channel":11,"Mode":"11n","RSSI":70,"Signal":-65,"LinkCount":1,"Downtime":"0T00:00:05"}}
12:44:39.430 MQT: tele/Wemo/STATE = {"Time":"2022-02-11T12:44:39","Uptime":"0T00:00:31","UptimeSec":31,"Heap":20,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"OpenWrt","BSSId":"94:10:3E:07:63:09","Channel":11,"Mode":"11n","RSSI":70,"Signal":-65,"LinkCount":1,"Downtime":"0T00:00:05"}}
12:44:49.389 MQT: tele/Wemo/STATE = {"Time":"2022-02-11T12:44:49","Uptime":"0T00:00:41","UptimeSec":41,"Heap":20,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"OpenWrt","BSSId":"94:10:3E:07:63:09","Channel":11,"Mode":"11n","RSSI":70,"Signal":-65,"LinkCount":1,"Downtime":"0T00:00:05"}}
12:44:59.412 MQT: tele/Wemo/STATE = {"Time":"2022-02-11T12:44:59","Uptime":"0T00:00:51","UptimeSec":51,"Heap":19,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"OpenWrt","BSSId":"94:10:3E:07:63:09","Channel":11,"Mode":"11n","RSSI":60,"Signal":-70,"LinkCount":1,"Downtime":"0T00:00:05"}}
12:45:09.412 MQT: tele/Wemo/STATE = {"Time":"2022-02-11T12:45:09","Uptime":"0T00:01:01","UptimeSec":61,"Heap":20,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"OpenWrt","BSSId":"94:10:3E:07:63:09","Channel":11,"Mode":"11n","RSSI":68,"Signal":-66,"LinkCount":1,"Downtime":"0T00:00:05"}}

Meter script is not working and no sensor display on webui

[onley]

apparently the script has to be ->sensor53 d1 when booted then switched to dump mode. If I switch to dump mode while it is running I get the following which shows that the sml command is not being sent.

D
P="0404UUuuUUuusxxxx@i"
h="1,=h

---

"
c=""
E=":1000,Energy,kWh,"
W=":2.5,Power,W,"
H="HotTub"
B="Boiler"
D="Dryer"
C="Compressor"
S="Stove"
WH="Waterheater"
num="1"
meterreset="r1542"
B

->sensor53 d1

S

print sending sml(1 3 meterreset)
sml(1 3 meterreset)

M 1

+1,3,m,0,9600,ENERGY,1,1,15040000,15040007,15040003,15040005

1,150404UUuuxxxxxxxx@i0:10,Voltage,V,Boiler-V,2
1,150404UUuuxxxxxxxx@i1:10,Frequency,Hz,Boiler-PF,2
%h%%c%%B%
1,15%P%2%W%%B%-W,2
1,15%P%3%E%%B%-kWh,4

14:21:47.403 > 15 04 00 00 00 02 72 df
14:21:47.406 sending sml(1 3 meterreset)
14:21:47.451 : 15 04 04 04 ca 00 3c 8e 9a
14:21:47.506 > 15 04 00 07 00 02 c3 1e
14:21:47.553 : 15 04 04 02 58 00 05 ef ed
14:21:47.604 > 15 04 00 03 00 02 82 df
14:21:47.653 : 15 04 04 00 04 00 00 ee 44
14:21:47.707 > 15 04 00 05 00 02 62 de
14:21:47.754 : 15 04 04 00 47 00 00 1f 90
14:21:47.804 > 15 04 00 00 00 02 72 df
14:21:47.854 : 15 04 04 04 ca 00 3c 8e 9a
14:21:47.910 > 15 04 00 07 00 02 c3 1e
14:21:47.955 : 15 04 04 02 58 00 05 ef ed
14:21:48.012 > 15 04 00 03 00 02 82 df
14:21:48.060 : 15 04 04 00 04 00 00 ee 44
14:21:48.113 > 15 04 00 05 00 02 62 de
14:21:48.165 : 15 04 04 00 47 00 00 1f 90
14:21:48.254 > 15 04 00 00 00 02 72 df
14:21:48.297 : 15 04 04 04 ca 00 3c 8e 9a
14:21:48.349 > 15 04 00 07 00 02 c3 1e
14:21:48.398 : 15 04 04 02 58 00 05 ef ed
14:21:48.401 > 15 04 00 03 00 02 82 df
14:21:48.403 sending sml(1 3 meterreset)
14:21:48.448 : 15 04 04 00 04 00 00 ee 44
14:21:48.551 > 15 04 00 05 00 02 62 de
14:21:48.599 : 15 04 04 00 47 00 00 1f 90
14:21:48.602 > 15 04 00 00 00 02 72 df
14:21:48.649 : 15 04 04 04 ca 00 3c 8e 9a
14:21:48.751 > 15 04 00 07 00 02 c3 1e
14:21:48.800 : 15 04 04 02 58 00 05 ef ed
14:21:48.805 > 15 04 00 03 00 02 82 df
14:21:48.849 : 15 04 04 00 04
14:21:48.891 : 00 00 ee 44
14:21:48.945 > 15 04 00 05 00 02 62 de
14:21:48.991 : 15 04 04 00 47 00 00 1f 90
14:21:49.044 > 15 04 00 00 00 02 72 df
14:21:49.094 : 15 04 04 04 ca 00 3c 8e 9a
14:21:49.149 > 15 04 00 07 00 02 c3 1e
14:21:49.193 : 15 04 04 02 58 00 05 ef ed
14:21:49.245 > 15 04 00 03 00 02 82 df
14:21:49.295 : 15 04 04 00 04 00 00 ee 44
14:21:49.345 > 15 04 00 05 00 02 62 de
14:21:49.396 : 15 04 04 00 47 00 00 1f 90
14:21:49.399 sending sml(1 3 meterreset)
14:21:49.447 > 15 04 00 00 00 02 72 df
14:21:49.497 : 15 04 04 04 ca 00 3c 8e 9a
14:21:49.549 > 15 04 00 07 00 02 c3 1e
14:21:49.599 : 15 04 04 02 58 00 00 2f ee
14:21:49.650 > 15 04 00 03 00 02 82 df
14:21:49.700 : 15 04 04 00 00 00 00 af 85
14:21:49.702 > 15 04 00 05 00 02 62 de
14:21:49.750 : 15 04 04 00 47 00 00 1f 90
14:21:49.851 > 15 04 00 00 00 02 72 df
14:21:49.900 : 15 04 04 04 ca 00 3c 8e 9a
14:21:49.952 > 15 04 00 07 00 02 c3 1e
14:21:49.003 : 15 04 04 02 57 00 00 1f ed
14:21:50.002 > 15 04 00 03 00 02 82 df
14:21:50.047 : 15 04 04 00 00 00 00 af 85
14:21:50.098 > 15 04 00 05 00 02 62 de
14:21:50.148 : 15 04 04 00 47 00 00 1f 90
14:21:50.201 > 15 04 00 00 00 02 72 df
14:21:50.248 : 15 04 04 04 ca 00 3c 8e 9a
14:21:50.299 > 15 04 00 07 00 02 c3 1e
14:21:50.349 : 15 04 04 02 58 00 00 2f ee
14:21:50.400 > 15 04 00 03 00 02 82 df
14:21:50.403 sending sml(1 3 meterreset)
14:21:50.449 : 15 04 04 00 00 00 00 af 85
14:21:50.501 > 15 04 00 05 00 02 62 de
14:21:50.550 : 15 04 04 00 47 00 00 1f 90
14:21:50.602 > 15 04 00 00 00 02 72 df
14:21:50.690 : 15 04 04 04 ca 00 3c 8e 9a
14:21:50.734 > 15 04 00 07 00 02 c3 1e

[onley]

I compiled with the 2 files you sent me but do I need any #defines?

[onley]

I'm using Arends Tasmota source, is that going to cause a problem with these changes?

[gemu2015]

your initialization is wrong
you omitted sensor53 r
this cmd is essential it loads the descriptor
i checked on a test system an all goes well.

[onley]

Sorry, I misunderstood the docs to mean that you use either sensor53 r OR sensor53 dN. Running the script below I do not see the 1542 sequence going out. The print is included so I know when the sml command went out. Could you send a copy of the script you used so I can compare to mine and see what I am doing wrong? Also was I supposed to do anything other than replace the 2 files you sent before compiling?

D
P="0404UUuuUUuusxxxx@i"
h="1,=h

---

"
c=""
E=":1000,Energy,kWh,"
W=":2.5,Power,W,"
H="HotTub"
B="Boiler"
D="Dryer"
C="Compressor"
S="Stove"
WH="Waterheater"
meterreset="r1542"
B
->sensor53 r
->sensor53 d1

M 1

+1,3,m,0,9600,ENERGY,1,1,15040000,15040007,15040003,15040005

1,150404UUuuxxxxxxxx@i0:10,Voltage,V,Boiler-V,2
1,150404UUuuxxxxxxxx@i1:10,Frequency,Hz,Boiler-hz,2
%h%%c%%B%
1,15%P%2%W%%B%-W,2
1,15%P%3%E%%B%-kWh,4

S
sml(1 3 meterreset)
print sml(1 3 %meterreset%)

Output:

04:18:04.229 : 15 04 04 2d 2a 00 00 87 21
04:18:04.281 > 15 04 00 00 00 02 72 df
04:18:04.330 : 15 04 04 04 c1 50 f1 02 cd
04:18:04.381 > 15 04 00 07 00 02 c3 1e
04:18:04.384 sml(1 3 r1542)
04:18:04.430 : 15 04 04 02 58 00 4f 6e 1a
04:18:04.484 > 15 04 00 03 00 02 82 df
04:18:04.573 : 15 04 04 4d 96 00 00 58 c5
04:18:04.617 > 15 04 00 05 00 02 62 de
04:18:04.666 : 15 04 04 2d 2b 00 00 d6 e1
04:18:04.717 > 15 04 00 00 00 02 72 df
04:18:04.766 : 15 04 04 04 c0 50 ad 53 34
04:18:04.816 > 15 04 00 07 00 02 c3 1e
04:18:04.865 : 15 04 04 02 58 00 50 2f d2
04:18:04.917 > 15 04 00 03 00 02 82 df
04:18:04.965 : 15 04 04 4e 63 00 00 48 b3
04:18:05.012 > 15 04 00 05 00 02 62 de
04:18:05.060 : 15 04 04 2d 2b 00 00 d6 e1
04:18:05.113 > 15 04 00 00 00 02 72 df
04:18:05.161 : 15 04 04 04 c0 50 ad 53 34
04:18:05.213 > 15 04 00 07 00 02 c3 1e
04:18:05.261 : 15 04 04 02 57 00 50 1f d1
04:18:05.312 > 15 04 00 03 00 02 82 df
04:18:05.362 : 15 04 04 4e 63 00 00 48 b3
04:18:05.412 > 15 04 00 05 00 02 62 de
04:18:05.415 sml(1 3 r1542)
04:18:05.462 : 15 04 04 2d 2b 00 00 d6 e1
04:18:05.514 > 15 04 00 00 00 02 72 df
04:18:05.563 : 15 04 04 04 c0 50 ad 53 34
04:18:05.614 > 15 04 00 07 00 02 c3 1e

[gemu2015]

i used your script slightly modified
and i get this

11:31:06.918 > 15 04 00 07 00 02 c3 1e
11:31:06.968 sending sml(1 3 meterreset)
11:31:07.020 > 15 42 8f 11
11:31:07.118 > 15 04 00 03 00 02 82 df
11:31:07.287 > 15 04 00 05 00 02 62 de
11:31:07.380 > 15 04 00 00 00 02 72 df
11:31:07.482 > 15 04 00 07 00 02 c3 1e
11:31:07.580 > 15 04 00 03 00 02 82 df
11:31:07.682 > 15 04 00 05 00 02 62 de
11:31:07.780 > 15 04 00 00 00 02 72 df
11:31:07.882 > 15 04 00 07 00 02 c3 1e
11:31:07.980 > 15 04 00 03 00 02 82 df
11:31:07.982 sending sml(1 3 meterreset)
11:31:08.083 > 15 42 8f 11
11:31:08.181 > 15 04 00 05 00 02 62 de
11:31:08.283 > 15 04 00 00 00 02 72 df
11:31:08.381 > 15 04 00 07 00 02 c3 1e
11:31:08.483 > 15 04 00 03 00 02 82 df
11:31:08.581 > 15 04 00 05 00 02 62 de
11:31:08.683 > 15 04 00 00 00 02 72 df
11:31:08.781 > 15 04 00 07 00 02 c3 1e
11:31:08.883 > 15 04 00 03 00 02 82 df
11:31:08.981 > 15 04 00 05 00 02 62 de
11:31:08.983 sending sml(1 3 meterreset)
11:31:09.083 > 15 42 8f 11
11:31:09.181 > 15 04 00 00 00 02 72 df
11:31:09.283 > 15 04 00 07 00 02 c3 1e
11:31:09.381 > 15 04 00 03 00 02 82 df
11:31:09.483 > 15 04 00 05 00 02 62 de
11:31:09.581 > 15 04 00 00 00 02 72 df
11:31:09.683 > 15 04 00 07 00 02 c3 1e
11:31:09.838 > 15 04 00 03 00 02 82 df
11:31:09.885 > 15 04 00 05 00 02 62 de
11:31:09.983 > 15 04 00 00 00 02 72 df
11:31:09.985 sending sml(1 3 meterreset)

test1_script.txt

[onley]

I loaded your script and this is what I get. This is compiled against the sonfftasmota source.
There is something different about out binaries

04:42:57.884 > 15 04 00 07 00 02 c3 1e
04:42:57.931 : 15 04 04 02 58 00 4e af da
04:42:57.981 > 15 04 00 03 00 02 82 df
04:42:58.030 : 15 04 04 4a b2 00 00 19 ba
04:42:58.081 > 15 04 00 05 00 02 62 de
04:42:58.130 : 15 04 04 30
04:42:58.173 : 4f 00 00 91 52
04:42:58.176 > 15 04 00 00 00 02 72 df
04:42:58.223 : 15 04 04 04 bc 4f 6d 9a 8c
04:42:58.274 > 15 04 00 07 00 02 c3 1e
04:42:58.324 : 15 04 04 02 58 00 4e af da
04:42:58.375 > 15 04 00 03 00 02 82 df
04:42:58.425 : 15 04 04 4a b2 00 00 19 ba
04:42:58.428 sending sml(1 3 meterreset)
04:42:58.476 > 15 04 00 05 00 02 62 de
04:42:58.525 : 15 04 04 30 4f 00 00 91 52
04:42:58.579 > 15 04 00 00 00 02 72 df
04:42:58.627 : 15 04 04 04 bc 4f 09 9b 67
04:42:58.679 > 15 04 00 07 00 02 c3 1e
04:42:58.728 : 15 04 04 02 58 00 4e af da
04:42:58.778 > 15 04 00 03 00 02 82 df
04:42:58.829 : 15 04 04 4b 09 00 00 68 63
04:42:58.879 > 15 04 00 05 00 02 62 de
04:42:58.928 : 15 04 04 30 50 00 00 a0 94
04:42:58.980 > 15 04 00 00 00 02 72 df
04:42:59.029 : 15 04 04 04 bc 4f 09 9b 67
04:42:59.081 > 15 04 00 07 00 02 c3 1e
04:42:59.129 : 15 04 04 02 58 00 4e af da
04:42:59.181 > 15 04 00 03 00 02 82 df
04:42:59.229 : 15 04 04 4b 09 00 00 68 63
04:42:59.283 > 15 04 00 05 00 02 62

[gemu2015]

this morning it was also integrated into latest Tasmota dev

in doubt use my last dev version to verify

did you forget to define USE_SML_SCRIPT_CMD ?

[onley]

USE_SML_SCRIPT_CMD was it. I did not have it defined, works like a champ now. Thank you very much for all your help.

[gemu2015]

it would be great if would put your working script into tasmota sml doc examples for others to use

[onley]

I will do that, I will remove all the var substitutions first so it is more readable. to be clear you mean in https://tasmota.github.io/docs/Smart-Meter-Interface/

[onley]

I'm trying to get the last piece of the puzzle together so I can post a script but I can't seem to get the string into the script from mqtt.

I created a sub, RST, and I can sent cmnd/Wemo/RST 1542 and it will reset the counter. However you stated that I should raw so I tried to send cmnd/Wemo/RST r1542 and the script gets garbage characters. I also tried the cmnd/Wemo/Script >num=r1542 but cannot change the variable value. As I stated I can get it to work if I just send the 1542 but this is not technically correct and I don't want to post something that will only sort of work. What am I missing?

[onley]

All of the above works but I needed to quote the quotes '"r1542"' so that my mqtt client didn't strip them and send numeric data to a string var.

[onley]

alas it appears to been in vain. The PZEM004T V3 cannot apparently be connected in parallel with another PZEM004T. The first one that sees the ESP8266 blocks the others. While the device is modbus it has it's own ttl converter and unless I am missing somet hing they do not play nice together.

[gemu2015]

this would be a serve design failure and not a MODBUS device.
may be you can decouple devices by diodes like you had to do with the older PZEM devices

[onley]

One of the devices has a power supply problem, possible short. the 3.3 supply is only 2.8 and it is spewing random data, sometimes part of a response that is correct sometime just garbage. In view of this I do not even know if it took the address change as I cannot successfully read the register. With that device out the other two I have seem to play nice. I need to get 10 more, I just hope I have a better failure rate.

[onley]

I can't seem to figure out how to use =m with my decode lines. I would like to subtract 65W from the value returned in this decode line.

1,020404UUuuUUuusxxxx@i4:10,Power,W,HotTub-W,2

[gemu2015]

since almost all meters are calibrated we did not need an offset up to now.
PZEM devices are not calibrated so i introduced an optional offset now.
add or subtract your offset after the scaling factor.

1,020404UUuuUUuusxxxx@i4:10+65,Power,W,HotTub-W,2

xsns_53_sml.ino.zip

[onley]

Fantastic! Thank you so much for all your help.