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

uhbiuhbi · 25 Grudzień 2024 16:20

Mój licznik w stoenie ma WMBUS wg informacji na obudowie:

Mam jednak problem następujący. Licznik nadaje ramki. Wg logów z wmbus readera (magic reader) odbiera komunikaty z kilku różnych liczników - każdy o długości 191 znaków (BE44ED…). Po długim oczekiwaniu dostałem ze Stoenu wiadomość z hasłem, ale niestety otrzymuję tylko taki błąd:
“2F2F check after decrypting !!!”
Hasło było w ASCII o długości 16 znaków, przerobiłem je na HEX.

Mam do Stoenu pisać o nowe hasło / reset licznika / reset wmbus’a? Macie jakiś pomysł?

Mhrok · 25 Grudzień 2024 17:56

Ustaw na odbiór telegramów na wmbus i pokaż kilka z nich. Może z wmbus mają tak samo dziko z szyfrowaniem, jak z P1. Czym odbierasz telegramy?

uhbiuhbi · 25 Grudzień 2024 18:42

Wrzucam link do logów. Wszystkie liczniki na klatce mają uruchomioną transmisję, więc jest trochę tych telegramów. Mój to 0x13876601.

Logi:
https://pastebin.com/YBEkSG4a

Do odbioru używam tego:
https://www.olx.pl/d/oferta/magic-reader-eth-czytnik-licznikow-wody-gazu-pradu-itp-ha-esphome-CID99-ID12dz3C.html

GSzabados · 26 Grudzień 2024 10:58

You are in the wrong topic for this kind of questions.

Ask it here:

Also, you can try to decode it here:

https://wmbusmeters.org/

And without your ESPHome configuration it is hard to tell, that you set your device to correctly decode.

_Szczepan · 26 Grudzień 2024 12:42

Co dokładnie zrobiłeś?

Klucze są w ASCII (w wielkim skrócie == odczytywalne przez człowieka) i takie się podaje do komponentu. A to że to jest reprezentacja HEXa to już jest sprawa drugorzędna.

Jedyna zabawa DEC-HEX występuje przy ID miernika.

btw
Pytaj sprzedawcy jak to skonfigurować, albo udostepnij wszystkie dane abyśmy mogli to odtworzyć a nie zgadywać.

minefield · 1 Styczeń 2025 12:32

Mam problem z czytaniem licznika Amiplus. Temat rozpocząłem już w wątku" Komponent wM-Bus do ESPHome (SzczepanLeon) wersja 3.x" Na urządzeniu “SIH-reader” czytało, potem czytało coraz rzadziej i w końcu przestało w ogóle odbierać ramki z Amiplus, jedynie z Izara (lecą moje i sąsiadów). Puściłem dezaktyawację HAN i aktywację, nic nie pomogło. Wróciłem do tematu gdy @_Szczepan wypuścił wersję 4.0. Zakupiłem od niego Ultimatereader i ta sama sytuacja, widzi Izary, logi lecą, że aż miło, z licznika Amiplus ni huhu. Napisałem do Taurona zlecili dezaktywację/aktywację i dostałem odpowiedź “Licznik działa prawidłowo. HAN aktywny” Ciśnąć dalej Taurona, czy coś źle robię?

