No Yaml jest ten sam nie zmieniłem nic.
jeśli w YAML realnie masz arduino a nie esp-idf, to w głównym menu dashboardu Buildera CLEAN ALL
i nie sądzę, że beta Buildera może pomóc, raczej zaszkodzi.
I jeszcze wróćmy do tematu walidacji - walidator to jest TYLKO linter,
a linter sprawdza TYLKO I WYŁĄCZNIE poprawność składniową
(więc można stworzyć YAMLa poprawnego składniowo, który za chiny ludowe się nie skompiluje)
Walidacja jest po to by uniknąć czasochłonnej kompilacji w przypadku, gdy masz YAMLa niepoprawnego składniowo (bo wtedy parser nie zbuduje poprawnego kodu żródłowego C++).
1 polubienie
masz racje tutaj wkleiłem arduino a miałem wpisane esp-idf.
Właśnie zmieniam na arduino i zobaczymy.
CO ty tu ZROBIŁEŚ???
Zrób Clean All masz jakieś problemy z frameworkami. Clean build Files czasem nie wystarcza gdy błąd dotyczy narzędzi kompilatora.
1 polubienie
Dobra od instalowałem wszystko. Zainstalowałem ESP na nowo i z poniższym plikiem yaml się skompilowało i poszło.
Dziękuję wszystkim za pomoc.
esphome:
name: licznik-wody-full
friendly_name: Licznik_Wody_FULL
esp32:
board: esp32dev
framework:
type: arduino
# Enable logging
logger:
level: DEBUG
# Enable Home Assistant API
api:
encryption:
key: "xxxxx"
ota:
- platform: esphome
password: "xxxxx"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Licznik-Wody-Full"
password: "BDRj2FkAeJYI"
captive_portal:
time:
platform: sntp
id: time_sntp
external_components:
- source: github://SzczepanLeon/esphome-components@version_4
components: [ wmbus ]
wmbus:
mosi_pin: GPIO23
miso_pin: GPIO19
clk_pin: GPIO18
cs_pin: GPIO15
gdo0_pin: GPIO4
gdo2_pin: GPIO27
all_drivers: False
log_all: False
sensor:
- platform: wmbus
meter_id: 0x12345678
type: apator162
key: "00000000000000000000000000000000"
sensors:
- name: "Licznik_wody_RSSI"
field: "rssi"
accuracy_decimals: 0
unit_of_measurement: "dBm"
device_class: "signal_strength"
state_class: "measurement"
entity_category: "diagnostic"
- name: "Licznik_wody_Full"
field: "total"
accuracy_decimals: 3
unit_of_measurement: "m³"
device_class: "water"
state_class: "total_increasing"
icon: "mdi:water"
Mam problem jedynie z odczytywaniem danych ale to już raczej problem z samym modułem CC1101. Poprawie luty lub polutuje następny.
Kwestie techniczne takie jak poprawność połączenia MCU z radiem, czy w ogóle poprawność działania samego komponentu w aktualnym ESPHome, są poza zakresem moich odpowiedzi wyżej (bez sprzętu to jest dla mnie niesprawdzalne).
Jeśli chodzi o pierwsze, to piny GDOxx traktuj jak piny xx z tamtego posta bo radio masz inne, ale założenia są zbliżone (tam wyszedłem z założeń użycia domyślnych pinów dla danej magistrali SPI oraz jako xx dowolnego niekolidującego pinu mającego obsługę przerwań).
1 polubienie
Cześć,
po ostatnich aktualizacjach (włączenie z ESP na 2026.1), przestały mi odpowiadać ESP z modułami wmbus Szczepana. Mam je na WT32-ETH01.
Walczyłem kilka dni, mam wersję 4, na radiu CC1101. Metodą prób i błędów dotarłem do momentu, gdzie poniższy kod po instalacji już się nie odpala.
esphome:
name: rack
friendly_name: RACK
esp32:
board: esp32dev
framework:
type: arduino
external_components:
- source: github://SzczepanLeon/esphome-components@version_4
refresh: 0d
components: [ wmbus ]
logger:
level: VERY_VERBOSE
api:
encryption:
key: !secret api_password_esphome
ota:
- platform: esphome
password: !secret ota_password
time:
- platform: sntp
id: time_sntp
ethernet:
type: LAN8720
mdc_pin: GPIO23
mdio_pin: GPIO18
# clk_mode: GPIO0_IN
clk:
pin: GPIO0
mode: CLK_EXT_IN
phy_addr: 1
power_pin: GPIO16
manual_ip:
static_ip: 192.168.0.56
gateway: 192.168.0.1
subnet: 255.255.255.0
wmbus:
mosi_pin: GPIO12 #
miso_pin: GPIO35 # INPUT
clk_pin: GPIO14 #
cs_pin: GPIO15 #
gdo0_pin: GPIO36 #INPUT
gdo2_pin: GPIO39 #INPUT
# frequency: 868.950
# all_drivers: False
# sync_mode: True
# log_all: True
# clients:
# - name: wmbusmeters_udp
# ip_address: 192.168.0.150
# port: 9022
# format: RTLWMBUS
# transport: TCP
INFO ESPHome 2026.1.5
INFO Reading configuration /config/esphome/rack.yaml...
INFO Detected timezone 'Europe/Warsaw'
WARNING GPIO0 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/#why-am-i-getting-a-warning-about-strapping-pins
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/#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/#why-am-i-getting-a-warning-about-strapping-pins
INFO Starting log output from 192.168.0.56 using esphome API
INFO Successfully resolved rack @ 192.168.0.56 in 0.000s
WARNING Can't connect to ESPHome API for rack @ 192.168.0.56: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.0.56', port=6053))]: [Errno 111] Connect call failed ('192.168.0.56', 6053) (SocketAPIError)
INFO Trying to connect to rack @ 192.168.0.56 in the background
Po zakomentowaniu sekcji wmbus, gdzie są zdefiniowane piny, moduł wstaje. Próbowałem kompiliwać na poprzednich wersjach ESP Home, 2025.6 oraz 2025.11 - różne błędy ale na żadnym nie wstało. Czy ktoś miał taki problem lub zna rozwiązanie? Albo podpowie w którą stronę iść? Już nie mam pomysłów…
Cześć,
mam kilka wodomierzy z nakładkami Apator 16-2, które monitoruje, wykorzystując kilka MAGIC READER od @Mariusz_Woszczyński
Z uwagi na to, że zaszła potrzeba dodania kolejnych wodomierzy do mojego HA musiałem zmienić konfiguracje i musiałem zaktualizować dawno nie ruszany EspHome. Przeszedłem na najnowszą wersję 2026.2.1, MagicReader próbuje uruchomić jako v4. Niestety nie mogę pozbyć się błędów wyświetlanych na czerwono:
Check connection to CC1101!
i
wmbus is marked FAILED: unspecified
Poniżej mój kod:
esphome:
name: mojdom
friendly_name: MojDom
esp32:
board: esp32dev
framework:
type: arduino
# Enable logging
logger:
level: DEBUG
# Enable Home Assistant API
api:
encryption:
key: "????+qXy9cU="
ota:
- platform: esphome
password: "????"
wifi:
ssid: Dom1SiecTechniczna
password: ?????
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Mojdom Fallback Hotspot"
password: "????????"
captive_portal:
time:
- platform: sntp
id: time_sntp
external_components:
- source: github://SzczepanLeon/esphome-components@version_4
refresh: 0d
components: [ wmbus ]
wmbus:
frequency: 868.950
mosi_pin: GPIO13 # blue
clk_pin: GPIO14 # purple
miso_pin: GPIO12 # green
gdo2_pin: GPIO4 # gray
gdo0_pin: GPIO21 # yellow
cs_pin: GPIO15 # orange
#mosi_pin: GPIO13
#miso_pin: GPIO5
#clk_pin: GPIO2
#cs_pin: GPIO14
#gdo0_pin: GPIO15
#gdo2_pin: GPIO16
led_pin: GPIO0
led_blink_time: "1s"
#frequency: 868.950
all_drivers: True
sync_mode: True
log_all: True
#mqtt:
# broker: 10.0.0.88
# username: mqttUser
# password: mqttPass
# clients:
# - name: "wmbusmeters"
# ip_address: "10.0.0.22"
# port: 7227
sensor:
# add driver to compile list (will be available for autodetect), don't create sensor
- platform: wmbus
type: itron
# add sensor with defined type (driver will be also added to compile list)
- platform: wmbus
meter_id: 0x00744561
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"
i log
INFO ESPHome 2026.2.1
INFO Reading configuration /config/esphome/mojdom.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/#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/#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO0 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/#why-am-i-getting-a-warning-about-strapping-pins
INFO Generating C++ source...
INFO Setting CONFIG_LWIP_MAX_SOCKETS to 11 (registered: api=4, captive_portal=4, mdns=2, ota=1)
INFO Compiling app... Build path: /data/build/mojdom
Processing mojdom (board: esp32dev; framework: arduino, espidf; platform: https://github.com/pioarduino/platform-espressif32/releases/download/55.03.37/platform-espressif32.zip)
--------------------------------------------------------------------------------
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
- contrib-piohome @ 3.4.4
- framework-arduinoespressif32 @ 3.3.7
- framework-arduinoespressif32-libs @ 5.5.2
- framework-espidf @ 3.50502.0 (5.5.2)
- tool-cmake @ 4.0.3
- tool-esp-rom-elfs @ 2024.10.11
- tool-esptoolpy @ 5.1.2
- tool-ninja @ 1.13.1
- tool-scons @ 4.40801.0 (4.8.1)
- toolchain-xtensa-esp-elf @ 14.2.0+20251107
Warning: the 'src_filter' option cannot be used with ESP-IDF. Select source files to build in the project CMakeLists.txt file.
Reading CMake configuration...
Dependency Graph
|-- noise-c @ 0.1.10
|-- WiFi @ 3.3.7
|-- SPI @ 3.3.7
|-- SmartRC-CC1101-Driver-Lib @ 2.5.7
RAM: [= ] 14.0% (used 45956 bytes from 327680 bytes)
Flash: [==========] 95.7% (used 1755539 bytes from 1835008 bytes)
========================= [SUCCESS] Took 17.09 seconds =========================
INFO Build Info: config_hash=0x13972f3a build_time_str=2026-02-22 20:16:55 +0100
INFO Successfully compiled program.
INFO Connecting to 192.168.0.121 port 3232...
INFO Connected to 192.168.0.121
INFO Uploading /data/build/mojdom/.pioenvs/mojdom/firmware.bin (1755936 bytes)
Uploading: [============================================================] 100% Done...
INFO Upload took 7.32 seconds, waiting for result...
INFO OTA successful
INFO Successfully uploaded program.
INFO Starting log output from 192.168.0.121 using esphome API
INFO Successfully resolved mojdom @ 192.168.0.121 in 0.000s
INFO Successfully connected to mojdom @ 192.168.0.121 in 5.218s
INFO Successful handshake with mojdom @ 192.168.0.121 in 0.067s
[21:26:12.922][I][app:215]: ESPHome version 2026.2.1 compiled on 2026-02-22 20:16:55 +0100
[21:26:12.927][I][app:222]: ESP32 Chip: ESP32 rev3.1, 2 core(s)
[21:26:12.927][W][app:231]: Set minimum_chip_revision: "3.1" to reduce binary size
[21:26:12.932][C][logger:237]: Logger:
[21:26:12.932][C][logger:237]: Max Level: DEBUG
[21:26:12.932][C][logger:237]: Initial Level: DEBUG
[21:26:12.932][C][logger:244]: Log Baud Rate: 115200
[21:26:12.932][C][logger:244]: Hardware UART: UART0
[21:26:12.936][C][logger:254]: Task Log Buffer Size: 768 bytes
[21:26:12.946][C][captive_portal:134]: Captive Portal:
[21:26:12.953][C][wifi:1450]: WiFi:
[21:26:12.953][C][wifi:1450]: Local MAC: 24:DC:C3:C3:28:54
[21:26:12.953][C][wifi:1450]: Connected: YES
[21:26:12.953][C][wifi:1202]: IP Address: 192.168.0.121
[21:26:12.958][C][wifi:1213]: SSID: 'Dom1SiecTechniczna'[redacted]
[21:26:12.958][C][wifi:1213]: BSSID: DA:B3:70:2B:D9:58[redacted]
[21:26:12.958][C][wifi:1213]: Hostname: 'mojdom'
[21:26:12.958][C][wifi:1213]: Signal strength: -63 dB ▂▄▆█
[21:26:12.958][C][wifi:1213]: Channel: 11
[21:26:12.958][C][wifi:1213]: Subnet: 255.255.255.0
[21:26:12.958][C][wifi:1213]: Gateway: 192.168.0.1
[21:26:12.958][C][wifi:1213]: DNS1: 192.168.0.1
[21:26:12.958][C][wifi:1213]: DNS2: 0.0.0.0
[21:26:12.986][C][sntp:059]: SNTP Time:
[21:26:12.986][C][sntp:062]: Server 0: '0.pool.ntp.org'
[21:26:12.993][C][sntp:062]: Server 1: '1.pool.ntp.org'
[21:26:13.003][C][sntp:062]: Server 2: '2.pool.ntp.org'
[21:26:13.003][C][time:028]: Timezone: 'CET-1CEST,M3.5.0,M10.5.0/3'
[21:26:13.007][C][time:031]: Current time: 2026-02-22 21:26:12
[21:26:13.013][C][esphome.ota:075]: Over-The-Air updates:
[21:26:13.013][C][esphome.ota:075]: Address: mojdom.local:3232
[21:26:13.013][C][esphome.ota:075]: Version: 2
[21:26:13.013][C][esphome.ota:082]: Password configured
[21:26:13.025][C][safe_mode:022]: Safe Mode:
[21:26:13.025][C][safe_mode:022]: Successful after: 60s
[21:26:13.025][C][safe_mode:022]: Invoke after: 10 attempts
[21:26:13.025][C][safe_mode:022]: Duration: 300s
[21:26:13.047][C][safe_mode:039]: Bootloader rollback: support unknown
[21:26:13.047][C][web_server.ota:238]: Web Server OTA
[21:26:13.051][C][api:237]: Server:
[21:26:13.051][C][api:237]: Address: mojdom.local:6053
[21:26:13.051][C][api:237]: Listen backlog: 4
[21:26:13.051][C][api:237]: Max connections: 8
[21:26:13.056][C][api:244]: Noise encryption: YES
[21:26:13.057][C][mdns:177]: mDNS:
[21:26:13.057][C][mdns:177]: Hostname: mojdom
[21:26:13.061][C][wmbus:417]: wM-Bus v4.2.1-1.17.1-b8f4a945:
[21:26:13.066][C][wmbus:430]: LED:
[21:26:13.066][C][wmbus:152]: Pin: GPIO0
[21:26:13.075][C][wmbus:432]: Duration: 1000 ms
[21:26:13.085][C][wmbus:435]: Chip ID: 5428C3C3DC24
[21:26:13.085][C][wmbus:437]: CC1101 frequency: 868.950 MHz
[21:26:13.089][C][wmbus:438]: CC1101 SPI bus:
[21:26:13.097][E][wmbus:440]: Check connection to CC1101!
[21:26:13.097][C][wmbus:152]: MOSI Pin: GPIO13
[21:26:13.100][C][wmbus:152]: MISO Pin: GPIO12
[21:26:13.107][C][wmbus:152]: CLK Pin: GPIO14
[21:26:13.107][C][wmbus:152]: CS Pin: GPIO15
[21:26:13.116][C][wmbus:152]: GDO0 Pin: GPIO21
[21:26:13.127][C][wmbus:152]: GDO2 Pin: GPIO4
[21:26:13.127][C][wmbus:453]: 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
[21:26:13.158][C][wmbus:467]: Meter:
[21:26:13.167][C][wmbus:468]: ID: 7619937 [0x00744561]
[21:26:13.167][C][wmbus:469]: Type: apator162
[21:26:13.170][C][wmbus:470]: Key: '00000000000000000000000000000000'
[21:26:13.189][C][wmbus:472]: Field: 'rssi'
[21:26:13.189][C][wmbus:017]: Name: 'my hot water RSSi'
[21:26:13.189][C][wmbus:017]: State Class: 'measurement'
[21:26:13.189][C][wmbus:017]: Unit of Measurement: 'dBm'
[21:26:13.189][C][wmbus:017]: Accuracy Decimals: 0
[21:26:13.199][C][wmbus:163]: Device Class: 'signal_strength'
[21:26:13.208][C][wmbus:472]: Field: 'total'
[21:26:13.208][C][wmbus:017]: Name: 'my hot water'
[21:26:13.208][C][wmbus:017]: State Class: 'total_increasing'
[21:26:13.208][C][wmbus:017]: Unit of Measurement: 'm³'
[21:26:13.208][C][wmbus:017]: Accuracy Decimals: 3
[21:26:13.218][C][wmbus:163]: Device Class: 'water'
[21:26:13.230][C][wmbus:157]: Icon: 'mdi:water'
[21:26:13.230][E][component:255]: wmbus is marked FAILED: unspecified
[21:26:37.853][D][sntp:100]: Synchronized time: 2026-02-22 21:26:37
[21:27:07.686][I][safe_mode:071]: Boot seems successful; resetting boot loop counter
[21:27:07.994][D][esp32.preferences:153]: Writing 1 items: 0 cached, 1 written, 0 failed
[21:31:12.365][D][wifi:2327]: Roam scan (-63 dBm, attempt 1/3)
Walcze z tym już chyba trzeci dzień i nic nie pomoga. Macie może jakieś sugestie, co powinienem zmienić w kodzie aby odczytywać poprawnie ramki z licznika? Tym czytnikiem już odczytywałem stany liczników ( na versji 3).
Zdefiniuj piny:
# Dodaj definicję SPI przed wmbus
spi:
clk_pin: GPIO14
mosi_pin: GPIO13
miso_pin: GPIO12
external_components:
- source: github://SzczepanLeon/esphome-components@version_4
refresh: 0d
components: [ wmbus ]
wmbus:
# Nie podawaj tutaj ponownie pinów mosi/miso/clk/cs,
# jeśli używasz standardowej szyny zdefiniowanej powyżej.
# Podaj tylko piny specyficzne dla CC1101:
gdo0_pin: GPIO21
gdo2_pin: GPIO4
# cs_pin musi być tutaj jeśli nie jest częścią głównego spi:
cs_pin: GPIO15
frequency: 868.950
led_pin: GPIO0
led_blink_time: "1s"
all_drivers: True
sync_mode: True
log_all: True
A nie zmianiłeś przypadkiem pinologiki GPIO dla urządzenia od @Mariusz_Woszczyński?
wmbus:
frequency: 868.950
mosi_pin: GPIO13 # blue
clk_pin: GPIO14 # purple
miso_pin: GPIO12 # green
gdo2_pin: GPIO4 # gray
gdo0_pin: GPIO21 # yellow
cs_pin: GPIO15 # orange
#mosi_pin: GPIO13
#miso_pin: GPIO5
#clk_pin: GPIO2
#cs_pin: GPIO14
#gdo0_pin: GPIO15
#gdo2_pin: GPIO16
tak, rzeczywiście zmieniałem Piny, po powrocie do domyślnych z instrukcji nic się nie zmieniło, dokładnie taki sam komunikat jak załączyłem wyżej
Po wprowadzeniu proponowanych zmian pojawia się błąd:
INFO ESPHome 2026.2.1
INFO Reading configuration /config/esphome/moj-dom.yaml...
INFO Updating https://github.com/SzczepanLeon/esphome-components.git@version_4
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/#why-am-i-getting-a-warning-about-strapping-pins
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/#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/#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO0 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/#why-am-i-getting-a-warning-about-strapping-pins
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/#why-am-i-getting-a-warning-about-strapping-pins
Failed config
spi: [source /config/esphome/moj-dom.yaml:38]
Pin 13 is used in multiple places.
- clk_pin:
number: 2
mode:
output: True
input: False
open_drain: False
pullup: False
pulldown: False
inverted: False
ignore_pin_validation_error: False
ignore_strapping_warning: False
drive_strength: 20.0
wmbus: [source /config/esphome/moj-dom.yaml:50]
Pin 13 is used in multiple places.
gdo0_pin:
number: 15
mode:
input: True
output: False
open_drain: False
pullup: False
pulldown: False
inverted: False
ignore_pin_validation_error: False
ignore_strapping_warning: False
drive_strength: 20.0
Pin 14 is used in multiple places
Pin 14 is used in multiple places
Sam log bez kompletnego YAMLa (dokładnie takiego, przy kompilacji którego masz te błędy) nie umożliwia udzielenia jakiejkolwiek pomocy.
Piny masz mieć takie jakie miałeś oryginalnie tj. wtedy, gdy działało (jeśli nie wiesz jakie wygrzeb starego YAMLA z backupu zrobionego zanim zacząłeś w tym grzebać), dokumentacja komponentu zawiera jakiś przykładowy układ jeden z wielu możliwych (one zależą od konstrukcji sprzętu, więc nigdy nie można ich zmieniać!), być może nie usunąłeś zbędnych fragmentów YAMLa…
Skutecznym rozwiązaniem (tj. dla ścisłości - obejściem problemu) było przez wiele miesięcy kompilowanie w odpowiednio starej wersji ESPHome (można równolegle z aktualną zainstalować starą wersję Dodatku/Aplikacji z nieoficjalnego repozytorium). Jeśli chodzi o v5 to polecana przez wiele osób archiwalna wersja ESPHome to 2025.09 (no i nie wiem czy komponent v4 ma obecnie jakieś fixy dla nowszych wydań).
dzięki za pomoc.
Rzeczywiście główny problem leżał w złym pinout. Wróciłem do starego i wszystko zaczęło działać.
Ale do momentu…Odczyt liczników (apator16-2) jest realizowany tylko jeśli nie dodam ich więcej niż 3 szt. jeśli jest więcej to już ramki nie są odczytywane.
Moj aktualny kod:
esphome:
name: mojdom
friendly_name: MojDom
esp32:
board: esp32dev
framework:
type: arduino
# Enable logging
logger:
level: DEBUG
# Enable Home Assistant API
api:
encryption:
key: "+="
ota:
- platform: esphome
password: "8586709c48e3d4a0c75fc90e587c0ea4"
wifi:
ssid:
password:
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Mojdom Fallback Hotspot"
password: ""
captive_portal:
time:
- platform: sntp
id: time_sntp
external_components:
- source: github://SzczepanLeon/esphome-components@version_4
refresh: 0d
components: [ wmbus ]
wmbus:
frequency: 868.950 #default
sync_mode: true #default
log_all: false
#log_unknown: true #default
mosi_pin: GPIO32
clk_pin: GPIO33
miso_pin: GPIO19
gdo2_pin: GPIO21
gdo0_pin: GPIO22
cs_pin: GPIO23
#mqtt:
# broker: 10.0.0.88
# username: mqttUser
# password: mqttPass
# clients:
# - name: "wmbusmeters"
# ip_address: "10.0.0.22"
# port: 7227
sensor:
#add driver to compile list (will be available for autodetect), don't create sensor
- platform: wmbus
type: itron
########### LOKAL ##############################
# lokal zimna
- platform: wmbus
meter_id: 0x00606059
type: apator162
key: "00000000000000000000000000000000"
sensors:
- name: "Lokal zimna woda"
field: "total"
accuracy_decimals: 3
unit_of_measurement: "m³"
device_class: "water"
state_class: "total_increasing"
icon: "mdi:water"
# lokal ciepla
- platform: wmbus
meter_id: 0x00746039
type: apator162
key: "00000000000000000000000000000000"
sensors:
- name: "Lokal ciepla woda"
field: "total"
accuracy_decimals: 3
unit_of_measurement: "m³"
device_class: "water"
state_class: "total_increasing"
icon: "mdi:water"
########### PARTER ##############################
# parter zimna
- platform: wmbus
meter_id: 0x00791869
type: apator162
key: "00000000000000000000000000000000"
sensors:
- name: "Parter zimna woda"
field: "total"
accuracy_decimals: 3
unit_of_measurement: "m³"
device_class: "water"
state_class: "total_increasing"
icon: "mdi:water"
# parter ciepla
- platform: wmbus
meter_id: 0x00638821
type: apator162
key: "00000000000000000000000000000000"
sensors:
- name: "Parter ciepla woda"
field: "total"
accuracy_decimals: 3
unit_of_measurement: "m³"
device_class: "water"
state_class: "total_increasing"
icon: "mdi:water"
########### PODDASZE ##############################
# PODDASZE zimna
- platform: wmbus
meter_id: 0x00638780
type: apator162
key: "00000000000000000000000000000000"
sensors:
- name: "Poddasze zimna woda"
field: "total"
accuracy_decimals: 3
unit_of_measurement: "m³"
device_class: "water"
state_class: "total_increasing"
icon: "mdi:water"
# PODDASZE ciepla
- platform: wmbus
meter_id: 0x00611344
type: apator162
key: "00000000000000000000000000000000"
sensors:
- name: "Poddasze ciepla woda"
field: "total"
accuracy_decimals: 3
unit_of_measurement: "m³"
device_class: "water"
state_class: "total_increasing"
icon: "mdi:water"
i odczyt z logów (musiałem go trochę pociąć bo miał 120000znaków):
INFO ESPHome 2026.2.1
INFO Reading configuration /config/esphome/moj-dom.yaml...
INFO Updating https://github.com/SzczepanLeon/esphome-components.git@version_4
INFO Detected timezone 'Europe/Warsaw'
INFO Generating C++ source...
INFO Setting CONFIG_LWIP_MAX_SOCKETS to 11 (registered: api=4, captive_portal=4, mdns=2, ota=1)
INFO Compiling app... Build path: /data/build/mojdom
********************************************************************************
If you like PlatformIO, please:
- star it on GitHub > https://github.com/platformio/platformio-core
- follow us on LinkedIn to stay up-to-date on the latest project news > https://www.linkedin.com/company/platformio/
- try PlatformIO IDE for embedded development > https://platformio.org/platformio-ide
********************************************************************************
Processing mojdom (board: esp32dev; framework: arduino, espidf; platform: https://github.com/pioarduino/platform-espressif32/releases/download/55.03.37/platform-espressif32.zip)
--------------------------------------------------------------------------------
Platform Manager: Installing https://github.com/pioarduino/platform-espressif32/releases/download/55.03.37/platform-espressif32.zip
INFO Installing https://github.com/pioarduino/platform-espressif32/releases/download/55.03.37/platform-espressif32.zip
Downloading [####################################] 100%
Unpacking [####################################] 100%
Platform Manager: espressif32@55.3.37 has been installed!
INFO espressif32@55.3.37 has been installed!
INFO tool-esp_install not installed, installing version https://github.com/pioarduino/esp_install/releases/download/v5.3.4/esp_install-v5.3.4.zip
INFO Installing tool-esp_install version https://github.com/pioarduino/esp_install/releases/download/v5.3.4/esp_install-v5.3.4.zip
Tool Manager: Installing https://github.com/pioarduino/esp_install/releases/download/v5.3.4/esp_install-v5.3.4.zip
INFO Installing https://github.com/pioarduino/esp_install/releases/download/v5.3.4/esp_install-v5.3.4.zip
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: tool-esp_install@5.3.4 has been installed!
INFO tool-esp_install@5.3.4 has been installed!
INFO tool-esp_install successfully installed and verified
Created pioarduino Python virtual environment using uv: /root/.platformio/penv
Tool Manager: Installing https://github.com/espressif/arduino-esp32/releases/download/3.3.7/esp32-core-3.3.7.tar.xz
INFO Installing https://github.com/espressif/arduino-esp32/releases/download/3.3.7/esp32-core-3.3.7.tar.xz
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: framework-arduinoespressif32@3.3.7 has been installed!
INFO framework-arduinoespressif32@3.3.7 has been installed!
Tool Manager: Installing file:///data/build/mojdom/arduino_libs_stub
INFO Installing file:///data/build/mojdom/arduino_libs_stub
Tool Manager: framework-arduinoespressif32-libs@5.5.2 has been installed!
INFO framework-arduinoespressif32-libs@5.5.2 has been installed!
Tool Manager: Installing https://github.com/pioarduino/esp-idf/releases/download/v5.5.2/esp-idf-v5.5.2.tar.xz
INFO Installing https://github.com/pioarduino/esp-idf/releases/download/v5.5.2/esp-idf-v5.5.2.tar.xz
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: framework-espidf@3.50502.0 has been installed!
INFO framework-espidf@3.50502.0 has been installed!
Tool Manager: Installing https://github.com/pioarduino/registry/releases/download/0.0.1/xtensa-esp-elf-14.2.0_20251107.zip
INFO Installing https://github.com/pioarduino/registry/releases/download/0.0.1/xtensa-esp-elf-14.2.0_20251107.zip
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: toolchain-xtensa-esp-elf@14.2.0+20251107 has been installed!
INFO toolchain-xtensa-esp-elf@14.2.0+20251107 has been installed!
Tool Manager: Installing https://github.com/pioarduino/registry/releases/download/0.0.1/esptoolpy-v5.1.2.zip
INFO Installing https://github.com/pioarduino/registry/releases/download/0.0.1/esptoolpy-v5.1.2.zip
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: tool-esptoolpy@5.1.2 has been installed!
INFO tool-esptoolpy@5.1.2 has been installed!
Tool Manager: Installing https://github.com/pioarduino/registry/releases/download/0.0.1/contrib-piohome-3.4.4.tar.gz
INFO Installing https://github.com/pioarduino/registry/releases/download/0.0.1/contrib-piohome-3.4.4.tar.gz
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: contrib-piohome@3.4.4 has been installed!
INFO contrib-piohome@3.4.4 has been installed!
Tool Manager: Installing https://github.com/pioarduino/registry/releases/download/0.0.1/cmake-4.0.3.zip
INFO Installing https://github.com/pioarduino/registry/releases/download/0.0.1/cmake-4.0.3.zip
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: tool-cmake@4.0.3 has been installed!
INFO tool-cmake@4.0.3 has been installed!
Tool Manager: Installing https://github.com/pioarduino/registry/releases/download/0.0.1/esp-rom-elfs-20241011.zip
INFO Installing https://github.com/pioarduino/registry/releases/download/0.0.1/esp-rom-elfs-20241011.zip
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: tool-esp-rom-elfs@2024.10.11 has been installed!
INFO tool-esp-rom-elfs@2024.10.11 has been installed!
Tool Manager: Installing https://github.com/pioarduino/registry/releases/download/0.0.1/ninja-1.13.1.zip
INFO Installing https://github.com/pioarduino/registry/releases/download/0.0.1/ninja-1.13.1.zip
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: tool-ninja@1.13.1 has been installed!
INFO tool-ninja@1.13.1 has been installed!
Tool Manager: Installing https://github.com/pioarduino/registry/releases/download/0.0.1/scons-4.8.1.zip
INFO Installing https://github.com/pioarduino/registry/releases/download/0.0.1/scons-4.8.1.zip
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: tool-scons@4.40801.0 has been installed!
INFO tool-scons@4.40801.0 has been installed!
Tool Manager: Installing platformio/tool-scons @ ~4.40801.0
INFO Installing platformio/tool-scons @ ~4.40801.0
Downloading [####################################] 100%
Unpacking [####################################] 100%
Tool Manager: tool-scons@4.40801.0 has been installed!
INFO tool-scons@4.40801.0 has been installed!
Library Manager: Installing esphome/noise-c @ 0.1.10
INFO Installing esphome/noise-c @ 0.1.10
Downloading [####################################] 100%
Unpacking [####################################] 100%
Library Manager: noise-c@0.1.10 has been installed!
INFO noise-c@0.1.10 has been installed!
Library Manager: Resolving dependencies...
INFO Resolving dependencies...
Library Manager: Installing esphome/libsodium @ 1.10020.7
INFO Installing esphome/libsodium @ 1.10020.7
Downloading [####################################] 100%
Unpacking [####################################] 100%
Library Manager: libsodium@1.10020.7 has been installed!
INFO libsodium@1.10020.7 has been installed!
Library Manager: Installing LSatan/SmartRC-CC1101-Driver-Lib @ 2.5.7
INFO Installing LSatan/SmartRC-CC1101-Driver-Lib @ 2.5.7
Downloading [####################################] 100%
Unpacking [####################################] 100%
Library Manager: SmartRC-CC1101-Driver-Lib@2.5.7 has been installed!
INFO SmartRC-CC1101-Driver-Lib@2.5.7 has been installed!
INFO Installing tools via idf_tools.py (this may take several minutes)...
Tool Manager: Installing file:///root/.platformio/tools/tool-esptoolpy
INFO Installing file:///root/.platformio/tools/tool-esptoolpy
Tool Manager: tool-esptoolpy@5.1.2 has been installed!
INFO tool-esptoolpy@5.1.2 has been installed!
INFO Tool tool-esptoolpy successfully installed
INFO Installing tools via idf_tools.py (this may take several minutes)...
Tool Manager: Installing file:///root/.platformio/tools/toolchain-xtensa-esp-elf
INFO Installing file:///root/.platformio/tools/toolchain-xtensa-esp-elf
Tool Manager: toolchain-xtensa-esp-elf@14.2.0+20251107 has been installed!
INFO toolchain-xtensa-esp-elf@14.2.0+20251107 has been installed!
INFO Tool toolchain-xtensa-esp-elf successfully installed
INFO Installing tools via idf_tools.py (this may take several minutes)...
Tool Manager: Installing file:///root/.platformio/tools/tool-cmake
INFO Installing file:///root/.platformio/tools/tool-cmake
Tool Manager: tool-cmake@4.0.3 has been installed!
INFO tool-cmake@4.0.3 has been installed!
INFO Tool tool-cmake successfully installed
INFO Installing tools via idf_tools.py (this may take several minutes)...
Tool Manager: Installing file:///root/.platformio/tools/tool-ninja
INFO Installing file:///root/.platformio/tools/tool-ninja
Tool Manager: tool-ninja@1.13.1 has been installed!
INFO tool-ninja@1.13.1 has been installed!
INFO Tool tool-ninja successfully installed
INFO Installing tools via idf_tools.py (this may take several minutes)...
Tool Manager: Installing file:///root/.platformio/tools/tool-esp-rom-elfs
INFO Installing file:///root/.platformio/tools/tool-esp-rom-elfs
Tool Manager: tool-esp-rom-elfs@2024.10.11 has been installed!
INFO tool-esp-rom-elfs@2024.10.11 has been installed!
INFO Tool tool-esp-rom-elfs successfully installed
Installed esptool from tl-install path: /data/cache/platformio/packages/tool-esptoolpy
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
- contrib-piohome @ 3.4.4
- framework-arduinoespressif32 @ 3.3.7
- framework-arduinoespressif32-libs @ 5.5.2
- framework-espidf @ 3.50502.0 (5.5.2)
- tool-cmake @ 4.0.3
- tool-esp-rom-elfs @ 2024.10.11
- tool-esptoolpy @ 5.1.2
- tool-ninja @ 1.13.1
- tool-scons @ 4.40801.0 (4.8.1)
- toolchain-xtensa-esp-elf @ 14.2.0+20251107
Creating a new virtual environment for IDF Python dependencies using uv
Using Python 3.12.10 environment at: /root/.platformio/penv/.espidf-5.5.2
Installing ESP-IDF's Python dependencies with uv
Using Python 3.12.10 environment at: /root/.platformio/penv/.espidf-5.5.2
Resolved 27 packages in 477ms
Installed 27 packages in 21ms
+ annotated-types==0.7.0
+ certifi==2026.1.4
+ cffi==2.0.0
+ charset-normalizer==3.4.4
+ click==8.3.1
+ colorama==0.4.6
+ cryptography==44.0.3
+ esp-idf-kconfig==2.5.2
+ idf-component-manager==2.4.6
+ idna==3.11
+ jsonref==1.1.0
+ psutil==7.2.2
+ pycparser==3.0
+ pydantic==2.12.5
+ pydantic-core==2.41.5
+ pydantic-settings==2.13.1
+ pyparsing==3.3.2
+ python-dotenv==1.2.1
+ requests==2.32.5
+ requests-file==3.0.1
+ requests-toolbelt==1.0.0
+ ruamel-yaml==0.19.1
+ tqdm==4.67.3
+ truststore==0.10.4
+ typing-extensions==4.15.0
+ typing-inspection==0.4.2
+ urllib3==1.26.20
Warning: the 'src_filter' option cannot be used with ESP-IDF. Select source files to build in the project CMakeLists.txt file.
Reading CMake configuration...
Generating assembly for certificate bundle...
Dependency Graph
|-- noise-c @ 0.1.10
|-- WiFi @ 3.3.7
|-- SPI @ 3.3.7
|-- SmartRC-CC1101-Driver-Lib @ 2.5.7
Compiling .pioenvs/mojdom/src/esphome/components/api/api_connection.cpp.o
Compiling .pioenvs/mojdom/src/esphome/components/api/api_frame_helper.cpp.o
Compiling .pioenvs/mojdom/src/esphome/components/api/api_frame_helper_noise.cpp.o
Compiling .pioenvs/mojdom/src/esphome/components/api/api_pb2.cpp.o
Compiling .pioenvs/mojdom/src/esphome/components/api/api_pb2_service.cpp.o
Compiling .pioenvs/mojdom/src/esphome/components/api/api_server.cpp.o
src/esphome/components/wmbus/wmbus.cpp:18:48: note: '#pragma message: Loop task stack increased.'
18 | #pragma message ( "Loop task stack increased." )
| ^
In file included from src/esphome/components/wmbus/wmbus.h:3,
from src/esphome/components/wmbus/wmbus.cpp:1:
src/esphome/components/wmbus/wmbus.cpp: In member function 'virtual void esphome::wmbus::WMBusComponent::dump_config()':
src/esphome/components/wmbus/wmbus.cpp:423:36: warning: 'std::string esphome::network::IPAddress::str() const' is deprecated: Use str_to() instead. Removed in 2026.8.0 [-Wdeprecated-declarations]
423 | client.ip.str().c_str(),
| ~~~~~~~~~~~~~^~
src/esphome/core/log.h:98:101: note: in definition of macro 'esph_log_config'
98 | ::esphome::esp_log_printf_(ESPHOME_LOG_LEVEL_CONFIG, tag, __LINE__, ESPHOME_LOG_FORMAT(format), ##__VA_ARGS__)
| ^~~~~~~~~~~
src/esphome/components/wmbus/wmbus.cpp:421:9: note: in expansion of macro 'ESP_LOGCONFIG'
421 | ESP_LOGCONFIG(TAG, " %s: %s:%d %s [%s]",
| ^~~~~~~~~~~~~
In file included from src/esphome/components/wmbus/wmbus.h:7:
src/esphome/components/network/ip_address.h:154:15: note: declared here
154 | std::string str() const {
| ^~~
Generating partitions .pioenvs/mojdom/partitions.bin
Archiving .pioenvs/mojdom/bootloader/esp-idf/spi_flash/libspi_flash.a
Indexing .pioenvs/mojdom/bootloader/esp-idf/spi_flash/libspi_flash.a
Linking .pioenvs/mojdom/bootloader.elf
Building .pioenvs/mojdom/bootloader.bin
Creating ESP32 image...
Successfully created ESP32 image.
Linking .pioenvs/mojdom/firmware.elf
Memory Type Usage Summary
┏━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┓
┃ Memory Type/Section ┃ Used [bytes] ┃ Used [%] ┃ Remain [bytes] ┃ Total [bytes] ┃
┡━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━┩
│ Flash Code │ 1251368 │ │ │ │
│ .text │ 1251368 │ │ │ │
│ Flash Data │ 411228 │ │ │ │
│ .rodata │ 410972 │ │ │ │
│ .appdesc │ 256 │ │ │ │
│ IRAM │ 77567 │ 59.18 │ 53505 │ 131072 │
│ .text │ 76539 │ 58.39 │ │ │
│ .vectors │ 1028 │ 0.78 │ │ │
│ DRAM │ 45988 │ 25.44 │ 134748 │ 180736 │
│ .bss │ 29448 │ 16.29 │ │ │
│ .data │ 16540 │ 9.15 │ │ │
└─────────────────────┴──────────────┴──────────┴────────────────┴───────────────┘
Total image size: 1756703 bytes (.bin may be padded larger)
Note: The reported total sizes may be smaller than those in the technical reference manual due to reserved memory and application configuration. The total flash size available for the application is not included by default, as it cannot be reliably determined due to the presence of other data like the bootloader, partition table, and application partition size.
RAM: [= ] 14.0% (used 45988 bytes from 327680 bytes)
Flash: [==========] 95.7% (used 1756447 bytes from 1835008 bytes)
Building .pioenvs/mojdom/firmware.bin
Creating ESP32 image...
Successfully created ESP32 image.
merge_factory_bin([".pioenvs/mojdom/firmware.bin"], [".pioenvs/mojdom/firmware.elf"])
Info: bootloader.bin not found - skipping
Info: partition-table.bin not found - skipping
Info: ota_data_initial.bin not found - skipping
Info: mojdom.bin not found - skipping
Using FLASH_EXTRA_IMAGES from PlatformIO environment
Merging binaries into /data/build/mojdom/.pioenvs/mojdom/firmware.factory.bin
Merging binaries with esptool
SHA digest in image updated.
Wrote 0x1bceb0 bytes to file '/data/build/mojdom/.pioenvs/mojdom/firmware.factory.bin', ready to flash to offset 0x0.
Successfully created /data/build/mojdom/.pioenvs/mojdom/firmware.factory.bin
esp32_copy_ota_bin([".pioenvs/mojdom/firmware.bin"], [".pioenvs/mojdom/firmware.elf"])
Copied firmware to /data/build/mojdom/.pioenvs/mojdom/firmware.ota.bin
======================== [SUCCESS] Took 351.42 seconds ========================
INFO Build Info: config_hash=0x53c0e7ae build_time_str=2026-02-23 22:05:09 +0100
INFO Successfully compiled program.
INFO Connecting to 192.168.0.121 port 3232...
INFO Connected to 192.168.0.121
INFO Uploading /data/build/mojdom/.pioenvs/mojdom/firmware.bin (1756848 bytes)
Uploading: [============================================================] 100% Done...
INFO Upload took 7.27 seconds, waiting for result...
INFO OTA successful
INFO Successfully uploaded program.
INFO Starting log output from 192.168.0.121 using esphome API
INFO Successfully resolved mojdom @ 192.168.0.121 in 0.000s
INFO Successfully connected to mojdom @ 192.168.0.121 in 5.118s
INFO Successful handshake with mojdom @ 192.168.0.121 in 0.093s
[22:11:23.599][I][app:215]: ESPHome version 2026.2.1 compiled on 2026-02-23 22:05:09 +0100
[22:11:23.605][I][app:222]: ESP32 Chip: ESP32 rev3.1, 2 core(s)
[22:11:23.605][W][app:231]: Set minimum_chip_revision: "3.1" to reduce binary size
[22:11:23.608][C][logger:237]: Logger:
[22:11:23.608][C][logger:237]: Max Level: DEBUG
[22:11:23.608][C][logger:237]: Initial Level: DEBUG
[22:11:23.608][C][logger:244]: Log Baud Rate: 115200
[22:11:23.608][C][logger:244]: Hardware UART: UART0
[22:11:23.609][C][logger:254]: Task Log Buffer Size: 768 bytes
[22:11:23.621][C][captive_portal:134]: Captive Portal:
[22:11:23.633][C][wifi:1450]: WiFi:
[22:11:23.633][C][wifi:1450]: Local MAC: 24:DC:C3:C3:28:54
[22:11:23.633][C][wifi:1450]: Connected: YES
[22:11:23.633][C][wifi:1202]: IP Address: 192.168.0.121
[22:11:23.638][C][wifi:1213]: SSID: 'Dom1SiecTechniczna'[redacted]
[22:11:23.638][C][wifi:1213]: BSSID: DA:B3:70:2B:D9:58[redacted]
[22:11:23.638][C][wifi:1213]: Hostname: 'mojdom'
[22:11:23.638][C][wifi:1213]: Signal strength: -71 dB ▂▄▆█
[22:11:23.638][C][wifi:1213]: Channel: 11
[22:11:23.638][C][wifi:1213]: Subnet: 255.255.255.0
[22:11:23.638][C][wifi:1213]: Gateway: 192.168.0.1
[22:11:23.638][C][wifi:1213]: DNS1: 192.168.0.1
[22:11:23.638][C][wifi:1213]: DNS2: 0.0.0.0
[22:11:23.649][C][sntp:059]: SNTP Time:
[22:11:23.649][C][sntp:062]: Server 0: '0.pool.ntp.org'
[22:11:23.652][C][sntp:062]: Server 1: '1.pool.ntp.org'
[22:11:23.674][C][sntp:062]: Server 2: '2.pool.ntp.org'
[22:11:23.674][C][time:028]: Timezone: 'CET-1CEST,M3.5.0,M10.5.0/3'
[22:11:23.686][C][time:031]: Current time: 2026-02-23 22:11:23
[22:11:23.686][C][esphome.ota:075]: Over-The-Air updates:
[22:11:23.686][C][esphome.ota:075]: Address: mojdom.local:3232
[22:11:23.686][C][esphome.ota:075]: Version: 2
[22:11:23.687][C][esphome.ota:082]: Password configured
[22:11:23.694][C][safe_mode:022]: Safe Mode:
[22:11:23.694][C][safe_mode:022]: Successful after: 60s
[22:11:23.694][C][safe_mode:022]: Invoke after: 10 attempts
[22:11:23.694][C][safe_mode:022]: Duration: 300s
[22:11:23.711][C][safe_mode:039]: Bootloader rollback: support unknown
[22:11:23.711][C][web_server.ota:238]: Web Server OTA
[22:11:23.717][C][api:237]: Server:
[22:11:23.717][C][api:237]: Address: mojdom.local:6053
[22:11:23.717][C][api:237]: Listen backlog: 4
[22:11:23.717][C][api:237]: Max connections: 8
[22:11:23.724][C][api:244]: Noise encryption: YES
[22:11:23.724][C][mdns:177]: mDNS:
[22:11:23.724][C][mdns:177]: Hostname: mojdom
[22:11:23.736][C][wmbus:417]: wM-Bus v4.2.1-1.17.1-b8f4a945:
[22:11:23.740][C][wmbus:435]: Chip ID: 5428C3C3DC24
[22:11:23.740][C][wmbus:437]: CC1101 frequency: 868.950 MHz
[22:11:23.744][C][wmbus:438]: CC1101 SPI bus:
[22:11:23.751][C][wmbus:152]: MOSI Pin: GPIO32
[22:11:23.751][C][wmbus:152]: MISO Pin: GPIO19
[22:11:23.755][C][wmbus:152]: CLK Pin: GPIO33
[22:11:23.763][C][wmbus:152]: CS Pin: GPIO23
[22:11:23.763][C][wmbus:152]: GDO0 Pin: GPIO22
[22:11:23.776][C][wmbus:152]: GDO2 Pin: GPIO21
[22:11:23.804][C][wmbus:453]: 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
[22:11:23.804][C][wmbus:467]: Meter:
[22:11:23.814][C][wmbus:468]: ID: 6316121 [0x00606059]
[22:11:23.823][C][wmbus:469]: Type: apator162
[22:11:23.823][C][wmbus:470]: Key: '00000000000000000000000000000000'
[22:11:23.834][C][wmbus:472]: Field: 'total'
[22:11:23.854][C][wmbus:017]: Name: 'Lokal zimna woda'
[22:11:23.854][C][wmbus:017]: State Class: 'total_increasing'
[22:11:23.854][C][wmbus:017]: Unit of Measurement: 'm³'
[22:11:23.854][C][wmbus:017]: Accuracy Decimals: 3
[22:11:23.854][C][wmbus:163]: Device Class: 'water'
[22:11:23.857][C][wmbus:157]: Icon: 'mdi:water'
[22:11:23.866][C][wmbus:467]: Meter:
[22:11:23.866][C][wmbus:468]: ID: 6361924 [0x00611344]
[22:11:23.874][C][wmbus:469]: Type: apator162
[22:11:23.879][C][wmbus:470]: Key: '00000000000000000000000000000000'
[22:11:23.879][C][wmbus:472]: Field: 'total'
[22:11:23.890][C][wmbus:017]: Name: 'Poddasze ciepla woda'
[22:11:23.890][C][wmbus:017]: State Class: 'total_increasing'
[22:11:23.890][C][wmbus:017]: Unit of Measurement: 'm³'
[22:11:23.890][C][wmbus:017]: Accuracy Decimals: 3
[22:11:23.896][C][wmbus:163]: Device Class: 'water'
[22:11:23.896][C][wmbus:157]: Icon: 'mdi:water'
[22:11:23.906][C][wmbus:467]: Meter:
[22:11:23.911][C][wmbus:468]: ID: 6522752 [0x00638780]
[22:11:23.911][C][wmbus:469]: Type: apator162
[22:11:23.926][C][wmbus:470]: Key: '00000000000000000000000000000000'
[22:11:23.930][C][wmbus:472]: Field: 'total'
[22:11:23.930][C][wmbus:017]: Name: 'Poddasze zimna woda'
[22:11:23.930][C][wmbus:017]: State Class: 'total_increasing'
[22:11:23.930][C][wmbus:017]: Unit of Measurement: 'm³'
[22:11:23.930][C][wmbus:017]: Accuracy Decimals: 3
[22:11:23.936][C][wmbus:163]: Device Class: 'water'
[22:11:23.949][C][wmbus:157]: Icon: 'mdi:water'
[22:11:23.949][C][wmbus:467]: Meter:
[22:11:23.953][C][wmbus:468]: ID: 6522913 [0x00638821]
[22:11:23.966][C][wmbus:469]: Type: apator162
[22:11:23.966][C][wmbus:470]: Key: '00000000000000000000000000000000'
[22:11:23.972][C][wmbus:472]: Field: 'total'
[22:11:23.990][C][wmbus:017]: Name: 'Parter ciepla woda'
[22:11:23.990][C][wmbus:017]: State Class: 'total_increasing'
[22:11:23.990][C][wmbus:017]: Unit of Measurement: 'm³'
[22:11:23.990][C][wmbus:017]: Accuracy Decimals: 3
[22:11:23.990][C][wmbus:163]: Device Class: 'water'
[22:11:23.993][C][wmbus:157]: Icon: 'mdi:water'
[22:11:24.001][C][wmbus:467]: Meter:
[22:11:24.001][C][wmbus:468]: ID: 7626809 [0x00746039]
[22:11:24.020][C][wmbus:469]: Type: apator162
[22:11:24.021][C][wmbus:470]: Key: '00000000000000000000000000000000'
[22:11:24.021][C][wmbus:472]: Field: 'total'
[22:11:24.027][C][wmbus:017]: Name: 'Lokal ciepla woda'
[22:11:24.027][C][wmbus:017]: State Class: 'total_increasing'
[22:11:24.027][C][wmbus:017]: Unit of Measurement: 'm³'
[22:11:24.027][C][wmbus:017]: Accuracy Decimals: 3
[22:11:24.038][C][wmbus:163]: Device Class: 'water'
[22:11:24.038][C][wmbus:157]: Icon: 'mdi:water'
[22:11:24.042][C][wmbus:467]: Meter:
[22:11:24.059][C][wmbus:468]: ID: 7936105 [0x00791869]
[22:11:24.059][C][wmbus:469]: Type: apator162
[22:11:24.062][C][wmbus:470]: Key: '00000000000000000000000000000000'
[22:11:24.069][C][wmbus:472]: Field: 'total'
[22:11:24.069][C][wmbus:017]: Name: 'Parter zimna woda'
[22:11:24.069][C][wmbus:017]: State Class: 'total_increasing'
[22:11:24.069][C][wmbus:017]: Unit of Measurement: 'm³'
[22:11:24.069][C][wmbus:017]: Accuracy Decimals: 3
[22:11:24.083][C][wmbus:163]: Device Class: 'water'
[22:11:24.128][C][wmbus:157]: Icon: 'mdi:water'
[22:11:49.153][D][sntp:100]: Synchronized time: 2026-02-23 22:11:49
[22:11:56.319][D][mbus:035]: Received T1 A frame
[22:12:18.434][I][safe_mode:071]: Boot seems successful; resetting boot loop counter
[22:12:19.115][D][esp32.preferences:153]: Writing 1 items: 0 cached, 1 written, 0 failed
[22:16:23.118][D][wifi:2327]: Roam scan (-73 dBm, attempt 1/3)
[22:17:02.432][D][mbus:035]: Received T1 A frame
[22:21:23.135][D][wifi:2327]: Roam scan (-71 dBm, attempt 2/3)
[22:22:38.440][D][mbus:035]: Received T1 A frame
Co może być przyczyną “korkowania” się odczytów?
Wrzuciłeś całą kompilację to co się dziwić.
Z własnego doświadczenia wiem, że wersje ESPHome późniejsze niż 2025.12 w połączeniu z V4 i CC1101 dają taki właśnie efekt - jest informacja o odbiorze ramki ale brak jej zdekodowania. Tu masz dodatkowo zawalony flash do granic możliwości załadowanymi wszystkimi sterownikami.
Ogólnie polecam V5 od Kuby + SX1267 - to po prostu działa.
Ostatnią wersją ESPHome gdzie nie ładowały się wszystkie drivery jest 2025.9.3. Sproboj na tej skompilować.
3 posty zostały podzielonye na nowy temat: Komponent IoTLabs-pl wM-Bus do ESPHome
Mam dokładnie to samo na najnowszym ESPHome
[11:07:52.577][D][mbus:035]: Received T1 A frame
[11:08:30.396][D][mbus:035]: Received T1 A frame
[11:08:55.833][D][mbus:035]: Received T1 A frame
[11:10:41.724][D][wifi:2327]: Roam scan (-60 dBm, attempt 1/3)
[11:11:22.048][D][mbus:035]: Received T1 A frame
[11:11:25.090][D][mbus:035]: Received T1 A frame
[11:11:30.364][D][mbus:035]: Received T1 A frame
[11:12:04.640][D][mbus:035]: Received T1 A frame
[11:12:33.074][D][mbus:035]: Received T1 A frame
[11:12:55.876][D][mbus:035]: Received T1 A frame
[11:13:13.301][D][mbus:035]: Received T1 A frame
[11:14:10.861][D][mbus:035]: Received T1 A frame
[11:14:22.658][D][mbus:035]: Received T1 A frame
[11:15:26.204][D][mbus:035]: Received T1 A frame
[11:15:28.731][D][mbus:035]: Received T1 A frame
[11:15:30.505][D][mbus:035]: Received T1 A frame
[11:15:41.732][D][wifi:2327]: Roam scan (-60 dBm, attempt 2/3)
[11:15:44.585][D][mbus:035]: Received T1 A frame
[11:16:23.509][D][mbus:035]: Received T1 A frame
[11:17:04.184][D][mbus:035]: Received T1 A frame
[11:17:44.896][D][mbus:035]: Received T1 A frame
[11:17:53.611][D][mbus:035]: Received T1 A frame
I tylko czasami
[11:17:57.011][D][mbus:035]: Received T1 A frame
[11:17:57.035][I][wmbus:094]: Using selected driver hydrocalm3 (detected driver was hydrocalm3)
[11:17:57.039][I][wmbus:100]: hydrocalm3 [0x0512...] RSSI: -80dBm T: 8644B40964011... (135) T1 A
Cześć,
Potrzebuje małej pomocy. Walczę z tematem odkodowania ramek z liniczka ciepła qualcosonic. Na początku odpaliłem bibliotekę w wersji 3 na dostępnym pod ręką Wemos D1 mini i CC1101 868 i udało mi się “posłuchać” tego nadają liczniki. Wiem, że liczniki wody mam kodowane i potrzebne jest mi hasło, ale licznik ciepła jest nieszyfrowany i nadaje w ciągu dnia co 10 minut (w godz. 08:00-16:00). Udało mi się złapać dla niego ramkę, w której przy pomocy WMBusmeters Analyze Telegram rozszyfrowałem i widać w niej różne wartości parametrów. Ramka: 59440907818401040c0d7a88000000046d250f5832048e3B0c6f0000048e3c000000000413143406000c788184010484086d3B175f3184088e3Bad66000084088e3c00000000446d3B173f3c448e3B7a5B0000448e3c00000000
Postanowiłem, że podłącze CC1101 do ESP32-WROOM i na nim postawię to samo, ale dla biblioteki w wersji 4, która wspiera odkodowywanie licznika qualcosonic.
Dojechałem do takowego momentu, gdzie niestety, ale nie mogę zdekodować ramki. W logach widzę tylko informację o wykryciu ramek i nic więcej.
Kod na ESP:
esphome:
name: esp32-wroom
friendly_name: ESP32_WROOM
esp32:
board: esp32dev
framework:
type: arduino
#flash_size: 4MB
partitions: custom_partitions.csv
external_components:
source: github://SzczepanLeon/esphome-components@version_4
refresh: 0d
components: [ wmbus ]
Enable logging
logger:
id: component_logger
level: DEBUG
Enable Home Assistant API
api:
encryption:
key: “X1q5zqdlERc301sdsda2edz891mMl62NxCZ48s=”
ota:
platform: esphome
password: “5f66571df7bdsd656808cd7e9b15fb88”
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: “Esp32-Wroom Fallback Hotspot”
password: “GdjhgrCCAS9N”
captive_portal:
mqtt:
broker: 192.168.0.111
port: 1883
username: esp
password: !secret mqtt_password
time:
platform: sntp
id: time_sntp
wmbus:
mosi_pin: GPIO23
miso_pin: GPIO19
clk_pin: GPIO18
cs_pin: GPIO15
gdo0_pin: GPIO21
gdo2_pin: GPIO22
log_all: true
sync_mode: False
all_drivers: true
sensor:
platform: wmbus
meter_id: 0x04018481
type: auto
key: “”
sensors:
name: “total_heat_energy_kwh”
field: “total_heat_energy_kwh”
unit_of_measurement: “MJ”
name: “total_cooling_energy_kwh”
field: “total_cooling_energy_kwh”
unit_of_measurement: “kwh”
name: “total_m3”
field: “total_m3”
unit_of_measurement: “m3”
To co w logach:
[08:00:33.045][D][mbus:035]: Received T1 A frame
[08:01:25.749][D][mbus:035]: Received T1 A frame
[08:02:17.306][D][mbus:035]: Received T1 A frame
[08:09:39.437][D][mbus:035]: Received T1 A frame
[08:12:06.375][D][sntp:100]: Synchronized time: 2026-03-03 08:12:06
[08:26:14.564][D][mbus:035]: Received T1 A frame
[08:27:06.422][D][sntp:100]: Synchronized time: 2026-03-03 08:27:06
[08:30:13.399][D][mbus:035]: Received T1 A frame
[08:31:18.053][D][mbus:035]: Received T1 A frame
[08:35:24.060][D][mbus:035]: Received T1 A frame
[08:37:49.309][D][mbus:035]: Received T1 A frame
[08:40:41.457][D][mbus:035]: Received T1 A frame
[08:42:06.587][D][sntp:100]: Synchronized time: 2026-03-03 08:42:06
[08:43:36.055][D][mbus:035]: Received T1 A frame
[08:57:06.647][D][sntp:100]: Synchronized time: 2026-03-03 08:57:06
[09:00:52.325][D][mbus:035]: Received T1 A frame
[09:01:56.669][D][mbus:035]: Received T1 A frame
[09:10:01.332][D][mbus:035]: Received T1 A frame
[09:12:06.702][D][sntp:100]: Synchronized time: 2026-03-03 09:12:06
[09:13:09.670][D][mbus:035]: Received T1 A frame
Czy możecie mnie nakierować i podwiedzieć co jest nie tak ? i gdzie robię bład ?