Komponent wM-Bus do ESPHome (SzczepanLeon) - liczniki ciepła i podzielniki kosztów ciepła

nie wiem dlaczego nie dekoduje mi telegramów - siedzę nad tym i nie mam już pomysłu :frowning:

kod w ESPHOME:

esphome:
  name: wmbus
  friendly_name: wmbus

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger: 
  level: DEBUG

# Enable Home Assistant API
api:
  encryption:
    key: "xxxxxxxxxxxxx"   

ota:
  password: "xxxxxxxxxxxxx" 

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Wmbus Fallback Hotspot"
    password: "xxxxxxxxxxxxx" 

time:
  - platform: sntp
    id: time_sntp

external_components:
  - source: github://SzczepanLeon/esphome-components@main
    components: [ wmbus ]

wmbus:
  mosi_pin: GPIO13
  miso_pin: GPIO5
  clk_pin:  GPIO2
  cs_pin:   GPIO14
  gdo0_pin: GPIO15
  gdo2_pin: GPIO16


captive_portal:

web_server:
  port: 80
  auth:
    username: xxxxxxxxxxxxx 
    password: xxxxxxxxxxxxx 
    
sensor:
  - platform: wmbus
    name: "licznik_ciepła_woda"
    meter_id: 0x83800243
    type: mkradio3
    key: "00000000000000000000000000000000"
  - platform: wmbus
    name: "licznik_ciepło"
    meter_id: 0x84230076
    type: vario451
    key: "00000000000000000000000000000000"
  - platform: wmbus
    name: "licznik_zimna_wodak"
    meter_id: 0x83800948
    type: mkradio3
    key: "00000000000000000000000000000000"     
  - platform: wmbus
    name: "licznik_zimna_wodap"
    meter_id: 0x83460234
    type: mkradio3
    key: "00000000000000000000000000000000" 
# 0x83800952
  - platform: wmbus
    name: "0x83800952"
    meter_id: 0x83800952
    type: mkradio3
    key: "00000000000000000000000000000000" 
# 0x83800229    
  - platform: wmbus
    name: "0x83800229"
    meter_id: 0x83800229
    type: mkradio3
    key: "00000000000000000000000000000000" 
# 0x83800230    
  - platform: wmbus
    name: "0x83800230"
    meter_id: 0x83800230
    type: mkradio3
    key: "00000000000000000000000000000000"

odczytuje dane z wielu liczników, ale jak dochodzi do jakiegoś zdefiniowanego to wyświetla tylko informację, ale nie dekoduje go.

02:19:21	[D]	[wmbus:091]	
Meter ID [0x84230072] RSSI: -75 dBm not found in configuration T: 374468507200238427C3A2129F2DAEA80090050D0000819944B551CED9632021C820050000000000000000008005C3A8E5D8868D8958EE72 (56)
02:19:22	[D]	[wmbus:091]	
Meter ID [0x83800238] RSSI: -70 dBm not found in configuration T: 2F446850380280839562A2069F2DAB0130250C000000010304030403080A040605020302030203030304030402020103 (48)
02:19:37	[I]	[wmbus:058]	
Using driver 'mkradio3' for ID [0x83800952] RSSI: -58 dBm T: 2F446850520980839572A2069F2D620430251700000000080C090C0B040A000C0603020702090308050B0A0D08080907 (48)
02:21:10	[D]	[wmbus:091]	
Meter ID [0x83800959] RSSI: -72 dBm not found in configuration T: 2F446850590980839572A2069F2D650130250A0000000003040203040303030405050405060404040505040202040302 (48)
02:22:09	[D]	[wmbus:091]	
Meter ID [0x83800953] RSSI: -61 dBm not found in configuration T: 2F446850530980839572A2069F2D5609302560000000061F241C1C1D1E1F1D201F1F271E20201E1F1B1C1C1917191B1C (48)

Telegram z tego licznika jest bez problemów dekodowany na stronie wmbuster.org - wynik poniżej

{
    "media":"cold water",
    "meter":"mkradio3",
    "name":"",
    "id":"83800952",
    "total_m3":114.5,
    "target_m3":112.2,
    "current_date":"2023-02-19T02:00:00Z",
    "prev_date":"2022-12-31T02:00:00Z",
    "timestamp":"2023-02-19T01:22:46Z"
}