No więc właśnie.
Tak czy inaczej posłałem im to z pytaniem, czy przypadkiem to po prostu nie jest nieaktywna nakładka.
Jutro dzwonię do bmeters.
Ale jednocześnie namierzam kogoś, kto być może ma program i moduł usb i po prostu mi to ogarnie za parę PLN.
EDIT:
Cud nad cuda - nagle rano nakładki zaczęły same z siebie dawać normalne czytelne telegramy.
A do Bmeters też dzwoniłem i byli gotowi pomóc i zaprogramować nakładki.
@_Szczepan proszę o pomoc, nie mogę poradzić sobie z problemem.
Mam w mieszkaniu 4 podzielniki ciepła Apator E-ITN 40. Spisałem ich numery z obudowy i dodałem do ESP Home.
- platform: wmbus # C.O. Salon
meter_id: 0x00019913
type: apatoreitn
mode: T1C1
#key: "00000000000000000000000000000000"
add_prefix: false
lqi:
name: "C.O. Salon LQI"
rssi:
name: "C.O. Salon RSSI"
current_hca:
name: "C.O. Salon aktualnie"
previous_hca:
name: "C.O. Salon poprzednio"
temp_room_avg_c:
name: "C.O. Salon Śr. temp."
Ramka, która jest odbierana przez te podzielniki wygląda tak:
11:25:00][I][wmbus:087]: Using driver 'apatoreitn' for ID [0x00019913] RSSI: -61 dBm LQI: 131 Mode: C1 T: 40440106139901000908A00000A10080016B011200A2004E00000000000000000000000000000018001E0007007800100002000201C70000000000273000000000 (65)
[11:25:00][D][sensor:094]: 'C.O. Salon LQI': Sending state 131.00000 with 0 decimals of accuracy
[11:25:00][D][sensor:094]: 'C.O. Salon RSSI': Sending state -61.00000 dBm with 0 decimals of accuracy
[11:25:00][D][sensor:094]: 'C.O. Salon aktualnie': Sending state 4609.00000 with 0 decimals of accuracy
[11:25:00][D][sensor:094]: 'C.O. Salon poprzednio': Sending state 32768.00000 with 0 decimals of accuracy
[11:25:00][D][sensor:094]: 'C.O. Salon Śr. temp.': Sending state 0.00000 °C with 2 decimals of accuracy
[11:25:00][W][component:214]: Component wmbus took a long time for an operation (0.14 s).
[11:25:00][W][component:215]: Components should block for at most 20-30ms.
Na stronie wybiera automatycznie driver bfw240radio.
Wskazania mam takie:
Jak sobie z tym poradzić, żeby wskazywało właściwe odczyty?
Jeżeli odczyty z bfw240radio są poprawne to wystarczy taki driver dodać do komponentu.
Z tego co widzę to nic tam zagmatwanego nie ma - wystarczy parę linijek kodu i jedna kawa.
Widocznie są zaprogramowane na nadawanie w godzinach pracy 
Sprawdzę czy odczyty są ok, aczkolwiek jak widzisz widać tam kilka odczytów, co jest trochę dziwne.
EDIT: Odczyty nie są dobre. Na podzielniku aktualna wartość to 105 natomiast ramka
[15:31:59][I][wmbus:087]: Using driver 'apatoreitn' for ID [0x00019915] RSSI: -77 dBm LQI: 150 Mode: C1 T: 40440106159901000908A00000A10088019501200023002600000000000000000000000000000006002600070049000E00000069008A0000000000273000000000 (65)
[15:31:59][D][sensor:094]: 'C.O. Sypialnia LQI': Sending state 150.00000 with 0 decimals of accuracy
[15:31:59][D][sensor:094]: 'C.O. Sypialnia RSSI': Sending state -77.00000 dBm with 0 decimals of accuracy
[15:31:59][D][sensor:094]: 'C.O. Sypialnia aktualnie': Sending state 8193.00000 with 0 decimals of accuracy
[15:31:59][D][sensor:094]: 'C.O. Sypialnia poprzednio': Sending state 34816.00000 with 0 decimals of accuracy
[15:31:59][D][sensor:094]: 'C.O. Sypialnia Śr. temp.': Sending state 0.00000 °C with 2 decimals of accuracy
Sprawdź na wmbusmeters czy nie ma zrobionego już takiego ticketa, jak by nie było to najwygodniej dodać nowego z prośba o update drivera do tego apatora.
Pozbieraj więcej telegramów. Bardzo szybki strzał wskazywał by że odczyt jest w polach zaznaczonych poniżej:
A przynajmniej to wskazuje na 105 (bez żadnych udziwnień).
Skoro masz więcej tych podzielników to najlepiej by było abyś wyzbierał telegramy z wszystkich (razem z wskazaniami) aby upewnić się że pomiary są rzeczywiście w tych miejscach co strzeliłem.
Poniżej wartości podzielników oraz dane z każdego
Salon:
Odczyt z licznika: 303
Numer licznika: 00019913
40440106139901000908A00000A10081016B013F00A2004E00000000000000000000000000000018001E0007007800100002005E038E00000000005A600C000001
40440106139901000908A00000A10081016B013F00A2004E00000000000000000000000000000018001E0007007800100002002F01C700000000002D3006000000
40440106139901000908A00000A10081016B013F00A2004E00000000000000000000000000000018001E0007007800100002002F01C700000000002D3006000000
Wiktoria:
Odczyt z licznika: 192
Numer licznika: 00019914
40440106149901000908A00000A100B201AF01150064004700000000000000000000000000000021004E006700930015000000C0007E01000000002D3006000000
40440106149901000908A00000A100B201AF01150064004700000000000000000000000000000021004E006700930015000000C0007E01000000002D3006000000
40440106149901000908A00000A100B201AF01150064004700000000000000000000000000000021004E006700930015000000C0007E01000000002D3006000000
Sypialnia:
Odczyt z licznika: 109
Numer licznika: 00019915
40440106159901000908A00000A1009C019501240023002600000000000000000000000000000006002600070049000E0000006D008A00000000002D3006000000
40440106159901000908A00000A1009C019501240023002600000000000000000000000000000006002600070049000E0000006D008A00000000002D3006000000
40440106159901000908A00000A1009C019501240023002600000000000000000000000000000006002600070049000E0000006D008A00000000002D3006000000
Kuchnia:
Odczyt z licznika: 0
Numer licznika: 00019916
40440106169901000908A00000A1000000000000000000000001000000000000000000000000000000010000000000000000000000000000000300B4C018000002
40440106169901000908A00000A10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002D3006000000
40440106169901000908A00000A1000000000000000000000000000000000000000000000000000000010000000000000000000000000000000300B4C018000002
Mam nadzieję, że coś pomoże i w końcu będe mógł odczytywać w HA.
Pomoże - idealnie widac gdzie są dane.
Cos naskrobię w driverze i będziesz mogl testować. Jedynie poerwszy telegram dla 00019913 jest jakis dziwny - nie wychodzi mi te 303 
Cześć! Mam problem i nie jestem pewny w czym rzecz. Wygląda to tak, jakby CC1101 niczego nie odbierał, więc może to problem z modułem (wiem, że to loteria z nimi…)? Zgodnie ze wcześniejszymi wskazówkami z tematu zakomentowałem na razie sensory i dałem log_unknown: True
Mój YAML:
esphome:
name: esphome-web-34de80
friendly_name: WMBus-ESP32
esp32:
board: esp32dev
framework:
type: arduino
# Enable logging
logger:
level: VERY_VERBOSE
# Enable Home Assistant API
api:
encryption:
key: "xxx"
ota:
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Esphome-Web-34De80"
password: "xxx"
captive_portal:
time:
- platform: sntp
id: time_sntp
external_components:
- source: github://SzczepanLeon/esphome-components@main
components: [ wmbus ]
wmbus:
mosi_pin: GPIO23
miso_pin: GPIO19
clk_pin: GPIO18
cs_pin: GPIO5
gdo0_pin: GPIO22
gdo2_pin: GPIO21
log_unknown: True
# led_pin: GPIO0
# led_blink_time: "1s"
# clients:
# - name: "wmbusmeters"
# ip_address: "10.0.0.1"
# port: 7227
#sensor:
# - platform: wmbus
# meter_id: 0x14057620
# type: bmeters
# key: "00000000000000000000000000000000"
# lqi:
# name: "Zimna woda LQI"
# total_water_m3:
# name: "Zimna woda"
#
# - platform: wmbus
# meter_id: 0x14054972
# type: bmeters
# key: "00000000000000000000000000000000"
# lqi:
# name: "Ciepła woda LQI"
# total_water_m3:
# name: "Ciepła woda"
# filters:
# - offset: 325.0
#
# - platform: wmbus
# meter_id: 0x02270962
# type: hydrocalm3
# key: "00000000000000000000000000000000"
# lqi:
# name: "Ogrzewanie LQI"
# total_water_m3:
# name: "Ogrzewanie_m3"
# total_heating_kwh:
# name: "Ogrzewanie_kWh"
Logi:
[18:55:37][C][wifi:573]: WiFi:
[18:55:37][C][wifi:405]: Local MAC: 94:3C:C6:34:DE:80
[18:55:37][C][wifi:410]: SSID: [redacted]
[18:55:37][C][wifi:411]: IP Address: 192.168.1.116
[18:55:37][C][wifi:413]: BSSID: [redacted]
[18:55:37][C][wifi:414]: Hostname: 'esphome-web-34de80'
[18:55:37][C][wifi:416]: Signal strength: -67 dB ▂▄▆█
[18:55:37][V][wifi:418]: Priority: 0.0
[18:55:37][C][wifi:420]: Channel: 13
[18:55:37][C][wifi:421]: Subnet: 255.255.255.0
[18:55:37][C][wifi:422]: Gateway: 192.168.1.1
[18:55:37][C][wifi:423]: DNS1: 192.168.1.1
[18:55:37][C][wifi:424]: DNS2: 0.0.0.0
[18:55:37][C][logger:443]: Logger:
[18:55:37][C][logger:444]: Level: VERY_VERBOSE
[18:55:37][C][logger:445]: Log Baud Rate: 115200
[18:55:37][C][logger:447]: Hardware UART: UART0
[18:55:37][C][captive_portal:088]: Captive Portal:
[18:55:37][C][sntp:053]: SNTP Time:
[18:55:37][C][sntp:054]: Server 1: '0.pool.ntp.org'
[18:55:37][C][sntp:055]: Server 2: '1.pool.ntp.org'
[18:55:37][C][sntp:056]: Server 3: '2.pool.ntp.org'
[18:55:37][C][sntp:057]: Timezone: 'CET-1CEST,M3.5.0,M10.5.0/3'
[18:55:37][C][mdns:115]: mDNS:
[18:55:37][C][mdns:116]: Hostname: esphome-web-34de80
[18:55:37][V][mdns:117]: Services:
[18:55:37][V][mdns:119]: - _esphomelib, _tcp, 6053
[18:55:37][V][mdns:121]: TXT: friendly_name = WMBus-ESP32
[18:55:37][V][mdns:121]: TXT: version = 2023.12.3
[18:55:37][V][mdns:121]: TXT: mac = 943cc634de80
[18:55:37][V][mdns:121]: TXT: platform = ESP32
[18:55:37][V][mdns:121]: TXT: board = esp32dev
[18:55:37][V][mdns:121]: TXT: network = wifi
[18:55:37][V][mdns:121]: TXT: api_encryption = Noise_NNpsk0_25519_ChaChaPoly_SHA256
[18:55:37][C][ota:097]: Over-The-Air Updates:
[18:55:37][C][ota:098]: Address: esphome-web-34de80.local:3232
[18:55:37][C][api:139]: API Server:
[18:55:37][C][api:140]: Address: esphome-web-34de80.local:6053
[18:55:37][C][api:142]: Using noise encryption: YES
[18:55:37][C][wmbus:416]: wM-Bus v2.4.11:
[18:55:37][C][wmbus:433]: CC1101 frequency: 868.950 MHz
[18:55:37][C][wmbus:434]: CC1101 SPI bus:
[18:55:37][C][wmbus:435]: MOSI Pin: GPIO23
[18:55:37][C][wmbus:436]: MISO Pin: GPIO19
[18:55:37][C][wmbus:437]: CLK Pin: GPIO18
[18:55:37][C][wmbus:438]: CS Pin: GPIO5
[18:55:37][C][wmbus:439]: GDO0 Pin: GPIO22
[18:55:37][C][wmbus:440]: GDO2 Pin: GPIO21
[18:55:37][C][wmbus:447]: Available drivers: amiplus, apator08, apator162, apatoreitn, bmeters, c5isf, compact5, dme07, elf, evo868, fhkvdataiii, hydrocalm3, hydrus, iperl, itron, izar, mkradio3, mkradio4, qheat, qwater, sharky774, topaseskr, ultrimis, unismart, vario451
[18:55:41][VV][api.service:558]: on_ping_request: PingRequest {}
[18:55:41][VV][api.service:043]: send_ping_response: PingResponse {}
[18:56:17][VV][api.service:558]: on_ping_request: PingRequest {}
[18:56:17][VV][api.service:043]: send_ping_response: PingResponse {}
[18:56:21][VV][api.service:558]: on_ping_request: PingRequest {}
[18:56:21][VV][api.service:043]: send_ping_response: PingResponse {}
[18:56:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=58407 (now=118409)
[18:56:57][VV][api.service:558]: on_ping_request: PingRequest {}
[18:56:57][VV][api.service:043]: send_ping_response: PingResponse {}
[18:57:01][VV][api.service:558]: on_ping_request: PingRequest {}
[18:57:01][VV][api.service:043]: send_ping_response: PingResponse {}
[18:57:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=118407 (now=178407)
[18:57:41][VV][api.service:558]: on_ping_request: PingRequest {}
[18:57:41][VV][api.service:043]: send_ping_response: PingResponse {}
[18:57:57][VV][api.connection:132]: Sending keepalive PING...
[18:57:57][VV][api.service:037]: send_ping_request: PingRequest {}
[18:57:57][VV][api.service:567]: on_ping_response: PingResponse {}
[18:58:21][VV][api.service:558]: on_ping_request: PingRequest {}
[18:58:21][VV][api.service:043]: send_ping_response: PingResponse {}
[18:58:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=178407 (now=238407)
[18:58:57][VV][api.connection:132]: Sending keepalive PING...
[18:58:57][VV][api.service:037]: send_ping_request: PingRequest {}
[18:58:57][VV][api.service:558]: on_ping_request: PingRequest {}
[18:58:57][VV][api.service:043]: send_ping_response: PingResponse {}
[18:58:57][VV][api.service:567]: on_ping_response: PingResponse {}
[18:59:01][VV][api.service:558]: on_ping_request: PingRequest {}
[18:59:01][VV][api.service:043]: send_ping_response: PingResponse {}
[18:59:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=238407 (now=298407)
[18:59:29][I][ota:117]: Boot seems successful, resetting boot loop counter.
[18:59:29][VV][esp32.preferences:040]: s_pending_save: key: 233825507, len: 4
[18:59:29][D][esp32.preferences:114]: Saving 1 preferences to flash...
[18:59:29][VV][esp32.preferences:123]: Checking if NVS data 233825507 has changed
[18:59:29][V][esp32.preferences:126]: sync: key: 233825507, len: 4
[18:59:29][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[18:59:29][W][component:214]: Component ota took a long time for an operation (0.05 s).
[18:59:29][W][component:215]: Components should block for at most 20-30ms.
[18:59:41][VV][api.service:558]: on_ping_request: PingRequest {}
[18:59:41][VV][api.service:043]: send_ping_response: PingResponse {}
[18:59:57][VV][api.connection:132]: Sending keepalive PING...
[18:59:57][VV][api.service:037]: send_ping_request: PingRequest {}
[18:59:57][VV][api.service:567]: on_ping_response: PingResponse {}
[19:00:21][VV][api.service:558]: on_ping_request: PingRequest {}
[19:00:21][VV][api.service:043]: send_ping_response: PingResponse {}
[19:00:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=298407 (now=358408)
[19:00:57][VV][api.service:558]: on_ping_request: PingRequest {}
[19:00:57][VV][api.service:043]: send_ping_response: PingResponse {}
[19:01:01][VV][api.service:558]: on_ping_request: PingRequest {}
[19:01:01][VV][api.service:043]: send_ping_response: PingResponse {}
[19:01:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=358407 (now=418407)
[19:01:41][VV][api.service:558]: on_ping_request: PingRequest {}
[19:01:41][VV][api.service:043]: send_ping_response: PingResponse {}
[19:01:57][VV][api.connection:132]: Sending keepalive PING...
[19:01:57][VV][api.service:037]: send_ping_request: PingRequest {}
[19:01:57][VV][api.service:567]: on_ping_response: PingResponse {}
[19:02:21][VV][api.service:558]: on_ping_request: PingRequest {}
[19:02:21][VV][api.service:043]: send_ping_response: PingResponse {}
[19:02:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=418407 (now=478407)
[19:02:54][VV][scheduler:226]: Running interval 'update' with interval=900000 last_execution=4294572517 (now=505221)
[19:02:54][D][sntp:078]: Synchronized time: 2024-01-13 19:02:54
[19:02:57][VV][api.connection:132]: Sending keepalive PING...
[19:02:57][VV][api.service:037]: send_ping_request: PingRequest {}
[19:02:57][VV][api.service:567]: on_ping_response: PingResponse {}
[19:03:01][VV][api.service:558]: on_ping_request: PingRequest {}
[19:03:01][VV][api.service:043]: send_ping_response: PingResponse {}
[19:03:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=478407 (now=538407)
[19:03:41][VV][api.service:558]: on_ping_request: PingRequest {}
[19:03:41][VV][api.service:043]: send_ping_response: PingResponse {}
[19:03:57][VV][api.connection:132]: Sending keepalive PING...
[19:03:57][VV][api.service:037]: send_ping_request: PingRequest {}
[19:03:57][VV][api.service:567]: on_ping_response: PingResponse {}
[19:04:21][VV][api.service:558]: on_ping_request: PingRequest {}
[19:04:21][VV][api.service:043]: send_ping_response: PingResponse {}
[19:04:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=538407 (now=598408)
[19:04:57][VV][api.connection:132]: Sending keepalive PING...
[19:04:57][VV][api.service:037]: send_ping_request: PingRequest {}
[19:04:57][VV][api.service:567]: on_ping_response: PingResponse {}
[19:05:01][VV][api.service:558]: on_ping_request: PingRequest {}
[19:05:01][VV][api.service:043]: send_ping_response: PingResponse {}
[19:05:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=598407 (now=658408)
[19:05:41][VV][api.service:558]: on_ping_request: PingRequest {}
[19:05:41][VV][api.service:043]: send_ping_response: PingResponse {}
[19:05:57][VV][api.connection:132]: Sending keepalive PING...
[19:05:57][VV][api.service:037]: send_ping_request: PingRequest {}
[19:05:57][VV][api.service:567]: on_ping_response: PingResponse {}
[19:06:21][VV][api.service:558]: on_ping_request: PingRequest {}
[19:06:21][VV][api.service:043]: send_ping_response: PingResponse {}
[19:06:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=658407 (now=718407)
[19:06:57][VV][api.connection:132]: Sending keepalive PING...
[19:06:57][VV][api.service:037]: send_ping_request: PingRequest {}
[19:06:57][VV][api.service:567]: on_ping_response: PingResponse {}
[19:07:01][VV][api.service:558]: on_ping_request: PingRequest {}
[19:07:01][VV][api.service:043]: send_ping_response: PingResponse {}
[19:07:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=718407 (now=778407)
[19:07:41][VV][api.service:558]: on_ping_request: PingRequest {}
[19:07:41][VV][api.service:043]: send_ping_response: PingResponse {}
[19:07:57][VV][api.connection:132]: Sending keepalive PING...
[19:07:57][VV][api.service:037]: send_ping_request: PingRequest {}
[19:07:57][VV][api.service:567]: on_ping_response: PingResponse {}
[19:08:21][VV][api.service:558]: on_ping_request: PingRequest {}
[19:08:21][VV][api.service:043]: send_ping_response: PingResponse {}
[19:08:27][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=778407 (now=838408)
Byłbym wdzięczny za jakąś radę 
Dzięki z góry!
Jak widzisz linię powyżej to znaczy ze na 99% SPI do CC1101 działa. Teraz możesz:
@KuChar przetestuj wersję 2.4.12, coś na szybko dodałem (mam nadzieję że zadziała - daj znać). Powinno łapać current_hca
Mam też prośbę, zrób ticketa na wmbusmeters z tymi telegramami żeby dodali obsługę Apator E-ITN 40.
Nie mam pojęcia z jaką częstością nadają, więc wrócę do pierwotnej konfiguracji (jak poniżej na zdjęciu z ESP32 30 pin) i poczekam do rana.
Dzięki, pzdr!
Może nie nadają w weekend?
No tak, być może. W takim razie wrócę do tematu w poniedziałek.
Dzięki za wszystkie sugestie do tej pory! To be continued…
Działa! Pokazuje aktualne zużycie. Brakuje ostatniego odczytu i temp.
Jak podeślesz znowu telegramy z ostatnim odczytem i temperaturą to coś dopasuję
Mogę strzelać analogicznie do v30 - ale wolę twarde dane
Cześć. Mały update ode mnie
Liczniki zaczęły “sypać” od ok. 5:00 rano, więc potwierdzam, że nie nadają w weekend.
Ramki się pojawiają, ale licznik czyta jako “rfmtx1”.
{
"media":"water",
"meter":"rfmtx1",
"name":"",
"id":"14057620",
"total_m3":99.286,
"meter_datetime":"2024-01-15 07:50:50",
"timestamp":"2024-01-15T06:05:35Z"
}
Jakieś stare zdjęcie jednego z liczników:
Logi:
[06:56:37][C][wmbus:416]: wM-Bus v2.4.12:
[06:56:37][C][wmbus:433]: CC1101 frequency: 868.950 MHz
[06:56:37][C][wmbus:434]: CC1101 SPI bus:
[06:56:37][C][wmbus:435]: MOSI Pin: GPIO23
[06:56:37][C][wmbus:436]: MISO Pin: GPIO19
[06:56:37][C][wmbus:437]: CLK Pin: GPIO18
[06:56:37][C][wmbus:438]: CS Pin: GPIO5
[06:56:37][C][wmbus:439]: GDO0 Pin: GPIO22
[06:56:37][C][wmbus:440]: GDO2 Pin: GPIO21
[06:56:37][C][wmbus:447]: Available drivers: amiplus, apator08, apator162, apatoreitn, bmeters, c5isf, compact5, dme07, elf, evo868, fhkvdataiii, hydrocalm3, hydrus, iperl, itron, izar, mkradio3, mkradio4, qheat, qwater, sharky774, topaseskr, ultrimis, unismart, vario451
[06:56:37][C][wmbus:465]: Meter:
[06:56:37][C][wmbus:466]: ID: 36112738 [0x02270962]
[06:56:37][C][wmbus:467]: Type: hydrocalm3
[06:56:37][C][wmbus:468]: Mode: T1
[06:56:37][C][wmbus:469]: Key: '00000000000000000000000000000000'
[06:56:37][C][wmbus:471]: Sensor '0x2270962 Heating LQI'
[06:56:37][C][wmbus:471]: Device Class: 'signal_strength'
[06:56:37][C][wmbus:471]: State Class: 'measurement'
[06:56:37][C][wmbus:471]: Unit of Measurement: ''
[06:56:37][C][wmbus:471]: Accuracy Decimals: 0
[06:56:37][C][wmbus:471]: Sensor '0x2270962 Heating_kWh'
[06:56:37][C][wmbus:471]: Device Class: 'energy'
[06:56:37][C][wmbus:471]: State Class: 'total_increasing'
[06:56:37][C][wmbus:471]: Unit of Measurement: 'kWh'
[06:56:37][C][wmbus:471]: Accuracy Decimals: 3
[06:56:37][C][wmbus:471]: Icon: 'mdi:radiator'
[06:56:37][C][wmbus:471]: Sensor '0x2270962 Heating_m3'
[06:56:37][C][wmbus:471]: Device Class: 'water'
[06:56:37][C][wmbus:471]: State Class: 'total_increasing'
[06:56:37][C][wmbus:471]: Unit of Measurement: 'm³'
[06:56:37][C][wmbus:471]: Accuracy Decimals: 3
[06:56:37][C][wmbus:471]: Icon: 'mdi:water'
[06:56:37][C][wmbus:465]: Meter:
[06:56:37][C][wmbus:466]: ID: 335890802 [0x14054972]
[06:56:37][C][wmbus:467]: Type: bmeters
[06:56:37][C][wmbus:468]: Mode: T1
[06:56:37][C][wmbus:469]: Key: '00000000000000000000000000000000'
[06:56:37][C][wmbus:471]: Sensor '0x14054972 Hot water LQI'
[06:56:38][C][wmbus:471]: Device Class: 'signal_strength'
[06:56:38][C][wmbus:471]: State Class: 'measurement'
[06:56:38][C][wmbus:471]: Unit of Measurement: ''
[06:56:38][C][wmbus:471]: Accuracy Decimals: 0
[06:56:38][C][wmbus:471]: Sensor '0x14054972 Hot water'
[06:56:38][C][wmbus:471]: Device Class: 'water'
[06:56:38][C][wmbus:471]: State Class: 'total_increasing'
[06:56:38][C][wmbus:471]: Unit of Measurement: 'm³'
[06:56:38][C][wmbus:471]: Accuracy Decimals: 3
[06:56:38][C][wmbus:471]: Icon: 'mdi:water'
[06:56:38][C][wmbus:465]: Meter:
[06:56:38][C][wmbus:466]: ID: 335902240 [0x14057620]
[06:56:38][C][wmbus:467]: Type: bmeters
[06:56:38][C][wmbus:468]: Mode: T1
[06:56:38][C][wmbus:469]: Key: '00004000000300000500001000000600'
[06:56:38][C][wmbus:471]: Sensor '0x14057620 Cold water LQI'
[06:56:38][C][wmbus:471]: Device Class: 'signal_strength'
[06:56:38][C][wmbus:471]: State Class: 'measurement'
[06:56:38][C][wmbus:471]: Unit of Measurement: ''
[06:56:38][C][wmbus:471]: Accuracy Decimals: 0
[06:56:38][C][wmbus:471]: Sensor '0x14057620 Cold water'
[06:56:38][C][wmbus:471]: Device Class: 'water'
[06:56:38][C][wmbus:471]: State Class: 'total_increasing'
[06:56:38][C][wmbus:471]: Unit of Measurement: 'm³'
[06:56:38][C][wmbus:471]: Accuracy Decimals: 3
[06:56:38][C][wmbus:471]: Icon: 'mdi:water'
[06:56:42][I][wmbus:087]: Using driver 'bmeters' for ID [0x14057620] RSSI: -60 dBm LQI: 128 Mode: T1 T: 4644B4092076051405077AB300061031DD4C26F0A50F1D5E00000000505007150124CE1D00A81E00901F007C2000482100982100602200192300CA2300D224005E250072260000 (71)
[06:56:42][E][wmbus:109]: Something was not OK during decrypting telegram for ID [0x14057620] 'bmeters' key: '00004000000300000500001000000600'
[06:56:42][E][wmbus:110]: T : 4644B4092076051405077AB300061031DD4C26F0A50F1D5E00000000505007150124CE1D00A81E00901F007C2000482100982100602200192300CA2300D224005E250072260000 (71)
[06:56:42][E][wmbus:111]: T': 4644B4092076051405077AB3000610A1BFC237676AA2A9BBFDE302F02A951C89FD894F879A2F1FBD17556953DD32B670CD88A712440E549E31C4B29DE5B2D0005E250072260000 (71)
[06:56:42][W][component:214]: Component wmbus took a long time for an operation (0.07 s).
[06:56:42][W][component:215]: Components should block for at most 20-30ms.
[06:56:47][D][wmbus:188]: Meter ID [0x14091750] RSSI: -76 dBm LQI: 140 Mode: T1 not found in configuration T: 4644B4095017091405077AC5000610717581E2ABCB0F1D5EBA010000352209150124F4CF0027D100E7D200ACD4001CD600E1D700A3D90059DB002ADD00DBDE007AE00004E20000 (71)
[06:56:51][D][wmbus:188]: Meter ID [0x14057251] RSSI: -80 dBm LQI: 146 Mode: T1 not found in configuration T: 4644B4095172051405077A250006109195710D0F2B0F1D5E00000000114207150124562800B02900562B00652D002F2F00CD30005232004A3300E03300A634004B3500EB350000 (71)
[06:56:56][I][wmbus:087]: Using driver 'bmeters' for ID [0x14054972] RSSI: -44 dBm LQI: 128 Mode: T1 T: 4944B4097249051405077A490806108716EB7FE4CF0F1F5E232C16000000000135071501247D1900691A00571B00F11B008B1C00DC1C00721D00EA1D005B1E00141F007C1F0042200000 (74)
[06:56:56][E][wmbus:109]: Something was not OK during decrypting telegram for ID [0x14054972] 'bmeters' key: '00000000000000000000000000000000'
[06:56:56][E][wmbus:110]: T : 4944B4097249051405077A490806108716EB7FE4CF0F1F5E232C16000000000135071501247D1900691A00571B00F11B008B1C00DC1C00721D00EA1D005B1E00141F007C1F0042200000 (74)
[06:56:56][E][wmbus:111]: T': 4944B4097249051405077A490806109278A26D7B096F07B2A3677274AB52B7DD4E8E442349ECBCF0267B91B78A2701CB886DF9173FF2AFB21674D822AE429A00141F007C1F0042200000 (74)
[07:22:37][I][wmbus:087]: Using driver 'hydrocalm3' for ID [0x02270962] RSSI: -38 dBm LQI: 128 Mode: T1 T: 8E44B409620927020B0D7A620080051EB7D752947FEDA1F9AD3C074707912F869669F25882C27E9028A064247B5668CE07EF2E2C7D8A88AB15AB9CB948D0989B81EFAAF9AC81F2EED7A6B6A755FCF76226398E158D0796D8C9DA34175044AC68F3F7689FE1CF2F01C8554200B9173616CE0DBB4094D01801EBC8462897EEBA53B89D0AFF33FBDCA5F53D3D4C657DBE (143)
[07:22:37][D][wmbus:094]: Decrypted T : 8E44B409620927020B0D7A620080052F2F0C0E91990000046D16280F310C13175727000C0E010000000C13030300000C13000000000C13000000000A5A52039B81EFAAF9AC81F2EED7A6B6A755FCF76226398E158D0796D8C9DA34175044AC68F3F7689FE1CF2F01C8554200B9173616CE0DBB4094D01801EBC8462897EEBA53B89D0AFF33FBDCA5F53D3D4C657DBE (143)
[07:22:37][D][sensor:094]: '0x2270962 Heating LQI': Sending state 128.00000 with 0 decimals of accuracy
[07:22:37][D][sensor:094]: '0x2270962 Heating_kWh': Sending state 2775.27783 kWh with 3 decimals of accuracy
[07:22:37][D][sensor:094]: '0x2270962 Heating_m3': Sending state 275.71701 m³ with 3 decimals of accuracy
[06:56:56][W][component:214]: Component wmbus took a long time for an operation (0.07 s).
[06:56:56][W][component:215]: Components should block for at most 20-30ms.
Już wcześniej przewijał się ten temat. Jest to jakiś stary model nakładki.
@klu16 Coś na szybko dodałem (nietestowane - nie mam pojęcia czy zadziała. Spróbuj wersji 2.4.13. jako driver wybierz rfmtx1
Hej @_Szczepan. Dzięki wielkie!
W dalszym ciągu widać błędy.
PS. Nie jestem pewny jakiego klucza używać, więc w jednym liczniku dałem same zera, a w drugim z Twojego przykładowego konfigu z githuba. Nie wiem czy to ma jakieś znaczenie…
Logi:
[14:23:42][C][wmbus:417]: wM-Bus v2.4.13:
[14:23:42][C][wmbus:434]: CC1101 frequency: 868.950 MHz
[14:23:42][C][wmbus:435]: CC1101 SPI bus:
[14:23:42][C][wmbus:436]: MOSI Pin: GPIO23
[14:23:42][C][wmbus:437]: MISO Pin: GPIO19
[14:23:42][C][wmbus:438]: CLK Pin: GPIO18
[14:23:42][C][wmbus:439]: CS Pin: GPIO5
[14:23:42][C][wmbus:440]: GDO0 Pin: GPIO22
[14:23:42][C][wmbus:441]: GDO2 Pin: GPIO21
[14:23:42][C][wmbus:448]: Available drivers: amiplus, apator08, apator162, apatoreitn, bmeters, c5isf, compact5, dme07, elf, evo868, fhkvdataiii, hydrocalm3, hydrus, iperl, itron, izar, mkradio3, mkradio4, qheat, qwater, rfmtx1, sharky774, topaseskr, ultrimis, unismart, vario451
[14:23:42][C][wmbus:466]: Meter:
[14:23:42][C][wmbus:467]: ID: 36112738 [0x02270962]
[14:23:42][C][wmbus:468]: Type: hydrocalm3
[14:23:42][C][wmbus:469]: Mode: T1
[14:23:42][C][wmbus:470]: Key: '00000000000000000000000000000000'
[14:23:42][C][wmbus:472]: Sensor '0x2270962 Heating LQI'
[14:23:42][C][wmbus:472]: Device Class: 'signal_strength'
[14:23:42][C][wmbus:472]: State Class: 'measurement'
[14:23:42][C][wmbus:472]: Unit of Measurement: ''
[14:23:42][C][wmbus:472]: Accuracy Decimals: 0
[14:23:42][C][wmbus:472]: Sensor '0x2270962 Heating_kWh'
[14:23:42][C][wmbus:472]: Device Class: 'energy'
[14:23:42][C][wmbus:472]: State Class: 'total_increasing'
[14:23:42][C][wmbus:472]: Unit of Measurement: 'kWh'
[14:23:42][C][wmbus:472]: Accuracy Decimals: 3
[14:23:42][C][wmbus:472]: Icon: 'mdi:radiator'
[14:23:42][C][wmbus:472]: Sensor '0x2270962 Heating_m3'
[14:23:42][C][wmbus:472]: Device Class: 'water'
[14:23:42][C][wmbus:472]: State Class: 'total_increasing'
[14:23:42][C][wmbus:472]: Unit of Measurement: 'm³'
[14:23:42][C][wmbus:472]: Accuracy Decimals: 3
[14:23:42][C][wmbus:472]: Icon: 'mdi:water'
[14:23:42][C][wmbus:466]: Meter:
[14:23:42][C][wmbus:467]: ID: 335890802 [0x14054972]
[14:23:42][C][wmbus:468]: Type: rfmtx1
[14:23:42][C][wmbus:469]: Mode: T1
[14:23:42][C][wmbus:470]: Key: '00000000000000000000000000000000'
[14:23:42][C][wmbus:472]: Sensor '0x14054972 Hot water LQI'
[14:23:42][C][wmbus:472]: Device Class: 'signal_strength'
[14:23:42][C][wmbus:472]: State Class: 'measurement'
[14:23:42][C][wmbus:472]: Unit of Measurement: ''
[14:23:42][C][wmbus:472]: Accuracy Decimals: 0
[14:23:42][C][wmbus:472]: Sensor '0x14054972 Hot water'
[14:23:42][C][wmbus:472]: Device Class: 'water'
[14:23:42][C][wmbus:472]: State Class: 'total_increasing'
[14:23:42][C][wmbus:472]: Unit of Measurement: 'm³'
[14:23:42][C][wmbus:472]: Accuracy Decimals: 3
[14:23:42][C][wmbus:472]: Icon: 'mdi:water'
[14:23:42][C][wmbus:466]: Meter:
[14:23:42][C][wmbus:467]: ID: 335902240 [0x14057620]
[14:23:42][C][wmbus:468]: Type: rfmtx1
[14:23:42][C][wmbus:469]: Mode: T1
[14:23:42][C][wmbus:470]: Key: '00004000000300000500001000000600'
[14:23:42][C][wmbus:472]: Sensor '0x14057620 Cold water LQI'
[14:23:42][C][wmbus:472]: Device Class: 'signal_strength'
[14:23:42][C][wmbus:472]: State Class: 'measurement'
[14:23:42][C][wmbus:472]: Unit of Measurement: ''
[14:23:42][C][wmbus:472]: Accuracy Decimals: 0
[14:23:42][C][wmbus:472]: Sensor '0x14057620 Cold water'
[14:23:42][C][wmbus:472]: Device Class: 'water'
[14:23:42][C][wmbus:472]: State Class: 'total_increasing'
[14:23:42][C][wmbus:472]: Unit of Measurement: 'm³'
[14:23:42][C][wmbus:472]: Accuracy Decimals: 3
[14:23:42][C][wmbus:472]: Icon: 'mdi:water'
[14:31:42][I][wmbus:088]: Using driver 'rfmtx1' for ID [0x14057620] RSSI: -60 dBm LQI: 128 Mode: T1 T: 4644B4092076051405077A7A0006102222EA7062240F1D5E00000000502515150124CE1D00A81E00901F007C2000482100982100602200192300CA2300D224005E250072260000 (71)
[14:31:42][E][wmbus:110]: Something was not OK during decrypting telegram for ID [0x14057620] 'rfmtx1' key: '00004000000300000500001000000600'
[14:31:42][E][wmbus:111]: T : 4644B4092076051405077A7A0006102222EA7062240F1D5E00000000502515150124CE1D00A81E00901F007C2000482100982100602200192300CA2300D224005E250072260000 (71)
[14:31:42][E][wmbus:112]: T': 4644B4092076051405077A7A00061019197D6098DAAE58D097F7F9F339AD849A022F19151B2F1FBD17556953DD47A470CD88A712440E549E31C4B29DE5B2D0005E250072260000 (71)
[14:31:42][W][component:214]: Component wmbus took a long time for an operation (0.07 s).
[14:31:42][W][component:215]: Components should block for at most 20-30ms.
[14:31:58][I][wmbus:088]: Using driver 'hydrocalm3' for ID [0x02270962] RSSI: -38 dBm LQI: 128 Mode: T1 T: 8E44B409620927020B0D7AE6008005E7C53A7FECE32589E7D2F77B9C62E9C6ACD938EE76D1D815BC79766A0A95BE60205A4A1E8EC2D9572BAE0D4A40228AC90A61DA0988C5EFCD136487F556CBE953FA6759FA33E8EEBEFC82094FE3C30A970AF680DAEB345C457EDB61F0312777048FF1936A78D9ECF1A671411F9A06CB1426D0089D582A84ADC9B3B04CF40437CB (143)
[14:31:58][D][wmbus:095]: Decrypted T : 8E44B409620927020B0D7AE60080052F2F0C0E91990000046D202F0F310C13175727000C0E010000000C13030300000C13000000000C13000000000A5A53030A61DA0988C5EFCD136487F556CBE953FA6759FA33E8EEBEFC82094FE3C30A970AF680DAEB345C457EDB61F0312777048FF1936A78D9ECF1A671411F9A06CB1426D0089D582A84ADC9B3B04CF40437CB (143)
[14:31:58][D][sensor:094]: '0x2270962 Heating LQI': Sending state 128.00000 with 0 decimals of accuracy
[14:31:58][D][sensor:094]: '0x2270962 Heating_kWh': Sending state 2775.27783 kWh with 3 decimals of accuracy
[14:31:58][D][sensor:094]: '0x2270962 Heating_m3': Sending state 275.71701 m³ with 3 decimals of accuracy
[14:31:58][W][component:214]: Component wmbus took a long time for an operation (0.10 s).
[14:31:58][W][component:215]: Components should block for at most 20-30ms.
[14:32:54][I][wmbus:088]: Using driver 'rfmtx1' for ID [0x14054972] RSSI: -44 dBm LQI: 128 Mode: T1 T: 4944B4097249051405077A11080610467D33313B020F1F5E232C16000000000011151501247D1900691A00571B00F11B008B1C00DC1C00721D00EA1D005B1E00141F007C1F0042200000 (74)
[14:32:54][E][wmbus:110]: Something was not OK during decrypting telegram for ID [0x14054972] 'rfmtx1' key: '00000000000000000000000000000000'
[14:32:54][E][wmbus:111]: T : 4944B4097249051405077A11080610467D33313B020F1F5E232C16000000000011151501247D1900691A00571B00F11B008B1C00DC1C00721D00EA1D005B1E00141F007C1F0042200000 (74)
[14:32:54][E][wmbus:112]: T': 4944B4097249051405077A110806104ECCBE2420835A0E793DC93A2472DB0C679E640857454A49DED73887E1DD9DC8CAAC7FF9173FF2AFB21674D822AE429A00141F007C1F0042200000 (74)
Dzięki! 
Dla tego sensora daj pusty klucz.
[14:51:43][C][wmbus:466]: Meter:
[14:51:43][C][wmbus:467]: ID: 335902240 [0x14057620]
[14:51:43][C][wmbus:468]: Type: rfmtx1
[14:51:43][C][wmbus:469]: Mode: T1
[14:51:43][C][wmbus:470]: Key: ''
[14:51:43][C][wmbus:472]: Sensor '0x14057620 Cold water LQI'
[14:51:43][C][wmbus:472]: Device Class: 'signal_strength'
[14:51:43][C][wmbus:472]: State Class: 'measurement'
[14:51:43][C][wmbus:472]: Unit of Measurement: ''
[14:51:43][C][wmbus:472]: Accuracy Decimals: 0
[14:51:43][C][wmbus:472]: Sensor '0x14057620 Cold water'
[14:51:43][C][wmbus:472]: Device Class: 'water'
[14:51:43][C][wmbus:472]: State Class: 'total_increasing'
[14:51:43][C][wmbus:472]: Unit of Measurement: 'm³'
[14:51:43][C][wmbus:472]: Accuracy Decimals: 3
[14:51:43][C][wmbus:472]: Icon: 'mdi:water'
[14:53:41][I][wmbus:088]: Using driver 'rfmtx1' for ID [0x14057620] RSSI: -59 dBm LQI: 128 Mode: T1 T: 4644B4092076051405077A90000610E9156C12839A0F1D5E00000000494715150124CE1D00A81E00901F007C2000482100982100602200192300CA2300D224005E250072260000 (71)
[14:53:41][E][wmbus:168]: Can't get value from telegram for ID [0x14057620] 'rfmtx1'
[14:53:41][E][wmbus:169]: T : 4644B4092076051405077A90000610E9156C12839A0F1D5E00000000494715150124CE1D00A81E00901F007C2000482100982100602200192300CA2300D224005E250072260000 (71)
Dalej nic… teraz w ogóle nie może pobrać wartości bez zdefiniowanego klucza
Poprzednio tez nie pobierał – ale teraz doszedł dalej 
Chyba miałem literówkę – przetestuj 2.4.14 - ustaw też logi na VERY_VERBOSE