search

SzczepanLeon / esphome-components

149 stars 52 forks source link

Support for flowiq2200 #62

Closed evilmumi closed 8 months ago

evilmumi commented 10 months ago

Hi,

is it possible to add flowiq2200 support? I found something here but dont know how to implement: https://github.com/wmbusmeters/wmbusmeters/blob/master/src/driver_flowiq2200.cc

Log is like:


wMBus-lib: Processing C1 B frame -- NOT supported yet
 FullFrame: 0x54, 0x3D, 0x34, 0x44, 0x37, 0x2C, 0x37, 0x79, 0x71, 0x23, 0x3A, 0x16, 0x8D, 0x20, 0xA0, 0xA0, 0x81, 0x12, 0x3D, 0x48, 0x20, 0x86, 0xA0, 0xA2, 0x57, 0x93, 0x83, 0x8C, 0xD2, 0xDF, 0xDB, 0x41, 0x45, 0xE8, 0x5B, 0x12, 0x1D, 0x72, 0x38, 0x71, 0x82, 0x91, 0x00, 0xF1, 0x8A, 0xA3, 0x9D, 0xD5, 0x67, 0x4F, 0xC3, 0xCF, 0x45, 0xAF, 0xFE, 
wMBus-lib:  Error during decoding 'unknown'

wMBus-lib: Processing C1 B frame -- NOT supported yet
 FullFrame: 0x54, 0x3D, 0x9A, 0x22, 0x1B, 0x96, 0x1B, 0xBC, 0xB8, 0xD8, 0xDE, 0x84, 0xA3, 0x48, 0x29, 0x29, 0x8A, 0xE1, 0xBF, 0x44, 0x93, 0x82, 0x18, 0x64, 0xA8, 0xFA, 0xD9, 0x9B, 0xF4, 0x2C, 0x3B, 0xE4, 0x19, 0x23, 0xBE, 0x10, 0xB9, 0xB9, 0x0B, 0xD1, 0xE1, 0x9D, 0x54, 0x09, 0x7B, 0x3C, 0x42, 0xF3, 0x5B, 0x5B, 0xE3, 0xC0, 0x13, 0x05, 0x8D, 0x21, 0xBF, 0x2D, 0xFF, 0x9C, 0x56, 0x61, 0x36, 0x11, 0xBD, 0xB7, 0x3D, 0x9A, 0x22, 0x1B, 0x96, 0x1B, 0xBC, 0xB8, 0xD8, 0xDE, 0x84, 0xA3, 0x48, 0x29, 0xBC, 0x47, 0x65, 0xA4, 0x2C, 0x5F, 0xFF, 0x81, 0xBB, 0x29, 0xDF, 0x9B, 0xF4, 0x2C, 0x3B, 0xE4, 0x19, 0x23, 0xBE, 0x10, 0xB9, 0xB9, 0x0B, 0xD1, 0xE1, 0x9D, 0x54, 0x09, 0x7B, 0x3C, 0x42, 0xF3, 0x5B, 0x5B, 0xE3, 0xC0, 0x13, 0x05, 0x8D, 0x21, 0xBF, 0x2D, 0xFF, 0x9C, 0x56, 0x61, 0x36, 0x11, 0xBD, 0xB7, 0x3D, 0x9A, 0x22, 0x1B, 0x96, 0x1B, 0xBC, 0xB8, 0xD8, 0xDE, 0x84, 0xA3, 0x48, 0x29, 0xBC, 0x47, 0x65, 0xA4, 0x2C, 0x5F, 0xFF, 0x81, 0xBB, 0x29, 0xDF, 0xC9, 0x7E, 
wMBus-lib:  Error during decoding 'unknown'
SzczepanLeon commented 10 months ago

Yes it is possible, but I don't have plans to add B frame support.

evilmumi commented 10 months ago

Yes it is possible, but I don't have plans to add B frame support.

Is there any chance to "bribe" you?

SzczepanLeon commented 10 months ago

It is not possible. I don't have time to read about B frame structure etc.

But if You really want that feature You can try to find in internet/github code for that B frame (how to calculate CRC and how to cut CRC from frame).

evilmumi commented 10 months ago

It is not possible. I don't have time to read about B frame structure etc.

But if You really want that feature You can try to find in internet/github code for that B frame (how to calculate CRC and how to cut CRC from frame).

I am not a big coder. I found 2 things https://github.com/wmbusmeters/wmbusmeters/blob/master/src/driver_flowiq2200.cc and https://github.com/chester4444/esp-multical21/tree/master/src

is this helpful that you integrate it?

SzczepanLeon commented 8 months ago

Please try version pre 3:

external_components:
  - source: github://SzczepanLeon/esphome-components@pre_v3.0
    refresh: 0d
    components: [ wmbus ]
evilmumi commented 8 months ago

Thanks. Now I am getting this:

[17:29:12][W][component:214]: Component debug took a long time for an operation (0.10 s). [17:29:12][W][component:215]: Components should block for at most 20-30ms. [17:29:12][E][rxLoop:157]: Length problem: req(53) != rx(51) [17:29:12][D][rxLoop:159]: Have 51 bytes from CC1101 Rx [17:29:12][D][mbus:024]: Processing C1 B frame [17:29:12][V][mbus:028]: Frame: 343D34000044372C347971233A168D202F6060253F212A014752D819915FB658B5C2128F20FEB43F9084041B18D2B3EBD80D26 (51) [with CRC] [17:29:12][V][mbus:153]: Package (51) too short for packet Length: 52 [17:29:12][V][mbus:154]: 53 > 51

SzczepanLeon commented 8 months ago

Now I am getting this:

Thanks for traces. I see couple places with bug in my code - will be fixed probably today.

evilmumi commented 8 months ago

If I can help - just pls say me how

SzczepanLeon commented 8 months ago

If I can help - just pls say me how

Yes You can. I don't have meter transmitting in C1 B, so I need logs. Please wait for next version with fix.

Next version is available. Please test it and collect VERBOSE logs.

btw For now you can use evo868 driver and collect total_water_m3 it should be the same as total_m3 in wmbusmeters.

evilmumi commented 8 months ago

so i should change sensor platform wmbus type flowiq2000 to type evo868 ?

SzczepanLeon commented 8 months ago

so i should change sensor platform wmbus type flowiq2000 to type evo868 ?

For now - yes. It should be like:

sensor:
  - platform: wmbus
    meter_id: 0x23717934
    type: evo868
    key: "key_key_key"
    total_water_m3:
      name: "test meter"

Driver for flowiq2000 should be ready soon, but first we should get correct C1 B frame.

evilmumi commented 8 months ago

image image image image image image

SzczepanLeon commented 8 months ago

Please include text logs.

evilmumi commented 8 months ago

here you go - fine with it?

