Tasmota SML MBus HeatMeter: delayed/wrong values after some time and sudden transfer stops #20460

evaluationevaluation · 2024-01-10T16:47:16Z

evaluationevaluation
Jan 10, 2024

Hi,

first of all I want to thank the whole Tasmota team and all supporters who help others!!!
I'm using Tasmota many years now, starting with simple ON/OFF Switches, then Power Metering with rules, then Smart Meters and now even a Heat Meter (usually based on prebuilt images).

But the Heat Meter drives me crazy.
It is a Sensus Pollucom F behind a HeatPump which is powerd by some internal battery (not exchangeable).
I get measurements from this device since months and until few weeks ago I was quite happy and just trusted the data.

But now after deeper analysis I found out that the values displayed on device sometimes differ from the values I get via IR-Interface (HICHI with Tasmota).

Tasmota is V12.3.0, don't remember whether I compiled by myown or found a precompiled image (and in the meantime my laptop changed :-))

I use the following script to retrieve the values.

;start, define variables
wkup=1
>B
;setup sensor
->sensor53 r
->sensor53 d0
->sensor53 l255
>S
if upsecs==10 {
->sensor53 d1
}
if upsecs<200{
  if upsecs%60==0{
    print read meter (modulo 60)
    =#readmeter
  }
}
if upsecs==80{
  ->sensor53 d0
}
if upsecs>=200{
  if upsecs%2700==0 {
    print read meter (modulo 2700)
    =#readmeter
  }
}

>M 1
+1,3,rE1,0,2400,WAERME,1
1,68080072bcd8@1,Zählernummer,,Zählernummer,0
1,0c06bcd8@1,Energie,kWh,Energie,16
1,0c13bcd8@1000,Volumen,m³,Volumen,0
1,0c3bbcd8@1,Durchfluss,l/h,Durchfluss,0
1,0c2bbcd8@1,Leistung,W,Leistung,0
1,025auuUU@10,Durchflusstemperatur,°C,Durchflusstemperatur,1
1,025euuUU@10,Rücklauftemperatur,°C,Rücklauftemperatur,1
1,0360uuUU@1000,Temperaturdifferenz,K,Temperaturdifferenz,3
#

#readmeter
print wakeup start
;set serial protocol
sml(-1 1 "2400:8N1")
;send 0x55 for 2,2 seconds with 8N1 (53x), 2400 baud (wakeup sequence)
for wkup 1 53 1
sml(1 1 "55555555555555555555")
next
print wakeup end
wkup=1
print wait for the meter
;wait for the meter to wake up
delay(350)
;switch serial protocol
sml(-1 1 "2400:8E1")
print Init MBus 1040004016; SCAN for Device 00
sml(1 1 "1040004016")
delay(350)
print request data 107BFE7916
sml(1 1 "107BFE7916")
;print request data 105BFE5916
;sml(1 1 "105BFE5916")
print request data finished
#

It starts in DEBUG mode to prove that communication is ok, then switches to NON-DEBUG mode, executed a short period in minute interval and then switches to a longer interval.
This timeing behaviour got necessary as the meter started to suddenly stopped working during the day. I then have to wait until 0:00h, wake up davice by button press and restart Tasmota.
I assume that this is some kind of battery save mode?! Before it was working fine every 5 minutes, then even every minutes and then issues started and now I can only cover the full day in 0,75-1h intervals.
If someone has ideas in this field I highly appreciate every tip!!!

In DEBUG mode I directly see valid data like this:

00:01:58.133 : 10 40 00 40 16 e5 10 7b fe 79 16 68 42 42 68 08 
00:01:58.388 : 00 72 89 50 67 21 ae 4c 1d 04 3c 00 00 00 0c 06 52 30 00 00 0c 13 02 43 55 01 0c 3b 19 09 00 00 0c 2b 78 18 00 00 02 5a 50 01 0\ 
00:01:58.691 : 21 0c fd 10 89 50 67 21 1f e5 16

This part of the byte response starts with 0c 06 (code for ENERGY) and value 00003052 (BCD reverse) = 3052kWh.

0c 06 52 30 00 00

But now the real strange behavior:
DEBUG directly shows valid values. After switch to NON-DEBUG I have to wait 2-3 executions until the WebUI shows the values.
DEBUG values are correct, the shown values in WebUI are correct
then after some hours
device display shows higher values than transferred by Tasmota.
i.e. today I received

{"Energie":3079}

at 2024-01-10T15:40:06 (note the precision 16 in code line for ENERGIE thus measure is transferred immediately) and display showed

at 15:52h. Produced energy is relatively constant 2kW, so it is impossible to consume 3kWh in 12min.

I don't see issues in my script but on the other hand I cannot imagine that Heat Meter returns different data to display and IR interface... Unfortunately it seems impossible to see debug values and at the same time Tasmota UI & MQTT data transfer.
Could it be that Tasmota delays values?! Remember the WebUI is updated after 2-3 executions although data is diectly available. If values regularly are delayed for 2-3 executions combined with interval 45-60min...

Thanks a lot for every tip and sorry for the long post!

Greetings
Eva

Answered by gemu2015

Jan 29, 2024

i took the dump from your first post and send it to your script (using buffer size 8)
e.g. 0c065230 and it decodes immediately
to

there has to be more explanation in the docs especially with slow heat meters. on fast meters sending every second the delay is not a problem.

here is a rough explanation how the decoder works.
there are 2 operating modes.

