Komponent wM-Bus do ESPHome (SzczepanLeon) wersja 4.x - wątek ogólny

Urządzenia Urządzenia inteligentnego domu
, , ,
178

Jak zrobiłem wpis z external komponent z 3.2.3 na version_3.
A jak wyrzucić drivery?
Jak próbuje instalować version_4 mam takie błędy

INFO ESPHome 2025.2.0
INFO Reading configuration /config/esphome/licznik.yaml...
INFO Updating https://github.com/SzczepanLeon/esphome-components.git@version_4
INFO Detected timezone 'Europe/Warsaw'
WARNING GPIO12 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO15 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
Failed config

sensor.wmbus: [source /config/esphome/licznik.yaml:64]
  platform: wmbus
  meter_id: 110454361
  type: apator162
  key: 00000000000000000000000000000000
  
  [lqi] is an invalid option for [sensor.wmbus]. Please check the indentation.
  lqi: 
    name: My_lqi
  
  [rssi] is an invalid option for [sensor.wmbus]. Please check the indentation.
  rssi: 
    name: My_RSSI
  
  [total_water_m3] is an invalid option for [sensor.wmbus]. Please check the indentation.
  total_water_m3: 
    name: Woda
179

1 - musisz YAML dostosowac
2 - o driverach poczytasz na głównej stronie komponentu na githubie

180

Masz może gotowca ? Wzór odnośnie dostosowania yamla?
Zmienilem wgrałem.wersje.4

wmbus:
  all_drivers: False
  log_all: False

sensor:
  - platform: wmbus
    meter_id: 0x00148686
    type: apator162
    key: "00000000000000000000000000000000"
    sensors:
      - name: "my hot water RSSi"
        field: "rssi"
        accuracy_decimals: 0
        unit_of_measurement: "dBm"
        device_class: "signal_strength"
        state_class: "measurement"
        entity_category: "diagnostic"
      - name: "my hot water"
        field: "total"
        accuracy_decimals: 3
        unit_of_measurement: "m³"
        device_class: "water"
        state_class: "total_increasing"
        icon: "mdi:water"

Meyer iD ma być 0x(numer tutaj z 0 czy bez 0)

181

Wszystko jest na github oraz forum.
Zawsze możesz jeszcze spróbować poprosic autora HW o support. A jak sam złożyłeś to poczytać przykłady - jest tu tego pełno.

182

Ja mam tak

  - platform: wmbus
    meter_id: 0x07654321
    type: apator162
    key: "00000000000000000000000000000000"
    sensors:
      - name: "Woda zimna"
        id: woda_zimna
        field: "total"
        accuracy_decimals: 3
        unit_of_measurement: "m³"
        device_class: "water"
        state_class: "total_increasing"
        icon: "mdi:water"
      - name: "Woda zimna RSSI"
        id: woda_zimna_rssi
        field: "rssi"
        accuracy_decimals: 0
        unit_of_measurement: "dBm"
        device_class: "signal_strength"
        state_class: "measurement"
        entity_category: "diagnostic"
  - platform: wmbus #następny licznik
    meter_id: 0x01234567
… # i tu cała reszta j/w

Ten numer hex 0x07654321 to oczywiście tylko przykład, wyczesałem go z nasłuchu eteru ale jak się okazuje 7-cyfrowy człon (w przykładzie 7654321) jest na nalepce naklejonej na nakładce obok kodu Data Matrix

data-matrix-plus-tlo
data-matrix-plus-tlo293×288 296 Bytes

(jeśli masz jakąś lepszą aplikację do czytania kodów kreskowych/qr/aztec itd. to ten numer jest też zakodowany i można go odczytać skanerem).

183

Dziękuję ogarnąłem nowy konfig z wersją 4 i wyłączyłem niepotrzebne drivery.
Numer licznika miałem wpisany i wszystko działo ale zastanawiam się już nad wszystkim nawet nad takimi rzeczami…Zobaczymy czy jutro coś licznik prześle

Zapomniałem że nie zakończyłem :joy:
Musiał się zawiesić po restarcie wstał

184

Dzień dobry wszystkim na tym forum. I’m late to the party z przeprowadzką do 4.x, ale prędzej czy później musiało trafić i na mnie. Z samymi przenosinami dzięki dokumentacji na githubie nie miałem problemu, ale pojawiły mi się na brokerze MQTT nowe tematy, które są mi niepotrzebne, nie za bardzo wiem co je wrzuca i jak to wyciąć. Chodzi o te zaznaczone ramką na czerwono.

Moja konfiguracja to: wmbus-gw.yaml - Pastebin.com

T.

wmbus
wmbus2282×730 173 KB

185

Cześć, wczoraj dostałem klucze dekodujące do licznika prądu Gama350 i walczę z konfiguracją na esp-s3-wroom + cc1101. HA postawione na RPi5
Log wygląda tak:



INFO Upload took 4.98 seconds, waiting for result...
INFO OTA successful
INFO Successfully uploaded program.
INFO Starting log output from 192.168.1.95 using esphome API
INFO Successfully connected to odczyt-prad @ 192.168.1.95 in 7.138s
INFO Successful handshake with odczyt-prad @ 192.168.1.95 in 0.254s
[17:06:46][I][app:100]: ESPHome version 2025.2.2 compiled on Mar 13 2025, 17:05:51
[17:06:46][C][wifi:600]: WiFi:
[17:06:46][C][wifi:428]:   Local MAC: xx:xx...
[17:06:46][C][wifi:433]:   SSID: 'domek'[redacted]
[17:06:46][C][wifi:436]:   IP Address: 192.168.1.95
[17:06:46][C][wifi:440]:   BSSID: 08:55:31:E4:48:3A[redacted]
[17:06:46][C][wifi:441]:   Hostname: 'odczyt-prad'
[17:06:46][C][wifi:443]:   Signal strength: -16 dB ▂▄▆█
[17:06:46][V][wifi:445]:   Priority: 0.0
[17:06:46][C][wifi:447]:   Channel: 8
[17:06:46][C][wifi:448]:   Subnet: 255.255.255.0
[17:06:46][C][wifi:449]:   Gateway: 192.168.xx.xx
[17:06:46][C][wifi:450]:   DNS1: 192.168.xx.xx
[17:06:46][C][wifi:451]:   DNS2: 192.168.xx.xx
[17:06:46][C][logger:177]: Logger:
[17:06:46][C][logger:178]:   Max Level: VERBOSE
[17:06:46][C][logger:179]:   Initial Level: VERBOSE
[17:06:46][C][logger:181]:   Log Baud Rate: 115200
[17:06:46][C][logger:182]:   Hardware UART: USB_CDC
[17:06:47][C][sntp:042]: SNTP Time:
[17:06:47][C][sntp:045]:   Server 0: '0.pool.ntp.org'
[17:06:47][C][sntp:045]:   Server 1: '1.pool.ntp.org'
[17:06:47][C][sntp:045]:   Server 2: '2.pool.ntp.org'
[17:06:47][C][mdns:116]: mDNS:
[17:06:47][C][mdns:117]:   Hostname: odczyt-prad
[17:06:47][V][mdns:118]:   Services:
[17:06:47][V][mdns:120]:   - _esphomelib, _tcp, 6053
[17:06:47][V][mdns:122]:     TXT: friendly_name = Odczyt_prad
[17:06:47][V][mdns:122]:     TXT: version = 2025.2.2
[17:06:47][V][mdns:122]:     TXT: mac = 3c8427e1aa90
[17:06:47][V][mdns:122]:     TXT: platform = ESP32
[17:06:47][V][mdns:122]:     TXT: board = esp32-s3-devkitc-1
[17:06:47][V][mdns:122]:     TXT: network = wifi
[17:06:47][V][mdns:122]:     TXT: api_encryption = Noise_NNpsk0_25519_ChaChaPoly_SHA256
[17:06:47][C][esphome.ota:073]: Over-The-Air updates:
[17:06:47][C][esphome.ota:074]:   Address: odczyt-prad.local:3232
[17:06:47][C][esphome.ota:075]:   Version: 2
[17:06:47][C][esphome.ota:078]:   Password configured
[17:06:47][C][safe_mode:018]: Safe Mode:
[17:06:47][C][safe_mode:020]:   Boot considered successful after 60 seconds
[17:06:47][C][safe_mode:021]:   Invoke after 10 boot attempts
[17:06:47][C][safe_mode:023]:   Remain in safe mode for 300 seconds
[17:06:47][C][api:140]: API Server:
[17:06:47][C][api:141]:   Address: odczyt-prad.local:6053
[17:06:47][C][api:143]:   Using noise encryption: YES
[17:06:47][C][mqtt:148]: MQTT:
[17:06:47][C][mqtt:150]:   Server Address: 192.168.1.xx:1883 (192.168.1.xx)
[17:06:47][C][mqtt:151]:   Username: 'mqtt_user'[redacted]
[17:06:47][C][mqtt:152]:   Client ID: 'odczyt-prad-3c8427e1aa90'[redacted]
[17:06:47][C][mqtt:153]:   Clean Session: NO
[17:06:47][C][mqtt:155]:   Discovery IP enabled
[17:06:47][C][mqtt:158]:   Discovery prefix: 'homeassistant'
[17:06:47][C][mqtt:159]:   Discovery retain: YES
[17:06:47][C][mqtt:161]:   Topic Prefix: 'odczyt-prad'
[17:06:47][C][mqtt:163]:   Log Topic: 'odczyt-prad/debug'
[17:06:47][C][mqtt:166]:   Availability: 'odczyt-prad/status'
[17:06:47][C][mqtt.sensor:028]: MQTT Sensor 'my current power consumption in Watts':
[17:06:47][C][mqtt.sensor:032]:   State Topic: 'odczyt-prad/sensor/my_current_power_consumption_in_watts/state'
[17:06:47][C][mqtt.sensor:028]: MQTT Sensor 'total energy on T1':
[17:06:47][C][mqtt.sensor:032]:   State Topic: 'odczyt-prad/sensor/total_energy_on_t1/state'
[17:06:47][C][mqtt.sensor:028]: MQTT Sensor 'voltage_at_phase_1':
[17:06:47][C][mqtt.sensor:032]:   State Topic: 'odczyt-prad/sensor/voltage_at_phase_1/state'
[17:06:47][C][wmbus:338]: wM-Bus v4.1.4-1.17.1-b8f4a945:
[17:06:47][C][wmbus:340]:   Clients:
[17:06:47][C][wmbus:347]:     wmbusmeters: 192.168.1.95:7227 TCP [rtl-wmbus]
[17:06:47][C][wmbus:351]:   LED:
[17:06:47][C][wmbus:352]:     Pin: GPIO0
[17:06:47][C][wmbus:353]:     Duration: 1000 ms
[17:06:47][C][wmbus:356]:   Chip ID: 90AAE127843C
[17:06:47][C][wmbus:358]:   CC1101 frequency: 868.900 MHz
[17:06:47][C][wmbus:359]:   CC1101 SPI bus:
[17:06:47][C][wmbus:363]:     MOSI Pin: GPIO15
[17:06:47][C][wmbus:364]:     MISO Pin: GPIO4
[17:06:47][C][wmbus:365]:     CLK Pin:  GPIO2
[17:06:47][C][wmbus:366]:     CS Pin:   GPIO5
[17:06:47][C][wmbus:367]:     GDO0 Pin: GPIO17
[17:06:47][C][wmbus:368]:     GDO2 Pin: GPIO6
[17:06:47][C][wmbus:374]:   Available drivers: unknown
[17:06:47][C][wmbus:388]:   Meter:
[17:06:47][C][wmbus:389]:     ID: 825688067 [0x31370003]
[17:06:47][C][wmbus:390]:     Type: auto detect
[17:06:47][C][wmbus:391]:     Key: 'hasło_do_odkodowania'
[17:06:47][C][wmbus:393]:     Field: 'current_power_consumption'
[17:06:47][C][wmbus:394]:      Name: 'my current power consumption in Watts'
[17:06:47][C][wmbus:394]:        Device Class: 'power'
[17:06:47][C][wmbus:394]:        State Class: 'measurement'
[17:06:47][C][wmbus:394]:        Unit of Measurement: 'w'
[17:06:47][C][wmbus:394]:        Accuracy Decimals: 1
[17:06:47][C][wmbus:394]:        Icon: 'mdi:transmission-tower-import'
[17:06:47][C][wmbus:393]:     Field: 'total_energy_consumption_tariff_1'
[17:06:47][C][wmbus:394]:      Name: 'total energy on T1'
[17:06:47][C][wmbus:394]:        Device Class: 'energy'
[17:06:47][C][wmbus:394]:        State Class: 'total_increasing'
[17:06:47][C][wmbus:394]:        Unit of Measurement: 'kwh'
[17:06:47][C][wmbus:394]:        Accuracy Decimals: 3
[17:06:47][C][wmbus:394]:        Icon: 'mdi:transmission-tower-import'
[17:06:47][C][wmbus:393]:     Field: 'voltage_at_phase_1'
[17:06:47][C][wmbus:394]:      Name: 'voltage_at_phase_1'
[17:06:47][C][wmbus:394]:        Device Class: 'voltage'
[17:06:47][C][wmbus:394]:        State Class: 'measurement'
[17:06:47][C][wmbus:394]:        Unit of Measurement: 'v'
[17:06:47][C][wmbus:394]:        Accuracy Decimals: 0
[17:06:47][C][wmbus:394]:        Icon: 'mdi:sine-wave'
[17:07:38][I][safe_mode:041]: Boot seems successful; resetting boot loop counter
[17:07:38][D][esp32.preferences:114]: Saving 1 preferences to flash...
[17:07:38][V][esp32.preferences:126]: sync: key: 233825507, len: 4
[17:07:38][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[17:08:46][V][rxLoop:167]: Have 326 bytes from CC1101 Rx, RSSI: -88 dBm LQI: 128
[17:08:46][V][rxLoop:172]: Synchronus mode enabled.
[17:08:46][D][mbus:035]: Received T1 A frame
[17:08:46][V][mbus:041]: Frame: 8F271CCB135C58B5962D32CD58D58E69C2D34E64EC5968D6599C72B0B4F1CB14E92D3B263662DAC4B69AB299932D92DC5A52F1A7235C5A636C9A3C564F2C5CC59A4B9A96B494E35A8D9666C69C99A69C63A595A69966964CE4D969A8DC34BA6994DA4BA71374C4B399B31C5C98B6962DC8D968BC662E52F298E3698E68D63A559365CD2995694DD342E66A5D1A5A9A693A36694CD5B22CD69636972CB23B34D0D95A9536B19693A68D969CC659658CB2D6A693B16B4B19B1A4CB69968E70B58E3A67299B25B23632 [RAW]
[17:08:46][V][mbus:043]:        F238EC99C8BB1A3AC65A3536B1369C5A8F44E965A69A8E935A3B135958DA5A4CE7253B42DC94B35A95C58E8F298BC4DC5AD0ECA3C536652CD38B9A39A55968D32D66992DC6A664EB13C9C66C2D6C8BA53996A69D26C966B42E668E71667158E6668E3A4D35C2F2B1338E6592D6956A4E4ECD1CD0D69C65C6A54CB34D9997 (326) [RAW]
[17:08:46][V][mbus:053]: Frame: BE44ED1403003731010264377A7800B005DE837DED7F378A1A36D3668FA73534093DFE140A18ABD07ED4D5F3AF6C9216B55ADFE5FFDBF50AA060727566B413FF91F3FD1CD3258DD4A36034B563DA393EA21FBAB0290754CF9091CC3A69C60FFF2B5F710E31601F488B8CC196976D9F2AB564D999B330FF2D6C858673656243022A4FAE0E1B3E22E5E3862856176D1FD6BC7F5666BF162D1501F672492C3493169402BEA3D1D6C2EBD7593123ABA900B73065346A5287E45830E3F7A0FFCAE06C3A62405D025ABBF1143E8722553090F278C4C16454697311A5 (217) [with CRC]
[17:08:46][V][mbus:096]: Validating CRC for Block1
[17:08:46][V][crc:031]:     calculated: 0x6437, read: 0x6437
[17:08:46][V][mbus:116]: Validating CRC for Block2
[17:08:46][V][crc:031]:     calculated: 0x8FA7, read: 0x8FA7
[17:08:46][V][mbus:116]: Validating CRC for Block3
[17:08:46][V][crc:031]:     calculated: 0x9216, read: 0x9216
[17:08:46][V][mbus:116]: Validating CRC for Block4
[17:08:46][V][crc:031]:     calculated: 0x91F3, read: 0x91F3
[17:08:46][V][mbus:116]: Validating CRC for Block5
[17:08:46][V][crc:031]:     calculated: 0xBAB0, read: 0xBAB0
[17:08:46][V][mbus:116]: Validating CRC for Block6
[17:08:46][V][crc:031]:     calculated: 0x3160, read: 0x3160
[17:08:46][V][mbus:116]: Validating CRC for Block7
[17:08:46][V][crc:031]:     calculated: 0xFF2D, read: 0xFF2D
[17:08:46][V][mbus:116]: Validating CRC for Block8
[17:08:46][V][crc:031]:     calculated: 0xE386, read: 0xE386
[17:08:46][V][mbus:116]: Validating CRC for Block9
[17:08:46][V][crc:031]:     calculated: 0x7249, read: 0x7249
[17:08:46][V][mbus:116]: Validating CRC for Block10
[17:08:46][V][crc:031]:     calculated: 0xABA9, read: 0xABA9
[17:08:46][V][mbus:116]: Validating CRC for Block11
[17:08:46][V][crc:031]:     calculated: 0xE06C, read: 0xE06C
[17:08:46][V][mbus:116]: Validating CRC for Block12
[17:08:46][V][crc:031]:     calculated: 0x78C4, read: 0x78C4
[17:08:46][V][mbus:116]: Validating CRC for Block13
[17:08:46][V][crc:031]:     calculated: 0x11A5, read: 0x11A5
[17:08:46][V][mbus:063]: Frame: BE44ED140300373101027A7800B005DE837DED7F378A1A36D3663534093DFE140A18ABD07ED4D5F3AF6CB55ADFE5FFDBF50AA060727566B413FFFD1CD3258DD4A36034B563DA393EA21F290754CF9091CC3A69C60FFF2B5F710E1F488B8CC196976D9F2AB564D999B3306C858673656243022A4FAE0E1B3E22E52856176D1FD6BC7F5666BF162D1501F62C3493169402BEA3D1D6C2EBD759312300B73065346A5287E45830E3F7A0FFCA3A62405D025ABBF1143E8722553090F2C164546973 (191) [without CRC]
[17:08:46][V][wmbus:270]: Will send RTLWMBUS telegram to 192.168.1.95:7227 via TCP
[17:08:46][E][wmbus:283]: Can't connect via TCP to 192.168.1.95:7227
[17:08:46][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 191
[17:08:46][V][Telegram.cpp:1178]: (wmbus) parseELL @10 181
[17:08:46][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 181
[17:08:46][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 181
[17:08:46][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 181
[17:08:46][I][wmbus:104]: Unknown! [0x31370003] RSSI: -88dBm T: BE44ED140300373101027A7800B005DE837DED7F378A1A36D3663534093DFE140A18ABD07ED4D5F3AF6CB55ADFE5FFDBF50AA060727566B413FFFD1CD3258DD4A36034B563DA393EA21F290754CF9091CC3A69C60FFF2B5F710E1F488B8CC196976D9F2AB564D999B3306C858673656243022A4FAE0E1B3E22E52856176D1FD6BC7F5666BF162D1501F62C3493169402BEA3D1D6C2EBD759312300B73065346A5287E45830E3F7A0FFCA3A62405D025ABBF1143E8722553090F2C164546973 (191) T1 A
[17:08:46][W][wmbus:111]: Link modes not defined in driver Unknown!. Processing anyway.
[17:08:46][W][wmbus:119]: Can't find driver for T: BE44ED140300373101027A7800B005DE837DED7F378A1A36D3663534093DFE140A18ABD07ED4D5F3AF6CB55ADFE5FFDBF50AA060727566B413FFFD1CD3258DD4A36034B563DA393EA21F290754CF9091CC3A69C60FFF2B5F710E1F488B8CC196976D9F2AB564D999B3306C858673656243022A4FAE0E1B3E22E52856176D1FD6BC7F5666BF162D1501F62C3493169402BEA3D1D6C2EBD759312300B73065346A5287E45830E3F7A0FFCA3A62405D025ABBF1143E8722553090F2C164546973 (191)
[17:08:46][W][component:237]: Component wmbus took a long time for an operation (152 ms).
[17:08:46][W][component:238]: Components should block for at most 30 ms.
[17:09:46][V][rxLoop:167]: Have 326 bytes from CC1101 Rx, RSSI: -88 dBm LQI: 129
[17:09:46][V][rxLoop:172]: Synchronus mode enabled.
[17:09:46][D][mbus:035]: Received T1 A frame
[17:09:46][V][mbus:041]: Frame: 8F271CCB135C58B5962D32CD58D58E69C2D34E64E55968D659964D731671C66C563992F1C99B163962E9CACA66729C563B26AC65C99368E2DA2DC95A68EA5C5B14F14F1C4D3653A669CC5C971A4B98EB0B65C34B66CD26A4BC8BA5CB292F1C8D69C656C8D38D8CD959656A72B32D0D65935C2E95A92E671671A2F1725C4D4D6C968CB2F4CB48D39694F2D19C994F2693356731965D1AB16A5A4CE64DD29D13CB2734A53971D262D6CA959C34D34D9569B497438B6639A594B39CC668D36999A3A5665AD2534E6B12 [RAW]
[17:09:46][V][mbus:043]:        D9C9C399CA53ACC69A6C8F4C65B345A66B43A93A36B4C6535A39C6AC95C7165932E93A38D9C5AC659ACD1A596599D0EB135B1D3458B71C9A68D6CA6A5AC5338ECB44CB67238BD3170E9AC70DB296A9372C56C8B5A367165C4F14F44ECA7234D94D2CDC6C2D959AA729A3963A729B2669D1C70D4CE4E66B46A3B0E8EC9A6B (326) [RAW]
[17:09:46][V][mbus:053]: Frame: BE44ED1403003731010264377A7900B005514D5DDAD0253DE580203FE8FA4FD02E6854A76236349662F40D7D7DD1192A64D49DF3A283541358CAF3E3F48F3DE16450E121B19550FE8EC155143F0F3A40463D49D170E0B33CECB79F7EC5E57E67104D99C680F67251CFC7EE4CF79DCA30EF04111190AC9C235BA99324DAB765ABF056C9126D35E425E928DFF8BCD98C0A6C2F2B6CD91624689440073F2BB5D6D9A8C60005C2870DCC0344AAB0EAF6D722EC735E23CD42A8418F6F1ED0E30B5D547D7C78FE119131D83506FEAB9BFEAE5FC441727A6C6B82B8AA (217) [with CRC]
[17:09:46][V][mbus:096]: Validating CRC for Block1
[17:09:46][V][crc:031]:     calculated: 0x6437, read: 0x6437
[17:09:46][V][mbus:116]: Validating CRC for Block2
[17:09:46][V][crc:031]:     calculated: 0xE8FA, read: 0xE8FA
[17:09:46][V][mbus:116]: Validating CRC for Block3
[17:09:46][V][crc:031]:     calculated: 0x192A, read: 0x192A
[17:09:46][V][mbus:116]: Validating CRC for Block4
[17:09:46][V][crc:031]:     calculated: 0x6450, read: 0x6450
[17:09:46][V][mbus:116]: Validating CRC for Block5
[17:09:46][V][crc:031]:     calculated: 0x49D1, read: 0x49D1
[17:09:46][V][mbus:116]: Validating CRC for Block6
[17:09:46][V][crc:031]:     calculated: 0x80F6, read: 0x80F6
[17:09:46][V][mbus:116]: Validating CRC for Block7
[17:09:46][V][crc:031]:     calculated: 0x9C23, read: 0x9C23
[17:09:46][V][mbus:116]: Validating CRC for Block8
[17:09:46][V][crc:031]:     calculated: 0xE928, read: 0xE928
[17:09:46][V][mbus:116]: Validating CRC for Block9
[17:09:48][V][crc:031]:     calculated: 0x073F, read: 0x073F
[17:09:48][V][mbus:116]: Validating CRC for Block11
[17:09:48][V][crc:031]:     calculated: 0x5D54, read: 0x5D54
[17:09:48][V][mbus:116]: Validating CRC for Block12
[17:09:48][V][crc:031]:     calculated: 0xC441, read: 0xC441
[17:09:48][V][mbus:116]: Validating CRC for Block13
[17:09:48][V][crc:031]:     calculated: 0xB8AA, read: 0xB8AA
[17:09:48][V][mbus:063]: Frame: BE44ED140300373101027A7900B005514D5DDAD0253DE580203F4FD02E6854A76236349662F40D7D7DD164D49DF3A283541358CAF3E3F48F3DE1E121B19550FE8EC155143F0F3A40463D70E0B33CECB79F7EC5E57E67104D99C67251CFC7EE4CF79DCA30EF04111190AC5BA99324DAB765ABF056C9126D35E425DFF8BCD98C0A6C2F2B6CD916246894402BB5D6D9A8C60005C2870DCC0344AAB0D722EC735E23CD42A8418F6F1ED0E30B7D7C78FE119131D83506FEAB9BFEAE5F727A6C6B82 (191) [without CRC]
[17:09:48][V][wmbus:270]: Will send RTLWMBUS telegram to 192.168.1.95:7227 via TCP
[17:09:48][E][wmbus:283]: Can't connect via TCP to 192.168.1.95:7227
[17:09:48][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 191
[17:09:48][V][Telegram.cpp:1178]: (wmbus) parseELL @10 181
[17:09:48][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 181
[17:09:48][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 181
[17:09:48][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 181
[17:09:48][I][wmbus:104]: Unknown! [0x31370003] RSSI: -88dBm T: BE44ED140300373101027A7900B005514D5DDAD0253DE580203F4FD02E6854A76236349662F40D7D7DD164D49DF3A283541358CAF3E3F48F3DE1E121B19550FE8EC155143F0F3A40463D70E0B33CECB79F7EC5E57E67104D99C67251CFC7EE4CF79DCA30EF04111190AC5BA99324DAB765ABF056C9126D35E425DFF8BCD98C0A6C2F2B6CD916246894402BB5D6D9A8C60005C2870DCC0344AAB0D722EC735E23CD42A8418F6F1ED0E30B7D7C78FE119131D83506FEAB9BFEAE5F727A6C6B82 (191) T1 A
[17:09:48][W][wmbus:111]: Link modes not defined in driver Unknown!. Processing anyway.
[17:09:48][W][wmbus:119]: Can't find driver for T: BE44ED140300373101027A7900B005514D5DDAD0253DE580203F4FD02E6854A76236349662F40D7D7DD164D49DF3A283541358CAF3E3F48F3DE1E121B19550FE8EC155143F0F3A40463D70E0B33CECB79F7EC5E57E67104D99C67251CFC7EE4CF79DCA30EF04111190AC5BA99324DAB765ABF056C9126D35E425DFF8BCD98C0A6C2F2B6CD916246894402BB5D6D9A8C60005C2870DCC0344AAB0D722EC735E23CD42A8418F6F1ED0E30B7D7C78FE119131D83506FEAB9BFEAE5F727A6C6B82 (191)
[17:09:48][W][component:237]: Component wmbus took a long time for an operation (2126 ms).
[17:09:48][W][component:238]: Components should block for at most 30 ms.

Jak widzicie z odbiorem zdekodowanych danych słabo… :frowning: - z tego co widzę brak połączenia z esp32 na porcie 7227.
Pomóżcie plz!!

186
  1. odbiera bardzo ładnie- musisz zdefiniowac teraz sensor z kluczem (w odpowiedniej kolejnosci w YAML)
  2. a cos nasluchuje na tym porcie? to nie brak polaczenia do esp32 a esp32 nie moze sie polaczyc z tym co w yamlu masz jako client zdefiniowane (po co?)
1 Like
187

W pliku configuration.yaml mam odwołanie:

binary_sensor: !include bin_sensor.yaml

bin_sensor.yaml

  - platform: wmbus
    meter_id: 0x31370003
    key: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
    #type: amiplus
    sensors:
      - name: "my current power consumption in Watts"
        field: "current_power_consumption"
        accuracy_decimals: 1
        unit_of_measurement: "w"
        device_class: "power"
        state_class: "measurement"
        icon: "mdi:transmission-tower-import"
      - name: "total energy on T1"
        field: "total_energy_consumption_tariff_1"
        accuracy_decimals: 3
        unit_of_measurement: "kwh"
        device_class: "energy"
        state_class: "total_increasing"
        icon: "mdi:transmission-tower-import"
      - name: "voltage_at_phase_1"
        accuracy_decimals: 0
        unit_of_measurement: "v"
        device_class: "voltage"
        state_class: "measurement"
        icon: "mdi:sine-wave"

Czy o to chodzi w pkt 1?
Pkt 2 - rozwiązany

PS: pojawiły sie odczyty!! … ale… mimo że nie mam instalacji fotowoltaicznej, na odczytach konsumpcja 0, produkcja 2.911 kwh !!! :smiley:

188

bez zmian w yamlu i tym samym wsadem?

Pokaz zdekodowany telegram.

189 
{
  "meter": "amiplus",
  "media": "electricity",
  "id": "31xxxx3",
  "rssi_dbm": -88,
  "current_power_consumption_kw": 0,
  "current_power_production_kw": 0.734,
  "total_energy_consumption_kwh": 0,
  "total_energy_consumption_tariff_1_kwh": 0,
  "total_energy_consumption_tariff_2_kwh": 0,
  "total_energy_consumption_tariff_3_kwh": 0,
  "total_energy_production_kwh": 276.61,
  "total_energy_production_tariff_1_kwh": 276.61,
  "total_energy_production_tariff_2_kwh": 0,
  "total_energy_production_tariff_3_kwh": 0,
  "voltage_at_phase_1_v": 242,
  "voltage_at_phase_2_v": 244,
  "voltage_at_phase_3_v": 242,
  "device_date_time": "2025-03-13 20:59:46",
  "timestamp": "2025-03-13T19:59:46Z",
  "device": "ESPHome wM-Bus"
}
190

To nie może działać… sensory których oczekujesz to zwykłe sensory, a nie binarne, zamiast na siłę wyrzucać konfigurację sensorów w niewłaściwe miejsce zrób to normalnie w configuration.yaml, a gdy zadziała to możesz przenieść w takie miejsce jak Ci pasuje tylko w poprawny sposób.

191

Powinienem byc precyzyjny. Pokaz telegram z logow ESPHome ale juz po zdekodowaniu kluczem.

192

… mam nadzieję, że o to chodzi :wink:

06:33:46][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 191
[06:33:46][V][Telegram.cpp:1178]: (wmbus) parseELL @10 181
[06:33:46][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 181
[06:33:46][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 181
[06:33:46][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 181
[06:33:46][I][wmbus:092]: Using selected driver amiplus (detected driver was amiplus)
[06:33:46][I][wmbus:104]: amiplus [0x31370003] RSSI: -94dBm T: BE44ED140300373101027A9D00B005A51022A1A0B4517868B7F478ACCFDC2BC8862C314A870CF97A641C9D780939D9F32FCF6F81A4FA1153849318B5893F8781A16A893F51B6AB3BB58CD71DD25C0631E0D6A817B9F734447C31A2CC0A5C687BEDB012093D83C236A812E84B13B9BF8946DF71C8769A8304E4195DA0DF5D49EFB013E8365F910D3F0918378B96DFCB8BAE08DD5972F7060646A147225096BC6B02DCF7FE76A9AB7CAD7CB8B1774CF45E36F4D387A107957E2AED1655E784DF (191) T1 A
[06:33:46][D][meters.cpp:1987]: (meter) created ESPHome amiplus 31370003 encrypted
[06:33:46][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 191
[06:33:46][V][Telegram.cpp:1178]: (wmbus) parseELL @10 181
[06:33:46][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 181
[06:33:46][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 181
[06:33:46][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 181
[06:33:46][V][meters.cpp:635]: (meter) ESPHome: for me? 31370003.M=EGM.V=01.T=02,31370003.M=EGM.V=01.T=02 in 31370003
[06:33:46][V][meters.cpp:686]: (meter) ESPHome: yes for me
[06:33:46][D][meters.cpp:911]: (meter) ESPHome(0) amiplus  handling telegram from 31370003.M=EGM.V=01.T=02
[06:33:46][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 191
[06:33:46][V][Telegram.cpp:545]: (telegram) DLL L=be C=44 (from meter SND_NR) M=14ed (EGM) A=31370003 VER=01 TYPE=02 (Electricity meter) (driver amiplus) DEV=ESPHome wM-Bus RSSI=-94
[06:33:46][V][Telegram.cpp:1178]: (wmbus) parseELL @10 181
[06:33:46][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 181
[06:33:46][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 181
[06:33:46][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 181
[06:33:46][V][Telegram.cpp:299]: (TPL) num encrypted blocks 11 (176 bytes and remaining unencrypted 0 bytes)
[06:33:46][V][Telegram.cpp:303]: (TPL) AES CBC IV decrypting
[06:33:46][V][Telegram.cpp:343]: (TPL) IV ED140300373101029D9D9D9D9D9D9D9D
[06:33:46][V][utils.cpp:823]: (TPL) decrypted  "2F2F066D2E21A62E33400C78030037310E030000000000008E10030000000000008E20030000000000008E30030000000000008E8010030000000000000E833C6711280000008E10833C6711280000008E20833C0000000000008E30833C0000000000008E8010833C0000000000000B2B0000000BAB3C5807000BFB145602000BFB943C0000000AFDC9FC0147020AFDC9FC0245020AFDC9FC0346020BABC8FC100000072F2F2F2F2F2F2F2F2F2F2F2F"
[06:33:46][V][dvparser.cpp:1471]: [DVPARSER] entry 19: 066D Instantaneous vif=6d  st=0 ta=0 su=0
[06:33:46][V][dvparser.cpp:1471]: [DVPARSER] entry 27: 0C78 Instantaneous vif=78  st=0 ta=0 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 33: 0E03 Instantaneous vif=3  st=0 ta=0 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 42: 8E1003 Instantaneous vif=3  st=0 ta=1 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 51: 8E2003 Instantaneous vif=3  st=0 ta=2 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 60: 8E3003 Instantaneous vif=3  st=0 ta=3 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 70: 8E801003 Instantaneous vif=3  st=0 ta=4 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 79: 0E833C Instantaneous vif=3 HASCOMB HASCOMBRAW  st=0 ta=0 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 89: 8E10833C Instantaneous vif=3 HASCOMB HASCOMBRAW  st=0 ta=1 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 99: 8E20833C Instantaneous vif=3 HASCOMB HASCOMBRAW  st=0 ta=2 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 109: 8E30833C Instantaneous vif=3 HASCOMB HASCOMBRAW  st=0 ta=3 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 120: 8E8010833C Instantaneous vif=3 HASCOMB HASCOMBRAW  st=0 ta=4 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 128: 0B2B Instantaneous vif=2b  st=0 ta=0 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 134: 0BAB3C Instantaneous vif=2b HASCOMB HASCOMBRAW  st=0 ta=0 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 140: 0BFB14 Instantaneous vif=7b14  st=0 ta=0 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 147: 0BFB943C Instantaneous vif=7b14 HASCOMB HASCOMBRAW  st=0 ta=0 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 155: 0AFDC9FC01 Instantaneous vif=7d49 HASCOMB HASCOMBRAW  st=0 ta=0 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 162: 0AFDC9FC02 Instantaneous vif=7d49 HASCOMB HASCOMBRAW  st=0 ta=0 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 169: 0AFDC9FC03 Instantaneous vif=7d49 HASCOMB HASCOMBRAW  st=0 ta=0 su=0
[06:33:47][V][dvparser.cpp:1471]: [DVPARSER] entry 176: 0BABC8FC10 Instantaneous vif=2b HASCOMB HASCOMBRAW  st=0 ta=0 su=0
[06:33:47][V][Telegram.cpp:634]: (telegram) TPL CI=7a
[06:33:47][V][Telegram.cpp:640]:  ACC=9d STS=00 CFG=05b0 (AES_CBC_IV nb=11 cntn=0 ra=0 hc=0)
[06:33:47][V][meters.cpp:975]: (meters) trying field info total_energy_consumption(Energy)[0]...
[06:33:47][V][meters.cpp:997]: (meters) using field info total_energy_consumption(Energy)[0] to extract 0E03 at offset 33
[06:33:47][V][meters.cpp:2162]: (meter) AnyEnergyVIF total_energy_consumption_kwh decoded kwh default kwh value 0 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info current_power_consumption(Power)[1]...
[06:33:47][V][meters.cpp:997]: (meters) using field info current_power_consumption(Power)[1] to extract 0B2B at offset 128
[06:33:47][V][meters.cpp:2162]: (meter) PowerW current_power_consumption_kw decoded kw default kw value 0 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info total_energy_production(Energy)[2]...
[06:33:47][V][meters.cpp:997]: (meters) using field info total_energy_production(Energy)[2] to extract 0E833C at offset 79
[06:33:47][V][meters.cpp:2162]: (meter) Any total_energy_production_kwh decoded kwh default kwh value 281.167 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info current_power_production(Power)[3]...
[06:33:47][V][meters.cpp:997]: (meters) using field info current_power_production(Power)[3] to extract 0BAB3C at offset 134
[06:33:47][V][meters.cpp:2162]: (meter) Any current_power_production_kw decoded kw default kw value 0.758 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info voltage_at_phase_1(Voltage)[4]...
[06:33:47][V][meters.cpp:997]: (meters) using field info voltage_at_phase_1(Voltage)[4] to extract 0AFDC9FC01 at offset 155
[06:33:47][V][meters.cpp:2162]: (meter) Any voltage_at_phase_1_v decoded v default v value 247 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info voltage_at_phase_2(Voltage)[5]...
[06:33:47][V][meters.cpp:997]: (meters) using field info voltage_at_phase_2(Voltage)[5] to extract 0AFDC9FC02 at offset 162
[06:33:47][V][meters.cpp:2162]: (meter) Any voltage_at_phase_2_v decoded v default v value 245 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info voltage_at_phase_3(Voltage)[6]...
[06:33:47][V][meters.cpp:997]: (meters) using field info voltage_at_phase_3(Voltage)[6] to extract 0AFDC9FC03 at offset 169
[06:33:47][V][meters.cpp:2162]: (meter) Any voltage_at_phase_3_v decoded v default v value 246 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info device_date_time(Text)[7]...
[06:33:47][V][meters.cpp:997]: (meters) using field info device_date_time(Text)[7] to extract 066D at offset 19
[06:33:47][V][meters.cpp:975]: (meters) trying field info total_energy_consumption_tariff_1(Energy)[8]...
[06:33:47][V][meters.cpp:997]: (meters) using field info total_energy_consumption_tariff_1(Energy)[8] to extract 8E1003 at offset 42
[06:33:47][V][meters.cpp:2162]: (meter) AnyEnergyVIF total_energy_consumption_tariff_1_kwh decoded kwh default kwh value 0 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info total_energy_consumption_tariff_2(Energy)[9]...
[06:33:47][V][meters.cpp:997]: (meters) using field info total_energy_consumption_tariff_2(Energy)[9] to extract 8E2003 at offset 51
[06:33:47][V][meters.cpp:2162]: (meter) AnyEnergyVIF total_energy_consumption_tariff_2_kwh decoded kwh default kwh value 0 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info total_energy_consumption_tariff_3(Energy)[10]...
[06:33:47][V][meters.cpp:997]: (meters) using field info total_energy_consumption_tariff_3(Energy)[10] to extract 8E3003 at offset 60
[06:33:47][V][meters.cpp:2162]: (meter) AnyEnergyVIF total_energy_consumption_tariff_3_kwh decoded kwh default kwh value 0 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info total_energy_production_tariff_1(Energy)[11]...
[06:33:47][V][meters.cpp:997]: (meters) using field info total_energy_production_tariff_1(Energy)[11] to extract 8E10833C at offset 89
[06:33:47][V][meters.cpp:2162]: (meter) Any total_energy_production_tariff_1_kwh decoded kwh default kwh value 281.167 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info total_energy_production_tariff_2(Energy)[12]...
[06:33:47][V][meters.cpp:997]: (meters) using field info total_energy_production_tariff_2(Energy)[12] to extract 8E20833C at offset 99
[06:33:47][V][meters.cpp:2162]: (meter) Any total_energy_production_tariff_2_kwh decoded kwh default kwh value 0 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info total_energy_production_tariff_3(Energy)[13]...
[06:33:47][V][meters.cpp:997]: (meters) using field info total_energy_production_tariff_3(Energy)[13] to extract 8E30833C at offset 109
[06:33:47][V][meters.cpp:2162]: (meter) Any total_energy_production_tariff_3_kwh decoded kwh default kwh value 0 (scale 1)
[06:33:47][V][meters.cpp:975]: (meters) trying field info max_power_consumption(Power)[14]...
[06:33:47][V][sensor:043]: 'Gama350 Moc importu': Received new state 0.000000
[06:33:47][D][sensor:094]: 'Gama350 Moc importu': Sending state 0.00000 kw with 3 decimals of accuracy
[06:33:47][V][mqtt:496]: Publish(topic='odczyt-prad/sensor/gama350_moc_importu/state' payload='0.000' retain=1 qos=0)
[06:33:47][W][wmbus:158]: Can't get proper unit from 'w'
[06:33:47][V][sensor:043]: 'Gama350 Moc exportu': Received new state 0.758000
[06:33:47][D][sensor:094]: 'Gama350 Moc exportu': Sending state 0.75800 kw with 3 decimals of accuracy
[06:33:47][V][mqtt:496]: Publish(topic='odczyt-prad/sensor/gama350_moc_exportu/state' payload='0.758' retain=1 qos=0)
[06:33:47][V][sensor:043]: 'Gama350 RSSI': Received new state -94.000000
[06:33:47][D][sensor:094]: 'Gama350 RSSI': Sending state -94.00000 dBm with 0 decimals of accuracy
[06:33:47][V][mqtt:496]: Publish(topic='odczyt-prad/sensor/gama350_rssi/state' payload='-94' retain=1 qos=0)
[06:33:47][V][sensor:043]: 'Gama350': Received new state 0.000000
[06:33:47][D][sensor:094]: 'Gama350': Sending state 0.00000 kwh with 3 decimals of accuracy
[06:33:47][V][mqtt:496]: Publish(topic='odczyt-prad/sensor/gama350/state' payload='0.000' retain=1 qos=0)
[06:33:47][V][sensor:043]: 'Całkowite zuzycie T1': Received new state 0.000000
[06:33:47][D][sensor:094]: 'Całkowite zuzycie T1': Sending state 0.00000 kwh with 3 decimals of accuracy
[06:33:47][V][mqtt:496]: Publish(topic='odczyt-prad/sensor/ca__kowite_zuzycie_t1/state' payload='0.000' retain=1 qos=0)
[06:33:47][V][sensor:043]: 'Gama350 napiecie na fazie 1': Received new state 247.000000
[06:33:47][D][sensor:094]: 'Gama350 napiecie na fazie 1': Sending state 247.00000 v with 0 decimals of accuracy
[06:33:47][V][mqtt:496]: Publish(topic='odczyt-prad/sensor/gama350_napiecie_na_fazie_1/state' payload='247' retain=1 qos=0)
[06:33:47][V][sensor:043]: 'Gama350 napiecie na fazie 2': Received new state 245.000000
[06:33:47][D][sensor:094]: 'Gama350 napiecie na fazie 2': Sending state 245.00000 v with 0 decimals of accuracy
[06:33:47][V][mqtt:496]: Publish(topic='odczyt-prad/sensor/gama350_napiecie_na_fazie_2/state' payload='245' retain=1 qos=0)
[06:33:47][V][sensor:043]: 'Gama350 napiecie na fazie 3': Received new state 246.000000
[06:33:47][D][sensor:094]: 'Gama350 napiecie na fazie 3': Sending state 246.00000 v with 0 decimals of accuracy
[06:33:47][V][mqtt:496]: Publish(topic='odczyt-prad/sensor/gama350_napiecie_na_fazie_3/state' payload='246' retain=1 qos=0)
[06:33:47][V][mqtt:496]: Publish(topic='odczyt-prad/wmbus/31370003' payload='{"meter":"amiplus","media":"electricity","id":"31370003","rssi_dbm":-94,"current_power_consumption_kw":0,"current_power_production_kw":0.758,"total_energy_consumption_kwh":0,"total_energy_consumption_tariff_1_kwh":0,"total_energy_consumption_tariff_2_kwh":0,"total_energy_consumption_tariff_3_kwh":0,"total_energy_production_kwh":281.167,"total_energy_production_tariff_1_kwh":281.167,"total_energy_production_tariff_2_kwh":0,"total_ener
[06:33:47][W][component:237]: Component wmbus took a long time for an operation (593 ms).
[06:33:47][W][component:238]: Components should block for at most 30 ms.
193

Pojawiają się też takie ramki:

06:44:46][D][mbus:035]: Received T1 A frame
[06:44:46][V][mbus:041]: Frame: 8F271CCB135C58B5962D32CD58D58E69C2D34E69AC5968D6599D1C3AC4DA3999A567169A8E6959A5AA6972639968B39A6B44F48D9CB2CB2393CAC98B5939B4C8D8CD969669956A5AD2934B3726A34E596CD196B67197329639632E6374B2564DA658F499AD16D3172665994DC724E52E672535495666571C36C98DB238EC3566692F438D365C6970D9658EC7259A3CB14CB38B4EC68E5B43AC2DC2DC98E3A3D0E94DB0E4D634D4DC8DC4E32E3C66C74B253A66B18DA2CEC748DAD254CE36366CA4B8EC99A59AA56C [RAW]
[06:44:46][V][mbus:043]:        72C934DA2E34E58F197138EB199593652CFC697138F4C635B22B4C656A6D1A2EC3A559AA56A4D9994CEB0B5B46A664D2E934DC4EC59B3171AA594E5D197138DA38D2F2C9C2F168D2F4D0D5966A39692DACB13B2965CAC94B38B9993632E67317329712CE59C3A998E36CCA59533996564E38D9D1CC93A4D2633654D371A8 (326) [RAW]
[06:44:46][V][3of6:083]: Decode 3 out of 6 failed..
194

Ramka jest dekodowana poprawnie. Jak jest zgodna z tym co na wyswietlaczu watomierza masz to jest OK. Ja bym monitorowal czy i ktore wartosci sie zmieniaja i w razie problemow od razu do wlasciciela licznika uderzal z oficjalnym pismem.

196

Witam, a jaki konkretnie teraz ESP32 i CC1101 najlepiej nadają się do odczytu Apator-16-2?

197

Cześć wszystkim!
Mam problem z odczytem z licznika HYDRODIGIT S1, nie widzę w ogóle komunikatów ID.
Prosił bym o sprawdzenie czy wszystko dobrze podłączyłem. Moje ESP32 to:

image
image1298×675 114 KB

konfiguracja ESPHome

esphome:
  name: esp32-pir
  friendly_name: ESP32_PIR

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

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:
  level: DEBUG
# Enable Home Assistant API
api:
  encryption:
    key: "="

ota:
  - platform: esphome
    password: ""

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

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Esp32-Pir Fallback Hotspot"
    password: "cJ56fI3MpTch"

captive_portal:

time:
  platform: sntp

wmbus:
  all_drivers: True
  log_all: True
  mosi_pin: GPIO23
  miso_pin: GPIO19
  clk_pin:  GPIO18
  cs_pin:   GPIO1
  gdo0_pin: GPIO22
  gdo2_pin: GPIO21





uart:
  tx_pin: GPIO2
  rx_pin: GPIO15
  #baud_rate: 256000
  baud_rate: 115200
  parity: NONE
  stop_bits: 1

ld2420: 

text_sensor:
  - platform: ld2420
    fw_version:
      name: LD2420 Firmware

sensor:
  - platform: ld2420
    moving_distance:
      name : Moving Distance

binary_sensor:
  - platform: ld2420
    has_target:
      name: Presence

switch:
  - platform: restart
    name: Restart ESPHome Node

select:
  - platform: ld2420
    operating_mode:
      name: Operating Mode

number:
  - platform: ld2420
    presence_timeout:
      name: Detection Presence Timeout
    min_gate_distance:
      name: Detection Gate Minimum
    max_gate_distance:
      name: Detection Gate Maximum
    gate_select:
      name: Select Gate to Set
    still_threshold:
      name: Set Still Threshold Value
    move_threshold:
      name: Set Move Threshold Value
button:
  - platform: ld2420
    apply_config:
      name: Apply Config
    factory_reset:
      name: Factory Reset
    restart_module:
      name: Restart Module
    revert_config:
      name: Undo Edits

Do tego ESP mam podpięty jeszcze czujnik obecności, ale wydaje mi się że on nie przeszkadza, poprawcie mnie jeśli się mylę.

log:

INFO ESPHome 2025.2.2
INFO Reading configuration /config/esphome/esp32-pir.yaml...
INFO Detected timezone 'Europe/Warsaw'
WARNING GPIO2 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO15 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
INFO Starting log output from 192.168.1.33 using esphome API
INFO Successfully connected to esp32-pir @ 192.168.1.33 in 0.058s
INFO Successful handshake with esp32-pir @ 192.168.1.33 in 0.084s
[23:59:07][I][app:100]: ESPHome version 2025.2.2 compiled on Mar 19 2025, 23:54:56
[23:59:07][C][wifi:600]: WiFi:
[23:59:07][C][wifi:428]:   Local MAC: 14:2B:2F:C2:01:6C
[23:59:07][C][wifi:433]:   SSID: [redacted]
[23:59:07][C][wifi:436]:   IP Address: 192.168.1.33
[23:59:07][C][wifi:440]:   BSSID: [redacted]
[23:59:07][C][wifi:441]:   Hostname: 'esp32-pir'
[23:59:07][C][wifi:443]:   Signal strength: -45 dB ▂▄▆█
[23:59:07][C][wifi:447]:   Channel: 3
[23:59:07][C][wifi:448]:   Subnet: 255.255.255.0
[23:59:07][C][wifi:449]:   Gateway: 192.168.1.1
[23:59:07][C][wifi:450]:   DNS1: 192.168.1.1
[23:59:07][C][wifi:451]:   DNS2: 0.0.0.0
[23:59:07][C][logger:177]: Logger:
[23:59:07][C][logger:178]:   Max Level: DEBUG
[23:59:07][C][logger:179]:   Initial Level: DEBUG
[23:59:07][C][logger:181]:   Log Baud Rate: 115200
[23:59:07][C][logger:182]:   Hardware UART: UART0
[23:59:07][C][uart.arduino_esp32:151]: UART Bus 1:
[23:59:07][C][uart.arduino_esp32:152]:   TX Pin: GPIO2
[23:59:07][C][uart.arduino_esp32:153]:   RX Pin: GPIO15
[23:59:07][C][uart.arduino_esp32:155]:   RX Buffer Size: 256
[23:59:07][C][uart.arduino_esp32:157]:   Baud Rate: 115200 baud
[23:59:07][C][uart.arduino_esp32:158]:   Data Bits: 8
[23:59:07][C][uart.arduino_esp32:159]:   Parity: NONE
[23:59:07][C][uart.arduino_esp32:160]:   Stop bits: 1
[23:59:07][C][ld2420:068]: LD2420:
[23:59:07][C][ld2420:069]:   Firmware Version :  v1.5.9
[23:59:07][C][ld2420:070]: LD2420 Number:
[23:59:07][C][ld2420:072]: ld2420  Gate Timeout: 'Detection Presence Timeout'
[23:59:07][C][ld2420:072]: ld2420  Icon: 'mdi:timelapse'
[23:59:07][C][ld2420:072]: ld2420  Unit of Measurement: 's'
[23:59:07][C][ld2420:073]: ld2420  Gate Max Distance: 'Detection Gate Maximum'
[23:59:07][C][ld2420:073]: ld2420  Icon: 'mdi:motion-sensor'
[23:59:07][C][ld2420:073]: ld2420  Device Class: 'distance'
[23:59:07][C][ld2420:074]: ld2420  Gate Min Distance: 'Detection Gate Minimum'
[23:59:07][C][ld2420:074]: ld2420  Icon: 'mdi:motion-sensor'
[23:59:07][C][ld2420:074]: ld2420  Device Class: 'distance'
[23:59:07][C][ld2420:075]: ld2420  Gate Select: 'Select Gate to Set'
[23:59:07][C][ld2420:075]: ld2420  Icon: 'mdi:motion-sensor'
[23:59:07][C][ld2420:075]: ld2420  Device Class: 'distance'
[23:59:07][C][ld2420:077]: ld2420  Gate Move Threshold: 'Set Move Threshold Value'
[23:59:07][C][ld2420:077]: ld2420  Icon: 'mdi:motion-sensor'
[23:59:07][C][ld2420:078]: ld2420  Gate Still Threshold:: 'Set Still Threshold Value'
[23:59:07][C][ld2420:078]: ld2420  Icon: 'mdi:motion-sensor'
[23:59:07][C][ld2420:082]: ld2420  Apply Config: 'Apply Config'
[23:59:07][C][ld2420:082]: ld2420  Icon: 'mdi:restart-alert'
[23:59:07][C][ld2420:083]: ld2420  Revert Edits: 'Undo Edits'
[23:59:07][C][ld2420:083]: ld2420  Icon: 'mdi:restart'
[23:59:07][C][ld2420:084]: ld2420  Factory Reset: 'Factory Reset'
[23:59:07][C][ld2420:084]: ld2420  Icon: 'mdi:database'
[23:59:08][C][ld2420:085]: ld2420  Restart Module: 'Restart Module'
[23:59:08][C][ld2420:085]: ld2420  Icon: 'mdi:database'
[23:59:08][C][ld2420:087]: LD2420 Select:
[23:59:08][C][ld2420:088]: ld2420  Operating Mode 'Operating Mode'
[23:59:08][C][LD2420.text_sensor:011]: LD2420 TextSensor:
[23:59:08][C][LD2420.text_sensor:012]:   Firmware 'LD2420 Firmware'
[23:59:08][C][LD2420.text_sensor:012]:     Icon: 'mdi:chip'
[23:59:08][C][LD2420.sensor:011]: LD2420 Sensor:
[23:59:08][C][LD2420.sensor:012]:   Distance 'Moving Distance'
[23:59:08][C][LD2420.sensor:012]:     Device Class: 'distance'
[23:59:08][C][LD2420.sensor:012]:     State Class: ''
[23:59:08][C][LD2420.sensor:012]:     Unit of Measurement: 'cm'
[23:59:08][C][LD2420.sensor:012]:     Accuracy Decimals: 0
[23:59:08][C][LD2420.binary_sensor:011]: LD2420 BinarySensor:
[23:59:08][C][LD2420.binary_sensor:012]:   Presence 'Presence'
[23:59:08][C][LD2420.binary_sensor:012]:     Device Class: 'occupancy'
[23:59:08][C][restart:068]: Restart Switch 'Restart ESPHome Node'
[23:59:08][C][restart:070]:   Icon: 'mdi:restart'
[23:59:08][C][restart:091]:   Restore Mode: always OFF
[23:59:08][C][captive_portal:089]: Captive Portal:
[23:59:08][C][sntp:042]: SNTP Time:
[23:59:08][C][sntp:045]:   Server 0: '0.pool.ntp.org'
[23:59:08][C][sntp:045]:   Server 1: '1.pool.ntp.org'
[23:59:08][C][sntp:045]:   Server 2: '2.pool.ntp.org'
[23:59:08][C][mdns:116]: mDNS:
[23:59:08][C][mdns:117]:   Hostname: esp32-pir
[23:59:08][C][esphome.ota:073]: Over-The-Air updates:
[23:59:08][C][esphome.ota:074]:   Address: esp32-pir.local:3232
[23:59:08][C][esphome.ota:075]:   Version: 2
[23:59:08][C][esphome.ota:078]:   Password configured
[23:59:08][C][safe_mode:018]: Safe Mode:
[23:59:08][C][safe_mode:020]:   Boot considered successful after 60 seconds
[23:59:08][C][safe_mode:021]:   Invoke after 10 boot attempts
[23:59:08][C][safe_mode:023]:   Remain in safe mode for 300 seconds
[23:59:08][C][api:140]: API Server:
[23:59:08][C][api:141]:   Address: esp32-pir.local:6053
[23:59:08][C][api:143]:   Using noise encryption: YES
[23:59:08][C][wmbus:338]: wM-Bus v4.1.4-1.17.1-b8f4a945:
[23:59:08][C][wmbus:356]:   Chip ID: 6C01C22F2B14
[23:59:08][C][wmbus:358]:   CC1101 frequency: 868.950 MHz
[23:59:08][C][wmbus:359]:   CC1101 SPI bus:
[23:59:08][C][wmbus:363]:     MOSI Pin: GPIO23
[23:59:08][C][wmbus:364]:     MISO Pin: GPIO19
[23:59:08][C][wmbus:365]:     CLK Pin:  GPIO18
[23:59:08][C][wmbus:366]:     CS Pin:   GPIO1
[23:59:08][C][wmbus:367]:     GDO0 Pin: GPIO22
[23:59:08][C][wmbus:368]:     GDO2 Pin: GPIO21
[23:59:08][C][wmbus:374]:   Available drivers: wme5, weh_07, watertech, waterstarm, vario451mid, vario451, vario411, unknown, unismart, ultrimis, ultraheat, tsd2, topaseskr, supercom587, sontex868, sharky774, sharky, sensostar, rfmtx1, rfmamb, qwater, qualcosonic, qsmoke, qheat_55_us, qheat, qcaloric, q400, pollucomf, piigth, omnipower, nemo, munia, multical21, mkradio4a, mkradio4, mkradio3, minomess, microclima, lse_08, lse_07_17, lansenth, lansensm, lansenrp, lansenpu, lansendw, kampress, kamheat, izar, iwm
[23:59:08][D][sensor:094]: 'Moving Distance': Sending state 192.00000 cm with 0 decimals of accuracy
[23:59:09][D][sensor:094]: 'Moving Distance': Sending state 169.00000 cm with 0 decimals of accuracy
[23:59:10][D][sensor:094]: 'Moving Distance': Sending state 155.00000 cm with 0 decimals of accuracy
198

Wyrzuć wszystkie inne komponenty.
Gdy już będzie działać dodasz ponownie po jednym i wtedy się wyjaśni co może działać razem, a co nie, na moje oko radar może być zasobożerny.

I w ogóle to może wywalić zbędne sterowniki, skoro wiesz, że chcesz nasłuchiwać bmeters?

I jeszcze jedno - nie wiem czy logger (który standardowo pracuje na UART0 → GPIO1) nie gryzie się z pinem CS (może przerzucić CS w inne miejsce? lub ustawić mu prędkość 0)

1 Like