Podzielisz się do tego konfiguracją ? Zakupiłem taki sam ale coś nie mogę go odpalić.
SX1276 ESP32 LoRa 868 MHz-915 MHz
esphome:
name: lora
friendly_name: Lora
platformio_options:
upload_speed: 921600
external_components:
- source: github://SzczepanLeon/esphome-components@main
refresh: 0d
esp32:
board: heltec_wifi_lora_32_V2
flash_size: 8MB
framework:
type: esp-idf
# Enable logging
logger:
id: component_logger
level: DEBUG
baud_rate: 0
# Enable Home Assistant API
api:
encryption:
key: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
ota:
platform: esphome
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Lora Fallback Hotspot"
password: "EyK1CEVSi4yt"
web_server:
version: 3
time:
- platform: sntp
id: sntp_time
spi:
clk_pin:
number: GPIO5
ignore_strapping_warning: true
mosi_pin: GPIO27
miso_pin: GPIO19
#socket_transmitter:
# id: my_socket
# ip_address: 192.168.1.1
# port: 3333
# protocol: TCP
#mqtt:
# broker: test.mosquitto.org
# port: 1883
# client_id: some_client_id
wmbus_radio:
radio_type: SX1276
cs_pin: GPIO18
reset_pin: GPIO14
irq_pin: GPIO35
# frequency: 868.950
# all_drivers: True
# sync_mode: True
# log_all: True
on_frame:
- then:
- logger.log:
format: "RSSI: %ddBm T: %s (%d)"
args: [ frame->rssi(), frame->as_hex().c_str(), frame->data().size() ]
#- then:
#- repeat:
#count: 3
#then:
# - output.turn_on: status_led
#- delay: 100ms
#- delay: 100ms
# - mark_as_handled: True
# then:
# - mqtt.publish:
# topic: wmbus-test/telegram_rtl
# payload: !lambda return frame->as_rtlwmbus();
# - mark_as_handled: True
# then:
# - socket_transmitter.send:
# data: !lambda return frame->as_hex();
wmbus_meter:
- id: water_meter
meter_id: 0xtwoj id nakladki
type: apator162
key: "00000000000000000000000000000000"
- id: electricity_meter
meter_id: 0xtwoj id licznika
type: amiplus
key: "xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
mode:
- T1
- C1
sensor:
- platform: wmbus_meter
parent_id: water_meter
field: total_m3
device_class: water
name: Zużycie wody
accuracy_decimals: 3
state_class: total_increasing
unit_of_measurement: "m³"
icon: "mdi:water"
- platform: wmbus_meter
parent_id: electricity_meter
field: total_energy_consumption_kwh
name: Suma konsumpcji
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:transmission-tower-export"
- platform: wmbus_meter
parent_id: electricity_meter
field: current_power_consumption_kw
name: Aktualny pobór
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:transmission-tower"
- platform: wmbus_meter
parent_id: electricity_meter
field: total_energy_production_kwh
name: Suma produkcji
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:transmission-tower-import"
- platform: wmbus_meter
parent_id: electricity_meter
field: current_power_production_kw
name: Aktualna produkcja
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:solar-power-variant"
- platform: wmbus_meter
parent_id: electricity_meter
field: voltage_at_phase_1_v
name: Faza V1
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:lightning-bolt"
- platform: wmbus_meter
parent_id: electricity_meter
field: voltage_at_phase_2_v
name: Faza V2
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:lightning-bolt"
- platform: wmbus_meter
parent_id: electricity_meter
field: voltage_at_phase_3_v
name: Faza V3
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:lightning-bolt"
- platform: wmbus_meter
parent_id: electricity_meter
field: rssi_dbm
name: Licznik RSSI
icon: "mdi:wifi"
2 polubienia
SX1276 ESP32 LoRa 868 MHz-915 MHz
Wrzucam wersję z dodanym wyswietlaczem. Pierwsza wersja była bez
esphome:
name: wmbus-lora
friendly_name: WMBus Lora
platformio_options:
upload_speed: 921600
external_components:
- source: github://SzczepanLeon/esphome-components@main
refresh: 0d
esp32:
board: heltec_wifi_lora_32_V2
flash_size: 8MB
framework:
type: esp-idf
logger:
id: component_logger
level: DEBUG
baud_rate: 0
api:
encryption:
key: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
ota:
platform: esphome
password: "xxxxxxxxxxxxxxxxxxxxxxxxx"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
ap:
ssid: "Wmbus-Lora Fallback Hotspot"
password: "i1QI0lIitl1i"
web_server:
version: 3
time:
- platform: sntp
id: sntp_time
spi:
clk_pin:
number: GPIO5
ignore_strapping_warning: true
mosi_pin: GPIO27
miso_pin: GPIO19
wmbus_radio:
radio_type: SX1276
cs_pin: GPIO18
reset_pin: GPIO14
irq_pin: GPIO35
on_frame:
- then:
- logger.log:
format: "RSSI: %ddBm T: %s (%d)"
args: [ frame->rssi(), frame->as_hex().c_str(), frame->data().size() ]
wmbus_meter:
- id: water_meter
meter_id: 0xyour_id
type: apator162
key: "00000000000000000000000000000000"
- id: electricity_meter
meter_id: 0xyour_id
type: amiplus
key: "your_key"
mode:
- T1
- C1
output:
- platform: gpio
id: vext_output
pin: GPIO21
- platform: gpio
id: oled_reset
pin: GPIO16
inverted: True
sensor:
- platform: wmbus_meter
parent_id: water_meter
field: total_m3
device_class: water
name: Zużycie wody
id: woda
accuracy_decimals: 3
state_class: total_increasing
unit_of_measurement: "m³"
icon: "mdi:water"
- platform: wmbus_meter
parent_id: electricity_meter
field: total_energy_consumption_kwh
name: Suma konsumpcji
id: suma_kons
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:transmission-tower-export"
- platform: wmbus_meter
parent_id: electricity_meter
field: current_power_consumption_kw
name: Aktualny pobór
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:transmission-tower"
- platform: wmbus_meter
parent_id: electricity_meter
field: total_energy_production_kwh
name: Suma produkcji
id: suma_prod
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:transmission-tower-import"
- platform: wmbus_meter
parent_id: electricity_meter
field: current_power_production_kw
name: Aktualna produkcja
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:solar-power-variant"
- platform: wmbus_meter
parent_id: electricity_meter
field: voltage_at_phase_1_v
name: Faza V1
id: faza1
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:lightning-bolt"
- platform: wmbus_meter
parent_id: electricity_meter
field: voltage_at_phase_2_v
name: Faza V2
id: faza2
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:lightning-bolt"
- platform: wmbus_meter
parent_id: electricity_meter
field: voltage_at_phase_3_v
name: Faza V3
id: faza3
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
icon: "mdi:lightning-bolt"
- platform: wmbus_meter
parent_id: electricity_meter
field: rssi_dbm
name: Licznik RSSI
icon: "mdi:wifi"
i2c:
sda: GPIO4
scl: GPIO15
scan: true
font:
- file: "gfonts://Roboto"
id: font_small
size: 12
- file: "gfonts://Roboto"
id: font_big
size: 16
display:
- platform: ssd1306_i2c
model: "SSD1306 128x64"
address: 0x3C
id: oled
pages:
- id: page1
lambda: |-
it.printf(0, 16, id(font_small), "Faza1: %.1f V", id(faza1).state);
it.printf(0, 28, id(font_small), "Faza2: %.1f V", id(faza2).state);
it.printf(0, 40, id(font_small), "Faza3: %.1f V", id(faza3).state);
- id: page2
lambda: |-
it.printf(0, 16, id(font_small), "Konsumpcja: %.1f kWh", id(suma_kons).state);
it.printf(0, 28, id(font_small), "Produkcja: %.1f kWh", id(suma_prod).state);
it.printf(0, 40, id(font_small), "Woda: %.3f m3", id(woda).state);
http_request:
verify_ssl: false
timeout: 10s
useragent: esphome/wmbus
interval:
- interval: 10s
then:
- display.page.show_next: oled
- interval: 60s
then:
- http_request.get:
url: !lambda |-
char url[512];
// Sprawdzenie wartości NaN, zamiana na 0
float sk = isnan(id(suma_kons).state) ? 0.0 : id(suma_kons).state;
float sp = isnan(id(suma_prod).state) ? 0.0 : id(suma_prod).state;
float f1 = isnan(id(faza1).state) ? 0.0 : id(faza1).state;
float f2 = isnan(id(faza2).state) ? 0.0 : id(faza2).state;
float f3 = isnan(id(faza3).state) ? 0.0 : id(faza3).state;
float w = isnan(id(woda).state) ? 0.0 : id(woda).state;
snprintf(url, sizeof(url),
"http://api.thingspeak.com/update?api_key=your_key"
"&field1=%.3f&field2=%.3f&field3=%.3f&field4=%.3f&field5=%.3f&field6=%.3f",
sk, // field1 = suma_kons
sp, // field2 = suma_prod
f1, // field4 = faza1
f2, // field5 = faza2
f3), // field6 = faza3
w; // field3 = woda
return std::string(url);
2 polubienia
Konfiguracja dla " ESP32 LilyGO LoRa SX1276 v1.3" z Tauron e-licznik HAN (wmbus).
Konfiguracja:
esphome:
name: esp-tauron
friendly_name: esp-tauron
platformio_options:
upload_speed: 921600
comment: Garaż
external_components:
- source: github://SzczepanLeon/esphome-components@main
refresh: 0d
esp32:
board: ttgo-lora32-v1
framework:
type: esp-idf
# Enable logging
logger:
id: component_logger
level: INFO
baud_rate: 115200
# Enable Home Assistant API
api:
encryption:
key: "X"
web_server:
version: 3
ota:
- platform: esphome
password: "X"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Esp-Tauron Fallback Hotspot"
password: "X"
captive_portal:
time:
- platform: homeassistant
spi:
clk_pin:
number: GPIO5
ignore_strapping_warning: true
mosi_pin: GPIO27
miso_pin: GPIO19
wmbus_radio:
radio_type: SX1276
cs_pin: GPIO18
reset_pin: GPIO14
irq_pin: GPIO33
wmbus_meter:
- id: electricity_meter
meter_id: "19390"
type: amiplus
key: "X"
sensor:
# --- Moc Chwilowa (kW) ---
- platform: wmbus_meter
parent_id: electricity_meter
field: "current_power_consumption_kw"
name: "Pobór mocy chwilowej"
unit_of_measurement: "kW"
accuracy_decimals: 3
device_class: power
state_class: measurement
- platform: wmbus_meter
parent_id: electricity_meter
field: "current_power_production_kw"
name: "Produkcja mocy chwilowej"
unit_of_measurement: "kW"
accuracy_decimals: 3
device_class: power
state_class: measurement
# --- Energia Całkowita POBRANA (kWh) ---
- platform: wmbus_meter
parent_id: electricity_meter
field: "total_energy_consumption_tariff_1_kwh"
name: "Całkowity pobór energii (Taryfa 1)"
unit_of_measurement: "kWh"
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
- platform: wmbus_meter
parent_id: electricity_meter
field: "total_energy_consumption_tariff_2_kwh"
name: "Całkowity pobór energii (Taryfa 2)"
unit_of_measurement: "kWh"
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
- platform: wmbus_meter
parent_id: electricity_meter
field: "total_energy_consumption_tariff_3_kwh"
name: "Całkowity pobór energii (Taryfa 3)"
unit_of_measurement: "kWh"
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
# --- Energia Całkowita ODDANA (kWh) ---
- platform: wmbus_meter
parent_id: electricity_meter
field: "total_energy_production_tariff_1_kwh"
name: "Całkowita produkcja energii (Taryfa 1)"
unit_of_measurement: "kWh"
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
- platform: wmbus_meter
parent_id: electricity_meter
field: "total_energy_production_tariff_2_kwh"
name: "Całkowita produkcja energii (Taryfa 2)"
unit_of_measurement: "kWh"
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
- platform: wmbus_meter
parent_id: electricity_meter
field: "total_energy_production_tariff_3_kwh"
name: "Całkowita produkcja energii (Taryfa 3)"
unit_of_measurement: "kWh"
accuracy_decimals: 3
device_class: energy
state_class: total_increasing
# --- Napięcie (V) ---
- platform: wmbus_meter
parent_id: electricity_meter
field: "voltage_at_phase_1_v"
name: "Napięcie (Faza 1)"
unit_of_measurement: "V"
accuracy_decimals: 0
device_class: voltage
state_class: measurement
- platform: wmbus_meter
parent_id: electricity_meter
field: "voltage_at_phase_2_v"
name: "Napięcie (Faza 2)"
unit_of_measurement: "V"
accuracy_decimals: 0
device_class: voltage
state_class: measurement
- platform: wmbus_meter
parent_id: electricity_meter
field: "voltage_at_phase_3_v"
name: "Napięcie (Faza 3)"
unit_of_measurement: "V"
accuracy_decimals: 0
device_class: voltage
state_class: measurement
Jedyny myk jest taki że wartość w e-liczniku jako meter_id trzeba przekonwertować z hexa na dec i potem włożyć w plik konfiguracyjny. Działa, dziękuje!
1 polubienie
A ma ktoś działający yaml z wyświetlaczem dla Lilygo T3S3?
No właśnei mi też nie działa. Jak przyjechał z wgranym softem to coś wyświetlało 
A potem pewnie wgrales nie to co trzeba.
Pewnie tak 
Ale bądźmy realistami: dokumentacja do tego praktycznie nie istnieje.
Zgodza sie 
Tak samo jak ¥.
Ale zbliza sie kolejna (r)ewolucja w komponencie, pewnie jakas dokumentacja sie pojawi.
Złożyłem SX1276 z ESP32S3 , stworzyłem taki config:
esphome:
name: czytnik-wmbus
friendly_name: czytnik_wmbus
platformio_options:
upload_speed: 921600
external_components:
- source: github://SzczepanLeon/esphome-components@main
esp32:
board: esp32-s3-devkitc-1
flash_size: 8MB
framework:
type: esp-idf
# Enable logging
logger:
level: DEBUG
# Enable Home Assistant API
api:
encryption:
key: "ixxxxxxx"
ota:
- platform: esphome
password: "xxxxxxxxxxxxxxxxxx"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Czytnik-Wmbus Fallback Hotspot"
password: "xxxxxxxxxL"
web_server:
version: 3
captive_portal:
time:
- platform: homeassistant
spi:
clk_pin: GPIO18
mosi_pin: GPIO17
miso_pin: GPIO16
wmbus_radio:
radio_type: SX1276
cs_pin: GPIO8
reset_pin: GPIO3
irq_pin: GPIO38
wmbus_meter:
- id: home_water_meter
meter_id: "57754755"
type: apator162
key: "00000000000000000000000000000000"
- id: garden_water_meter
meter_id: "1885828456"
type: apator162
key: "00000000000000000000000000000000"
- id: garden_water_meter2
meter_id: "108042277"
type: apator162
key: "00000000000000000000000000000000"
- id: garden_water_meter3
meter_id: "121190275"
type: apator162
key: "00000000000000000000000000000000"
sensor:
- platform: wmbus_meter
parent_id: home_water_meter
field: total
name: "Licznik Wody Dom"
accuracy_decimals: 3
unit_of_measurement: "m³"
device_class: water
state_class: total_increasing
- platform: wmbus_meter
parent_id: garden_water_meter
field: total
name: "Licznik Wody Ogród"
accuracy_decimals: 3
unit_of_measurement: "m³"
device_class: water
state_class: total_increasing
- platform: wmbus_meter
parent_id: garden_water_meter2
field: total
name: "Licznik Wody Ogród2"
accuracy_decimals: 3
unit_of_measurement: "m³"
device_class: water
state_class: total_increasing
- platform: wmbus_meter
parent_id: garden_water_meter3
field: total
name: "Licznik Wody Ogród3"
accuracy_decimals: 3
unit_of_measurement: "m³"
device_class: water
state_class: total_increasing
- platform: uptime
name: "Uptime"
id: uptime_sensor
- platform: wifi_signal
name: "WiFi Signal dBm"
id: wifi_signal_db
update_interval: 60s
- platform: copy
source_id: wifi_signal_db
name: "WiFi Signal %"
id: wifi_signal_percent
filters:
- lambda: return min(max(2 * (x + 100.0), 0.0), 100.0);
unit_of_measurement: "%"
- platform: internal_temperature
name: "CPU Temperature"
id: cpu_temp
- platform: template
name: "Free Heap"
id: free_heap
lambda: 'return heap_caps_get_free_size(MALLOC_CAP_INTERNAL);'
unit_of_measurement: "B"
update_interval: 30s
filters:
- lambda: return x / 1024.0;
accuracy_decimals: 1
W logach jest np:
[21:19:46.230][D][packet:097]: Have data from radio (191 bytes)
[21:19:46.238][D][wmbusmeters:351]: raw packet "6B271C58D59A39996C4D659A599593D26D264E694B596696B1970DD31A598D6C654F1693C639564E3A533AC972965C74B16A6CC4D4DA7266936A9A71A5C6B26B4666A72365C5CA5CCA9D0B371A56A5635C94B72666639C365C56996C93C74D0D369D1C36C6A56594F42F28E3A7168B2D3C6373437194ED0D38BD31D1372CD259659694D958DA66C74A6670EC8D69A70D4DA9B4359D1CD1968B34ED2568D8EC9A5D234DAC9CD0E8D939A4E53AC66C665399CA6713C5CA5C5A3D29B26C9AD165"
[21:19:46.246][D][wmbusmeters:351]: (wmbus) trimming frame A "6E440106259870060507CACA7A9300608541CDF5B0D97D67DB907BF7289E99DC80F8D1764A676FFDF46E6C5AFE19D4F4EFC31DF0F014934A5A2419D0A0E7DCC11FC41869557C3EBBFD6337DB4C1D92C123CDC748C9999F7501FADCFA42E1664176AC15C4C56312C961B8A9CB76E4C2B5267928585925EA47D4F40BCF8AE6C0"
[21:19:46.251][D][wmbusmeters:351]: (wmbus) trimmed frame A "6E4401062598700605077A9300608541CDF5B0D97D67DB907BF799DC80F8D1764A676FFDF46E6C5AFE19EFC31DF0F014934A5A2419D0A0E7DCC11869557C3EBBFD6337DB4C1D92C123CDC9999F7501FADCFA42E1664176AC15C412C961B8A9CB76E4C2B5267928585925D4F40BCF8A"
[21:19:46.259][D][wmbusmeters:351]: (wmbus) checkWMBUSFrame "6E4401062598700605077A9300608541CDF5B0D97D67DB907BF799DC80F8D1764A676FFDF46E6C5AFE19EFC31DF0F014934A5A2419D0A0E7DCC11869557C3EBBFD6337DB4C1D92C123CDC9999F7501FADCFA42E1664176AC15C412C961B8A9CB76E4C2B5267928585925D4F40BCF8A"
[21:19:46.264][I][wmbus:047]: Have data (111 bytes) [RSSI: -51dBm, mode: T1 A]
[21:19:46.273][D][wmbusmeters:779]: (meter) apator162-06709825(0) apator162 handling telegram from 06709825.M=APA.V=05.T=07
[21:19:46.279][D][wmbusmeters:267]: (telegram) DLL L=6e C=44 (from meter SND_NR) M=0601 (APA) A=06709825 VER=05 TYPE=07 (Water meter) (driver apator162) DEV=czytnik_wmbus RSSI=-51
[21:19:46.285][D][wmbusmeters:351]: (TPL) AES CBC IV decrypting "41CDF5B0D97D67DB907BF799DC80F8D1764A676FFDF46E6C5AFE19EFC31DF0F014934A5A2419D0A0E7DCC11869557C3EBBFD6337DB4C1D92C123CDC9999F7501FADCFA42E1664176AC15C412C961B8A9CB76E4C2B5267928585925D4F40BCF8A"
[21:19:46.292][D][wmbusmeters:357]: (TPL) decrypted "2F2F0F4EA5AC99880208431203874073361075360261090010EE8200007B01EE82000098820000398200003F790000CD6A00006F5E00006D120000390A00001D030000560000005600000000000000A08E17CD04FFFFFFFFFFFFFFFFFFFF6876"
[21:19:46.296][D][wmbusmeters:322]: (telegram) TPL CI=7a
[21:19:46.300][D][wmbusmeters:326]: ACC=93 STS=00 CFG=8560 (bidirectional AES_CBC_IV nb=6 cntn=0 ra=0 hc=0)
[21:19:46.309][I][wmbus:056]: Telegram handled by 1 handlers
[21:19:47.437][D][packet:097]: Have data from radio (8 bytes)
Ale żaden sensor się nie uaktualnił… Ani w web ,ani tym bardziejencjaw HA…
Próbowałem meter_id wpisywać i jako 0x ,i z zamienianiem HEX na DEC ( tu akurat zamienione) , i nic się nie zmienia… Co robię źle…
Teoretycznie piszę ,że “Telegram handled by 1 handlers” , ale wcale się tym nie zajął 
Próbowałeś z ID 0x06709825 ?
Tak, ale dla pewności jeszcze raz zrobiłem , nic się nie zmieniło ,( no może teraz jest 2 handlers )
[00:25:39.350][D][wmbusmeters:351]: raw packet "6B271C58D59A39996C4D659A599593D26D264E68EC596696B19C9CD25C8BD0D8CE9663569993728D9D1635638B68E8EC9A62F2CA98DA3A39663B138B9698D9D314E9699B1A6598E634DC93C74669953B3169A65671366964BCAC8D6729C99A4BA667264DC965672C992D3A5694ED1CA6365936C36C9723B135CC4D726596D31B198E564B2F2D269A34D6CA699339967466CD29B0ED0D2D6CA9C8D7197299536997194F1A71C8D68DA56966C712CBC8D38EB1C669CA368D38EC539A5D0D3725"
[00:25:39.357][D][wmbusmeters:351]: (wmbus) trimming frame A "6E440106259870060507CACA7AB8006085E4C9E3C1B29A10A51EB5C0102362B8AA3EEFB62B9A2D239FB5CD7F658655BA11E7DC5F978D6650475F53E8B04FE5F3FA4A74995EE537F092C4FB5518189E2D14D14A00CD85B9533ECAAB70EAA7255C58CF82C130EFE1454F9765457DFDE161F09ADD33E122845FEB6122D7A9C11E"
[00:25:39.363][D][wmbusmeters:351]: (wmbus) trimmed frame A "6E4401062598700605077AB8006085E4C9E3C1B29A10A51EB5C062B8AA3EEFB62B9A2D239FB5CD7F658611E7DC5F978D6650475F53E8B04FE5F374995EE537F092C4FB5518189E2D14D1CD85B9533ECAAB70EAA7255C58CF82C1E1454F9765457DFDE161F09ADD33E122EB6122D7A9"
[00:25:39.370][D][wmbusmeters:351]: (wmbus) checkWMBUSFrame "6E4401062598700605077AB8006085E4C9E3C1B29A10A51EB5C062B8AA3EEFB62B9A2D239FB5CD7F658611E7DC5F978D6650475F53E8B04FE5F374995EE537F092C4FB5518189E2D14D1CD85B9533ECAAB70EAA7255C58CF82C1E1454F9765457DFDE161F09ADD33E122EB6122D7A9"
[00:25:39.375][I][wmbus:047]: Have data (111 bytes) [RSSI: -51dBm, mode: T1 A]
[00:25:39.389][D][wmbusmeters:779]: (meter) apator162-06709825(0) apator162 handling telegram from 06709825.M=APA.V=05.T=07
[00:25:39.392][D][wmbusmeters:267]: (telegram) DLL L=6e C=44 (from meter SND_NR) M=0601 (APA) A=06709825 VER=05 TYPE=07 (Water meter) (driver apator162) DEV=czytnik_wmbus RSSI=-51
[00:25:39.398][D][wmbusmeters:351]: (TPL) AES CBC IV decrypting "E4C9E3C1B29A10A51EB5C062B8AA3EEFB62B9A2D239FB5CD7F658611E7DC5F978D6650475F53E8B04FE5F374995EE537F092C4FB5518189E2D14D1CD85B9533ECAAB70EAA7255C58CF82C1E1454F9765457DFDE161F09ADD33E122EB6122D7A9"
[00:25:39.404][D][wmbusmeters:357]: (TPL) decrypted "2F2F0F1306CC9988020843130383000D3213062C0345820610EE8200007B01EE82000098820000398200003F790000CD6A00006F5E00006D120000390A00001D030000560000005600000000000000A08E17CD04FFFFFFFFFFFFFFFFFFFF5F99"
[00:25:39.409][D][wmbusmeters:322]: (telegram) TPL CI=7a
[00:25:39.413][D][wmbusmeters:326]: ACC=b8 STS=00 CFG=8560 (bidirectional AES_CBC_IV nb=6 cntn=0 ra=0 hc=0)
[00:25:39.422][D][wmbusmeters:779]: (meter) apator162-06709825(0) apator162 handling telegram from 06709825.M=APA.V=05.T=07
[00:25:39.428][D][wmbusmeters:267]: (telegram) DLL L=6e C=44 (from meter SND_NR) M=0601 (APA) A=06709825 VER=05 TYPE=07 (Water meter) (driver apator162) DEV=czytnik_wmbus RSSI=-51
[00:25:39.435][D][wmbusmeters:351]: (TPL) AES CBC IV decrypting "E4C9E3C1B29A10A51EB5C062B8AA3EEFB62B9A2D239FB5CD7F658611E7DC5F978D6650475F53E8B04FE5F374995EE537F092C4FB5518189E2D14D1CD85B9533ECAAB70EAA7255C58CF82C1E1454F9765457DFDE161F09ADD33E122EB6122D7A9"
[00:25:39.442][D][wmbusmeters:357]: (TPL) decrypted "2F2F0F1306CC9988020843130383000D3213062C0345820610EE8200007B01EE82000098820000398200003F790000CD6A00006F5E00006D120000390A00001D030000560000005600000000000000A08E17CD04FFFFFFFFFFFFFFFFFFFF5F99"
[00:25:39.447][D][wmbusmeters:322]: (telegram) TPL CI=7a
[00:25:39.450][D][wmbusmeters:326]: ACC=b8 STS=00 CFG=8560 (bidirectional AES_CBC_IV nb=6 cntn=0 ra=0 hc=0)
[00:25:39.460][I][wmbus:056]: Telegram handled by 2 handlers
W każdym razie sensor się nie zaktualizował…
1 polubienie
Nie wierzyłem , ale dokładnie to był ten błąd Dzięki
a w najnowszym esphome ESPHome 2025.12.0 - December 2025 - ESPHome - Smart Home Made Simple dodano nowy komponent, można to jakoś u nas wykorzystać?
nie - niestety troche jeszcze brakuje po stronie ESPHome
@_Szczepan zerknij na githuba. Wrzuciłem mały Issue - chodzi o dostosowanie softu do ESPHome 2025.12.0
Czyli to : ?
1. wmbus_common zawsze kompiluje wszystkie drivery
drivers: w YAML (np. hydrodigit) jest walidowane, ale przy buildzie ESP-IDF i tak kompilowane są wszystkie driver_*.cpp.
src_filter nie działa z ESP-IDF (warning w logu), więc obecnie nie da się ograniczyć driverów bez patcha CMake.
Issue #276 nadal aktualne.
2.Kolizja symbolu STATUS na ESP32-S3
W wmbus_common/meters.h enum zawiera STATUS, co koliduje z STATUS z ESP-IDF (ets_sys.h) → build error.
Lokalne obejście: rename STATUS → np. METER_STATUS.
Sugestia fixu:
– rename enum STATUS
– umożliwić filtrowanie driverów na etapie CMake (zgodnie z drivers: z YAML lub flagą build)
Też macie taki błąd po aktualizacji ESPHome Device Builder (2025.11.5):
INFO Reading configuration /config/esphome/lora.yaml...
INFO Updating https://github.com/SzczepanLeon/esphome-components.git@main
ERROR Unable to import component logger:
Traceback (most recent call last):
File "/esphome/esphome/loader.py", line 199, in _lookup_module
module = importlib.import_module(f"esphome.components.{domain}")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/importlib/__init__.py", line 90, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 999, in exec_module
File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
File "/esphome/esphome/components/logger/__init__.py", line 6, in <module>
from esphome.components.esp32 import (
ImportError: cannot import name 'VARIANT_ESP32C61' from 'esphome.components.esp32' (/data/external_components/5c086c68/components/esp32/__init__.py)
Failed config
logger: [source /config/esphome/lora.yaml:21]
Component not found: logger.
id: component_logger
level: DEBUG
baud_rate: 0
Już to przerobiłem ( bo mi też się to wywaliło ), spróbuj tak :
external_components:
- source: github://SzczepanLeon/esphome-components@main
components:
- wmbus_common
- wmbus_radio
- wmbus_meter
- socket_transmitter
I tu mała UWAGA : Uwaga: po update ESPHome 2025.x wmbus_common skompiluje Ci wszystkie drivery niezależnie od drivers: – znany problem (#276).