Smart Meter Interface/Scripting: Decode multiple string lines

[GolterU]

Hello,
I successfully read the meter ID from my Smart Meter ZPA ZE311 (OBIS-ASCII):
Raw data: 0.0.0(1ZPA5723035xyz)
Script line: 1,0.0.0(@#),meter ID ,,Meter_ID,0
Web UI display: Electricity meter ID "1ZPA5723035xyz"

However, the meter also supplies 25 lines of historical data (meter readings).
Raw data:
...
1.8.0*09(0007797.306*kWh)
1.8.0*10(0007628.544*kWh)
1.8.0*11(0007418.247*kWh)
...
and the corresponding Timestamps in separate lines:
...
0.1.2*09(220301000000)
0.1.2*10(220201000000)
0.1.2*11(220101000000)
...

The Timestamps are in the format YYMMDDhhmmss
A line with
1,0.1.2*09(@#),time,,DateTime09,0
to decode already works. But how do I do that with the other entries if only one is allowed per meter (Meter Metrics at scale)???

The decode as a numeric value with
1,0.1.2*09(@1,timestamp09:,,DateTime09,0
obviously exceeds the range of values of a floating point variable. Numerical decoding always returns the number 2147483647 (2^31 - 1).
Is there a solution to decode multiple string lines?

Golter

[gemu2015]

all numbers in this driver are double precision because meter values can get really large. i however just realized that the function dtostrfd() passes a double but does a call to dtostrf (float) thus reducing the resolution. i will modify the driver with a real double to string conversion and make a pr soon.

[gemu2015]

remark. since the timestamp is very large as a number you may need to set the divider to 10000

[GolterU]

Hello gemu,
I tested the modified file "xsns_53_sml.ino". The 10-digit decimal should fit comfortably in a double-precision variable. The division with the scale parameter (see below) is carried out, but apparently the original value has already been truncated. In any case, the result is still wrong, e.g.:
source data
...
0.1.2*01(221101000000)
or
0.1.2*25(201101000000)
...

decode line:
...
1,0.1.2*25(@1,date oldest value:,,Date_oldest,0
or
1,0.1.2*01(@1000000,date youngest value:,,Date_youngest,0
...

Results:
...
Current date oldest value: 2147483647
or
Current date most recent: 2147
...

Did I maybe do something wrong when compiling?
I'm using Gitpod's web-based compiler. I unzipped your file "xsns_53_sml.ino.zip" and copied the content into the file of the same name "/workspace/Tasmota/tasmota/tasmota_xsns_sensor/xsns_53_sml.ino" and compiled. The file is left in the "modified" state. The Tasmota master was used and later also the development branch, each with the adapted "user_config_override.h".

What else can I do?

Thanks for further help!
Golter

[gemu2015]

ok, found the bug and fixed

xsns_53_sml.ino.zip

[GolterU]

Hi gemu,
many thanks for the support! It now works as intended.

What I noticed (but doesn't bother me):
If the raw data line
0.1.2*01(221101000000)
is decoded as a complete 12-digit decimal number with
1,0.1.2*01(@1,date youngest value:,YYMMdd,Date_youngest,0
the result is as desired
221101000000.
Accessing the decode line (my line is No. 5) with
dat=sml[5]
then the result is
201200992256
Somewhere, apparently, full double precision is not always used for calculation.

Anyway, thank you and Merry Christmas

Golter

[gemu2015]

scripter only supports float values while sml supports only double.
i modified the sources so that you may get a double value as string into scripting.
you may then divide the string into peaces and reconvert to smaller numbers.

smls[M] usually return the string of a meter

now

string = smls[-DL] returns the double number of decode line as string

remark:
the sml driver attached is a complete rework of the last driver with dynamic memory allocation and software settable options instead of #defines. this greatly reduces the RAM consumption especially useful on ESP8266
however it is not yet well tested. i will do a pr next week when i have done more tests.

Archiv.zip

[ciinema]

@GolterU

did u get the "current Power" field in your Script. Im asking because we are query the hole Power Meter but cant find the "current power" (1.7.0).

thanks.

[Einwich]

Thanks a lot. I used your power calculations and it works as expected.

Karsten

[schokominzpfefferlade]

Hi,

I just don't get any values from the meter. Tried with script from Einwich:

with scripts from GolterU it´s the same:

What am I doing wrong?
Does the meter have to be unlocked by a PIN? I asked my electricity provider and they said "no".
The reader is correctly placed on the IR interface.
Any ideas?

[Noschvie]

Have you tried the debug mode?

[schokominzpfefferlade]

you mean the "sensor53 d1" command? i tried but it didn't make a difference

[YoungJules]

That command turns on dumping the raw SML data to the console...(sorry for the late reply!)