block mode:
blocks of data are read e.g on demand of a request, like modbus,
or lines which end with LF like OBIS asci.
then depending on the decoder there is a pattern search inside this buffer or the line is compared from byte zero (OBIS asci)

shift mode:
each incoming byte is shifted into a serial buffer from right to left. the serial buf…

View full answer

evaluationevaluation · 2024-01-14T11:35:04Z

evaluationevaluation
Jan 14, 2024
Author

no one with an idea?

Here a very short summary:
Via Tasmota I query measures from Sensus Pollucom (Mbus, IR-Interface)
Problem 1: If I retrieve value i.e. every 5min the Device will stop communicating with me during the day. A much higher interval is needed, i.e. 45min (Low Battery Mode?!)
Problem 2: The values are valid in the beginning and get worse. I get new values but they do not match the value displayed ion the device anymore... At the end of the day there is a gap of ~4kWh. Restart of Tasmota solves it.

For me it seems to be a Tasmota bug.

13 replies

evaluationevaluation Jan 28, 2024
Author

I compiled 13.3.0 release using PlatformIO now.
I freshly flashed a new device assembled a new Hichi head and replaced the old combination.

But the behaviour is still wrong.
Please skip this verbose section and jump directly to the bold line (SYSLOG tests) at the end.

I changed the buffer size several times but didn't see a positive effect. Explicitly tested 20, 77 (current value and should be the correct size of data package) and even 500.

Here is the output from NodeRed and a screenshot from fotos taken by a surveillance cam in front of the HeatMeater device.

{"Time":"2024-01-27T18:23:16","WAERME":{"Energie":4010},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T18:23:25","WAERME":{"Zählernummer":21675089,"Energie":4010,"Volumen":1934,"Durchfluss":939,"Leistung":2839,"Durchflusstemperatur":39.5,"Rücklauftemperatur":37,"Temperaturdifferenz":2.559},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T19:08:18","WAERME":{"Energie":4012},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T19:08:27","WAERME":{"Zählernummer":21675089,"Energie":4012,"Volumen":1935,"Durchfluss":944,"Leistung":2977,"Durchflusstemperatur":40.4,"Rücklauftemperatur":37.6,"Temperaturdifferenz":2.762},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T19:53:20","WAERME":{"Energie":4014},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T19:53:29","WAERME":{"Zählernummer":21675089,"Energie":4014,"Volumen":1936,"Durchfluss":946,"Leistung":3032,"Durchflusstemperatur":40.6,"Rücklauftemperatur":37.9,"Temperaturdifferenz":2.734},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T20:38:22","WAERME":{"Energie":4017},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T20:38:31","WAERME":{"Zählernummer":21675089,"Energie":4017,"Volumen":1936,"Durchfluss":942,"Leistung":2846,"Durchflusstemperatur":40.1,"Rücklauftemperatur":37.5,"Temperaturdifferenz":2.641},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T21:23:24","WAERME":{"Energie":4019},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T21:23:33","WAERME":{"Zählernummer":21675089,"Energie":4019,"Volumen":1937,"Durchfluss":943,"Leistung":2880,"Durchflusstemperatur":39.8,"Rücklauftemperatur":37.2,"Temperaturdifferenz":2.598},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T22:08:26","WAERME":{"Energie":4021},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T22:08:35","WAERME":{"Zählernummer":21675089,"Energie":4021,"Volumen":1938,"Durchfluss":947,"Leistung":2482,"Durchflusstemperatur":36.5,"Rücklauftemperatur":34.2,"Temperaturdifferenz":2.238},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T22:53:28","WAERME":{"Energie":4023},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T22:53:37","WAERME":{"Zählernummer":21675089,"Energie":4023,"Volumen":1938,"Durchfluss":956,"Leistung":2853,"Durchflusstemperatur":39.2,"Rücklauftemperatur":36.6,"Temperaturdifferenz":2.57},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T23:38:30","WAERME":{"Energie":4025},"source":"Wärmemengenzähler"}
{"Time":"2024-01-27T23:38:38","WAERME":{"Zählernummer":21675089,"Energie":4025,"Volumen":1939,"Durchfluss":946,"Leistung":2747,"Durchflusstemperatur":39.3,"Rücklauftemperatur":36.8,"Temperaturdifferenz":2.477},"source":"Wärmemengenzähler"}

Remark: all timestamps are local time (Middle European Timezone).
Looking at the first log entry: "{"Time":"2024-01-27T18:23:16","WAERME":{"Energie":4010},"source":"Wärmemengenzähler"}"
This is the result of "immediate data transfer because of the following line of my Tasmota script:

1,0c06bcd8@1,Energie,kWh,Energie,16
The next log line shows the full struct delivered by the Tasmota.

The energy value is 4010.

Looking now at the pictures of the webcam you can see that

4010 is the value of 17:25h
4011 of 17:49h
4012 of 18:08h
4013 of 18:32
4014 of 18:48h.

Thus the correct value in Tasmota data message should be 4012 and not 4010.

Looking closer at the log you can see that every line is individual. There are no duplicates. So it is not an issue of broken IR communication and sending an old struct again... It just seems to be delayed?!

To eliminate all doubts I just try to activate SYSLOG for Tasmota and do query IR head "twice" every 45min: once with DEBUG and onc without DEBUG.

Here the very first output of the double IR query script from SYSLOG:

<13>1 2024-01-28T01:06:55.663481+01:00 TasmotaWemos12 ESP-RSL - - - ESP-RSL: RESULT = {"Time":"2024-01-28T01:07:11","SML":{"CMD":"dump: 0"}}
<13>1 2024-01-28T01:06:55.663481+01:00 TasmotaWemos12 ESP-read - - - ESP-read meter (modulo 2700s debug off)
<13>1 2024-01-28T01:06:55.663563+01:00 TasmotaWemos12 ESP-wakeup - - - ESP-wakeup start
<13>1 2024-01-28T01:06:55.664997+01:00 TasmotaWemos12 ESP-wakeup - - - ESP-wakeup end
<13>1 2024-01-28T01:06:55.666710+01:00 TasmotaWemos12 ESP-wait - - - ESP-wait for the meter
<13>1 2024-01-28T01:06:55.668311+01:00 TasmotaWemos12 ESP-Init - - - ESP-Init MBus 1040004016; SCAN for Device 00
<13>1 2024-01-28T01:06:55.670462+01:00 TasmotaWemos12 ESP-request - - - ESP-request data 107BFE7916 aktuelle Werte!!!
<13>1 2024-01-28T01:06:55.671815+01:00 TasmotaWemos12 ESP-request - - - ESP-request data finished
<13>1 2024-01-28T01:06:55.673772+01:00 TasmotaWemos12 ESP-RSL - - - ESP-RSL: RESULT = {"Time":"2024-01-28T01:07:14","SML":{"CMD":"dump: 1"}}
<13>1 2024-01-28T01:06:55.675283+01:00 TasmotaWemos12 ESP-read - - - ESP-read meter (modulo 2700s debug on)
<13>1 2024-01-28T01:06:55.676956+01:00 TasmotaWemos12 ESP-wakeup - - - ESP-wakeup start
<13>1 2024-01-28T01:06:55.678771+01:00 TasmotaWemos12 ESP-wakeup - - - ESP-wakeup end
<13>1 2024-01-28T01:06:55.680510+01:00 TasmotaWemos12 ESP-wait - - - ESP-wait for the meter
<13>1 2024-01-28T01:06:55.682471+01:00 TasmotaWemos12 ESP-Init - - - ESP-Init MBus 1040004016; SCAN for Device 00
<13>1 2024-01-28T01:06:55.684038+01:00 TasmotaWemos12 ESP-request - - - ESP-request data 107BFE7916 aktuelle Werte!!!
<13>1 2024-01-28T01:06:55.686078+01:00 TasmotaWemos12 ESP-request - - - ESP-request data finished
<13>1 2024-01-28T01:06:55.692315+01:00 TasmotaWemos12 ESP- - - - ESP-: 10 40 00 40 16 e5 10 7b fe 79 16 68 42 42 68 08 00 72 89 50 67 21 ae 4c 1d 04 1e 00 00 00 0c 06
<13>1 2024-01-28T01:06:55.696390+01:00 TasmotaWemos12 ESP- - - - ESP-: 30 40 00 00 0c 13 59 12 94 01 0c 3b 47 09 00 00 0c 2b 02 27 00 00 02 5a 6f 01 02 5e 57 01 03 60
<13>1 2024-01-28T01:06:55.696390+01:00 TasmotaWemos12 ESP- - - - ESP-: 86 09 00 0c 78 89 50 67 21 0c fd 10 89 50 67 21 1f a0 16
<13>1 2024-01-28T01:07:05.702097+01:00 TasmotaWemos12 ESP-MQT - - - ESP-MQT: tele/TasmotaWemos12/SENSOR = {"Time":"2024-01-28T01:07:26","WAERME":{"Zählernummer":21675089,"Energie":4028,"Volumen":1941,"Durchfluss":949,"Leistung":2719,"Durchflusstemperatur":38.3,"Rücklauftemperatur":35.8,"Temperaturdifferenz":2.520}}

According to the Tasmota script:

1,0c06bcd8@1,Energie,kWh,Energie,16

the energy value can be found right after code 0c 06 in BC format: 30 40 00 00
So the correct value is 4030 (which fits to the webcam foto) but the Tasmota sends 4028 as energy value.

Any idea what's going wrong here.
Is there something wrong with this configuration?

1,0c06bcd8@1,Energie,kWh,Energie,16

Greetings
Eva

gemu2015 Jan 28, 2024

i have to apologize that i didn't check your descriptor well enough. since you have a different ID for every decode unit your serial buffer has to be as small as a decode unit, not as the complete block.
0c06bcd8 would yield in 6 bytes, such serial buffer should be 6 bytes only
while 68080072bcd8 would give 8 bytes,
i would suggest to set your serial buffer to 8 bytes then

evaluationevaluation Jan 29, 2024
Author

thanks a lot for your patience and hints!

I understand now what you meant with serial buffer size. It should fit the size of every "matching line".
So using a buffer size of 8 will save memory but greater buffer sizes ashould lso work fine as I get a lot of results that make sense.
I will nevertheless change the buffer size to 8 and observe but I don't think that this is the core issue.

I fear I still do not understand this decoding fully.
0c06bcd8 IMHO means

search for code sequence 06 0c
then read the next 8 half bytes
interpret them as BCD numbers (reversely).
or?

17:41:58.693 : 10 40 00 40 16 e5 10 7b fe 79 16 68 42 42 68 08 00 72 89 50 67 21 ae 4c 1d 04 54 00 00 00 0c 06
17:41:58.840 : 21 41 00 00 0c 13 06 45 97 01 0c 3b 88 08 00 00 0c 2b 16 26 00 00 02 5a 7f 01 02 5e 66 01 03 60
17:41:58.967 : 0a 0a 00 0c 78 89 50 67 21 0c fd 10 89 50 67 21 1f a2 16

