Cześć,
czy mógłbym prosić o pomoc w konfiguracji sensorów do tego licznika?
Wgrałem ESP i moduł odbiera ramki. Jednak kiedy taką ramkę analizuję za pomocą https://wmbusmeters.org/ to część danych jest dalej zaszyfrowana.
Według informacji jakie dostałem od operatora powinienem móc odczytać następujące parametry:
- numer fabryczny licznika,
- zegar,
- energia czynna pobrana we wszystkich strefach,
- energia czynna oddana we wszystkich strefach,
- energia bierna pobrana we wszystkich strefach,
- energia bierna oddana we wszystkich strefach,
- wypadkowa moc chwilowa czynna pobrana,
- wypadkowa moc chwilowa czynna oddana,
a odczyt wykonywany jest cyklicznie co 1 minutę.
Z przeanalizowanej ramki dostaję jednak tylko część parametrów.
Strona https://www.miller-alex.de/WMbus pokazuje jednak już wszystkie parametry (chyba). Z czego to wynika i jak powinna wyglądać moja konfiguracja?
Poniżej załączam kod yaml oraz log z działania.
YAML
esphome:
name: wmbus
friendly_name: wmbus
esp32:
board: esp32dev
framework:
type: arduino
time:
- platform: sntp
id: sntp_time
servers:
- tempus1.gum.gov.pl
- tempus2.gum.gov.pl
external_components:
- source: github://SzczepanLeon/esphome-components@main
refresh: 0d
components: [ wmbus ]
wmbus:
mosi_pin: GPIO23
miso_pin: GPIO19
clk_pin: GPIO18
cs_pin: GPIO5
gdo0_pin: GPIO12
gdo2_pin: GPIO27
led_pin: GPIO2
led_blink_time: "1s"
frequency: 868.950
all_drivers: True
sync_mode: True
log_all: True
sensor:
- platform: wmbus
meter_id: 0x56505530
type: amiplus
key: "11111111111111111111111111111111"
sensors:
- name: "my energy RSSi"
field: "rssi"
accuracy_decimals: 0
unit_of_measurement: "dBm"
device_class: "signal_strength"
state_class: "measurement"
entity_category: "diagnostic"
- platform: wmbus
meter_id: 0x17099985
type: rfmtx1
# Enable logging
logger:
level: DEBUG
# Enable Home Assistant API
api:
encryption:
key: "REDACTED"
ota:
- platform: esphome
password: "REDACTED"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "REDACTED"
password: "REDACTED"
captive_portal:
Log
INFO ESPHome 2025.3.2
INFO Reading configuration /config/esphome/wmbus.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 GPIO12 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING 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.189 using esphome API
INFO Successfully connected to wmbus @ 192.168.1.189 in 0.079s
INFO Successful handshake with wmbus @ 192.168.1.189 in 0.146s
[19:21:02][I][app:100]: ESPHome version 2025.3.2 compiled on Mar 28 2025, 19:15:44
[19:21:02][C][wifi:600]: WiFi:
[19:21:02][C][wifi:428]: Local MAC: EC:E3:34:DB:9D:18
[19:21:02][C][wifi:433]: SSID: 'T-Mobile_Swiatlowod_8936'[redacted]
[19:21:02][C][wifi:436]: IP Address: 192.168.1.189
[19:21:02][C][wifi:440]: BSSID: 58:9B:4A:F2:CC:C0[redacted]
[19:21:02][C][wifi:441]: Hostname: 'wmbus'
[19:21:02][C][wifi:443]: Signal strength: -13 dB ▂▄▆█
[19:21:02][C][wifi:447]: Channel: 8
[19:21:02][C][wifi:448]: Subnet: 255.255.255.0
[19:21:02][C][wifi:449]: Gateway: 192.168.1.1
[19:21:02][C][wifi:450]: DNS1: 192.168.1.1
[19:21:02][C][wifi:451]: DNS2: 0.0.0.0
[19:21:03][C][logger:177]: Logger:
[19:21:03][C][logger:178]: Max Level: DEBUG
[19:21:03][C][logger:179]: Initial Level: DEBUG
[19:21:03][C][logger:181]: Log Baud Rate: 115200
[19:21:03][C][logger:182]: Hardware UART: UART0
[19:21:03][C][captive_portal:089]: Captive Portal:
[19:21:03][C][sntp:042]: SNTP Time:
[19:21:03][C][sntp:045]: Server 0: 'tempus1.gum.gov.pl'
[19:21:03][C][sntp:045]: Server 1: 'tempus2.gum.gov.pl'
[19:21:03][C][mdns:116]: mDNS:
[19:21:03][C][mdns:117]: Hostname: wmbus
[19:21:03][C][esphome.ota:073]: Over-The-Air updates:
[19:21:03][C][esphome.ota:074]: Address: wmbus.local:3232
[19:21:03][C][esphome.ota:075]: Version: 2
[19:21:03][C][esphome.ota:078]: Password configured
[19:21:03][C][safe_mode:018]: Safe Mode:
[19:21:03][C][safe_mode:020]: Boot considered successful after 60 seconds
[19:21:03][C][safe_mode:021]: Invoke after 10 boot attempts
[19:21:03][C][safe_mode:023]: Remain in safe mode for 300 seconds
[19:21:03][C][api:140]: API Server:
[19:21:03][C][api:141]: Address: wmbus.local:6053
[19:21:03][C][api:143]: Using noise encryption: YES
[19:21:03][C][wmbus:413]: wM-Bus v4.2.0-1.17.1-b8f4a945:
[19:21:03][C][wmbus:426]: LED:
[19:21:03][C][wmbus:427]: Pin: GPIO2
[19:21:03][C][wmbus:428]: Duration: 1000 ms
[19:21:03][C][wmbus:431]: Chip ID: 189DDB34E3EC
[19:21:03][C][wmbus:433]: CC1101 frequency: 868.950 MHz
[19:21:03][C][wmbus:434]: CC1101 SPI bus:
[19:21:03][C][wmbus:438]: MOSI Pin: GPIO23
[19:21:03][C][wmbus:439]: MISO Pin: GPIO19
[19:21:03][C][wmbus:440]: CLK Pin: GPIO18
[19:21:07][D][mbus:035]: Received T1 A frame
[19:21:07][I][wmbus:094]: Using selected driver amiplus (detected driver was amiplus)
[19:21:07][I][wmbus:106]: amiplus [0x56505530] RSSI: -84dBm T: 5E4401063055505601027AFF0050056EB06B2CFB37AD457D505F8DCBFF2F1BBA9DA0EAE97C77ED7AE586EEED38A62641C5410A24926AB578EB6BA80682240B95337D405402F72DE005192E805F414F2361913772300DA3BBA439BE56A5B70E (95) T1 A
[19:21:07][D][meters.cpp:1989]: (meter) created ESPHome amiplus 56505530 encrypted
[19:21:07][D][meters.cpp:913]: (meter) ESPHome(0) amiplus handling telegram from 56505530.M=APA.V=01.T=02
[19:21:07][D][sensor:094]: 'my energy RSSi': Sending state -84.00000 dBm with 0 decimals of accuracy
[19:21:07][W][component:237]: Component wmbus took a long time for an operation (129 ms).
[19:21:07][W][component:238]: Components should block for at most 30 ms.
[19:24:07][D][mbus:035]: Received T1 A frame
[19:24:07][I][wmbus:094]: Using selected driver amiplus (detected driver was amiplus)
[19:24:07][I][wmbus:106]: amiplus [0x56505530] RSSI: -84dBm T: 5E4401063055505601027A02005005D34524E30A66F4A9ACE80DA70BD8E0B4EBA88B40CE9B64548A036A530728D1395C6A4C24363F103190F39DFA77DAB570818B8699C97CC0118D14A6681AEC96491D2815506342C1D36E96FEF7455D7BCD (95) T1 A
[19:24:07][D][meters.cpp:1989]: (meter) created ESPHome amiplus 56505530 encrypted
[19:24:07][D][meters.cpp:913]: (meter) ESPHome(0) amiplus handling telegram from 56505530.M=APA.V=01.T=02
[19:24:07][D][sensor:094]: 'my energy RSSi': Sending state -84.00000 dBm with 0 decimals of accuracy
[19:24:07][W][component:237]: Component wmbus took a long time for an operation (130 ms).
[19:24:07][W][component:238]: Components should block for at most 30 ms.
[19:25:07][D][mbus:035]: Received T1 A frame
[19:25:07][I][wmbus:094]: Using selected driver amiplus (detected driver was amiplus)
[19:25:07][I][wmbus:106]: amiplus [0x56505530] RSSI: -84dBm T: 5E4401063055505601027A030050052D94197C124F0C1EC687064AAC0BE50571A4FE166A9A96005FFDF82B2BB6DBE4121416FAC5FB1D180D1D31DFB4632E04EA1D77B4DF7903A0071BEC23840E0782658EBAAB349F957AEB0430739F732BE5 (95) T1 A
[19:25:07][D][meters.cpp:1989]: (meter) created ESPHome amiplus 56505530 encrypted
[19:25:07][D][meters.cpp:913]: (meter) ESPHome(0) amiplus handling telegram from 56505530.M=APA.V=01.T=02
[19:25:07][D][sensor:094]: 'my energy RSSi': Sending state -84.00000 dBm with 0 decimals of accuracy
[19:25:07][W][component:237]: Component wmbus took a long time for an operation (131 ms).
[19:25:07][W][component:238]: Components should block for at most 30 ms.
[19:26:07][D][mbus:035]: Received T1 A frame
[19:26:07][I][wmbus:094]: Using selected driver amiplus (detected driver was amiplus)
[19:26:07][I][wmbus:106]: amiplus [0x56505530] RSSI: -84dBm T: 5E4401063055505601027A040050059BFBF287D2B164F5CC0378DEA5224DAE83293E83A74E1502059E7888F2BC6D746F68D5BDD691189A6F24CC8FD6836E1E21B41BDD98C519EE7B2D834E250A2B5559C5ABB76FB6DDCA2CE411ECFDE06418 (95) T1 A
[19:26:07][D][meters.cpp:1989]: (meter) created ESPHome amiplus 56505530 encrypted
[19:26:07][D][meters.cpp:913]: (meter) ESPHome(0) amiplus handling telegram from 56505530.M=APA.V=01.T=02
[19:26:07][D][sensor:094]: 'my energy RSSi': Sending state -84.00000 dBm with 0 decimals of accuracy
[19:26:07][W][component:237]: Component wmbus took a long time for an operation (130 ms).
[19:26:07][W][component:238]: Components should block for at most 30 ms.
[19:27:07][D][mbus:035]: Received T1 A frame
[19:27:07][I][wmbus:094]: Using selected driver amiplus (detected driver was amiplus)
[19:27:07][I][wmbus:106]: amiplus [0x56505530] RSSI: -85dBm T: 5E4401063055505601027A050050058D84E536BBB39C4AD0CBF9A086C7AF192273203AE74A9C2F50D4F93F54527F908FC3C180803706309388F6C44A88282627A6383866B23C7823F616D3557C69434A1DE20F486738CAA702128E03D606AF (95) T1 A
[19:27:07][D][meters.cpp:1989]: (meter) created ESPHome amiplus 56505530 encrypted
[19:27:07][D][meters.cpp:913]: (meter) ESPHome(0) amiplus handling telegram from 56505530.M=APA.V=01.T=02
[19:27:07][D][sensor:094]: 'my energy RSSi': Sending state -85.00000 dBm with 0 decimals of accuracy
[19:27:07][W][component:237]: Component wmbus took a long time for an operation (129 ms).
[19:27:07][W][component:238]: Components should block for at most 30 ms.
[19:28:07][D][mbus:035]: Received T1 A frame
[19:28:07][I][wmbus:094]: Using selected driver amiplus (detected driver was amiplus)
[19:28:07][I][wmbus:106]: amiplus [0x56505530] RSSI: -85dBm T: 5E4401063055505601027A06005005AD5CEBA1E9400CC98793796B612B45CC763E81AC24DBAB7A7B72E9541899B98DAE857EDC982508219D1327DE12597D133A22A2C8B5C76907ABCB7AB7221A84330825FA7397B91B52D9A688CC4002140A (95) T1 A
[19:28:07][D][meters.cpp:1989]: (meter) created ESPHome amiplus 56505530 encrypted
[19:28:07][D][meters.cpp:913]: (meter) ESPHome(0) amiplus handling telegram from 56505530.M=APA.V=01.T=02
[19:28:07][D][sensor:094]: 'my energy RSSi': Sending state -85.00000 dBm with 0 decimals of accuracy
[19:28:07][W][component:237]: Component wmbus took a long time for an operation (129 ms).
[19:28:07][W][component:238]: Components should block for at most 30 ms.
[19:29:07][D][mbus:035]: Received T1 A frame
[19:29:07][I][wmbus:094]: Using selected driver amiplus (detected driver was amiplus)
[19:29:07][I][wmbus:106]: amiplus [0x56505530] RSSI: -84dBm T: 5E4401063055505601027A0700500556D9C8243DBBB3F272A02B1BFFCA4E146A83AE9026A47E9FDF68CBBBB8EAB3AD7F64E3D991CF040738BAD4BF6E5A602FA83BEDD86CC95C656815070FBBFCDC7E204E7D665D68814DDBA8587A8289F5B4 (95) T1 A
[19:29:07][D][meters.cpp:1989]: (meter) created ESPHome amiplus 56505530 encrypted
[19:29:07][D][meters.cpp:913]: (meter) ESPHome(0) amiplus handling telegram from 56505530.M=APA.V=01.T=02
[19:29:07][D][sensor:094]: 'my energy RSSi': Sending state -84.00000 dBm with 0 decimals of accuracy
[19:29:07][W][component:237]: Component wmbus took a long time for an operation (130 ms).
[19:29:07][W][component:238]: Components should block for at most 30 ms.
[19:30:07][D][mbus:035]: Received T1 A frame
[19:30:07][I][wmbus:094]: Using selected driver amiplus (detected driver was amiplus)
[19:30:07][I][wmbus:106]: amiplus [0x56505530] RSSI: -84dBm T: 5E4401063055505601027A08005005A0744EE6CCA02488B4E67F864B7929188E3936B48E6DBCD2236FEC4730C78202F68331922EA2791E65386EB500D522EE44B79830A59F7A0ADD2933F443DFB5B3645E68E641B2D5ECB547EDE503EA6DEF (95) T1 A
[19:30:07][D][meters.cpp:1989]: (meter) created ESPHome amiplus 56505530 encrypted
[19:30:07][D][meters.cpp:913]: (meter) ESPHome(0) amiplus handling telegram from 56505530.M=APA.V=01.T=02
[19:30:07][D][sensor:094]: 'my energy RSSi': Sending state -84.00000 dBm with 0 decimals of accuracy
[19:30:07][W][component:237]: Component wmbus took a long time for an operation (129 ms).
[19:30:08][W][component:238]: Components should block for at most 30 ms.
WARNING wmbus @ 192.168.1.189: Connection error occurred: Ping response not received after 90.0 seconds
INFO Processing unexpected disconnect from ESPHome API for wmbus @ 192.168.1.189
WARNING Disconnected from API
WARNING Can't connect to ESPHome API for wmbus @ 192.168.1.189: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.189', port=6053))]: [Errno 113] Connect call failed ('192.168.1.189', 6053) (SocketAPIError)
INFO Trying to connect to wmbus @ 192.168.1.189 in the background
INFO Successfully connected to wmbus @ 192.168.1.189 in 0.020s
INFO Successful handshake with wmbus @ 192.168.1.189 in 0.145s
[19:38:07][D][mbus:035]: Received T1 A frame
[19:38:07][I][wmbus:094]: Using selected driver amiplus (detected driver was amiplus)
[19:38:07][I][wmbus:106]: amiplus [0x56505530] RSSI: -85dBm T: 5E4401063055505601027A1000500503A0D12CF7A5B714352424D451AEEEB312A0BBD151938BBEF4C033F1F6500D1047D548496E66B1C2AC7FF27BE4506694CD918E53B2A2310999A560766D3EB86F62BF6916E6D35A3D0A5E5056B57B3740 (95) T1 A
[19:38:07][D][meters.cpp:1989]: (meter) created ESPHome amiplus 56505530 encrypted
[19:38:07][D][meters.cpp:913]: (meter) ESPHome(0) amiplus handling telegram from 56505530.M=APA.V=01.T=02
[19:38:07][D][sensor:094]: 'my energy RSSi': Sending state -85.00000 dBm with 0 decimals of accuracy
[19:38:07][W][component:237]: Component wmbus took a long time for an operation (130 ms).
[19:38:07][W][component:238]: Components should block for at most 30 ms.
! Nie jestem obeznany w temacie.
Jeśli klucz (key) jest niepoprawny ESPHome będzie w stanie odczytać jedynie parametry techniczne, takie jak: RSSI, LQI
Czyli dopiero po autoryzacji “pozwoli” na odczyt innych danych
1 polubienie
Klucz jest raczej dobry, dostałem go od dostawcy i pozwala na odczyt części danych więc to raczej nie jest jego wina.
Podejrzewam albo nieumiejętną konfigurację (czyli moja wina) albo dostawca jednak skonfigurował licznik inaczej niż napisał.
No nie wiem, w tych logach raczej nie widać żadnych takich danych, które są szyfrowane, więc pierwsze podejrzenie, że klucz jest zły lub podałeś go w konfiguracji w nieprawidłowy sposób.
Ale w konfiguracji nie widzę też niczego poza RSSI…
edit - jakkolwiek zdekodowałem ramkę i klucz jest OK, więc zdefiniuj brakujące sensory
https://wmbusmeters.org/analyze/5e4401063055505601027aff0050056eB06B2cfB37ad457d505f8dcBff2f1BBa9da0eae97c77ed7ae586eeed38a62641c5410a24926aB578eB6Ba80682240B95337d405402f72de005192e805f414f2361913772300da3BBa439Be56a5B70e:auto:11111111111111111111111111111111
Właśnie o to mi chodzi, jak mam je zdefiniować?
Te które widać z ramki to nie problem. Obecny yaml, wygląda tak (nie deklarowałem wszystkich sensorów):
esphome:
name: wmbus
friendly_name: wmbus
esp32:
board: esp32dev
framework:
type: arduino
time:
- platform: sntp
id: sntp_time
servers:
- tempus1.gum.gov.pl
- tempus2.gum.gov.pl
external_components:
- source: github://SzczepanLeon/esphome-components@main
refresh: 0d
components: [ wmbus ]
wmbus:
mosi_pin: GPIO23
miso_pin: GPIO19
clk_pin: GPIO18
cs_pin: GPIO5
gdo0_pin: GPIO12
gdo2_pin: GPIO27
led_pin: GPIO2
led_blink_time: "1s"
frequency: 868.950
all_drivers: False
sync_mode: True
log_all: True
sensor:
- platform: wmbus
meter_id: 0x56505530
type: amiplus
key: "11111111111111111111111111111111"
sensors:
- name: "my energy RSSi"
field: "rssi"
accuracy_decimals: 0
unit_of_measurement: "dBm"
device_class: "signal_strength"
state_class: "measurement"
entity_category: "diagnostic"
- name: "my current power consumption in kiloWatts"
field: "current_power_consumption"
accuracy_decimals: 3
unit_of_measurement: "kw"
device_class: "power"
state_class: "measurement"
icon: "mdi:transmission-tower-import"
- name: "total energy"
field: "total_energy_consumption"
accuracy_decimals: 3
unit_of_measurement: "kwh"
device_class: "energy"
state_class: "total_increasing"
icon: "mdi:transmission-tower-import"
- platform: wmbus
meter_id: 0x17099985
type: rfmtx1
# Enable logging
logger:
level: DEBUG
# Enable Home Assistant API
api:
encryption:
key: "4+REDACTED="
ota:
- platform: esphome
password: "REDACTED"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Wmbus Fallback Hotspot"
password: "REDACTED"
captive_portal:
Ze strony https://wmbusmeters.org/ zwracane są 4 wartości:
"_":"telegram",
"media":"electricity",
"meter":"amiplus",
"name":"",
"id":"56505530",
"current_power_consumption_kw":0.299,
"current_power_production_kw":0,
"total_energy_consumption_kwh":2087.267,
"total_energy_production_kwh":1.041,
"device_date_time":"2025-03-29 09:45:00",
"timestamp":"2025-03-29T08:45:39Z"
zaś ze strony https://www.miller-alex.de/WMbus wartości jest 6.
VALUES
- 2025-03-29 08:49:09 Heating energy: 2087267 Wh
- 2025-03-29 08:49:09 Energy only negative: 1041 Wh
- 2025-03-29 08:49:09 Reserved_02: 8.258
- 2025-03-29 08:49:09 Reserved_02: 1541.747
- 2025-03-29 08:49:09 Power: 299 W
- 2025-03-29 08:49:09 Power only negative: 0 W
Według informacji od dostawcy tych wartości powinno być właśnie 6 tj.
- energia czynna pobrana we wszystkich strefach
- energia czynna oddana we wszystkich strefach
- energia bierna pobrana we wszystkich strefach
- energia bierna oddana we wszystkich strefach
- wypadkowa moc chwilowa czynna pobrana
- wypadkowa moc chwilowa czynna oddana
Chodzi mi o to jak powinien wyglądać kod sensora tj. czy nazwa pola nie ma znaczenia i mogę nazwę pola (sensora) wziąć e strony gdzie pokazuje tych wartości 6?
SzczepanLeon w dokumentacji odwołuje się do strony wmbusmeters.org dlatego nie bardzo wiem skąd różnica w odczycie parametrów przez te dwie strony.
Plus stąd moje stwierdzenie, że nie wszystko jest odszyfrowane:
Auto driver : amiplus
Similar driver : amiplus 24/40
Using driver : amiplus 00/00
000 : 5e length (94 bytes)
001 : 44 dll-c (from meter SND_NR)
002 : 0106 dll-mfct (APA)
004 : 30555056 dll-id (56505530)
008 : 01 dll-version
009 : 02 dll-type (Electricity meter)
010 : 7a tpl-ci-field (EN 13757-3 Application Layer (short tplh))
011 : 61 tpl-acc-field
012 : 00 tpl-sts-field (OK)
013 : 5005 tpl-cfg 0550 (AES_CBC_IV nb=5 cntn=0 ra=0 hc=0 )
015 : 2f2f decrypt check bytes (OK)
017 : 0C dif (8 digit BCD Instantaneous value)
018 : 78 vif (Fabrication no)
019 C?: 30555056
023 : 06 dif (48 Bit Integer/Binary Instantaneous value)
024 : 6D vif (Date and time type)
025 C!: 006D093D3340 ("device_date_time":"2025-03-29 09:45:00")
031 : 0E dif (12 digit BCD Instantaneous value)
032 : 03 vif (Energy Wh)
033 C!: 677208020000 ("total_energy_consumption_kwh":2087.267)
039 : 0E dif (12 digit BCD Instantaneous value)
040 : 83 vif (Energy Wh)
041 : 3C combinable vif (BackwardFlow)
042 C!: 411000000000 ("total_energy_production_kwh":1.041)
048 : 0E dif (12 digit BCD Instantaneous value)
049 : FB vif (First extension FB of VIF-codes)
050 : 82 vife (Reserved)
051 : 73 combinable vif (MultiplicativeCorrectionFactorForValue)
052 C?: 588200000000
058 : 0E dif (12 digit BCD Instantaneous value)
059 : FB vif (First extension FB of VIF-codes)
060 : 82 vife (Reserved)
061 : F3 combinable vif (MultiplicativeCorrectionFactorForValue)
062 : 3C combinable vif (BackwardFlow)
063 C?: 471754010000
069 : 0B dif (6 digit BCD Instantaneous value)
070 : 2B vif (Power W)
071 C!: 990200 ("current_power_consumption_kw":0.299)
074 : 0B dif (6 digit BCD Instantaneous value)
075 : AB vif (Power W)
076 : 3C combinable vif (BackwardFlow)
077 C!: 000000 ("current_power_production_kw":0)
080 : 2F skip
081 : 2F skip
082 : 2F skip
083 : 2F skip
084 : 2F skip
085 : 2F skip
086 : 2F skip
087 : 2F skip
088 : 2F skip
089 : 2F skip
090 : 2F skip
091 : 2F skip
092 : 2F skip
093 : 2F skip
094 : 2F skip
Więc pomóż autorom wmbusmeters je odkodować., a skoro dekoder wmbusmeters online tego nie potrafi, to starszy dekoder zaimplementowany w driverze w komponencie dla ESPHome też tego nie będzie umiał, ani nawet wysyłanie surowych telegramów do własnej instancji serwera wmbusmeters tu nie pomoże.
Z drugiej strony nie wydaje się, że tamten dekoder jest w pełni OK, skoro nazwa sensora jest totalnie od czapy
Natomiast możesz skonfigurować te sensory, których odkodowanie jest możliwe.
current_power_consumption
current_power_production
total_energy_consumption
total_energy_production
Dodałem brakujące sensory.
Poprosiłem też operatora o dodanie napięcia na każdej z 3 faz i potwierdził mi, że te parametry włączył, jednak nie widzę ich w ramce.
Czy mógłbym poprosić o potwierdzenie, że to nie jest kwestia błędnej konfiguracji z mojej strony, że ich nie widzę w telegramie?
# Apator Otus 3 meter
- platform: wmbus
meter_id: 0x56505530
type: amiplus
key: "11111111111111111111111111111111"
sensors:
- name: "RSSi Otus 3"
field: "rssi"
accuracy_decimals: 0
unit_of_measurement: "dBm"
device_class: "signal_strength"
state_class: "measurement"
entity_category: "diagnostic"
- name: "Current power consumption"
field: "current_power_consumption"
accuracy_decimals: 3
unit_of_measurement: "kW"
device_class: "power"
state_class: "measurement"
icon: "mdi:transmission-tower-export"
- name: "Total energy consumption"
field: "total_energy_consumption"
accuracy_decimals: 3
unit_of_measurement: "kWh"
device_class: "energy"
state_class: "total_increasing"
icon: "mdi:transmission-tower-export"
- name: "Voltage phase 1"
field: "voltage_at_phase_1"
accuracy_decimals: 0
unit_of_measurement: "V"
device_class: "voltage"
state_class: "measurement"
icon: "mdi:sine-wave"
- name: "Voltage phase 2"
field: "voltage_at_phase_2"
accuracy_decimals: 0
unit_of_measurement: "V"
device_class: "voltage"
state_class: "measurement"
icon: "mdi:sine-wave"
- name: "Voltage phase 3"
field: "voltage_at_phase_3"
accuracy_decimals: 0
unit_of_measurement: "V"
device_class: "voltage"
state_class: "measurement"
icon: "mdi:sine-wave"
INFO ESPHome 2025.3.3
INFO Reading configuration /config/esphome/wmbus-reader.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 GPIO12 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING 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.189 using esphome API
INFO Successfully connected to wmbus-reader @ 192.168.1.189 in 0.059s
INFO Successful handshake with wmbus-reader @ 192.168.1.189 in 0.132s
[10:23:42][I][app:100]: ESPHome version 2025.3.3 compiled on Apr 3 2025, 10:08:32
[10:23:42][C][wifi:600]: WiFi:
[10:23:42][C][wifi:428]: Local MAC: EC:E3:34:DB:9D:18
[10:23:42][C][wifi:433]: SSID: 'T-Mobile_Swiatlowod_8936'[redacted]
[10:23:42][C][wifi:436]: IP Address: 192.168.1.189
[10:23:42][C][wifi:440]: BSSID: 58:9B:4A:F2:CC:C0[redacted]
[10:23:42][C][wifi:441]: Hostname: 'wmbus-reader'
[10:23:42][C][wifi:443]: Signal strength: -24 dB ▂▄▆█
[10:23:42][V][wifi:445]: Priority: 0.0
[10:23:42][C][wifi:447]: Channel: 12
[10:23:42][C][wifi:448]: Subnet: 255.255.255.0
[10:23:42][C][wifi:449]: Gateway: 192.168.1.1
[10:23:42][C][wifi:450]: DNS1: 192.168.1.1
[10:23:42][C][wifi:451]: DNS2: 0.0.0.0
[10:23:42][VV][scheduler:226]: Running interval '' with interval=10000 last_execution=844289 (now=854303)
[10:23:42][C][logger:177]: Logger:
[10:23:42][C][logger:178]: Max Level: VERY_VERBOSE
[10:23:42][C][logger:179]: Initial Level: VERY_VERBOSE
[10:23:42][C][logger:181]: Log Baud Rate: 115200
[10:23:42][C][logger:182]: Hardware UART: UART0
[10:23:42][C][copy.sensor:015]: Copy Sensor 'WiFi Signal Percent'
[10:23:42][C][copy.sensor:015]: Device Class: 'signal_strength'
[10:23:42][C][copy.sensor:015]: State Class: 'measurement'
[10:23:42][C][copy.sensor:015]: Unit of Measurement: 'Signal %'
[10:23:42][C][copy.sensor:015]: Accuracy Decimals: 0
[10:23:42][C][captive_portal:089]: Captive Portal:
[10:23:42][C][web_server:285]: Web Server:
[10:23:42][C][web_server:286]: Address: wmbus-reader.local:80
[10:23:42][C][sntp:042]: SNTP Time:
[10:23:42][C][sntp:045]: Server 0: '0.pool.ntp.org'
[10:23:42][C][sntp:045]: Server 1: '1.pool.ntp.org'
[10:23:42][C][sntp:045]: Server 2: '2.pool.ntp.org'
[10:23:42][C][mdns:116]: mDNS:
[10:23:42][C][mdns:117]: Hostname: wmbus-reader
[10:23:42][V][mdns:118]: Services:
[10:23:42][V][mdns:120]: - _esphomelib, _tcp, 6053
[10:23:42][V][mdns:122]: TXT: friendly_name = wmbus-reader
[10:23:42][V][mdns:122]: TXT: version = 2025.3.3
[10:23:42][V][mdns:122]: TXT: mac = ece334db9d18
[10:23:42][V][mdns:122]: TXT: platform = ESP32
[10:23:42][V][mdns:122]: TXT: board = esp32dev
[10:23:42][V][mdns:122]: TXT: network = wifi
[10:23:42][V][mdns:122]: TXT: api_encryption = Noise_NNpsk0_25519_ChaChaPoly_SHA256
[10:23:42][V][mdns:120]: - _http, _tcp, 80
[10:23:42][C][esphome.ota:073]: Over-The-Air updates:
[10:23:42][C][esphome.ota:074]: Address: wmbus-reader.local:3232
[10:23:42][C][esphome.ota:075]: Version: 2
[10:23:42][C][esphome.ota:078]: Password configured
[10:23:42][C][safe_mode:018]: Safe Mode:
[10:23:42][C][safe_mode:020]: Boot considered successful after 60 seconds
[10:23:42][C][safe_mode:021]: Invoke after 10 boot attempts
[10:23:42][C][safe_mode:023]: Remain in safe mode for 300 seconds
[10:23:42][C][api:140]: API Server:
[10:23:42][C][api:141]: Address: wmbus-reader.local:6053
[10:23:42][C][api:143]: Using noise encryption: YES
[10:23:42][C][wifi_signal.sensor:010]: WiFi Signal 'WiFi Signal dB'
[10:23:42][C][wifi_signal.sensor:010]: Device Class: 'signal_strength'
[10:23:42][C][wifi_signal.sensor:010]: State Class: 'measurement'
[10:23:42][C][wifi_signal.sensor:010]: Unit of Measurement: 'dBm'
[10:23:42][C][wifi_signal.sensor:010]: Accuracy Decimals: 0
[10:23:42][V][wifi_signal.sensor:010]: Unique ID: 'ece334db9d18-wifisignal'
[10:23:42][C][wmbus:413]: wM-Bus v4.2.0-1.17.1-b8f4a945:
[10:23:42][C][wmbus:426]: LED:
[10:23:42][C][wmbus:427]: Pin: GPIO2
[10:23:42][C][wmbus:428]: Duration: 150 ms
[10:23:42][C][wmbus:431]: Chip ID: 189DDB34E3EC
[10:23:42][C][wmbus:433]: CC1101 frequency: 868.950 MHz
[10:23:42][C][wmbus:434]: CC1101 SPI bus:
[10:23:42][C][wmbus:438]: MOSI Pin: GPIO23
[10:23:42][C][wmbus:439]: MISO Pin: GPIO19
[10:23:42][C][wmbus:440]: CLK Pin: GPIO18
[10:23:42][C][wmbus:441]: CS Pin: GPIO5
[10:23:42][C][wmbus:442]: GDO0 Pin: GPIO12
[10:23:42][C][wmbus:443]: GDO2 Pin: GPIO27
[10:23:42][C][wmbus:449]: Available drivers: unknown, amiplus
[10:23:42][C][wmbus:463]: Meter:
[10:23:42][C][wmbus:464]: ID: 1448105264 [0x56505530]
[10:23:42][C][wmbus:465]: Type: amiplus
[10:23:43][C][wmbus:466]: Key: '11111111111111111111111111111111'
[10:23:43][C][wmbus:468]: Field: 'current_power_consumption'
[10:23:43][C][wmbus:469]: Name: 'Current power consumption'
[10:23:43][C][wmbus:469]: Device Class: 'power'
[10:23:43][C][wmbus:469]: State Class: 'measurement'
[10:23:43][C][wmbus:469]: Unit of Measurement: 'kW'
[10:23:43][C][wmbus:469]: Accuracy Decimals: 3
[10:23:43][C][wmbus:469]: Icon: 'mdi:transmission-tower-export'
[10:23:43][C][wmbus:468]: Field: 'rssi'
[10:23:43][C][wmbus:469]: Name: 'RSSi Otus 3'
[10:23:43][C][wmbus:469]: Device Class: 'signal_strength'
[10:23:43][C][wmbus:469]: State Class: 'measurement'
[10:23:43][C][wmbus:469]: Unit of Measurement: 'dBm'
[10:23:43][C][wmbus:469]: Accuracy Decimals: 0
[10:23:43][C][wmbus:468]: Field: 'total_energy_consumption'
[10:23:43][C][wmbus:469]: Name: 'Total energy consumption'
[10:23:43][C][wmbus:469]: Device Class: 'energy'
[10:23:43][C][wmbus:469]: State Class: 'total_increasing'
[10:23:43][C][wmbus:469]: Unit of Measurement: 'kWh'
[10:23:43][C][wmbus:469]: Accuracy Decimals: 3
[10:23:43][C][wmbus:469]: Icon: 'mdi:transmission-tower-export'
[10:23:43][C][wmbus:468]: Field: 'voltage_at_phase_1'
[10:23:43][C][wmbus:469]: Name: 'Voltage phase 1'
[10:23:43][C][wmbus:469]: Device Class: 'voltage'
[10:23:43][C][wmbus:469]: State Class: 'measurement'
[10:23:43][C][wmbus:469]: Unit of Measurement: 'V'
[10:23:43][C][wmbus:469]: Accuracy Decimals: 0
[10:23:43][C][wmbus:469]: Icon: 'mdi:sine-wave'
[10:23:43][C][wmbus:468]: Field: 'voltage_at_phase_2'
[10:23:43][C][wmbus:469]: Name: 'Voltage phase 2'
[10:23:43][C][wmbus:469]: Device Class: 'voltage'
[10:23:43][C][wmbus:469]: State Class: 'measurement'
[10:23:43][C][wmbus:469]: Unit of Measurement: 'V'
[10:23:43][C][wmbus:469]: Accuracy Decimals: 0
[10:23:43][C][wmbus:469]: Icon: 'mdi:sine-wave'
[10:23:43][C][wmbus:468]: Field: 'voltage_at_phase_3'
[10:23:43][C][wmbus:469]: Name: 'Voltage phase 3'
[10:23:43][C][wmbus:469]: Device Class: 'voltage'
[10:23:43][C][wmbus:469]: State Class: 'measurement'
[10:23:43][C][wmbus:469]: Unit of Measurement: 'V'
[10:23:43][C][wmbus:469]: Accuracy Decimals: 0
[10:23:43][C][wmbus:469]: Icon: 'mdi:sine-wave'
[10:23:52][VV][scheduler:226]: Running interval '' with interval=10000 last_execution=854289 (now=864289)
[10:23:57][V][rxLoop:167]: Have 137 bytes from CC1101 Rx, RSSI: -94 dBm LQI: 129
[10:23:57][V][rxLoop:172]: Synchronus mode enabled.
[10:23:57][D][mbus:035]: Received T1 A frame
[10:23:57][V][mbus:046]: Frame: 73271C8DC5E5B199655A535334B59371CB264E772572C716599DFCCB18F1672B1398BB195B2A74C71CF1A652D9C8BB0B2E634E714593C57F0D5AD3AF38D8F9B132D9A71D139E67325A9C4ED343ACCB46A59A58D3D0E5B46632F2C93C9BA654C6CB1716B1A5B2CAC7D395C9914DA4E536934EC4B66C94D2D9C8D9A64E6C4BA738D92E998D8CB659D365 (137) [RAW]
[10:23:57][V][3of6:083]: Decode 3 out of 6 failed..
[10:23:57][W][component:237]: Component wmbus took a long time for an operation (60 ms).
[10:23:57][W][component:238]: Components should block for at most 30 ms.
[10:24:02][VV][scheduler:226]: Running interval '' with interval=10000 last_execution=864289 (now=874289)
[10:24:08][V][rxLoop:167]: Have 164 bytes from CC1101 Rx, RSSI: -84 dBm LQI: 128
[10:24:08][V][rxLoop:172]: Synchronus mode enabled.
[10:24:08][D][mbus:035]: Received T1 A frame
[10:24:08][V][mbus:046]: Frame: 67271C58D59A2D665965665A58D58E7137134E66B25966565994D3D1C6A697459C4D3D328F166C71AC662F1A539668CE38B393972374C74C59723653C9CA633A538D693CB49568DCC8E98BB0D723C564E969C67199C6B18DC8DA3A35A9C74D1A9B48DC3A37255994E35A5C8D34D7292F26A9C8B35A8E569959935A7162E52E96B12F234D2DC965D2573172971670EA632F295958E6A671CC722F165CC5971A5AC2D635A5 (164) [RAW]
[10:24:08][VV][3of6:095]: Decode 3 out of 6 OK.
[10:24:08][V][mbus:053]: Frame: 5E44010630555056010247477A6E00500577C46A9C0477CEBD5846DA3DF79AB223279E1CDCD54B57E4FB292167EC90B4E2A3814BD07F645DA46DB4B62B0FDCC6ACB42B49057B09E1114F3E6FE316B965051640393F6D3E113499C94D4F4042FB3E95026A44DE3D54D546083016 (109) [with CRC]
[10:24:08][V][mbus:096]: Validating CRC for Block1
[10:24:08][V][crc:031]: calculated: 0x4747, read: 0x4747
[10:24:08][V][mbus:116]: Validating CRC for Block2
[10:24:08][V][crc:031]: calculated: 0x3DF7, read: 0x3DF7
[10:24:08][V][mbus:116]: Validating CRC for Block3
[10:24:08][V][crc:031]: calculated: 0x90B4, read: 0x90B4
[10:24:08][V][mbus:116]: Validating CRC for Block4
[10:24:08][V][crc:031]: calculated: 0xACB4, read: 0xACB4
[10:24:08][V][mbus:116]: Validating CRC for Block5
[10:24:08][V][crc:031]: calculated: 0x4039, read: 0x4039
[10:24:08][V][mbus:116]: Validating CRC for Block6
[10:24:08][V][crc:031]: calculated: 0x44DE, read: 0x44DE
[10:24:08][V][mbus:116]: Validating CRC for Block7
[10:24:08][V][crc:031]: calculated: 0x3016, read: 0x3016
[10:24:08][V][mbus:063]: Frame: 5E4401063055505601027A6E00500577C46A9C0477CEBD5846DA9AB223279E1CDCD54B57E4FB292167ECE2A3814BD07F645DA46DB4B62B0FDCC62B49057B09E1114F3E6FE316B96505163F6D3E113499C94D4F4042FB3E95026A3D54D54608 (95) [without CRC]
[10:24:08][VV][wmbus:058]: Have data from RF ...
[10:24:08][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 95
[10:24:08][V][Telegram.cpp:1178]: (wmbus) parseELL @10 85
[10:24:08][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 85
[10:24:08][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 85
[10:24:08][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 85
[10:24:08][I][wmbus:094]: Using selected driver amiplus (detected driver was amiplus)
[10:24:08][I][wmbus:106]: amiplus [0x56505530] RSSI: -84dBm T: 5E4401063055505601027A6E00500577C46A9C0477CEBD5846DA9AB223279E1CDCD54B57E4FB292167ECE2A3814BD07F645DA46DB4B62B0FDCC62B49057B09E1114F3E6FE316B96505163F6D3E113499C94D4F4042FB3E95026A3D54D54608 (95) T1 A
[10:24:08][D][meters.cpp:1989]: (meter) created ESPHome amiplus 56505530 encrypted
[10:24:08][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 95
[10:24:08][V][Telegram.cpp:1178]: (wmbus) parseELL @10 85
[10:24:08][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 85
[10:24:08][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 85
[10:24:08][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 85
[10:24:08][V][meters.cpp:635]: (meter) ESPHome: for me? 56505530.M=APA.V=01.T=02,56505530.M=APA.V=01.T=02 in 56505530
[10:24:08][V][meters.cpp:686]: (meter) ESPHome: yes for me
[10:24:08][D][meters.cpp:913]: (meter) ESPHome(0) amiplus handling telegram from 56505530.M=APA.V=01.T=02
[10:24:08][V][Telegram.cpp:1131]: (wmbus) parseDLL @0 95
[10:24:08][V][Telegram.cpp:545]: (telegram) DLL L=5e C=44 (from meter SND_NR) M=0601 (APA) A=56505530 VER=01 TYPE=02 (Electricity meter) (driver amiplus) DEV=ESPHome wM-Bus RSSI=-84
[10:24:08][V][Telegram.cpp:1178]: (wmbus) parseELL @10 85
[10:24:08][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 85
[10:24:08][V][Telegram.cpp:1391]: (wmbus) parseAFL @10 85
[10:24:08][V][Telegram.cpp:2078]: (wmbus) parseTPL @10 85
[10:24:08][V][Telegram.cpp:299]: (TPL) num encrypted blocks 5 (80 bytes and remaining unencrypted 0 bytes)
[10:24:08][V][Telegram.cpp:303]: (TPL) AES CBC IV decrypting
[10:24:08][V][Telegram.cpp:343]: (TPL) IV 01063055505601026E6E6E6E6E6E6E6E
[10:24:08][V][utils.cpp:823]: (TPL) decrypted "2F2F0C7830555056066D40580A2334800E035824110200000E833C4110000000000EFB82739082000000000EFB82F33C0363550100000B2B2701000BAB3C0000002F2F2F2F2F2F2F2F2F2F2F2F2F2F2F"
[10:24:08][V][dvparser.cpp:1471]: [DVPARSER] entry 19: 0C78 Instantaneous vif=78 st=0 ta=0 su=0
[10:24:08][V][dvparser.cpp:1471]: [DVPARSER] entry 25: 066D Instantaneous vif=6d st=0 ta=0 su=0
[10:24:08][V][dvparser.cpp:1471]: [DVPARSER] entry 33: 0E03 Instantaneous vif=3 st=0 ta=0 su=0
[10:24:08][V][dvparser.cpp:1471]: [DVPARSER] entry 42: 0E833C Instantaneous vif=3 HASCOMB HASCOMBRAW st=0 ta=0 su=0
[10:24:09][V][dvparser.cpp:1471]: [DVPARSER] entry 52: 0EFB8273 Instantaneous vif=7b02 HASCOMB HASCOMBRAW st=0 ta=0 su=0
[10:24:09][V][dvparser.cpp:1471]: [DVPARSER] entry 63: 0EFB82F33C Instantaneous vif=7b02 HASCOMB HASCOMBRAW st=0 ta=0 su=0
[10:24:09][V][dvparser.cpp:1471]: [DVPARSER] entry 71: 0B2B Instantaneous vif=2b st=0 ta=0 su=0
[10:24:09][V][dvparser.cpp:1471]: [DVPARSER] entry 77: 0BAB3C Instantaneous vif=2b HASCOMB HASCOMBRAW st=0 ta=0 su=0
[10:24:09][V][Telegram.cpp:634]: (telegram) TPL CI=7a
[10:24:09][V][Telegram.cpp:640]: ACC=6e STS=00 CFG=0550 (AES_CBC_IV nb=5 cntn=0 ra=0 hc=0)
[10:24:09][V][meters.cpp:977]: (meters) trying field info total_energy_consumption(Energy)[0]...
[10:24:09][V][meters.cpp:999]: (meters) using field info total_energy_consumption(Energy)[0] to extract 0E03 at offset 33
[10:24:09][V][meters.cpp:2164]: (meter) AnyEnergyVIF total_energy_consumption_kwh decoded kwh default kwh value 2112.46 (scale 1)
[10:24:09][V][meters.cpp:977]: (meters) trying field info current_power_consumption(Power)[1]...
[10:24:09][V][meters.cpp:999]: (meters) using field info current_power_consumption(Power)[1] to extract 0B2B at offset 71
[10:24:09][V][meters.cpp:2164]: (meter) PowerW current_power_consumption_kw decoded kw default kw value 0.127 (scale 1)
[10:24:09][V][meters.cpp:977]: (meters) trying field info total_energy_production(Energy)[2]...
[10:24:09][V][meters.cpp:999]: (meters) using field info total_energy_production(Energy)[2] to extract 0E833C at offset 42
[10:24:09][V][meters.cpp:2164]: (meter) Any total_energy_production_kwh decoded kwh default kwh value 1.041 (scale 1)
[10:24:09][V][meters.cpp:977]: (meters) trying field info current_power_production(Power)[3]...
[10:24:09][V][meters.cpp:999]: (meters) using field info current_power_production(Power)[3] to extract 0BAB3C at offset 77
[10:24:09][V][meters.cpp:2164]: (meter) Any current_power_production_kw decoded kw default kw value 0 (scale 1)
[10:24:09][V][meters.cpp:977]: (meters) trying field info voltage_at_phase_1(Voltage)[4]...
[10:24:09][V][meters.cpp:977]: (meters) trying field info voltage_at_phase_2(Voltage)[5]...
[10:24:09][V][meters.cpp:977]: (meters) trying field info voltage_at_phase_3(Voltage)[6]...
[10:24:09][V][meters.cpp:977]: (meters) trying field info device_date_time(Text)[7]...
[10:24:09][V][meters.cpp:999]: (meters) using field info device_date_time(Text)[7] to extract 066D at offset 25
[10:24:09][V][meters.cpp:977]: (meters) trying field info total_energy_consumption_tariff_1(Energy)[8]...
[10:24:09][V][meters.cpp:977]: (meters) trying field info total_energy_consumption_tariff_2(Energy)[9]...
[10:24:09][V][meters.cpp:977]: (meters) trying field info total_energy_consumption_tariff_3(Energy)[10]...
[10:24:09][V][meters.cpp:977]: (meters) trying field info total_energy_production_tariff_1(Energy)[11]...
[10:24:09][V][meters.cpp:977]: (meters) trying field info total_energy_production_tariff_2(Energy)[12]...
[10:24:09][V][meters.cpp:977]: (meters) trying field info total_energy_production_tariff_3(Energy)[13]...
[10:24:09][V][meters.cpp:977]: (meters) trying field info max_power_consumption(Power)[14]...
[10:24:09][V][sensor:043]: 'Current power consumption': Received new state 0.127000
[10:24:09][D][sensor:094]: 'Current power consumption': Sending state 0.12700 kW with 3 decimals of accuracy
[10:24:09][VV][api.service:140]: send_sensor_state_response: SensorStateResponse {
key: 1025134458
state: 0.127
missing_state: NO
}
[10:24:09][V][sensor:043]: 'RSSi Otus 3': Received new state -84.000000
[10:24:09][D][sensor:094]: 'RSSi Otus 3': Sending state -84.00000 dBm with 0 decimals of accuracy
[10:24:09][VV][api.service:140]: send_sensor_state_response: SensorStateResponse {
key: 563131060
state: -84
missing_state: NO
}
[10:24:09][V][sensor:043]: 'Total energy consumption': Received new state 2112.458008
[10:24:09][D][sensor:094]: 'Total energy consumption': Sending state 2112.45801 kWh with 3 decimals of accuracy
[10:24:09][VV][api.service:140]: send_sensor_state_response: SensorStateResponse {
key: 3297958248
state: 2112.46
missing_state: NO
}
[10:24:09][W][wmbus:156]: Can't get requested field 'voltage_at_phase_1' with unit 'V'
[10:24:09][W][wmbus:156]: Can't get requested field 'voltage_at_phase_2' with unit 'V'
[10:24:09][W][wmbus:156]: Can't get requested field 'voltage_at_phase_3' with unit 'V'
[10:24:09][W][component:237]: Component wmbus took a long time for an operation (870 ms).
[10:24:09][W][component:238]: Components should block for at most 30 ms.
[10:24:12][VV][scheduler:226]: Running interval '' with interval=10000 last_execution=874289 (now=884289)
[10:24:13][VV][scheduler:226]: Running interval 'update' with interval=60000 last_execution=825054 (now=885054)
[10:24:13][V][sensor:043]: 'WiFi Signal dB': Received new state -27.000000
[10:24:13][D][sensor:094]: 'WiFi Signal dB': Sending state -27.00000 dBm with 0 decimals of accuracy
[10:24:13][V][sensor:043]: 'WiFi Signal Percent': Received new state -27.000000
[10:24:13][VV][sensor.filter:014]: Filter(0x3ffb13e0)::input(-27.000000)
[10:24:13][VV][sensor.filter:286]: LambdaFilter(0x3ffb13e0)::new_value(-27.000000) -> 100.000000
[10:24:13][VV][sensor.filter:021]: Filter(0x3ffb13e0)::output(100.000000) -> SENSOR
[10:24:13][D][sensor:094]: 'WiFi Signal Percent': Sending state 100.00000 Signal % with 0 decimals of accuracy
[10:24:13][VV][api.service:140]: send_sensor_state_response: SensorStateResponse {
key: 463138235
state: 100
missing_state: NO
}
[10:24:13][VV][api.service:140]: send_sensor_state_response: SensorStateResponse {
key: 1535411390
state: -27
missing_state: NO
}
[10:24:13][W][component:237]: Component wifi_signal.sensor took a long time for an operation (88 ms).
[10:24:13][W][component:238]: Components should block for at most 30 ms.
[10:24:17][V][rxLoop:167]: Have 230 bytes from CC1101 Rx, RSSI: -96 dBm LQI: 136
[10:24:17][V][rxLoop:172]: Synchronus mode enabled.
[10:24:17][D][mbus:035]: Received T1 A frame
[10:24:17][V][mbus:041]: Frame: B1A71C8DC5A52CE70B59C59D3665B195A2D9F3459645A4E6DAC596D9659759C6B33A69AE38B2F85B45A34F46725992E54D314B5B434B65AAADF9D59FEB43FE5AC6EC69AB8D95C5B158FB3435634B36C58D5B65965A969C58D5965965967965967A670DDA95A35B1B1DEDC3CB6DE3CD30E3DA2CE5A5B2572559A3438F1A4B65A58B34E70D58D39659ED96597596596596596596586596A73959596D87FD65B4497DD77D25A35E565A54B38E3CD66516538DEB1C4BE6536538D66136538D66536538D67536562E70B3 [RAW]
[10:24:17][V][mbus:043]: D968E79B919CFA35D68E7A935994D2CD34BBCD2CD34BB1675C348CA9D335 (230) [RAW]
[10:24:17][V][3of6:083]: Decode 3 out of 6 failed..
[10:24:17][W][component:237]: Component wmbus took a long time for an operation (83 ms).
[10:24:17][W][component:238]: Components should block for at most 30 ms.
[10:24:19][VV][scheduler:226]: Running interval '' with interval=60000 last_execution=831045 (now=891045)
[10:24:22][VV][scheduler:226]: Running interval '' with interval=10000 last_execution=884289 (now=894289)
[10:24:32][VV][scheduler:226]: Running interval '' with interval=10000 last_execution=894289 (now=904289)