[11:28:40][V][sensor:043]: 'Heap Free': Received new state 14056.000000
[11:28:40][D][sensor:093]: 'Heap Free': Sending state 14056.00000 B with 0 decimals of accuracy
[11:28:40][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:40][V][json:058]: Size after shrink 76 bytes
[11:28:40][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:28:40][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:28:40][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:40][V][json:058]: Size after shrink 80 bytes
[11:28:40][V][sensor:043]: 'Heap Fragmentation': Received new state 18.000000
[11:28:40][D][sensor:093]: 'Heap Fragmentation': Sending state 18.00000 % with 1 decimals of accuracy
[11:28:40][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:40][V][json:058]: Size after shrink 84 bytes
[11:28:40][V][sensor:043]: 'Application Loop Time': Received new state 342.000000
[11:28:40][D][sensor:093]: 'Application Loop Time': Sending state 342.00000 ms with 0 decimals of accuracy
[11:28:40][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:40][V][json:058]: Size after shrink 84 bytes
[11:28:40][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:28:40][W][component:215]: Components should block for at most 20-30ms.
[11:28:45][V][sensor:043]: 'Heap Free': Received new state 14056.000000
[11:28:45][D][sensor:093]: 'Heap Free': Sending state 14056.00000 B with 0 decimals of accuracy
[11:28:45][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:45][V][json:058]: Size after shrink 76 bytes
[11:28:45][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:28:45][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:28:45][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:45][V][json:058]: Size after shrink 80 bytes
[11:28:45][V][sensor:043]: 'Heap Fragmentation': Received new state 18.000000
[11:28:45][D][sensor:093]: 'Heap Fragmentation': Sending state 18.00000 % with 1 decimals of accuracy
[11:28:45][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:45][V][json:058]: Size after shrink 84 bytes
[11:28:45][V][sensor:043]: 'Application Loop Time': Received new state 117.000000
[11:28:45][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy
[11:28:45][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:45][V][json:058]: Size after shrink 84 bytes
[11:28:45][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:28:45][W][component:215]: Components should block for at most 20-30ms.
[11:28:50][V][sensor:043]: 'Heap Free': Received new state 14056.000000
[11:28:50][D][sensor:093]: 'Heap Free': Sending state 14056.00000 B with 0 decimals of accuracy
[11:28:50][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:50][V][json:058]: Size after shrink 76 bytes
[11:28:50][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:28:50][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:28:50][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:50][V][json:058]: Size after shrink 80 bytes
[11:28:50][V][sensor:043]: 'Heap Fragmentation': Received new state 21.000000
[11:28:50][D][sensor:093]: 'Heap Fragmentation': Sending state 21.00000 % with 1 decimals of accuracy
[11:28:50][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:50][V][json:058]: Size after shrink 84 bytes
[11:28:50][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[11:28:50][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[11:28:50][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:50][V][json:058]: Size after shrink 84 bytes
[11:28:50][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:28:50][W][component:215]: Components should block for at most 20-30ms.
[11:28:55][V][sensor:043]: 'Heap Free': Received new state 14200.000000
[11:28:55][D][sensor:093]: 'Heap Free': Sending state 14200.00000 B with 0 decimals of accuracy
[11:28:55][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:55][V][json:058]: Size after shrink 76 bytes
[11:28:55][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:28:55][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:28:55][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:55][V][json:058]: Size after shrink 80 bytes
[11:28:55][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:28:55][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:28:55][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:55][V][json:058]: Size after shrink 84 bytes
[11:28:55][V][sensor:043]: 'Application Loop Time': Received new state 120.000000
[11:28:55][D][sensor:093]: 'Application Loop Time': Sending state 120.00000 ms with 0 decimals of accuracy
[11:28:55][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:28:55][V][json:058]: Size after shrink 84 bytes
[11:28:55][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:28:55][W][component:215]: Components should block for at most 20-30ms.
[11:28:59][D][rxLoop:161]: Have 53 bytes from CC1101 Rx
[11:28:59][D][mbus:024]: Processing C1 B frame
[11:28:59][V][mbus:028]: Frame: 3444372C347971233A168D2001D3673F3F215E187B289C571B180068A7DC4BA2FC9E39709BDD3087B10D3C46451A53EAFD9EE955DD (53) [with CRC]
[11:28:59][V][mbus:161]: Validating CRC for Block1 + Block2
[11:28:59][I][crc:035]:   calculated: 0x0F0A, read: 0x55DD  !!!
[11:28:59][D][rxLoop:171]: Error during decoding.
[11:29:00][V][sensor:043]: 'Heap Free': Received new state 14200.000000
[11:29:00][D][sensor:093]: 'Heap Free': Sending state 14200.00000 B with 0 decimals of accuracy
[11:29:00][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:00][V][json:058]: Size after shrink 76 bytes
[11:29:00][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:29:00][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:29:00][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:00][V][json:058]: Size after shrink 80 bytes
[11:29:00][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:29:00][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:29:00][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:00][V][json:058]: Size after shrink 84 bytes
[11:29:00][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[11:29:00][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[11:29:00][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:00][V][json:058]: Size after shrink 84 bytes
[11:29:00][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:29:00][W][component:215]: Components should block for at most 20-30ms.
[11:29:05][V][sensor:043]: 'Heap Free': Received new state 14200.000000
[11:29:05][D][sensor:093]: 'Heap Free': Sending state 14200.00000 B with 0 decimals of accuracy
[11:29:05][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:05][V][json:058]: Size after shrink 76 bytes
[11:29:05][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:29:05][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:29:05][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:05][V][json:058]: Size after shrink 80 bytes
[11:29:05][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:29:05][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:29:05][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:05][V][json:058]: Size after shrink 84 bytes
[11:29:05][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[11:29:05][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[11:29:05][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:05][V][json:058]: Size after shrink 84 bytes
[11:29:05][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:29:05][W][component:215]: Components should block for at most 20-30ms.
[11:29:10][V][sensor:043]: 'Heap Free': Received new state 14200.000000
[11:29:10][D][sensor:093]: 'Heap Free': Sending state 14200.00000 B with 0 decimals of accuracy
[11:29:10][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:10][V][json:058]: Size after shrink 76 bytes
[11:29:10][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:29:10][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:29:10][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:10][V][json:058]: Size after shrink 80 bytes
[11:29:10][V][sensor:043]: 'Heap Fragmentation': Received new state 19.000000
[11:29:10][D][sensor:093]: 'Heap Fragmentation': Sending state 19.00000 % with 1 decimals of accuracy
[11:29:10][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:10][V][json:058]: Size after shrink 84 bytes
[11:29:10][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[11:29:10][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[11:29:10][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:10][V][json:058]: Size after shrink 84 bytes
[11:29:10][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:29:10][W][component:215]: Components should block for at most 20-30ms.
[11:29:13][V][sensor:043]: 'Boot counter': Received new state 13.000000
[11:29:13][D][sensor:093]: 'Boot counter': Sending state 13.00000  with 0 decimals of accuracy
[11:29:13][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:13][V][json:058]: Size after shrink 72 bytes
[11:29:15][V][sensor:043]: 'Heap Free': Received new state 14200.000000
[11:29:15][D][sensor:093]: 'Heap Free': Sending state 14200.00000 B with 0 decimals of accuracy
[11:29:15][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:15][V][json:058]: Size after shrink 76 bytes
[11:29:15][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:29:15][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:29:15][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:15][V][json:058]: Size after shrink 80 bytes
[11:29:15][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:29:15][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:29:15][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:15][V][json:058]: Size after shrink 84 bytes
[11:29:15][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[11:29:15][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[11:29:15][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:15][V][json:058]: Size after shrink 84 bytes
[11:29:15][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:29:15][W][component:215]: Components should block for at most 20-30ms.
[11:29:16][D][rxLoop:161]: Have 53 bytes from CC1101 Rx
[11:29:16][D][mbus:024]: Processing C1 B frame
[11:29:16][V][mbus:028]: Frame: 3444372C347971233A168D2002E0673F213A3ACD1AA8EA11533902963D73744CECFD508CD1C27C7D76759A6D1D6D210FFB362F13DD (53) [with CRC]
[11:29:16][V][mbus:161]: Validating CRC for Block1 + Block2
[11:29:16][I][crc:035]:   calculated: 0x41F6, read: 0x13DD  !!!
[11:29:16][D][rxLoop:171]: Error during decoding.
[11:29:20][V][sensor:043]: 'Device WLAN Signal': Received new state -49.000000
[11:29:20][D][sensor:093]: 'Device WLAN Signal': Sending state 100.00000 % with 0 decimals of accuracy
[11:29:20][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:20][V][json:058]: Size after shrink 80 bytes
[11:29:20][V][sensor:043]: 'Heap Free': Received new state 9352.000000
[11:29:20][D][sensor:093]: 'Heap Free': Sending state 9352.00000 B with 0 decimals of accuracy
[11:29:20][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:20][V][json:058]: Size after shrink 72 bytes
[11:29:20][V][sensor:043]: 'Heap Max Block': Received new state 5968.000000
[11:29:20][D][sensor:093]: 'Heap Max Block': Sending state 5968.00000 B with 0 decimals of accuracy
[11:29:20][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:20][V][json:058]: Size after shrink 80 bytes
[11:29:20][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:29:20][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:29:20][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:20][V][json:058]: Size after shrink 84 bytes
[11:29:20][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[11:29:20][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[11:29:20][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:20][V][json:058]: Size after shrink 84 bytes
[11:29:20][W][component:214]: Component debug took a long time for an operation (0.11 s).
[11:29:20][W][component:215]: Components should block for at most 20-30ms.
[11:29:25][V][sensor:043]: 'Heap Free': Received new state 14200.000000
[11:29:25][D][sensor:093]: 'Heap Free': Sending state 14200.00000 B with 0 decimals of accuracy
[11:29:25][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:25][V][json:058]: Size after shrink 76 bytes
[11:29:25][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:29:25][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:29:25][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:25][V][json:058]: Size after shrink 80 bytes
[11:29:25][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:29:25][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:29:25][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:25][V][json:058]: Size after shrink 84 bytes
[11:29:25][V][sensor:043]: 'Application Loop Time': Received new state 124.000000
[11:29:25][D][sensor:093]: 'Application Loop Time': Sending state 124.00000 ms with 0 decimals of accuracy
[11:29:25][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:25][V][json:058]: Size after shrink 84 bytes
[11:29:25][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:29:25][W][component:215]: Components should block for at most 20-30ms.
[11:29:30][V][sensor:043]: 'Heap Free': Received new state 14192.000000
[11:29:30][D][sensor:093]: 'Heap Free': Sending state 14192.00000 B with 0 decimals of accuracy
[11:29:30][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:30][V][json:058]: Size after shrink 76 bytes
[11:29:30][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:29:30][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:29:30][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:30][V][json:058]: Size after shrink 80 bytes
[11:29:30][V][sensor:043]: 'Heap Fragmentation': Received new state 19.000000
[11:29:30][D][sensor:093]: 'Heap Fragmentation': Sending state 19.00000 % with 1 decimals of accuracy
[11:29:30][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:30][V][json:058]: Size after shrink 84 bytes
[11:29:30][V][sensor:043]: 'Application Loop Time': Received new state 117.000000
[11:29:30][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy
[11:29:30][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:30][V][json:058]: Size after shrink 84 bytes
[11:29:30][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:29:30][W][component:215]: Components should block for at most 20-30ms.
[11:29:35][V][sensor:043]: 'Heap Free': Received new state 14192.000000
[11:29:35][D][sensor:093]: 'Heap Free': Sending state 14192.00000 B with 0 decimals of accuracy
[11:29:35][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:35][V][json:058]: Size after shrink 76 bytes
[11:29:35][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:29:35][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:29:35][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:35][V][json:058]: Size after shrink 80 bytes
[11:29:35][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:29:35][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:29:35][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:35][V][json:058]: Size after shrink 84 bytes
[11:29:35][V][sensor:043]: 'Application Loop Time': Received new state 117.000000
[11:29:35][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy
[11:29:35][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:35][V][json:058]: Size after shrink 84 bytes
[11:29:35][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:29:35][W][component:215]: Components should block for at most 20-30ms.
[11:29:40][V][sensor:043]: 'Heap Free': Received new state 14192.000000
[11:29:40][D][sensor:093]: 'Heap Free': Sending state 14192.00000 B with 0 decimals of accuracy
[11:29:40][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:40][V][json:058]: Size after shrink 76 bytes
[11:29:40][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:29:40][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:29:40][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:40][V][json:058]: Size after shrink 80 bytes
[11:29:40][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:29:40][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:29:40][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:40][V][json:058]: Size after shrink 84 bytes
[11:29:40][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[11:29:40][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[11:29:40][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:40][V][json:058]: Size after shrink 84 bytes
[11:29:40][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:29:40][W][component:215]: Components should block for at most 20-30ms.
[11:29:45][V][sensor:043]: 'Heap Free': Received new state 14192.000000
[11:29:45][D][sensor:093]: 'Heap Free': Sending state 14192.00000 B with 0 decimals of accuracy
[11:29:45][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:45][V][json:058]: Size after shrink 76 bytes
[11:29:45][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:29:45][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:29:45][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:45][V][json:058]: Size after shrink 80 bytes
[11:29:45][V][sensor:043]: 'Heap Fragmentation': Received new state 19.000000
[11:29:45][D][sensor:093]: 'Heap Fragmentation': Sending state 19.00000 % with 1 decimals of accuracy
[11:29:45][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:45][V][json:058]: Size after shrink 84 bytes
[11:29:45][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[11:29:45][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[11:29:45][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:45][V][json:058]: Size after shrink 84 bytes
[11:29:45][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:29:45][W][component:215]: Components should block for at most 20-30ms.
[11:29:49][D][rxLoop:161]: Have 74 bytes from CC1101 Rx
[11:29:49][D][mbus:024]: Processing C1 B frame
[11:29:49][V][mbus:028]: Frame: 4944372C347971233A168D2004E2673F212724BEBE98AE300F4249DCE704AE78E894D9BA4DBDDD3ED3E503629AB1FDDE25A27758DC897E133E8DF69DEEBE86953D4944372C347971233A (74) [with CRC]
[11:29:49][V][mbus:161]: Validating CRC for Block1 + Block2
[11:29:49][I][crc:035]:   calculated: 0x43BD, read: 0x233A  !!!
[11:29:49][D][rxLoop:171]: Error during decoding.
[11:29:50][V][sensor:043]: 'Heap Free': Received new state 14192.000000
[11:29:50][D][sensor:093]: 'Heap Free': Sending state 14192.00000 B with 0 decimals of accuracy
[11:29:50][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:50][V][json:058]: Size after shrink 76 bytes
[11:29:50][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:29:50][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:29:50][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:50][V][json:058]: Size after shrink 80 bytes
[11:29:50][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:29:50][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:29:50][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:50][V][json:058]: Size after shrink 84 bytes
[11:29:50][V][sensor:043]: 'Application Loop Time': Received new state 117.000000
[11:29:50][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy
[11:29:50][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:50][V][json:058]: Size after shrink 84 bytes
[11:29:50][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:29:50][W][component:215]: Components should block for at most 20-30ms.
[11:29:55][V][sensor:043]: 'Heap Free': Received new state 14144.000000
[11:29:55][D][sensor:093]: 'Heap Free': Sending state 14144.00000 B with 0 decimals of accuracy
[11:29:55][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:55][V][json:058]: Size after shrink 76 bytes
[11:29:55][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:29:55][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:29:55][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:55][V][json:058]: Size after shrink 80 bytes
[11:29:55][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:29:55][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:29:55][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:55][V][json:058]: Size after shrink 84 bytes
[11:29:55][V][sensor:043]: 'Application Loop Time': Received new state 117.000000
[11:29:55][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy
[11:29:55][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:29:55][V][json:058]: Size after shrink 84 bytes
[11:29:55][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:29:55][W][component:215]: Components should block for at most 20-30ms.
[11:30:00][V][sensor:043]: 'Heap Free': Received new state 14144.000000
[11:30:00][D][sensor:093]: 'Heap Free': Sending state 14144.00000 B with 0 decimals of accuracy
[11:30:00][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:00][V][json:058]: Size after shrink 76 bytes
[11:30:00][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:30:00][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:30:00][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:00][V][json:058]: Size after shrink 80 bytes
[11:30:00][V][sensor:043]: 'Heap Fragmentation': Received new state 19.000000
[11:30:00][D][sensor:093]: 'Heap Fragmentation': Sending state 19.00000 % with 1 decimals of accuracy
[11:30:00][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:00][V][json:058]: Size after shrink 84 bytes
[11:30:00][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[11:30:00][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[11:30:00][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:00][V][json:058]: Size after shrink 84 bytes
[11:30:00][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:30:00][W][component:215]: Components should block for at most 20-30ms.
[11:30:05][V][sensor:043]: 'Heap Free': Received new state 14144.000000
[11:30:05][D][sensor:093]: 'Heap Free': Sending state 14144.00000 B with 0 decimals of accuracy
[11:30:05][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:05][V][json:058]: Size after shrink 76 bytes
[11:30:05][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:30:05][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:30:05][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:05][V][json:058]: Size after shrink 80 bytes
[11:30:05][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:30:05][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:30:05][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:05][V][json:058]: Size after shrink 84 bytes
[11:30:05][V][sensor:043]: 'Application Loop Time': Received new state 117.000000
[11:30:05][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy
[11:30:05][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:05][V][json:058]: Size after shrink 84 bytes
[11:30:05][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:30:05][W][component:215]: Components should block for at most 20-30ms.
[11:30:10][V][sensor:043]: 'Heap Free': Received new state 14144.000000
[11:30:10][D][sensor:093]: 'Heap Free': Sending state 14144.00000 B with 0 decimals of accuracy
[11:30:10][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:10][V][json:058]: Size after shrink 76 bytes
[11:30:10][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:30:10][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:30:10][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:10][V][json:058]: Size after shrink 80 bytes
[11:30:10][V][sensor:043]: 'Heap Fragmentation': Received new state 19.000000
[11:30:10][D][sensor:093]: 'Heap Fragmentation': Sending state 19.00000 % with 1 decimals of accuracy
[11:30:10][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:10][V][json:058]: Size after shrink 84 bytes
[11:30:10][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[11:30:10][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[11:30:10][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:10][V][json:058]: Size after shrink 84 bytes
[11:30:10][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:30:10][W][component:215]: Components should block for at most 20-30ms.
[11:30:13][V][sensor:043]: 'Boot counter': Received new state 13.000000
[11:30:13][D][sensor:093]: 'Boot counter': Sending state 13.00000  with 0 decimals of accuracy
[11:30:13][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:13][V][json:058]: Size after shrink 72 bytes
[11:30:15][V][sensor:043]: 'Heap Free': Received new state 14144.000000
[11:30:15][D][sensor:093]: 'Heap Free': Sending state 14144.00000 B with 0 decimals of accuracy
[11:30:15][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:15][V][json:058]: Size after shrink 76 bytes
[11:30:15][V][sensor:043]: 'Heap Max Block': Received new state 7552.000000
[11:30:15][D][sensor:093]: 'Heap Max Block': Sending state 7552.00000 B with 0 decimals of accuracy
[11:30:15][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:15][V][json:058]: Size after shrink 80 bytes
[11:30:15][V][sensor:043]: 'Heap Fragmentation': Received new state 22.000000
[11:30:15][D][sensor:093]: 'Heap Fragmentation': Sending state 22.00000 % with 1 decimals of accuracy
[11:30:15][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:15][V][json:058]: Size after shrink 84 bytes
[11:30:15][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[11:30:15][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[11:30:15][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[11:30:15][V][json:058]: Size after shrink 84 bytes
[11:30:15][W][component:214]: Component debug took a long time for an operation (0.10 s).
[11:30:15][W][component:215]: Components should block for at most 20-30ms.
SzczepanLeon commented 8 months ago

Please try this version and collect VERBOSE:

external_components:
  - source: github://SzczepanLeon/esphome-components@pre_v3.0_noCrc
    refresh: 0d
    components: [ wmbus ]
evilmumi commented 8 months ago

here we go again. do you need more lines?

`[2:04:09][D][rxLoop:159]: Have 53 bytes from CC1101 Rx
[12:04:09][D][mbus:022]: Processing C1 B frame
[12:04:09][V][mbus:026]: Frame: 3444372C347971233A168D208503034D47E4267B29F54D2C0DBAFEABFBFD637A980568CC43188EAFA09126B45AD56753CF785DDB64 (53) [with CRC]
[12:04:09][V][mbus:159]: Validating CRC for Block1 + Block2
[12:04:09][I][crc:035]:   calculated: 0x7E01, read: 0xDB64  !!!
[12:04:09][D][mbus:056]: Frame: 3244372C347971233A168D208503034D47E4267B29F54D2C0DBAFEABFBFD637A980568CC43188EAFA09126B45AD56753CF785D (51) [without CRC]
[12:04:09][D][wmbus:195]: Meter ID [0x23717934] RSSI: -95 dBm LQI: 159 Frame: C1 B not found in configuration T: 3244372C347971233A168D208503034D47E4267B29F54D2C0DBAFEABFBFD637A980568CC43188EAFA09126B45AD56753CF785D (51)
[12:05:42][D][rxLoop:159]: Have 53 bytes from CC1101 Rx
[12:05:42][D][mbus:022]: Processing C1 B frame
[12:05:42][V][mbus:026]: Frame: 34443728347971233A168D208BA2A2B51F90DA26D6D3003A3E1AFBAF2B69D5D768B2921C8BBA984B6479423CE27BD81D060DDB92D6 (53) [with CRC]
[12:05:42][V][mbus:159]: Validating CRC for Block1 + Block2
[12:05:42][I][crc:035]:   calculated: 0x3310, read: 0x92D6  !!!
[12:05:42][D][mbus:056]: Frame: 32443728347971233A168D208BA2A2B51F90DA26D6D3003A3E1AFBAF2B69D5D768B2921C8BBA984B6479423CE27BD81D060DDB (51) [without CRC]
[12:05:42][D][wmbus:195]: Meter ID [0x23717934] RSSI: -96 dBm LQI: 155 Frame: C1 B not found in configuration T: 32443728347971233A168D208BA2A2B51F90DA26D6D3003A3E1AFBAF2B69D5D768B2921C8BBA984B6479423CE27BD81D060DDB (51)
SzczepanLeon commented 8 months ago

Please add sensor configuration with popper key.

sensor:
  - platform: wmbus
    meter_id: 0x23717934
    type: evo868
    key: "key_key_key"
    total_water_m3:
      name: "test meter"
evilmumi commented 8 months ago

here we go

[12:24:19][C][wmbus:441]:     ID: 594639156 [0x23717934]
[12:24:19][C][wmbus:442]:     Type: evo868
[12:24:19][C][wmbus:443]:     Mode: T1
[12:24:19][C][wmbus:444]:     Key: '05234353253523342434234432(FAKE)F3B3'
[12:24:19][C][wmbus:446]:     Sensor '0x23717934 test meter'
[12:24:19][C][wmbus:446]:       Device Class: 'water'
[12:24:19][C][wmbus:446]:       State Class: 'total_increasing'
[12:24:19][C][wmbus:446]:       Unit of Measurement: 'm³'
[12:24:19][C][wmbus:446]:       Accuracy Decimals: 3
[12:24:19][C][wmbus:446]:       Icon: 'mdi:water'

after that i got no information about any meter in log. only this stuff

[12:27:28][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy
[12:27:28][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[12:27:28][V][json:058]: Size after shrink 84 bytes
[12:27:28][W][component:214]: Component debug took a long time for an operation (0.10 s).
[12:27:28][W][component:215]: Components should block for at most 20-30ms.
[12:27:33][V][sensor:043]: 'Heap Free': Received new state 17160.000000
[12:27:33][D][sensor:093]: 'Heap Free': Sending state 17160.00000 B with 0 decimals of accuracy
[12:27:33][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[12:27:33][V][json:058]: Size after shrink 76 bytes
[12:27:33][V][sensor:043]: 'Heap Max Block': Received new state 10376.000000
[12:27:33][D][sensor:093]: 'Heap Max Block': Sending state 10376.00000 B with 0 decimals of accuracy
[12:27:33][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[12:27:33][V][json:058]: Size after shrink 80 bytes
[12:27:33][V][sensor:043]: 'Heap Fragmentation': Received new state 16.000000
[12:27:33][D][sensor:093]: 'Heap Fragmentation': Sending state 16.00000 % with 1 decimals of accuracy
[12:27:33][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[12:27:33][V][json:058]: Size after shrink 84 bytes
[12:27:33][V][sensor:043]: 'Application Loop Time': Received new state 117.000000
[12:27:33][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy
[12:27:33][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[12:27:33][V][json:058]: Size after shrink 84 bytes
[12:27:33][W][component:214]: Component debug took a long time for an operation (0.10 s).
[12:27:33][W][component:215]: Components should block for at most 20-30ms.

is the id wrong inteprated? hex / binary?

edit: some found now:

[12:32:36][D][rxLoop:159]: Have 53 bytes from CC1101 Rx [12:32:36][D][mbus:022]: Processing C1 B frame [12:32:36][V][mbus:026]: Frame: 3444372C3479F1233A168D2470D14B3F2121BCE837990E7DEB658FFFDCF58F1C98D1B77E004E6EE145DD1C3FAC3EA2386E6A4C90D0 (53) [with CRC] [12:32:36][V][mbus:159]: Validating CRC for Block1 + Block2 [12:32:36][I][crc:035]: calculated: 0x3B0C, read: 0x90D0 !!! [12:32:36][D][mbus:056]: Frame: 3244372C3479F1233A168D2470D14B3F2121BCE837990E7DEB658FFFDCF58F1C98D1B77E004E6EE145DD1C3FAC3EA2386E6A4C (51) [without CRC] [12:32:36][D][wmbus:195]: Meter ID [0x23F17934] RSSI: -97 dBm LQI: 168 Frame: C1 B not found in configuration T: 3244372C3479F1233A168D2470D14B3F2121BCE837990E7DEB658FFFDCF58F1C98D1B77E004E6EE145DD1C3FAC3EA2386E6A4C (51)

what id setting is correct? meter_id: 0x169E82E or meter_id: 0x23717934

why does log show [0x23F17934]

SzczepanLeon commented 8 months ago

Please also set mode.

sensor:
  - platform: wmbus
    meter_id: 0x23717934
    mode: T1C1
    type: evo868
    key: "key_key_key"
    total_water_m3:
      name: "test meter"
evilmumi commented 8 months ago

no useful output in log since 8 minutes - only repeating stuff: 12:43:43][V][sensor:043]: 'Application Loop Time': Received new state 117.000000 [12:43:43][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy [12:43:43][V][json:038]: Attempting to allocate 512 bytes for JSON serialization [12:43:43][V][json:058]: Size after shrink 84 bytes [12:43:43][W][component:214]: Component debug took a long time for an operation (0.10 s). [12:43:43][W][component:215]: Components should block for at most 20-30ms. [12:43:48][V][sensor:043]: 'Heap Free': Received new state 16992.000000 [12:43:48][D][sensor:093]: 'Heap Free': Sending state 16992.00000 B with 0 decimals of accuracy [12:43:48][V][json:038]: Attempting to allocate 512 bytes for JSON serialization [12:43:48][V][json:058]: Size after shrink 76 bytes [12:43:48][V][sensor:043]: 'Heap Max Block': Received new state 10360.000000 [12:43:48][D][sensor:093]: 'Heap Max Block': Sending state 10360.00000 B with 0 decimals of accuracy [12:43:48][V][json:038]: Attempting to allocate 512 bytes for JSON serialization [12:43:48][V][json:058]: Size after shrink 80 bytes [12:43:48][V][sensor:043]: 'Heap Fragmentation': Received new state 15.000000 [12:43:48][D][sensor:093]: 'Heap Fragmentation': Sending state 15.00000 % with 1 decimals of accuracy [12:43:48][V][json:038]: Attempting to allocate 512 bytes for JSON serialization [12:43:48][V][json:058]: Size after shrink 84 bytes [12:43:48][V][sensor:043]: 'Application Loop Time': Received new state 117.000000 [12:43:48][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy [12:43:48][V][json:038]: Attempting to allocate 512 bytes for JSON serialization [12:43:48][V][json:058]: Size after shrink 84 bytes [12:43:48][W][component:214]: Component debug took a long time for an operation (0.10 s). [12:43:48][W][component:215]: Components should block for at most 20-30ms.

evilmumi commented 8 months ago

postioned it nearer to the watermeter:


[12:48:25][D][mbus:022]: Processing C1 B frame
[12:48:25][V][mbus:026]: Frame: 3444372C347971233A168D202AD16C3F2121019F00A219D2AF992B490B4ECF84A1DEA0DFA04E456E6F7864A9BF00BFA9051E86FAC0 (53) [with CRC]
[12:48:25][V][mbus:159]: Validating CRC for Block1 + Block2
[12:48:25][I][crc:035]:   calculated: 0xA936, read: 0xFAC0  !!!
[12:48:25][D][mbus:056]: Frame: 3244372C347971233A168D202AD16C3F2121019F00A219D2AF992B490B4ECF84A1DEA0DFA04E456E6F7864A9BF00BFA9051E86 (51) [without CRC]
[12:48:25][D][wmbus:195]: Meter ID [0x23717934] RSSI: -87 dBm LQI: 136 Frame: C1 B not found in configuration T: 3244372C347971233A168D202AD16C3F2121019F00A219D2AF992B490B4ECF84A1DEA0DFA04E456E6F7864A9BF00BFA9051E86 (51)`

`[12:48:57][D][rxLoop:159]: Have 74 bytes from CC1101 Rx
[12:48:57][D][mbus:022]: Processing C1 B frame
[12:48:57][V][mbus:026]: Frame: 4944372C347971233A168D202CD36C3F3F4D2904B1502C07371EC0A83FE653CBAD684C3CD82959BECD869A709FDBE74597696BB8E688686FF4101D10DB4B5CA93D4944372C347971233A (74) [with CRC]
[12:48:57][V][mbus:159]: Validating CRC for Block1 + Block2
[12:48:57][I][crc:035]:   calculated: 0x5C6B, read: 0x233A  !!!
[12:48:57][D][mbus:056]: Frame: 4744372C347971233A168D202CD36C3F3F4D2904B1502C07371EC0A83FE653CBAD684C3CD82959BECD869A709FDBE74597696BB8E688686FF4101D10DB4B5CA93D4944372C347971 (72) [without CRC]
[12:48:58][D][wmbus:195]: Meter ID [0x23717934] RSSI: -86 dBm LQI: 135 Frame: C1 B not found in configuration T: 4744372C347971233A168D202CD36C3F3F4D2904B1502C07371EC0A83FE653CBAD684C3CD82959BECD869A709FDBE74597696BB8E688686FF4101D10DB4B5CA93D4944372C347971 (72)
[12:48:58][W][component:214]: Component wmbus took a long time for an operation (0.07 s).`

`[12:49:14][D][rxLoop:159]: Have 53 bytes from CC1101 Rx
[12:49:14][D][mbus:022]: Processing C1 B frame
[12:49:14][V][mbus:026]: Frame: 3444372C347971233A168D202DE0E056BA9C3AC46950D41803CA5E0C39D6E95041C43EC14B633D4FC899D793AABEE7945F624E7002 (53) [with CRC]
[12:49:14][V][mbus:159]: Validating CRC for Block1 + Block2
[12:49:14][I][crc:035]:   calculated: 0x88BA, read: 0x7002  !!!
[12:49:14][D][mbus:056]: Frame: 3244372C347971233A168D202DE0E056BA9C3AC46950D41803CA5E0C39D6E95041C43EC14B633D4FC899D793AABEE7945F624E (51) [without CRC]
[12:49:14][D][wmbus:195]: Meter ID [0x23717934] RSSI: -86 dBm LQI: 132 Frame: C1 B not found in configuration T: 3244372C347971233A168D202DE0E056BA9C3AC46950D41803CA5E0C39D6E95041C43EC14B633D4FC899D793AABEE7945F624E (51)`
`[12:49:30][D][rxLoop:159]: Have 53 bytes from CC1101 Rx
[12:49:30][D][mbus:022]: Processing C1 B frame
[12:49:30][V][mbus:026]: Frame: 3444372C347971233A168D202EE16C3F21EEEE736FE442E28D8347A020E1B9AE475FDE18CECFD9EFFBC76E35852977E7F977C1E784 (53) [with CRC]
[12:49:30][V][mbus:159]: Validating CRC for Block1 + Block2
[12:49:30][I][crc:035]:   calculated: 0xDEB2, read: 0xE784  !!!
[12:49:30][D][mbus:056]: Frame: 3244372C347971233A168D202EE16C3F21EEEE736FE442E28D8347A020E1B9AE475FDE18CECFD9EFFBC76E35852977E7F977C1 (51) [without CRC]
[12:49:30][D][wmbus:195]: Meter ID [0x23717934] RSSI: -88 dBm LQI: 130 Frame: C1 B not found in configuration T: 3244372C347971233A168D202EE16C3F21EEEE736FE442E28D8347A020E1B9AE475FDE18CECFD9EFFBC76E35852977E7F977C1 (51)`
`[12:49:46][D][rxLoop:159]: Have 53 bytes from CC1101 Rx
[12:49:46][D][mbus:022]: Processing C1 B frame
[12:49:46][V][mbus:026]: Frame: 3444372C347971233A168D202FE26C3F3F2121EE17F45B3326F5DA5AF2E1D72D0CF1F191D0D3A3F63850AD905BBA238278FDBA0563 (53) [with CRC]
[12:49:46][V][mbus:159]: Validating CRC for Block1 + Block2
[12:49:46][I][crc:035]:   calculated: 0xF875, read: 0x0563  !!!
[12:49:46][D][mbus:056]: Frame: 3244372C347971233A168D202FE26C3F3F2121EE17F45B3326F5DA5AF2E1D72D0CF1F191D0D3A3F63850AD905BBA238278FDBA (51) [without CRC]
[12:49:46][D][wmbus:195]: Meter ID [0x23717934] RSSI: -87 dBm LQI: 141 Frame: C1 B not found in configuration T: 3244372C347971233A168D202FE26C3F3F2121EE17F45B3326F5DA5AF2E1D72D0CF1F191D0D3A3F63850AD905BBA238278FDBA (51)```
SzczepanLeon commented 8 months ago

With sensor section?

evilmumi commented 8 months ago

with

---------------------------------------------------

SENSORS

---------------------------------------------------

sensor:

evilmumi commented 8 months ago

[13:06:43][D][rxLoop:159]: Have 53 bytes from CC1101 Rx [13:06:43][D][mbus:022]: Processing C1 B frame [13:06:43][V][mbus:026]: Frame: 3444372C347971233A168D206FF26DBF235391EBC6C6B708F5B941EAFFB022E23097FCD8D875A086D7B18E954EAB566ADF4B2112EF (53) [with CRC] [13:06:43][V][mbus:159]: Validating CRC for Block1 + Block2 [13:06:43][I][crc:035]: calculated: 0x2748, read: 0x12EF !!! [13:06:43][D][mbus:056]: Frame: 3244372C347971233A168D206FF26DBF235391EBC6C6B708F5B941EAFFB022E23097FCD8D875A086D7B18E954EAB566ADF4B21 (51) [without CRC] [13:06:43][D][wmbus:195]: Meter ID [0x23717934] RSSI: -87 dBm LQI: 139 Frame: C1 B not found in configuration T: 3244372C347971233A168D206FF26DBF235391EBC6C6B708F5B941EAFFB022E23097FCD8D875A086D7B18E954EAB566ADF4B21 (51)

[13:07:45][D][rxLoop:159]: Have 53 bytes from CC1101 Rx [13:07:45][D][mbus:022]: Processing C1 B frame [13:07:45][V][mbus:026]: Frame: 3444372C347971233A168D2073026E3F217DA8A845C21B9F88AA5244D503B12B625855FCAC21EA0E7C5309347C9556BA7CF57CE68B (53) [with CRC] [13:07:45][V][mbus:159]: Validating CRC for Block1 + Block2 [13:07:45][I][crc:035]: calculated: 0x9B42, read: 0xE68B !!! [13:07:45][D][mbus:056]: Frame: 3244372C347971233A168D2073026E3F217DA8A845C21B9F88AA5244D503B12B625855FCAC21EA0E7C5309347C9556BA7CF57C (51) [without CRC] [13:07:45][D][wmbus:195]: Meter ID [0x23717934] RSSI: -86 dBm LQI: 137 Frame: C1 B not found in configuration T: 3244372C347971233A168D2073026E3F217DA8A845C21B9F88AA5244D503B12B625855FCAC21EA0E7C5309347C9556BA7CF57C (51)

SzczepanLeon commented 8 months ago

Please remove " from Meter ID.

evilmumi commented 8 months ago

`

all watermeters wmid: "0", your watermeter: wmid: !secret watermeterId

wmid: "0"

wmid: 23717934

---------------------------------------------------

SENSORS

---------------------------------------------------

sensor:

evilmumi commented 8 months ago

Must be string, got <class 'esphome.helpers.EInt'>. did you forget putting quotes around the value?. wmid: 23717934

SzczepanLeon commented 8 months ago

This is HEX so 0x at the beginning should be.

evilmumi commented 8 months ago

changed to wmid: "0x23717934"

evilmumi commented 8 months ago 
[13:17:53][D][rxLoop:159]: Have 53 bytes from CC1101 Rx
[13:17:53][D][mbus:022]: Processing C1 B frame
[13:17:53][V][mbus:026]: Frame: 3444372C347971233A168D209AA26E6E3F213B42131EBD78EC7E29118E58815E0754503644F3FC5876E6D8DD15AA90CB6BCA482A5A (53) [with CRC]
[13:17:53][V][mbus:159]: Validating CRC for Block1 + Block2
[13:17:53][I][crc:035]:   calculated: 0x4EE9, read: 0x2A5A  !!!
[13:17:53][D][mbus:056]: Frame: 3244372C347971233A168D209AA26E6E3F213B42131EBD78EC7E29118E58815E0754503644F3FC5876E6D8DD15AA90CB6BCA48 (51) [without CRC]
[13:17:53][I][wmbus:090]: Using driver 'evo868' for ID [0x23717934] RSSI: -87 dBm LQI: 133 Mode: X T: 3244372C347971233A168D209AA26E6E3F213B42131EBD78EC7E29118E58815E0754503644F3FC5876E6D8DD15AA90CB6BCA48 (51)
[13:17:53][V][utils:109]: (ELL)  CI: 8D  offset: 17
[13:17:53][V][utils:110]: (ELL)  IV: 372C347971233A1620A26E6E3F000000
[13:17:53][V][utils:115]: (ELL) KEY: key(16)
[13:17:53][D][utils:124]: (ELL) AES_CTR decrypting: 213B42131EBD78EC7E29118E58815E0754503644F3FC5876E6D8DD15AA90CB6BCA48 (34)
[13:17:53][D][utils:152]: (ELL) AES_CTR  decrypted: B1DBF085A732476A5825D441372F20E3C8D9D639652BE393437CE21B8F375D17467F (34)
[13:17:53][V][wmbus:302]: Validating CRC for ELL payload
[13:17:53][I][crc:051]:   calculated: 0x2295, read: 0xDBB1  !!!
[13:17:53][E][wmbus:115]: Something was not OK during decrypting telegram for ID [0x23717934] 'evo868' key: 'FAKE'
[13:17:53][E][wmbus:119]: T : 3244372C347971233A168D209AA26E6E3F213B42131EBD78EC7E29118E58815E0754503644F3FC5876E6D8DD15AA90CB6BCA48 (51)
[13:17:53][E][wmbus:120]: T': 3244372C347971233A168D209AA26E6E3FB1DBF085A732476A5825D441372F20E3C8D9D639652BE393437CE21B8F375D17467F (51)
SzczepanLeon commented 8 months ago

It is number.

evilmumi commented 8 months ago 
[13:18:09][W][component:214]: Component wmbus took a long time for an operation (0.14 s).
[13:18:09][W][component:215]: Components should block for at most 20-30ms.
[13:18:13][V][sensor:043]: 'Heap Free': Received new state 17144.000000
[13:18:13][D][sensor:093]: 'Heap Free': Sending state 17144.00000 B with 0 decimals of accuracy
[13:18:13][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:13][V][json:058]: Size after shrink 76 bytes
[13:18:13][V][sensor:043]: 'Heap Max Block': Received new state 11184.000000
[13:18:13][D][sensor:093]: 'Heap Max Block': Sending state 11184.00000 B with 0 decimals of accuracy
[13:18:13][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:13][V][json:058]: Size after shrink 80 bytes
[13:18:13][V][sensor:043]: 'Heap Fragmentation': Received new state 9.000000
[13:18:13][D][sensor:093]: 'Heap Fragmentation': Sending state 9.00000 % with 1 decimals of accuracy
[13:18:13][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:13][V][json:058]: Size after shrink 80 bytes
[13:18:13][V][sensor:043]: 'Application Loop Time': Received new state 163.000000
[13:18:13][D][sensor:093]: 'Application Loop Time': Sending state 163.00000 ms with 0 decimals of accuracy
[13:18:13][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:13][V][json:058]: Size after shrink 84 bytes
[13:18:13][W][component:214]: Component debug took a long time for an operation (0.10 s).
[13:18:13][W][component:215]: Components should block for at most 20-30ms.
[13:18:18][V][sensor:043]: 'Heap Free': Received new state 17144.000000
[13:18:18][D][sensor:093]: 'Heap Free': Sending state 17144.00000 B with 0 decimals of accuracy
[13:18:18][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:18][V][json:058]: Size after shrink 76 bytes
[13:18:18][V][sensor:043]: 'Heap Max Block': Received new state 11184.000000
[13:18:18][D][sensor:093]: 'Heap Max Block': Sending state 11184.00000 B with 0 decimals of accuracy
[13:18:18][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:18][V][json:058]: Size after shrink 80 bytes
[13:18:18][V][sensor:043]: 'Heap Fragmentation': Received new state 9.000000
[13:18:18][D][sensor:093]: 'Heap Fragmentation': Sending state 9.00000 % with 1 decimals of accuracy
[13:18:18][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:18][V][json:058]: Size after shrink 80 bytes
[13:18:18][V][sensor:043]: 'Application Loop Time': Received new state 118.000000
[13:18:18][D][sensor:093]: 'Application Loop Time': Sending state 118.00000 ms with 0 decimals of accuracy
[13:18:18][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:18][V][json:058]: Size after shrink 84 bytes
[13:18:18][W][component:214]: Component debug took a long time for an operation (0.10 s).
[13:18:18][W][component:215]: Components should block for at most 20-30ms.
[13:18:20][D][esp8266.preferences:238]: Saving preferences to flash...
[13:18:23][V][sensor:043]: 'Heap Free': Received new state 17144.000000
[13:18:23][D][sensor:093]: 'Heap Free': Sending state 17144.00000 B with 0 decimals of accuracy
[13:18:23][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:23][V][json:058]: Size after shrink 76 bytes
[13:18:23][V][sensor:043]: 'Heap Max Block': Received new state 11184.000000
[13:18:23][D][sensor:093]: 'Heap Max Block': Sending state 11184.00000 B with 0 decimals of accuracy
[13:18:23][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:23][V][json:058]: Size after shrink 80 bytes
[13:18:23][V][sensor:043]: 'Heap Fragmentation': Received new state 9.000000
[13:18:23][D][sensor:093]: 'Heap Fragmentation': Sending state 9.00000 % with 1 decimals of accuracy
[13:18:23][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:23][V][json:058]: Size after shrink 80 bytes
[13:18:23][V][sensor:043]: 'Application Loop Time': Received new state 117.000000
[13:18:23][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy
[13:18:23][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:23][V][json:058]: Size after shrink 84 bytes
[13:18:23][W][component:214]: Component debug took a long time for an operation (0.10 s).
[13:18:23][W][component:215]: Components should block for at most 20-30ms.
[13:18:24][V][sensor:043]: 'Boot counter': Received new state 22.000000
[13:18:24][D][sensor:093]: 'Boot counter': Sending state 22.00000  with 0 decimals of accuracy
[13:18:24][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:24][V][json:058]: Size after shrink 72 bytes
[13:18:24][D][rxLoop:159]: Have 74 bytes from CC1101 Rx
[13:18:24][D][mbus:022]: Processing C1 B frame
[13:18:24][V][mbus:026]: Frame: 4944372C347971233A168D209CB06E3F21E55959232A9B1FB0BFAF2AFC406CC38FF07603BF841B9E0C26356DB8EA43A453553D0F5DE98B3A580B2ACF2DE864046E3D4944372C34797123 (74) [with CRC]
[13:18:24][V][mbus:159]: Validating CRC for Block1 + Block2
[13:18:24][I][crc:035]:   calculated: 0x82A7, read: 0x7123  !!!
[13:18:24][D][mbus:056]: Frame: 4744372C347971233A168D209CB06E3F21E55959232A9B1FB0BFAF2AFC406CC38FF07603BF841B9E0C26356DB8EA43A453553D0F5DE98B3A580B2ACF2DE864046E3D4944372C3479 (72) [without CRC]
[13:18:24][I][wmbus:090]: Using driver 'evo868' for ID [0x23717934] RSSI: -86 dBm LQI: 139 Mode: X T: 4744372C347971233A168D209CB06E3F21E55959232A9B1FB0BFAF2AFC406CC38FF07603BF841B9E0C26356DB8EA43A453553D0F5DE98B3A580B2ACF2DE864046E3D4944372C3479 (72)
[13:18:24][V][utils:109]: (ELL)  CI: 8D  offset: 17
[13:18:24][V][utils:110]: (ELL)  IV: 372C347971233A1620B06E3F21000000
[13:18:24][V][utils:115]: (ELL) KEY: KEYEKYEKEYK(16)
[13:18:24][D][utils:124]: (ELL) AES_CTR decrypting: E55959232A9B1FB0BFAF2AFC406CC38FF07603BF841B9E0C26356DB8EA43A453553D0F5DE98B3A580B2ACF2DE864046E3D4944372C3479 (55)
[13:18:24][D][utils:152]: (ELL) AES_CTR  decrypted: 5E9902456F02D4610013561392A80E112FD6837018E4408F6AC71740A4127744B10B0FB852255D219A4F52D605AC6ABAE74EB4C9BBD559 (55)
[13:18:24][V][wmbus:302]: Validating CRC for ELL payload
[13:18:24][I][crc:051]:   calculated: 0x8120, read: 0x995E  !!!
[13:18:24][E][wmbus:115]: Something was not OK during decrypting telegram for ID [0x23717934] 'evo868' key: 'KEYEKYEKEYK'
[13:18:24][E][wmbus:119]: T : 4744372C347971233A168D209CB06E3F21E55959232A9B1FB0BFAF2AFC406CC38FF07603BF841B9E0C26356DB8EA43A453553D0F5DE98B3A580B2ACF2DE864046E3D4944372C3479 (72)
[13:18:24][E][wmbus:120]: T': 4744372C347971233A168D209CB06E3F215E9902456F02D4610013561392A80E112FD6837018E4408F6AC71740A4127744B10B0FB852255D219A4F52D605AC6ABAE74EB4C9BBD559 (72)
[13:18:25][W][component:214]: Component wmbus took a long time for an operation (0.17 s).
[13:18:25][W][component:215]: Components should block for at most 20-30ms.
[13:18:28][V][sensor:043]: 'Heap Free': Received new state 17088.000000
[13:18:28][D][sensor:093]: 'Heap Free': Sending state 17088.00000 B with 0 decimals of accuracy
[13:18:28][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:28][V][json:058]: Size after shrink 76 bytes
[13:18:28][V][sensor:043]: 'Heap Max Block': Received new state 11184.000000
[13:18:28][D][sensor:093]: 'Heap Max Block': Sending state 11184.00000 B with 0 decimals of accuracy
[13:18:28][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:28][V][json:058]: Size after shrink 80 bytes
[13:18:28][V][sensor:043]: 'Heap Fragmentation': Received new state 9.000000
[13:18:28][D][sensor:093]: 'Heap Fragmentation': Sending state 9.00000 % with 1 decimals of accuracy
[13:18:28][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:28][V][json:058]: Size after shrink 80 bytes
[13:18:28][V][sensor:043]: 'Application Loop Time': Received new state 187.000000
[13:18:28][D][sensor:093]: 'Application Loop Time': Sending state 187.00000 ms with 0 decimals of accuracy
[13:18:28][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:28][V][json:058]: Size after shrink 84 bytes
[13:18:28][W][component:214]: Component debug took a long time for an operation (0.10 s).
[13:18:28][W][component:215]: Components should block for at most 20-30ms.
[13:18:33][V][sensor:043]: 'Heap Free': Received new state 17168.000000
[13:18:33][D][sensor:093]: 'Heap Free': Sending state 17168.00000 B with 0 decimals of accuracy
[13:18:33][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:33][V][json:058]: Size after shrink 76 bytes
[13:18:33][V][sensor:043]: 'Heap Max Block': Received new state 11184.000000
[13:18:33][D][sensor:093]: 'Heap Max Block': Sending state 11184.00000 B with 0 decimals of accuracy
[13:18:33][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:33][V][json:058]: Size after shrink 80 bytes
[13:18:33][V][sensor:043]: 'Heap Fragmentation': Received new state 10.000000
[13:18:33][D][sensor:093]: 'Heap Fragmentation': Sending state 10.00000 % with 1 decimals of accuracy
[13:18:33][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:33][V][json:058]: Size after shrink 84 bytes
[13:18:33][V][sensor:043]: 'Application Loop Time': Received new state 117.000000
[13:18:33][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy
[13:18:33][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:33][V][json:058]: Size after shrink 84 bytes
[13:18:33][W][component:214]: Component debug took a long time for an operation (0.10 s).
[13:18:33][W][component:215]: Components should block for at most 20-30ms.
[13:18:38][V][sensor:043]: 'Heap Free': Received new state 17168.000000
[13:18:38][D][sensor:093]: 'Heap Free': Sending state 17168.00000 B with 0 decimals of accuracy
[13:18:38][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:38][V][json:058]: Size after shrink 76 bytes
[13:18:38][V][sensor:043]: 'Heap Max Block': Received new state 11184.000000
[13:18:38][D][sensor:093]: 'Heap Max Block': Sending state 11184.00000 B with 0 decimals of accuracy
[13:18:38][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:38][V][json:058]: Size after shrink 80 bytes
[13:18:38][V][sensor:043]: 'Heap Fragmentation': Received new state 10.000000
[13:18:38][D][sensor:093]: 'Heap Fragmentation': Sending state 10.00000 % with 1 decimals of accuracy
[13:18:38][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:38][V][json:058]: Size after shrink 84 bytes
[13:18:38][V][sensor:043]: 'Application Loop Time': Received new state 117.000000
[13:18:38][D][sensor:093]: 'Application Loop Time': Sending state 117.00000 ms with 0 decimals of accuracy
[13:18:38][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[13:18:38][V][json:058]: Size after shrink 84 bytes
[13:18:38][W][component:214]: Component debug took a long time for an operation (0.10 s).
SzczepanLeon commented 8 months ago

As you can see below frame C1 B is received, but CRC check is failed (I don't know why - other frames that I have are OK): obraz

Seems that received frame is corrupted, so next step decrypting is also failing: obraz

But why frame is corrupted (or seems to be corrupted) I don't know.

evilmumi commented 8 months ago

my other solution from https://github.com/pthalin/esp32-multical21 is still working - maybe you can grab there some information in code?

SzczepanLeon commented 8 months ago

Can you provide me logs from that other solution?

evilmumi commented 8 months ago

atm i dont know how to get logs - will give it a try

SzczepanLeon commented 8 months ago

As I see there is output to serial, just connect to serial port and collect output.

evilmumi commented 8 months ago

yeah - but i only got `ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8

and it is not connecting to wlan

SzczepanLeon commented 8 months ago

Can you decrypt this with propper key: https://wmbusmeters.org/analyze/4944372C347971233A168D209CB06E3F21E55959232A9B1FB0BFAF2AFC406CC38FF07603BF841B9E0C26356DB8EA43A453553D0F5DE98B3A580B2ACF2DE864046E3D4944372C34797123 ??

evilmumi commented 8 months ago

i found some old stuff: image

SzczepanLeon commented 8 months ago

Great - do you have that in txt format?

evilmumi commented 8 months ago

found old here 

StateOperating:
Payload: 44372c347971233a168d20b260262421855f9737ba8cab271cac23ab626a30f68d1907e                                                  ec34dcb5831dd91766de5fde8e2d55cbe
Data: 6eed790509059a00000000f57803002105065000066000e12b11140000838d030010
calc_crc: 0xed6e
read_crc: 0xed6e
CRC: OK
total: 2029322.2 m▒ - target: 86048.771 m▒ -  6 ▒C - 80 ▒C

StateOperating:
Payload: 44372c347971233a168d20bb82262421366199761da2c0ba71d59e730878273ab495f809203def2520579dd3a8bec879da40a9cd
Data: 6eed790509059a00000000f57803002105065000066000e12b11140000838d030010
calc_crc: 0xed6e
read_crc: 0xed6e
CRC: OK
total: 2029322.2 m▒ - target: 86048.771 m▒ -  6 ▒C - 80 ▒C

StateOperating:
Payload: 44372c347971233a168d201db2702421c794afac403e72f56807d5051aa039e276be0cb3b825381237dfe80b46a2e4c0eb759b71
Data: 4a477905090d5c00000000f57803002105055000056000e12b111400004d8e030010
calc_crc: 0x474a
read_crc: 0x474a
CRC: OK
total: 2029322.2 m▒ - target: 86048.771 m▒ -  5 ▒C - 80 ▒C

StateConnected:
MQTT-SEND: watermeter/0/online True
MQTT-SEND: watermeter/0/ipaddr 192.168.0.181
StateOperating:
Payload: 44372c347971233a168d20311071242196508919b2b811f9c911fb84f7a696c291272a6eaa1a9e39b68df4a26fb84a7138eebc36
Data: 4a477905090d5c00000000f57803002105055000056000e12b111400004d8e030010
calc_crc: 0x474a
read_crc: 0x474a
CRC: OK
total: 2029322.2 m▒ - target: 86048.771 m▒ -  5 ▒C - 80 ▒C
evilmumi commented 8 months ago

Can you decrypt this with propper key: https://wmbusmeters.org/analyze/4944372C347971233A168D209CB06E3F21E55959232A9B1FB0BFAF2AFC406CC38FF07603BF841B9E0C26356DB8EA43A453553D0F5DE98B3A580B2ACF2DE864046E3D4944372C34797123 ??

no failed decryption. Wrong key?

evilmumi commented 8 months ago

from now: 

StateOperating:
Payload: 44372c347971233a168d2030b2793f21430559765f701639ab46f8b02fa7a14a7624a4170ebd7c3298658b383dcf34f98ef301cb
Data: e7947905095875000000007ce203007c0506600006d00001320b1100001de703000f
calc_crc: 0x94e7
read_crc: 0x94e7
CRC: OK
total: 255.773 m▒ - target: 92012.547 m▒ -  6 ▒C - 96 ▒C

only total is correct - rest of values are wrong

SzczepanLeon commented 8 months ago

https://wmbusmeters.org/analyze/4744372c347971233a168d209cB06e3f21e55959232a9B1fB0Bfaf2afc406cc38ff07603Bf841B9e0c26356dB8ea43a453553d0f5de98B3a580B2acf2de864046e3d4944372c3479

https://wmbusmeters.org/analyze/4944372C347971233A168D209CB06E3F21E55959232A9B1FB0BFAF2AFC406CC38FF07603BF841B9E0C26356DB8EA43A453553D0F5DE98B3A580B2ACF2DE864046E3D4944372C34797123

but with key that you have - is it OK?

evilmumi commented 8 months ago

https://wmbusmeters.org/analyze/4744372c347971233a168d209cB06e3f21e55959232a9B1fB0Bfaf2afc406cc38ff07603Bf841B9e0c26356dB8ea43a453553d0f5de98B3a580B2acf2de864046e3d4944372c3479

https://wmbusmeters.org/analyze/4944372C347971233A168D209CB06E3F21E55959232A9B1FB0BFAF2AFC406CC38FF07603BF841B9E0C26356DB8EA43A453553D0F5DE98B3A580B2ACF2DE864046E3D4944372C34797123

but with key that you have - is it OK?

both links failed decryption. Wrong key?

evilmumi commented 8 months ago

one guy told me to change source code of his to get it work with me:

void WMBusFrame::printMeterInfo(uint8_t *data, size_t len) { // init positions for compact frame // int pos_tt = 9; // total consumption, 9, 10, 11, 12 his int pos_tt = 29;

and if(data[2] == 0x79) //compact frame { pos_tt = 29; pos_tg = 13; //pos_ic = 7; pos_ft = 17; pos_at = 18; }

in https://github.com/pthalin/esp32-multical21/blob/master/src/WMBusFrame.cpp

not sure if helpful or nothing do to with encrypting

SzczepanLeon commented 8 months ago

And frame: https://wmbusmeters.org/analyze/3444372c347971233a168d2030b2793f21430559765f701639ab46f8b02fa7a14a7624a4170ebd7c3298658b383dcf34f98ef301cb

is OK, and can be decrypted?

evilmumi commented 8 months ago

now grabbed: 

Payload: 44372c347971233a168d20b9f27b3f2164fa16c9ff63f85cb8b050296dffcb6f858f928afd1daa57a8ea16fbb6d79695f80852c1
Data: e7947905095875000000007ce203007c0506600006d00001320b1100001de703000f
calc_crc: 0x94e7
read_crc: 0x94e7
CRC: OK
total: 255.773 m▒ - target: 92012.547 m▒ -  6 ▒C - 96 ▒C

Payload: 44372c347971233a168d20bd027c3f21352dc34eb25afe9131557e7e9a2a2c0417648a48eef85e90973c5a1806f4c3a2394219be
Data: e7947905095875000000007ce203007c0506600006d00001320b1100001de703000f
calc_crc: 0x94e7
read_crc: 0x94e7
CRC: OK
total: 255.773 m▒ - target: 92012.547 m▒ -  6 ▒C - 96 ▒C
evilmumi commented 8 months ago

And frame: https://wmbusmeters.org/analyze/3444372c347971233a168d2030b2793f21430559765f701639ab46f8b02fa7a14a7624a4170ebd7c3298658b383dcf34f98ef301cb

is OK, and can be decrypted?

Auto driver : flowiq2200 Best driver : unknown 00/00 Using driver : flowiq2200 00/00 000 : 32 length (50 bytes) 001 : 44 dll-c (from meter SND_NR) 002 : 372c dll-mfct (KAW) 004 : 34797123 dll-id (23717934) 008 : 3a dll-version 009 : 16 dll-type (Cold water meter) 010 : 8d ell-ci-field (ELL: Extended Link Layer II (8 Byte)) 011 : 20 ell-cc (slow_resp sync) 012 : 30 ell-acc 013 : b2793f21 sn (AES_CTR) 017 : e794 payload crc (calculated e794 OK) 019 : 79 tpl-ci-field (EN 13757-3 Application Layer with Compact frame (no tplh)) 020 : 0509 format signature (unknown) 022 CC: 5875000000007CE203007C0506600006D00001320B1100001DE703000F compressed and signature unknown

{ "media":"cold water", "meter":"flowiq2200", "name":"", "id":"23717934", "timestamp":"1970-01-01T00:00:00Z" }