INFO ESPHome 2024.10.0
INFO Detected timezone 'Europe/Warsaw'
WARNING GPIO37 is used by the PSRAM interface on ESP32-S3R8 / ESP32-S3R8V and should be avoided on these models
INFO Starting log output from 192.168.1.68 using esphome API
INFO Successfully connected to ultimatereader-5a1298 @ 192.168.1.68 in 0.121s
INFO Successful handshake with ultimatereader-5a1298 @ 192.168.1.68 in 0.008s
[11:29:24][I][app:100]: ESPHome version 2024.10.0 compiled on Dec 24 2024, 17:19:42
[11:29:24][I][app:102]: Project wmbus.UltimateReader version 1.2
[11:29:24][C][wifi:600]: WiFi:
[11:29:24][C][wifi:428]:   Local MAC: 34:B7:DA:5A:12:98
[11:29:24][C][wifi:433]:   SSID: [redacted]
[11:29:24][C][wifi:436]:   IP Address: 192.168.1.68
[11:29:24][C][wifi:440]:   BSSID: [redacted]
[11:29:24][C][wifi:441]:   Hostname: 'ultimatereader-5a1298'
[11:29:24][C][wifi:443]:   Signal strength: -64 dB ▂▄▆█
[11:29:24][C][wifi:447]:   Channel: 1
[11:29:24][C][wifi:448]:   Subnet: 255.255.255.0
[11:29:24][C][wifi:449]:   Gateway: 192.168.1.1
[11:29:24][C][wifi:450]:   DNS1: 192.168.1.1
[11:29:24][C][wifi:451]:   DNS2: 0.0.0.0
[11:29:24][C][logger:185]: Logger:
[11:29:24][C][logger:186]:   Level: DEBUG
[11:29:24][C][logger:188]:   Log Baud Rate: 115200
[11:29:24][C][logger:189]:   Hardware UART: USB_CDC
[11:29:24][C][uptime.sensor:033]: Uptime Sensor 'Ultimate Reader uptime'
[11:29:24][C][uptime.sensor:033]:   Device Class: 'duration'
[11:29:24][C][uptime.sensor:033]:   State Class: 'total_increasing'
[11:29:24][C][uptime.sensor:033]:   Unit of Measurement: 's'
[11:29:24][C][uptime.sensor:033]:   Accuracy Decimals: 0
[11:29:24][C][uptime.sensor:033]:   Icon: 'mdi:timer-outline'
[11:29:24][C][uptime.sensor:034]:   Type: Seconds
[11:29:24][C][psram:020]: PSRAM:
[11:29:24][C][psram:021]:   Available: YES
[11:29:24][C][psram:024]:   Size: 2047 KB
[11:29:24][C][homeassistant.time:010]: Home Assistant Time:
[11:29:24][C][homeassistant.time:011]:   Timezone: 'CET-1CEST,M3.5.0,M10.5.0/3'
[11:29:24][C][captive_portal:089]: Captive Portal:
[11:29:24][C][mdns:116]: mDNS:
[11:29:24][C][mdns:117]:   Hostname: ultimatereader-5a1298
[11:29:24][C][esphome.ota:073]: Over-The-Air updates:
[11:29:24][C][esphome.ota:074]:   Address: ultimatereader-5a1298.local:3232
[11:29:24][C][esphome.ota:075]:   Version: 2
[11:29:24][C][safe_mode:018]: Safe Mode:
[11:29:24][C][safe_mode:020]:   Boot considered successful after 60 seconds
[11:29:24][C][safe_mode:021]:   Invoke after 10 boot attempts
[11:29:24][C][safe_mode:023]:   Remain in safe mode for 300 seconds
[11:29:24][C][api:140]: API Server:
[11:29:24][C][api:141]:   Address: ultimatereader-5a1298.local:6053
[11:29:24][C][api:145]:   Using noise encryption: NO
[11:29:24][C][wmbus:557]: wM-Bus vSX4.2.0-1.17.1-b8f4a945:
[11:29:24][C][wmbus:570]:   LED:
[11:29:24][C][wmbus:571]:     Duration: 123 ms
[11:29:24][C][wmbus:574]:   Chip ID: 98125ADAB734
[11:29:24][C][wmbus:584]:   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
[11:29:26][I][wmbus:217]: izar [0x4131de85] RSSI: -104dBm T: 1944304C85DE3141CC01A2511600137FCCDF58B8FA9B1F78354D (26) T1 A
[11:29:30][I][wmbus:217]: izar [0x4131de8f] RSSI: -105dBm T: 1944304C8FDE3141CC01A231160013E85AA492426BB474CFA551 (26) T1 A
[11:29:35][I][wmbus:217]: izar [0x4131de85] RSSI: -112dBm T: 1944304C85DE3141CC01A2611600137FF5AE824598EF75151E4A (26) T1 A
[11:29:38][I][wmbus:217]: izar [0x4131de90] RSSI: -106dBm T: 1944304C90DE3141CC01A211160013347D4CE7DD716C7D7B6957 (26) T1 A
[11:29:38][I][wmbus:217]: izar [0x4131de8f] RSSI: -107dBm T: 1944304C8FDE3141CC01A241160013E83F686E138E8F79CEEA5C (26) T1 A
[11:29:39][I][wmbus:217]: izar [0x4131de8b] RSSI: -101dBm T: 1944304C8BDE3141CC01A261160013B4D27A9110F4EAD9EAA452 (26) T1 A
[11:29:43][I][wmbus:217]: izar [0x4131de85] RSSI: -106dBm T: 1944304C85DE3141CC01A2711600137FE281CBEEB93CACCE0748 (26) T1 A
[11:29:46][I][wmbus:217]: izar [0x4131de90] RSSI: -105dBm T: 1944304C90DE3141CC01A22116001334443D3D20131817164250 (26) T1 A
[11:29:47][I][wmbus:217]: izar [0x4131de8b] RSSI: -100dBm T: 1944304C8BDE3141CC01A271160013B4C555D8BBD5390031BD50 (26) T1 A
[11:29:47][I][wmbus:217]: izar [0x4131de8f] RSSI: -106dBm T: 1944304C8FDE3141CC01A251160013E8284727B8AF5CA015F35E (26) T1 A
[11:29:51][I][wmbus:217]: izar [0x4131de85] RSSI: -108dBm T: 1944304C85DE3141CC01A2011600137F874D37BF5C07A1CF4845 (26) T1 A
[11:29:54][I][wmbus:217]: izar [0x4131de90] RSSI: -102dBm T: 1944304C90DE3141CC01A231160013345312748B32CBCECD5B52 (26) T1 A
[11:29:55][I][wmbus:217]: izar [0x4131de8b] RSSI: -111dBm T: 1944304C8BDE3141CC01A201160013B4A09924EA30020D30F25D (26) T1 A
[11:29:56][I][wmbus:217]: izar [0x4131de8f] RSSI: -108dBm T: 1944304C8FDE3141CC01A261160013E81136FD45CD28CA78D859 (26) T1 A
[11:30:03][I][wmbus:217]: izar [0x4131de90] RSSI: -103dBm T: 1944304C90DE3141CC01A2411600133436DE88DAD7F0C3CC145F (26) T1 A
[11:30:04][I][wmbus:217]: izar [0x4131de8b] RSSI: -110dBm T: 1944304C8BDE3141CC01A211160013B4B7B66D4111D1D4EBEB5F (26) T1 A
[11:30:04][I][wmbus:217]: izar [0x4131de8f] RSSI: -110dBm T: 1944304C8FDE3141CC01A271160013E80619B4EEECFB13A3C15B (26) T1 A
[11:30:09][I][wmbus:217]: izar [0x4131de85] RSSI: -111dBm T: 1944304C85DE3141CC01A2211600137FA913A4E91FA012797A40 (26) T1 A
[11:30:11][I][wmbus:217]: izar [0x4131de90] RSSI: -101dBm T: 1944304C90DE3141CC01A2511600133421F1C171F6231A170D5D (26) T1 A
[11:30:13][I][wmbus:217]: izar [0x4131de8b] RSSI: -109dBm T: 1944304C8BDE3141CC01A221160013B48EC7B7BC73A5BE86C058 (26) T1 A
[11:30:13][I][wmbus:217]: izar [0x4131de8f] RSSI: -107dBm T: 1944304C8FDE3141CC01A201160013E863D548BF09C01EA28E56 (26) T1 A
[11:30:14][D][sensor:094]: 'Ultimate Reader uptime': Sending state 139179.73438 s with 0 decimals of accuracy
[11:30:16][D][time:051]: Synchronized time: 2025-01-01 11:30:16