Result should be 00004121 what is 4121kWh

I made the syslog-test decribed above and there all values are correct when I decode them manually using the logic from above.
But the decoded values in Tasmota WebUI are wrong/delayed.
So there need to be a bug in my decoding script, an unintended delaying feature or a bug in Tasmota itself.

Probably my decoding script is wrong:

1,0c06bcd8@1,Energie,kWh,Energie,16

But how should it look like?

gemu2015 Jan 29, 2024

i took the dump from your first post and send it to your script (using buffer size 8)
e.g. 0c065230 and it decodes immediately
to

there has to be more explanation in the docs especially with slow heat meters. on fast meters sending every second the delay is not a problem.

here is a rough explanation how the decoder works.
there are 2 operating modes.

block mode:
blocks of data are read e.g on demand of a request, like modbus,
or lines which end with LF like OBIS asci.
then depending on the decoder there is a pattern search inside this buffer or the line is compared from byte zero (OBIS asci)

shift mode:
each incoming byte is shifted into a serial buffer from right to left. the serial buffer is compared from byte zero with the pattern described in the decoder, and when found decodes the value.
if the serial buffer is much larger than the message it takes some time until the message arrives at the beginning of the buffer and only then is decoded correctly.
the raw mode for the heat meter works in shift mode.

Answer selected by evaluationevaluation

evaluationevaluation Jan 30, 2024
Author

i took the dump from your first post and send it to your script (using buffer size 8)
how did you do this?
Would love to be able to do tests like this when implementing/testing scripts.
Was is done directly in Tasmota's script environment?

gemu2015 Jan 30, 2024

just send your dump (as binary) with a PC to an esp device with your script running.

evaluationevaluation · 2024-01-31T12:04:58Z

evaluationevaluation
Jan 31, 2024
Author

first of all: @gemu2015 thanks a lot for your efforts. I learned a lot!

Let me try to summarize what went wrong and what fixed the issue

The issue mainly occurs when there is a longer time between 2 SmartMeter queries. So users of fast queryable devices perhaps never saw it because a delay of few seconds is usually ok.
Im my case there is 45min between 2 queries (battery device) and I encountered that the data displayed in TasmotaWebUI and sent via MQTT were 1-2h old.

Reason is the serial buffer. In my case every line of byte stream has a maximum of 8 chars. Then I should set serial buffer to 8 to speed up the decoding by the script.
Unnecessaryly big serial buffers lead to delays.
When using DEBUG mode you directly get the right values. It is only delayed in "normal" mode using WebUI and MQTT.

After having set serial buffer to 8 I get proper values in SYSLOG and MQTT without delays.

I proved this using this approach:
Execute device query every 2700s.

upsecs % 5400 == 0 => DEBUG on
upsecs % 5400 == 2700 => DEBUG off
So I see values via MQTT and SYSLOG and can check whether the values are "continuously increasing according to the timestamps".
This was not true with serial buffers size of i.e. 77 but is fine with serial buffer 8!

2 replies

gemu2015 Jan 31, 2024

glad that it works now for you.
may be you can add your working descriptor to the sml docs and you are also invited to improve the docs according this issue.
(anybody can edit the docs by the pencil symbol)

evaluationevaluation Jan 31, 2024
Author

@gemu2015
just did. But never did before and hope did nothing wrong...

one last question: is it possible to additionally mark my latest post as an "answer"?
You should get the credits for your help but on the other hand I feel that my summary is also important...

horstvogel · 2025-01-22T19:56:29Z

horstvogel
Jan 22, 2025

Hello, I have a Sensus PolluWatt Duo II, data generally comes with the Sensus Script, but only the serial number is displayed correctly by the meter. Sensor53 d1 produces the following data. The Sensus has a power supply

e5 is alone in a row, I think that there is something fundamentally wrong here.

Thanks!

0 replies

hoepfner · 2025-02-03T08:59:43Z

hoepfner
Feb 3, 2025

Hello,

I've a simulary behavior.
I've tried to set serial-buffer to 8 - behavior still exists.
I've tried to update to 14.4.1 - behavior still exists.

datas are read from smart meter, but values in WebGUI and MQTT are not updated.
can you please give me a hint, what I've done wrong.

for instance Checksum:

09:50:10.292 : 10 00 04 61 b1 0a 00 00 02 23 9a 16 01 fd 17 10 04 90 28 05 00 00 00 e7 16
Value is e7 = 231

09:50:41.755 RSL: SENSOR = {"Time":"2025-02-03T09:50:41","WA":{"Zählernummer":64480508,"Energie":45.463,"Letzter Stichtag EnergieStichtag Energie":45.463,"Volumenstrom":0.000,"Max. Volumenstrom":0.294,"Leistung":0,"Max. Leistung":11572,"Vorlauftemperatur":43,"Rücklauftemperatur":15,"Betriebsdauer":5786,"Checksum":33}}
"Checksum":33

script begin

D
wkup=1

B
;setup sensor
->sensor53 d0
->sensor53 r