_Szczepan · 1 Styczeń 2025 13:05

Możesz załączyć logi VERBOSE, ale pewnie nic więcej nie zobaczysz.
Skoro na paru urzadzeniach tak samo działa (nie działa Tauron), a UR i SIH są na innym sprzęcie i z troche innym kodem, jedyne co widze to “podsłuchanie” tunerem albo innym SDRem czy coś tam lata od Taurona i potem dręczenie ich że nie działa.

Jabol · 1 Styczeń 2025 13:57

@_Szczepan Cześć, a jest możliwosć zakupu od Ciebie gotowej płytki która współpracuje ze stacjami pogodowymi również?

_Szczepan · 1 Styczeń 2025 14:38

Nie mam pojęcia jaki kod wchodzi do obsługi tych stacji.

szopen · 1 Styczeń 2025 14:58

Ja znam tylko rozwiązanie (o ile mówimy o rozwiązaniach bezprzewodowych 433MHz lub 868MHz, ale nie lora) oparte na rtl_433, a wmbusmeters nie obsługuje żadnych stacji pogodowych, bo nie do tego służy. Wiem, że są też inne rozwiązania, niż rtl_433 ale z nich nigdy nie korzystałem.

Właściwie stacje pogodowe to są tak ustandaryzowane jak RF433 (czytaj: nie są), a to, że wiele modeli amatorskich stacji różnych brandów daje się odczytywać tymi samymi rozwiązaniami wynika tylko z faktu, że raczej ponad 90% sprzętu dostępnego na rynku pochodzi zaledwie od 3 chińskich producentów white-label.

madse · 7 Styczeń 2025 15:56

Dear Community,
wish all Happy New Year.

Inspired by SzczepanLeon´s esphome component I was wondering if the following would work.
Currently I´m looking for a solution to integrate a couple of UltraMaXX/UltraLite heat meters into Home-Assistent as well as into Grafana. Therefore I would attach “EquaScan hMIURF V2” wmbus module and receive telegrams via esp32 and cc1101 868MHz and publish to Mqtt.
The EquaScan hMIURF V2 as the following specs:
Protocol: Bidirectional EN 13757-3/-4 wireless M-BUS or unidirectional OMS V
Operating mode C2 Mode or C1
Frequency band Tx: 868,95 MHz / Rx: 869,525 MHz

My question would be is the itron heating meter is supported “out of the box”?
What would be required to write the driver-file for it?
or would be possible to generate the driver via xmq-file from here drivers/src/itronheat.xmq

Thank you very much in advance for your feedback.

_Szczepan · 7 Styczeń 2025 16:36

Should be if configured as C1 OMS.

First I would try existing drivers, maybe there is something similar. WMBusmeters Analyze Telegram

No, v3 and v4 are without xmq support.

madse · 8 Styczeń 2025 18:34

Thanks, @_Szczepan, for your feedback. I will start as you suggested. I am still waiting for the hardware, but I will keep you updated here.

Peter · 14 Styczeń 2025 14:08

Witam, mam problem z odczytywanie licznika energii amiplus. Jako czytnika używam Magic Reader-a z oprogramowaniem SzczepanLeon w wersji 4.0. Licznik który próbuje czytać wygląda jak na zdjęciu:

ID licznika + klucz ze strony tauron. Jest to już trzeci klucz, który próbuje tym razem amiplus zostało aktywowane przez Tauron, wcześniej robiłem to sam i efekt jest cały czas taki sam, że w logach dostaję informację o niepoprawnym kluczu. Może robie coś nie tak i ten klucz musi być podany w jakieś innej formie niż kopiuj wklej ze strony Tauronu?

Config licznika:

  - platform: wmbus
    meter_id: 0x86094804
    key: "################################"
    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"

Tutaj kawałki logów:

[14:19:34][I][wmbus:092]: Using selected driver amiplus (detected driver was amiplus)
[14:19:34][I][wmbus:104]: amiplus [0x86094804] RSSI: -90dBm T: 8E4401060448098602027A00008005630A7BD43C601EFBE8D53838C60C47C72A8C1CFF3233CB4E44CCEB8BF257BC50E0F112477B2B01C931516492FFACB4279E81569B0A1AE79954A696E7BA774B51999EEAD131C10D6CFA3DB29B65DD81154B8A50DEE8EBDBEAC427BF25487DAAE1A393EE430480E1E83A5A1B7BB75A63FFE41EBF21BD8B560049C7FDD6D8FDCD3C (143) T1 A
[14:19:34][D][meters.cpp:1985]: (meter) created ESPHome amiplus 86094804 encrypted
[14:19:34][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 143
[14:19:34][V][Telegram.cpp:1178]: (wmbus) parseELL @10 133
[14:19:34][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 133
[14:19:34][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 133
[14:19:34][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 133
[14:19:34][V][meters.cpp:635]: (meter) ESPHome: for me? 86094804.M=APA.V=02.T=02,86094804.M=APA.V=02.T=02 in 86094804
[14:19:34][V][meters.cpp:686]: (meter) ESPHome: yes for me
[14:19:34][D][meters.cpp:909]: (meter) ESPHome(0) amiplus  handling telegram from 86094804.M=APA.V=02.T=02
[14:19:34][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 143
[14:19:34][V][Telegram.cpp:545]: (telegram) DLL L=8e C=44 (from meter SND_NR) M=0601 (APA) A=86094804 VER=02 TYPE=02 (Electricity meter) (driver amiplus) DEV=ESPHome wM-Bus RSSI=-90
[14:19:34][V][Telegram.cpp:1178]: (wmbus) parseELL @10 133
[14:19:34][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 133
[14:19:34][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 133
[14:19:34][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 133
[14:19:34][V][Telegram.cpp:299]: (TPL) num encrypted blocks 8 (128 bytes and remaining unencrypted 0 bytes)
[14:19:34][V][Telegram.cpp:303]: (TPL) AES CBC IV decrypting
[14:19:34][V][Telegram.cpp:343]: (TPL) IV 01060448098602020000000000000000
[14:19:34][V][utils.cpp:823]: (TPL) decrypted  "015A81C90FF6F8D52DE6F6C6C6E96ED23ABC8AABED03515C9C1AB0091616434CEB9B24897CB668642D965724D6E51AFF7FD1F1F93005FF158A055A306F3378A4C62BCB1AC8F8161746FB4A3FEE54AD9BA36EB1032DC3D83072F9C8937C2FBF1C0C2E54580EB9DCD5C75A663E9A35DA3E354C67037B793A519481464D0A2471AF"
[14:19:34][W][Telegram.cpp:1832]: (wmbus) WARNING!! decrypted content failed check, did you use the correct decryption key? Permanently ignoring telegrams from id: 86094804 mfct: (APA) Apator, Poland (0x601) type: Electricity meter (0x02) ver: 0x02
[14:19:34][V][Telegram.cpp:634]: (telegram) TPL CI=7a
[14:19:34][V][Telegram.cpp:640]:  ACC=00 STS=00 CFG=0580 (AES_CBC_IV nb=8 cntn=0 ra=0 hc=0)
[14:19:34][W][wmbus:158]: Can't get proper unit from 'w'
[14:19:34][W][wmbus:154]: Can't get requested field 'total_energy_consumption_tariff_1' with unit 'kwh'
[14:19:34][W][wmbus:154]: Can't get requested field 'voltage_at_phase_1' with unit 'v'
[14:19:34][W][component:237]: Component wmbus took a long time for an operation (424 ms).
[14:19:34][W][component:238]: Components should block for at most 30 ms.

[14:23:04][I][wmbus:092]: Using selected driver amiplus (detected driver was amiplus)
[14:23:04][I][wmbus:104]: amiplus [0x86094804] RSSI: -91dBm T: 8E4401060448098602027A00008005EA426081135504A23505ADA0B643BDC51D99E64F1DC79D0B90A162E77570F984EF2EF40B03F6A3C6AC205AC1158CB0DB22E4D7C3F0827550E5EB42945EB770EDC7319A8AEA49F21C5E048EA9F128B49B2A1DDACAF3C20AA342BFA24FFF3D2CE1E81693C600E493F02BA130A0B1353AF92B5D59B4305B03D315693F28D97D7308 (143) T1 A
[14:23:04][D][meters.cpp:1985]: (meter) created ESPHome amiplus 86094804 encrypted
[14:23:04][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 143
[14:23:04][V][Telegram.cpp:1178]: (wmbus) parseELL @10 133
[14:23:04][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 133
[14:23:04][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 133
[14:23:04][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 133
[14:23:04][V][meters.cpp:635]: (meter) ESPHome: for me? 86094804.M=APA.V=02.T=02,86094804.M=APA.V=02.T=02 in 86094804
[14:23:04][V][meters.cpp:686]: (meter) ESPHome: yes for me
[14:23:04][D][meters.cpp:909]: (meter) ESPHome(0) amiplus  handling telegram from 86094804.M=APA.V=02.T=02
[14:23:04][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 143
[14:23:04][V][Telegram.cpp:545]: (telegram) DLL L=8e C=44 (from meter SND_NR) M=0601 (APA) A=86094804 VER=02 TYPE=02 (Electricity meter) (driver amiplus) DEV=ESPHome wM-Bus RSSI=-91
[14:23:04][V][Telegram.cpp:1178]: (wmbus) parseELL @10 133
[14:23:04][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 133
[14:23:04][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 133
[14:23:04][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 133
[14:23:04][V][Telegram.cpp:299]: (TPL) num encrypted blocks 8 (128 bytes and remaining unencrypted 0 bytes)
[14:23:04][V][Telegram.cpp:303]: (TPL) AES CBC IV decrypting
[14:23:04][V][Telegram.cpp:343]: (TPL) IV 01060448098602020000000000000000
[14:23:04][V][utils.cpp:823]: (TPL) decrypted  "3D8A6CDE37B54B43139822FBC7197EEF74E917DFA7D095E8A0A5EE13BCFAEB8C702F3A060CA7FBD833E2BE986B6795F5F674ECEDD4A27055E49BAC31156FC626CC98F6DF763460719D784CCA0739E1CB5670337B4D0F70562E86ED0B4F26E2030485B9C90DE66005947802465974004333EB666C980D97465BB4156DCC6C5E09"
[14:23:04][W][Telegram.cpp:1832]: (wmbus) WARNING!! decrypted content failed check, did you use the correct decryption key? Permanently ignoring telegrams from id: 86094804 mfct: (APA) Apator, Poland (0x601) type: Electricity meter (0x02) ver: 0x02
[14:23:04][V][Telegram.cpp:634]: (telegram) TPL CI=7a
[14:23:04][V][Telegram.cpp:640]:  ACC=00 STS=00 CFG=0580 (AES_CBC_IV nb=8 cntn=0 ra=0 hc=0)
[14:23:04][W][wmbus:158]: Can't get proper unit from 'w'
[14:23:04][W][wmbus:154]: Can't get requested field 'total_energy_consumption_tariff_1' with unit 'kwh'
[14:23:04][W][wmbus:154]: Can't get requested field 'voltage_at_phase_1' with unit 'v'
[14:23:04][W][component:237]: Component wmbus took a long time for an operation (432 ms).
[14:23:04][W][component:238]: Components should block for at most 30 ms.

Dodam jeszcze, że bez problemu czytam dwa liczniki wody apator162, tym samym zestawem.

Będą wdzięczny za jakaś podpowiedź co robię nie tak.

Peter · 14 Styczeń 2025 20:07

Wygląda na to, że udało mi się dojść do rozwiązania (w końcu!). Klucz na stronie licznik Tauron jest zapisany w formacie BIG ENDIAN, po jego konwersji do LITTLE ENDIAN ramki dekodują się już bez problemu.

Także dla potomnych licznik od Taurona - Apator smartEMU 3 wymaga konwersji klucza do LITTLE ENDIAN.

Po zdekodowaniu można z niego czytać takie dane:

  "_":"telegram",
    "media":"electricity",
    "meter":"amiplus",
    "name":"",
    "id":"86094804",
    "current_power_consumption_kw":0.226,
    "current_power_production_kw":0,
    "max_power_consumption_kw":5.216,
    "total_energy_consumption_tariff_1_kwh":4207.764,
    "total_energy_consumption_tariff_2_kwh":0,
    "total_energy_consumption_tariff_3_kwh":0,
    "total_energy_production_tariff_1_kwh":0.595,
    "total_energy_production_tariff_2_kwh":0,
    "total_energy_production_tariff_3_kwh":0,
    "voltage_at_phase_1_v":236,
    "voltage_at_phase_2_v":236,
    "voltage_at_phase_3_v":236,
    "device_date_time":"2025-01-14 14:19:30",
    "timestamp":"2025-01-14T18:32:47Z"

beteem · 29 Styczeń 2025 20:27

Dobry wieczór Grupo!
Udało mi się dodać licznik do HA, bardzo prosze o sprawdzenie logów, ponieważ chyba nie do końca wszystko jest dobrze

INFO ESPHome 2024.12.4
INFO Reading configuration /config/esphome/liczniki.yaml...
INFO Updating https://github.com/SzczepanLeon/esphome-components.git@main
INFO Detected timezone 'Europe/Warsaw'
WARNING GPIO5 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 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
INFO Starting log output from 192.168.1.122 using esphome API
INFO Successfully connected to liczniki @ 192.168.1.122 in 0.012s
INFO Successful handshake with liczniki @ 192.168.1.122 in 0.161s
[21:21:14][I][app:100]: ESPHome version 2024.12.4 compiled on Jan 29 2025, 21:11:02
[21:21:14][C][wifi:600]: WiFi:
[21:21:14][C][wifi:428]:   Local MAC: CC:7B:5C:24:FD:B4
[21:21:14][C][wifi:433]:   SSID: [redacted]
[21:21:14][C][wifi:436]:   IP Address: 192.168.1.122
[21:21:14][C][wifi:440]:   BSSID: [redacted]
[21:21:14][C][wifi:441]:   Hostname: 'liczniki'
[21:21:14][C][wifi:443]:   Signal strength: -48 dB ▂▄▆█
[21:21:14][V][wifi:445]:   Priority: 0.0
[21:21:14][C][wifi:447]:   Channel: 6
[21:21:14][C][wifi:448]:   Subnet: 255.255.255.0
[21:21:14][C][wifi:449]:   Gateway: 192.168.1.1
[21:21:14][C][wifi:450]:   DNS1: 208.67.222.222
[21:21:14][C][wifi:451]:   DNS2: 208.67.220.220
[21:21:14][C][logger:185]: Logger:
[21:21:14][C][logger:186]:   Level: VERY_VERBOSE
[21:21:14][C][logger:188]:   Log Baud Rate: 115200
[21:21:14][C][logger:189]:   Hardware UART: UART0
[21:21:14][C][captive_portal:089]: Captive Portal:
[21:21:14][C][sntp:042]: SNTP Time:
[21:21:14][C][sntp:045]:   Server 0: '0.pool.ntp.org'
[21:21:14][C][sntp:045]:   Server 1: '1.pool.ntp.org'
[21:21:14][C][sntp:045]:   Server 2: '2.pool.ntp.org'
[21:21:14][C][mdns:116]: mDNS:
[21:21:14][C][mdns:117]:   Hostname: liczniki
[21:21:14][V][mdns:118]:   Services:
[21:21:14][V][mdns:120]:   - _esphomelib, _tcp, 6053
[21:21:14][V][mdns:122]:     TXT: network = wifi
[21:21:14][V][mdns:122]:     TXT: api_encryption = Noise_NNpsk0_25519_ChaChaPoly_SHA256
[21:21:14][C][esphome.ota:073]: Over-The-Air updates:
[21:21:14][C][esphome.ota:074]:   Address: liczniki.local:3232
[21:21:14][C][esphome.ota:075]:   Version: 2
[21:21:14][C][esphome.ota:078]:   Password configured
[21:21:14][C][safe_mode:018]: Safe Mode:
[21:21:14][C][safe_mode:020]:   Boot considered successful after 60 seconds
[21:21:14][C][safe_mode:021]:   Invoke after 10 boot attempts
[21:21:14][C][safe_mode:023]:   Remain in safe mode for 300 seconds
[21:21:14][C][api:140]: API Server:
[21:21:14][C][api:141]:   Address: liczniki.local:6053
[21:21:14][C][api:143]:   Using noise encryption: YES
[21:21:14][C][wmbus:338]: wM-Bus v4.1.1-1.17.1-b8f4a945:
[21:21:14][C][wmbus:356]:   Chip ID: B4FD245C7BCC
[21:21:14][C][wmbus:358]:   CC1101 frequency: 868.950 MHz
[21:21:14][C][wmbus:359]:   CC1101 SPI bus:
[21:21:14][C][wmbus:363]:     MOSI Pin: GPIO23
[21:21:14][C][wmbus:364]:     MISO Pin: GPIO19
[21:21:14][C][wmbus:365]:     CLK Pin:  GPIO18
[21:21:14][C][wmbus:366]:     CS Pin:   GPIO5
[21:21:14][C][wmbus:367]:     GDO0 Pin: GPIO2
[21:21:14][C][wmbus:368]:     GDO2 Pin: GPIO4
[21:21:14][C][wmbus:374]:   Available drivers: unknown, apator162
[21:21:14][C][wmbus:388]:   Meter:
[21:21:14][C][wmbus:389]:     ID: 1128041 [0x00113669]
[21:21:14][C][wmbus:390]:     Type: apator162
[21:21:14][C][wmbus:391]:     Key: '00000000000000000000000000000000'
[21:21:14][C][wmbus:393]:     Field: 'rssi'
[21:21:14][C][wmbus:394]:      Name: 'RSSi kuchnia'
[21:21:14][C][wmbus:394]:        Device Class: 'signal_strength'
[21:21:14][C][wmbus:394]:        State Class: 'measurement'
[21:21:14][C][wmbus:394]:        Unit of Measurement: 'dBm'
[21:21:14][C][wmbus:394]:        Accuracy Decimals: 0
[21:21:14][C][wmbus:393]:     Field: 'total'
[21:21:14][C][wmbus:394]:      Name: 'zużycie kuchnia'
[21:21:14][C][wmbus:394]:        Device Class: 'water'
[21:21:14][C][wmbus:394]:        State Class: 'total_increasing'
[21:21:14][C][wmbus:394]:        Unit of Measurement: 'm³'
[21:21:14][C][wmbus:394]:        Accuracy Decimals: 3
[21:21:14][C][wmbus:394]:        Icon: 'mdi:water'
[21:21:14][C][wmbus:388]:   Meter:
[21:21:14][C][wmbus:389]:     ID: 6316343 [0x00606137]
[21:21:14][C][wmbus:390]:     Type: apator162
[21:21:14][C][wmbus:391]:     Key: '00000000000000000000000000000000'
[21:21:14][C][wmbus:393]:     Field: 'rssi'
[21:21:14][C][wmbus:394]:      Name: 'RSSi łazienka'
[21:21:14][C][wmbus:394]:        Device Class: 'signal_strength'
[21:21:14][C][wmbus:394]:        State Class: 'measurement'
[21:21:14][C][wmbus:394]:        Unit of Measurement: 'dBm'
[21:21:14][C][wmbus:394]:        Accuracy Decimals: 0
[21:21:14][C][wmbus:393]:     Field: 'total'
[21:21:14][C][wmbus:394]:      Name: 'zużycie łazienka'
[21:21:14][C][wmbus:394]:        Device Class: 'water'
[21:21:14][C][wmbus:394]:        State Class: 'total_increasing'
[21:21:14][C][wmbus:394]:        Unit of Measurement: 'm³'
[21:21:14][C][wmbus:394]:        Accuracy Decimals: 3
[21:21:14][C][wmbus:394]:        Icon: 'mdi:water'
[21:21:29][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=526366 (now=586366)
[21:21:31][VV][api.service:697]: on_ping_request: PingRequest {}
[21:21:31][VV][api.service:043]: send_ping_response: PingResponse {}
[21:21:54][VV][api.service:697]: on_ping_request: PingRequest {}
[21:21:54][VV][api.service:043]: send_ping_response: PingResponse {}
[21:22:11][VV][api.service:697]: on_ping_request: PingRequest {}
[21:22:11][VV][api.service:043]: send_ping_response: PingResponse {}
[21:22:29][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=586366 (now=646366)
[21:22:51][VV][api.service:697]: on_ping_request: PingRequest {}
[21:22:51][VV][api.service:043]: send_ping_response: PingResponse {}
[21:22:54][VV][api.connection:133]: Sending keepalive PING...
[21:22:54][VV][api.service:037]: send_ping_request: PingRequest {}
[21:22:54][VV][api.service:706]: on_ping_response: PingResponse {}
[21:23:29][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=646366 (now=706366)
[21:23:31][VV][api.service:697]: on_ping_request: PingRequest {}
[21:23:31][VV][api.service:043]: send_ping_response: PingResponse {}
[21:23:31][V][rxLoop:167]: Have 191 bytes from CC1101 Rx, RSSI: -33 dBm LQI: 128
[21:23:31][V][rxLoop:172]: Synchronus mode enabled.
[21:23:31][D][mbus:035]: Received T1 A frame
[21:23:31][V][mbus:046]: Frame: 6B271C58D59A2D368D69659659959338D94D4E6996596696B19D0B68E65A3A6D2C6A9593B0B4D62CD4F4C5934B73165A2E5C5C34E2F1A4B4EC5A6C5368D9A68CB5AC96C4EC99C674C9958D4DA3636B198B64E8E58D32E6731D16716A72CAC6639722CB996B192E6663353B167298D65936AC2CB39C3654F15964CD399D2CD1A96337169CC66B0B65A35CA6638B8E65939A566CC6CCB23B2A595A3C9C353C719A98E3D2958B35C58E37195CC8BC4BCB4659969A5A6B1B233A664B5AC98ED0B5 (191) [RAW]
[21:23:31][VV][3of6:095]: Decode 3 out of 6 OK.
[21:23:31][V][mbus:053]: Frame: 6E44010637616000050721917AA0006085C362562AC86F078370317CD5134D5639D4123DF3780AD761AAB3089878A45CE501761B6DA352B9B73A4DC040FEE85B9E33A0853A5B17804FB007683324197D007125C8C69B1D64DA835614FA23BA07A958D8EE2EF50BE417DDAFBBCF0314021D94E3D3EC559FF66D8B2A5308A2C3 (127) [with CRC]
[21:23:31][V][mbus:096]: Validating CRC for Block1
[21:23:31][V][crc:031]:     calculated: 0x2191, read: 0x2191
[21:23:31][V][mbus:116]: Validating CRC for Block2
[21:23:31][V][crc:031]:     calculated: 0xD513, read: 0xD513
[21:23:31][V][mbus:116]: Validating CRC for Block3
[21:23:31][V][crc:031]:     calculated: 0xA45C, read: 0xA45C
[21:23:31][V][mbus:116]: Validating CRC for Block4
[21:23:31][V][crc:031]:     calculated: 0x9E33, read: 0x9E33
[21:23:31][V][mbus:116]: Validating CRC for Block5
[21:23:31][V][crc:031]:     calculated: 0x25C8, read: 0x25C8
[21:23:32][V][mbus:116]: Validating CRC for Block6
[21:23:32][V][crc:031]:     calculated: 0x2EF5, read: 0x2EF5
[21:23:32][V][mbus:116]: Validating CRC for Block7
[21:23:32][V][crc:031]:     calculated: 0x9FF6, read: 0x9FF6
[21:23:32][V][mbus:116]: Validating CRC for Block8
[21:23:32][V][crc:031]:     calculated: 0xA2C3, read: 0xA2C3
[21:23:32][V][mbus:063]: Frame: 6E4401063761600005077AA0006085C362562AC86F078370317C4D5639D4123DF3780AD761AAB3089878E501761B6DA352B9B73A4DC040FEE85BA0853A5B17804FB007683324197D0071C69B1D64DA835614FA23BA07A958D8EE0BE417DDAFBBCF0314021D94E3D3EC556D8B2A5308 (111) [without CRC]
[21:23:32][VV][wmbus:056]: Have data from RF ...
[21:23:32][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 111
[21:23:32][V][Telegram.cpp:1178]: (wmbus) parseELL @10 101
[21:23:32][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 101
[21:23:32][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 101
[21:23:32][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 101
[21:23:32][I][wmbus:092]: Using selected driver apator162 (detected driver was apator162)
[21:23:32][I][wmbus:104]: apator162 [0x00606137] RSSI: -33dBm T: 6E4401063761600005077AA0006085C362562AC86F078370317C4D5639D4123DF3780AD761AAB3089878E501761B6DA352B9B73A4DC040FEE85BA0853A5B17804FB007683324197D0071C69B1D64DA835614FA23BA07A958D8EE0BE417DDAFBBCF0314021D94E3D3EC556D8B2A5308 (111) T1 A
[21:23:32][D][meters.cpp:1985]: (meter) created ESPHome apator162 00606137 encrypted
[21:23:32][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 111
[21:23:32][V][Telegram.cpp:1178]: (wmbus) parseELL @10 101
[21:23:32][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 101
[21:23:32][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 101
[21:23:32][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 101
[21:23:32][V][meters.cpp:635]: (meter) ESPHome: for me? 00606137.M=APA.V=05.T=07,00606137.M=APA.V=05.T=07 in 00606137
[21:23:32][V][meters.cpp:686]: (meter) ESPHome: yes for me
[21:23:32][D][meters.cpp:909]: (meter) ESPHome(0) apator162  handling telegram from 00606137.M=APA.V=05.T=07
[21:23:32][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 111
[21:23:32][V][Telegram.cpp:545]: (telegram) DLL L=6e C=44 (from meter SND_NR) M=0601 (APA) A=00606137 VER=05 TYPE=07 (Water meter) (driver apator162) DEV=ESPHome wM-Bus RSSI=-33
[21:23:32][V][Telegram.cpp:1178]: (wmbus) parseELL @10 101
[21:23:32][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 101
[21:23:32][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 101
[21:23:32][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 101
[21:23:32][V][Telegram.cpp:299]: (TPL) num encrypted blocks 6 (96 bytes and remaining unencrypted 0 bytes)
[21:23:32][V][Telegram.cpp:303]: (TPL) AES CBC IV decrypting
[21:23:32][V][Telegram.cpp:343]: (TPL) IV 0106376160000507A0A0A0A0A0A0A0A0
[21:23:32][V][utils.cpp:823]: (TPL) decrypted  "2F2F0F38BD61990E0200435C05814B5B0B685B21FF41010010978701007B01898701005C8701001F84010004800100437C010029780100B8720100536E0100A969010096650100116101005C5D0100A0E2EED903FFFFFFFFFFFFFFFFFFFFDFFA"
[21:23:32][V][Telegram.cpp:634]: (telegram) TPL CI=7a
[21:23:32][V][Telegram.cpp:640]:  ACC=a0 STS=00 CFG=8560 (bidirectional AES_CBC_IV nb=6 cntn=0 ra=0 hc=0)
[21:23:32][V][meters.cpp:966]: (meters) skipping field without matcher total(Volume)[0]...
[21:23:32][V][sensor:043]: 'RSSi łazienka': Received new state -33.000000
[21:23:32][D][sensor:094]: 'RSSi łazienka': Sending state -33.00000 dBm with 0 decimals of accuracy
[21:23:32][VV][api.service:140]: send_sensor_state_response: SensorStateResponse {
  key: 2225515433
  state: -33
  missing_state: NO
}
[21:23:32][V][sensor:043]: 'zużycie łazienka': Received new state 100.247002
[21:23:32][VV][sensor.filter:014]: Filter(0x3ffb137c)::input(100.247002)
[21:23:32][VV][sensor.filter:021]: Filter(0x3ffb137c)::output(85.712006) -> SENSOR
[21:23:32][D][sensor:094]: 'zużycie łazienka': Sending state 85.71201 m³ with 3 decimals of accuracy
[21:23:32][VV][api.service:140]: send_sensor_state_response: SensorStateResponse {
  key: 777016352
  state: 85.712
  missing_state: NO
}
[21:23:32][W][component:237]: Component wmbus took a long time for an operation (525 ms).
[21:23:32][W][component:238]: Components should block for at most 30 ms.
[21:23:54][VV][api.connection:133]: Sending keepalive PING...
[21:23:54][VV][api.service:037]: send_ping_request: PingRequest {}
[21:23:54][VV][api.service:706]: on_ping_response: PingResponse {}
[21:24:11][VV][api.service:697]: on_ping_request: PingRequest {}
[21:24:11][VV][api.service:043]: send_ping_response: PingResponse {}
[21:24:29][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=706366 (now=766367)

_Szczepan · 29 Styczeń 2025 20:48

Ja tam widze że łazienka jest OK.

beteem · 29 Styczeń 2025 21:17

Szczepan, a te:

[22:15:09][V][3of6:083]: Decode 3 out of 6 failed..
...
[22:16:46][V][mbus:053]: Frame: 6E44010637616000050721917AAB006085CD095472CAF6198BF858AC56FA51C5072FFEA9E268C5FA694587F19583BD819A6BF77B75504748FE99ACB08F734C5BA5D63298D7B92898442B444B13138F2CD0E7D3005EE7A9C2C78CB73470AFDD5C231C0E6C4C2B34E11C6BC2A57DAA435F5809152E9133C770DBDE7C5E9BEB5D (127) [with CRC]
[22:16:47][V][mbus:096]: Validating CRC for Block1
[22:16:47][V][crc:031]:     calculated: 0x2191, read: 0x2191
[22:16:47][V][mbus:116]: Validating CRC for Block2
[22:16:47][V][crc:031]:     calculated: 0x56FA, read: 0x56FA
[22:16:47][V][mbus:116]: Validating CRC for Block3
[22:16:47][V][crc:031]:     calculated: 0xBD81, read: 0xBD81
[22:16:47][V][mbus:116]: Validating CRC for Block4
[22:16:47][V][crc:031]:     calculated: 0xA5D6, read: 0xA5D6
[22:16:47][V][mbus:116]: Validating CRC for Block5
[22:16:47][V][crc:031]:     calculated: 0xD300, read: 0xD300
[22:16:47][V][mbus:116]: Validating CRC for Block6
[22:16:47][V][crc:031]:     calculated: 0x4C2B, read: 0x4C2B
[22:16:47][V][mbus:116]: Validating CRC for Block7
[22:16:47][V][crc:031]:     calculated: 0xC770, read: 0xC770
[22:16:47][V][mbus:116]: Validating CRC for Block8
[22:16:47][V][crc:031]:     calculated: 0xEB5D, read: 0xEB5D
...
[22:16:47][W][component:237]: Component wmbus took a long time for an operation (538 ms).
[22:16:47][W][component:238]: Components should block for at most 30 ms.

[edit]
czepiam się?

szopen · 29 Styczeń 2025 21:44

Jeśli wszystko co Cię interesuje działa to zmniejsz poziom logowania, bo już go nie potrzebujesz ustawionego na tak dokładne informacje.

telegram
https://wmbusmeters.org/analyze/6E44010637616000050721917AAB006085CD095472CAF6198BF858AC56FA51C5072FFEA9E268C5FA694587F19583BD819A6BF77B75504748FE99ACB08F734C5BA5D63298D7B92898442B444B13138F2CD0E7D3005EE7A9C2C78CB73470AFDD5C231C0E6C4C2B34E11C6BC2A57DAA435F5809152E9133C770DBDE7C5E9BEB5D
jest zaszyfrowany, więc tu mimo prawidłowego CRC bez poprawnego klucza raczej sukcesu nie będzie.

a nie, sorry, nie zauważyłem że masz klucz same zera
https://wmbusmeters.org/analyze/6e44010637616000050721917aaB006085cd095472caf6198Bf858ac56fa51c5072ffea9e268c5fa694587f19583Bd819a6Bf77B75504748fe99acB08f734c5Ba5d63298d7B92898442B444B13138f2cd0e7d3005ee7a9c2c78cB73470afdd5c231c0e6c4c2B34e11c6Bc2a57daa435f5809152e9133c770dBde7c5e9BeB5d:auto:0000000000000000

_Szczepan · 29 Styczeń 2025 21:54

Masz odczyty w HA? To działa. Nie masz to nie działa?