S
; this device is powered by battery
; frequent requests will lead to blocking and reduces lifetime
; starting sequence:
;- press button on device once
;- restart Tasmota with script activated (you have 5 minutes to do this)
;- after 30s data is retrieved and logged (including SYSLOG depending on Tasmota log config)
;- now every 45min a new request is done, updated in WebUI (and transferred by MQTT every TPER period); polling period needs to be less 60min to avoid sleep mode of device!

;if ((upsecs==1) or (upsecs%2700==0)) {
if ((upsecs==1) or (upsecs%55==0)) {
print read meter
=#readmeter
}

if upsecs==30 {
->sensor53 d1
print read meter (dump)
=#readmeter
}

;if upsecs==55 {
; disable dump
;->sensor53 d0
;}

M 1
+1,3,rE1,0,2400,WA,1
1,=so3,8
1,0478u32s@1,Zählernummer,,Zählernummer,0
1,0406u32s@1000,Energie,MWh,Energie,3
1,4406u32s@1000,Stichtag Energie,MWh,Letzter Stichtag Energie,3
1,043bu32s@1000,Volumenstrom,m³/h,Volumenstrom,3
1,143bu32s@1000,Max. Volumenstrom,m³/h,Max. Volumenstrom,3
1,042bu32s@1,Leistung,W,Leistung,0
1,142bu32s@1,Max. Leistung,W,Max. Leistung,0
1,025buuUU@1,Vorlauftemperatur,°C,Vorlauftemperatur,0
1,025fuuUU@1,Rücklauftemperatur,°C,Rücklauftemperatur,0
1,0223uuUU@1,Betriebsdauer,Tage,Betriebsdauer,0
1,04902805x3uu@1,Checksum,C,Checksum,0

#readmeter
print wakeup start
;set serial protocol
sml(-1 1 "2400:8N1")
;send 0x55 for 2,2 seconds with 8N1 (53x), 2400 baud (wakeup sequence)
for wkup 1 53 1
sml(1 1 "55555555555555555555")
next
print wakeup end
wkup=1
print wait for the meter
delay(350)
;switch serial protocol
sml(-1 1 "2400:8E1")
print init MBus (1040004016); scan for device 00
sml(1 1 "1040004016")
delay(350)
print request current data (107BFE7916)
sml(1 1 "107BFE7916")
print request current data finished

script ende

00:00:00.250 CMD: Fall back to serial port, no SOF packet detected on USB port
00:00:00.250 HDW: ESP32-C3 v0.4
00:00:00.268 UFS: FlashFS mounted with 300 kB free
00:00:00.278 CFG: Loaded from File, Count 54
00:00:00.285 QPC: Count 1
00:00:00.286 CFG: CR 377/699, Busy 0
00:00:00.287 SCR: ufilesystem found
00:00:00.309 SCR: nv=1, tv=0, vns=5, vmem=34, smem=8192, gmem=348, tmem=8579
00:00:00.311 TYA: Active=0
00:00:00.314 ROT: Mode 1
00:00:00.320 BRY: GC from 3898 to 3698 bytes, objects freed 4/17 (in 0 ms) - slots from 33/61 to 25/61
00:00:00.339 CFG: No '*.autoconf' file found
00:00:00.343 BRY: GC from 5826 to 4260 bytes, objects freed 8/35 (in 1 ms) - slots from 55/76 to 35/76
00:00:00.344 BRY: Berry initialized, RAM used 4260 bytes
00:00:00.350 BRY: No 'preinit.be'
00:00:00.352 SRC: Restart
00:00:00.355 Project tasmota - Tasmota Version 14.4.1(tasmota32)-3_1_0(2025-02-03T08:24:03)
00:00:00.356 SRC: Rule
00:00:00.357 CMD: Grp 0, Cmd 'SENSOR', Idx 53, Len 2, Pld -99, Data 'd0'
00:00:00.358 RSL: RESULT = {"Command":"Error","Input":"SENSOR53 d0"}
00:00:00.360 SRC: Rule
00:00:00.361 CMD: Grp 0, Cmd 'SENSOR', Idx 53, Len 1, Pld -99, Data 'r'
00:00:00.363 SML: uart used: 1
00:00:00.368 meters: 1 , decode lines: 11, memory used: 2241 bytes
00:00:00.369 RSL: RESULT = {"Time":"1970-01-01T00:00:00","SML":{"CMD":"restart"}}
00:00:00.382 ETH: No ETH MDC and ETH MDIO GPIO defined
00:00:00.384 SML: uart used: 1
00:00:00.385 meters: 1 , decode lines: 11, memory used: 2241 bytes
00:00:00.406 BRY: No 'autoexec.be'
00:00:00.416 read meter
00:00:00.417 wakeup start
00:00:02.083 wakeup end
00:00:02.083 wait for the meter
00:00:02.434 init MBus (1040004016); scan for device 00
00:00:02.785 request current data (107BFE7916)
00:00:02.786 request current data finished
00:00:04.161 WIF: Checking connection...
00:00:04.162 WIF: Attempting connection...
00:00:05.002 WIF: Connecting to AP1 FRITZ!Box Fon WLAN 7570 vDSL Channel 1 BSSId 38:10:D5:0F:67:DA in mode HE20 as tasmota-FA5F88-8072...
00:00:05.059 WIF: IPv4 192.168.1.36, mask 255.255.254.0, gateway 192.168.1.1
00:00:07.295 WIF: Checking connection...
00:00:07.295 WIF: Connected
00:00:07.363 WIF: IPv6 Local fe80::da3b:daff:fefa:5f88%st1
00:00:07.507 HTP: Web server active on tasmota-FA5F88-8072 with IP address 192.168.1.36
00:00:07.545 HTP: Main Menu
00:00:07.741 NTP: Sync time...
00:00:07.760 WIF: DNS resolved '2.pool.ntp.org' (185.183.159.238) in 18 ms
00:00:07.794 RTC: UTC 2025-02-03T08:45:31Z, DST 2025-03-30T02:00:00, STD 2025-10-26T03:00:00
09:45:31.000 RTC: Synced by NTP
09:45:31.512 RSL: INFO1 = {"Info1":{"Module":"ESP32C3","Version":"14.4.1(tasmota32)","FallbackTopic":"cmnd/DVES_FA5F88_fb/","GroupTopic":"cmnd/tasmotas/"}}
09:45:31.525 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-FA5F88-8072","IPAddress":"192.168.1.36","IP6Global":"","IP6Local":"fe80::da3b:daff:fefa:5f88%st1"}}
09:45:31.538 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":46}}
09:45:31.552 TFS: File 'autoexec.bat' not found
09:45:34.364 WIF: IPv6 Global 2003:c5:971b:9f00:da3b:daff:fefa:5f88
09:45:34.737 QPC: Reset
09:45:35.709 BRY: GC from 5533 to 4607 bytes, objects freed 15/46 (in 0 ms) - slots from 73/91 to 50/91
09:45:35.712 RSL: STATE = {"Time":"2025-02-03T09:45:35","Uptime":"0T00:00:08","UptimeSec":8,"Heap":170,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":4,"Objects":46},"Wifi":{"AP":1,"SSId":"FRITZ!Box Fon WLAN 7570 vDSL","BSSId":"38:10:D5:0F:67:DA","Channel":1,"Mode":"HE20","RSSI":100,"Signal":-46,"LinkCount":1,"Downtime":"0T00:00:03"}}
09:45:35.749 RSL: SENSOR = {"Time":"2025-02-03T09:45:35","WA":{"Zählernummer":64480508,"Energie":45.463,"Letzter Stichtag EnergieStichtag Energie":45.463,"Volumenstrom":0.000,"Max. Volumenstrom":0.294,"Leistung":0,"Max. Leistung":11572,"Vorlauftemperatur":43,"Rücklauftemperatur":15,"Betriebsdauer":5786,"Checksum":33}}
09:45:36.738 APP: Boot Count 46
09:45:37.223 CFG: Saved, Count 55, Bytes 4096
09:45:40.725 RSL: config = {"ip":"192.168.1.36","dn":"Tasmota","fn":["Tasmota",null,null,null,null,null,null,null],"hn":"tasmota-FA5F88-8072","mac":"D83BDAFA5F88","md":"ESP32C3","ty":0,"if":0,"ofln":"Offline","onln":"Online","state":["OFF","ON","TOGGLE","HOLD"],"sw":"14.4.1","t":"tasmota_FA5F88","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"bat":0,"dslp":0,"sho":[],"sht":[],"ver":1}
09:45:40.732 RSL: sensors = {"sn":{"Time":"2025-02-03T09:45:40","WA":{"Zählernummer":64480508,"Energie":45.463,"Letzter Stichtag EnergieStichtag Energie":45.463,"Volumenstrom":0.000,"Max. Volumenstrom":0.294,"Leistung":0,"Max. Leistung":11572,"Vorlauftemperatur":43,"Rücklauftemperatur":15,"Betriebsdauer":5786,"Checksum":33}},"ver":1}
09:45:50.545 WIF: Checking connection...
09:45:56.751 read meter (dump)
09:45:56.752 wakeup start
09:45:58.705 wakeup end
09:45:58.707 wait for the meter
09:45:59.058 init MBus (1040004016); scan for device 00
09:45:59.409 request current data (107BFE7916)
09:45:59.411 request current data finished
09:45:59.460 : e5
09:45:59.741 : 68 93 93 68 08 00 72 08 05 48 64 c5 14 00 04 06 27 00 00 04 78 fc e4 d7 03 04 6d 02 00 c5 29 04
09:45:59.891 : 15 1f 9f 00 00 44 15 ff 9e 00 00 84 01 15 f0 9e 00 00 04 06 97 b1 00 00 44 06 97 b1 00 00 84 01
09:46:00.042 : 06 97 b1 00 00 84 10 06 00 00 00 00 c4 10 06 00 00 00 00 84 11 06 00 00 00 00 42 6c bf 2c 02 6c
09:46:00.192 : df 0c 04 3b 00 00 00 00 14 3b 26 01 00 00 04 2b 00 00 00 00 14 2b 34 2d 00 00 02 5b 2b 00 02 5f
09:46:00.350 : 0f 00 04 61 fc 0a 00 00 02 23 9a 16 01 fd 17 10 04 90 28 05 00 00 00 23 16
09:46:13.653 WIF: Checking connection...
09:46:22.736 read meter
09:46:22.738 wakeup start
09:46:24.691 wakeup end
09:46:24.693 wait for the meter
09:46:25.045 init MBus (1040004016); scan for device 00
09:46:25.396 request current data (107BFE7916)
09:46:25.398 request current data finished
09:46:25.479 : e5
09:46:25.741 : 68 93 93 68 08 00 72 08 05 48 64 c5 14 00 04 08 27 00 00 04 78 fc e4 d7 03 04 6d 03 00 c5 29 04
09:46:25.892 : 15 1f 9f 00 00 44 15 ff 9e 00 00 84 01 15 f0 9e 00 00 04 06 97 b1 00 00 44 06 97 b1 00 00 84 01
09:46:26.042 : 06 97 b1 00 00 84 10 06 00 00 00 00 c4 10 06 00 00 00 00 84 11 06 00 00 00 00 42 6c bf 2c 02 6c
09:46:26.193 : df 0c 04 3b 00 00 00 00 14 3b 26 01 00 00 04 2b 00 00 00 00 14 2b 34 2d 00 00 02 5b 2b 00 02 5f
09:46:26.350 : 0f 00 04 61 fc 0a 00 00 02 23 9a 16 01 fd 17 10 04 90 28 05 00 00 00 26 16
09:46:36.860 WIF: Checking connection...
09:46:56.892 WIF: Checking connection...
09:47:16.903 WIF: Checking connection...
09:47:18.738 read meter
09:47:18.739 wakeup start
09:47:20.694 wakeup end
09:47:20.695 wait for the meter
09:47:21.047 init MBus (1040004016); scan for device 00
09:47:21.398 request current data (107BFE7916)
09:47:21.400 request current data finished
09:47:21.480 : e5
09:47:21.742 : 68 93 93 68 08 00 72 08 05 48 64 c5 14 00 04 0a 27 00 00 04 78 fc e4 d7 03 04 6d 04 00 c5 29 04
09:47:21.893 : 15 1f 9f 00 00 44 15 ff 9e 00 00 84 01 15 f0 9e 00 00 04 06 97 b1 00 00 44 06 97 b1 00 00 84 01
09:47:22.043 : 06 97 b1 00 00 84 10 06 00 00 00 00 c4 10 06 00 00 00 00 84 11 06 00 00 00 00 42 6c bf 2c 02 6c
09:47:22.194 : df 0c 04 3b 00 00 00 00 14 3b 26 01 00 00 04 2b 00 00 00 00 14 2b 34 2d 00 00 02 5b 2b 00 02 5f
09:47:22.351 : 0f 00 04 61 fc 0a 00 00 02 23 9a 16 01 fd 17 10 04 90 28 05 00 00 00 29 16
09:47:40.120 WIF: Checking connection...
09:48:00.126 WIF: Checking connection...
09:48:14.732 read meter
09:48:14.734 wakeup start
09:48:16.687 wakeup end
09:48:16.689 wait for the meter
09:48:17.040 init MBus (1040004016); scan for device 00
09:48:17.392 request current data (107BFE7916)
09:48:17.394 request current data finished
09:48:17.467 : e5
09:48:17.743 : 68 93 93 68 08 00 72 08 05 48 64 c5 14 00 04 0c 27 00 00 04 78 fc e4 d7 03 04 6d 04 00 c5 29 04
09:48:17.894 : 15 1f 9f 00 00 44 15 ff 9e 00 00 84 01 15 f0 9e 00 00 04 06 97 b1 00 00 44 06 97 b1 00 00 84 01
09:48:18.044 : 06 97 b1 00 00 84 10 06 00 00 00 00 c4 10 06 00 00 00 00 84 11 06 00 00 00 00 42 6c bf 2c 02 6c
09:48:18.195 : df 0c 04 3b 00 00 00 00 14 3b 26 01 00 00 04 2b 00 00 00 00 14 2b 34 2d 00 00 02 5b 2b 00 02 5f
09:48:18.352 : 0f 00 04 61 fc 0a 00 00 02 23 9a 16 01 fd 17 10 04 90 28 05 00 00 00 2b 16
09:48:23.401 WIF: Checking connection...
09:48:43.396 WIF: Checking connection...
09:49:03.394 WIF: Checking connection...
09:49:10.728 read meter
09:49:10.729 wakeup start
09:49:12.683 wakeup end
09:49:12.684 wait for the meter
09:49:13.036 init MBus (1040004016); scan for device 00
09:49:13.387 request current data (107BFE7916)
09:49:13.389 request current data finished
09:49:13.469 : e5
09:49:13.744 : 68 93 93 68 08 00 72 08 05 48 64 c5 14 00 04 0e 27 00 00 04 78 fc e4 d7 03 04 6d 05 00 c5 29 04
09:49:13.895 : 15 1f 9f 00 00 44 15 ff 9e 00 00 84 01 15 f0 9e 00 00 04 06 97 b1 00 00 44 06 97 b1 00 00 84 01
09:49:14.045 : 06 97 b1 00 00 84 10 06 00 00 00 00 c4 10 06 00 00 00 00 84 11 06 00 00 00 00 42 6c bf 2c 02 6c
09:49:14.195 : df 0c 04 3b 00 00 00 00 14 3b 26 01 00 00 04 2b 00 00 00 00 14 2b 34 2d 00 00 02 5b 2b 00 02 5f
09:49:14.353 : 10 00 04 61 b1 0a 00 00 02 23 9a 16 01 fd 17 10 04 90 28 05 00 00 00 e4 16
09:49:26.609 WIF: Checking connection...
09:49:46.627 WIF: Checking connection...
09:50:06.666 WIF: Checking connection...
09:50:06.713 read meter
09:50:06.715 wakeup start
09:50:08.668 wakeup end
09:50:08.669 wait for the meter
09:50:09.021 init MBus (1040004016); scan for device 00
09:50:09.372 request current data (107BFE7916)
09:50:09.374 request current data finished
09:50:09.454 : e5
09:50:09.683 : 68 93 93 68 08 00 72 08 05 48 64 c5 14 00 04 10 27 00 00 04 78 fc e4 d7 03 04 6d 06 00 c5 29 04
09:50:09.833 : 15 1f 9f 00 00 44 15 ff 9e 00 00 84 01 15 f0 9e 00 00 04 06 97 b1 00 00 44 06 97 b1 00 00 84 01
09:50:09.984 : 06 97 b1 00 00 84 10 06 00 00 00 00 c4 10 06 00 00 00 00 84 11 06 00 00 00 00 42 6c bf 2c 02 6c
09:50:10.134 : df 0c 04 3b 00 00 00 00 14 3b 26 01 00 00 04 2b 00 00 00 00 14 2b 34 2d 00 00 02 5b 2b 00 02 5f
09:50:10.292 : 10 00 04 61 b1 0a 00 00 02 23 9a 16 01 fd 17 10 04 90 28 05 00 00 00 e7 16
09:50:29.818 WIF: Checking connection...
09:50:41.714 BRY: GC from 5353 to 4607 bytes, objects freed 2/46 (in 1 ms) - slots from 51/91 to 50/91
09:50:41.716 RSL: STATE = {"Time":"2025-02-03T09:50:41","Uptime":"0T00:05:14","UptimeSec":314,"Heap":169,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":99,"MqttCount":0,"Berry":{"HeapUsed":4,"Objects":46},"Wifi":{"AP":1,"SSId":"FRITZ!Box Fon WLAN 7570 vDSL","BSSId":"38:10:D5:0F:67:DA","Channel":1,"Mode":"HE20","RSSI":100,"Signal":-48,"LinkCount":1,"Downtime":"0T00:00:03"}}
09:50:41.755 RSL: SENSOR = {"Time":"2025-02-03T09:50:41","WA":{"Zählernummer":64480508,"Energie":45.463,"Letzter Stichtag EnergieStichtag Energie":45.463,"Volumenstrom":0.000,"Max. Volumenstrom":0.294,"Leistung":0,"Max. Leistung":11572,"Vorlauftemperatur":43,"Rücklauftemperatur":15,"Betriebsdauer":5786,"Checksum":33}}
09:50:49.818 WIF: Checking connection...
09:51:02.717 read meter
09:51:02.718 wakeup start
09:51:04.672 wakeup end
09:51:04.673 wait for the meter
09:51:05.025 init MBus (1040004016); scan for device 00
09:51:05.376 request current data (107BFE7916)
09:51:05.378 request current data finished
09:51:05.458 : e5
09:51:05.684 : 68 93 93 68 08 00 72 08 05 48 64 c5 14 00 04 12 27 00 00 04 78 fc e4 d7 03 04 6d 07 00 c5 29 04
09:51:05.834 : 15 1f 9f 00 00 44 15 ff 9e 00 00 84 01 15 f0 9e 00 00 04 06 97 b1 00 00 44 06 97 b1 00 00 84 01
09:51:05.985 : 06 97 b1 00 00 84 10 06 00 00 00 00 c4 10 06 00 00 00 00 84 11 06 00 00 00 00 42 6c bf 2c 02 6c
09:51:06.135 : df 0c 04 3b 00 00 00 00 14 3b 26 01 00 00 04 2b 00 00 00 00 14 2b 34 2d 00 00 02 5b 2b 00 02 5f
09:51:06.292 : 10 00 04 61 b1 0a 00 00 02 23 9a 16 01 fd 17 10 04 90 28 05 00 00 00 ea 16
09:51:13.068 WIF: Checking connection...
09:51:33.083 WIF: Checking connection...

2 replies

horstvogel Feb 20, 2025

Moin, was für einen Zähler hast Du? Beim PolluWatt Duo II komme ich nun an einige Daten ran.
Zählernummer, Betriebsstunden, Energie und Leistung passen. Für den Rest habe ich keine Ahnung was da gesetzt werden muss. u32s bbcd8, uuUU....alles durchprobiert. Das Dokument für das Modbus Protokoll habe ich bei Sensus angefragt und auch bekommen, aber es ist da für mich nicht erkenntlich aufgeführt, wie ich die Daten dort "umwandeln" muss

horstvogel Feb 22, 2025

Laut der Software von "Sensus" sind die Werte für Temperatur, Leistung etc, alle 32 Bit Real, dass finde ich so nicht auf der Tasmotaseite, wie man einen 32 bit Real auflösen kann, dass Bild zeigt einen anderen Zähler, gleicher Typ....

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Tasmota SML MBus HeatMeter: delayed/wrong values after some time and sudden transfer stops #20460

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 4 comments 17 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Tasmota SML MBus HeatMeter: delayed/wrong values after some time and sudden transfer stops #20460

Replies: 4 comments · 17 replies

evaluationevaluation Jan 14, 2024 Author

evaluationevaluation Jan 28, 2024 Author

evaluationevaluation Jan 29, 2024 Author

evaluationevaluation Jan 30, 2024 Author

evaluationevaluation Jan 31, 2024 Author

evaluationevaluation Jan 31, 2024 Author

script begin

script ende

Replies: 4 comments 17 replies

evaluationevaluation
Jan 14, 2024
Author

evaluationevaluation Jan 28, 2024
Author

evaluationevaluation Jan 29, 2024
Author

evaluationevaluation Jan 30, 2024
Author

evaluationevaluation
Jan 31, 2024
Author

evaluationevaluation Jan 31, 2024
Author