WMBus esp32 -problem ze wszystkim

Home Assistant
,
1

Witam .
Jestem świeżym użytkownikiem HA i na siłę próbuje ogarnąć odczyt licznika energii elektrycznej. Po wielkich bataliach z zainstalowaniem HA na laptopie jako maszyna wirtualna ,i wgraniu softu do modułu ,tutaj chylę czoła dla twórcy komponentu “wmbus” SzczepanLeon, udało się pobrać dane z licznika bez rozkodowania. Może ktoś pomoże zielonemu człowieczkowi, bo sam nie dam rady.
Mam kilka pytań , bo log z HA pokazuje prawidłowo dane- telegram , a z terminala rs już jest inaczej, telegram jast obcięty. Dlaczego?
Wysyłam konfigurację i log z HA oraz z terminala. Proszę o proste i zrozumiałe podpowiedzi. Używam linuxa Mint.

 /////// Konfiguracja modułu //////
esphome:
  name: wm-bus
  friendly_name: Wm-Bus

esp32:
  board: wemos_d1_mini32
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: "7sag7VW+87ZQy2nY/mf0AhG1blAJKr0JFTXnW93zXUo="

ota:
  - platform: esphome
    password: "02b52b3e8d09306df6a3a4d49e102aa5"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  manual_ip: 
    gateway: 192.168.33.1
    static_ip: 192.168.33.222
    subnet: 255.255.255.0    
  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Wm-Bus Local"
    password: "xxxxxxxxxxx"

captive_portal:

time:
  - platform: sntp
    id: time_sntp
    
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: GPIO17
  gdo2_pin: GPIO4

  led_pin: GPIO2
  led_blink_time: "1s"

  frequency: 868.950
  all_drivers: False
  sync_mode: True
  log_all: True

  mqtt:
    broker: 192.168.33.200
    username: ""
    password: ""
    port: 1883
    

  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: amiplus


# add more sensors, one without field (name will be used)
  - platform: wmbus
    meter_id: 0x36308BC
    type: amiplus
    key:  "32001568219480000000000000000000"
    sensors:
      - name: "my current power consumption in Watts"
        field: "current_power_consumption"
        accuracy_decimals: 1
        unit_of_measurement: "w"
        device_class: "power"
        state_class: "measurement"
        icon: "mdi:transmission-tower-import"
      - name: "my current power production in Watts"
        field: "current_power_production"
        accuracy_decimals: 1
        unit_of_measurement: "w"
        device_class: "power"
        state_class: "measurement"
        icon: "mdi:transmission-tower-import"
      - name: "total energy on T1"
        field: "total_energy_consumption_tariff_1"
        accuracy_decimals: 3
        unit_of_measurement: "kwh"
        device_class: "energy"
        state_class: "total_increasing"
        icon: "mdi:transmission-tower-import"
      - name: "total energy production on T1"
        field: "total_energy_production_tariff_1"
        accuracy_decimals: 3
        unit_of_measurement: "kwh"
        device_class: "energy"
        state_class: "total_increasing"
        icon: "mdi:transmission-tower-import"
      - name: "voltage_at_phase_1"
        accuracy_decimals: 0
        unit_of_measurement: "v"
        device_class: "voltage"
        state_class: "measurement"
        icon: "mdi:sine-wave"



text_sensor:
  - platform: wmbus
    meter_id: 0x36308BC
    type: amiplus
    sensors:
      - name: "my current power consumption in Watts"
        field: "current_power_consumption"
        icon: "mdi:transmission-tower-import"

Log z Home Assistant

/////// Log z konsoli HA połączenie przez wifi //////

INFO ESPHome 2025.2.2
INFO Reading configuration /config/esphome/wm-bus.yaml...
INFO Updating https://github.com/SzczepanLeon/esphome-components.git@main
INFO Detected timezone 'Europe/Warsaw'
WARNING GPIO5 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO2 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
INFO Starting log output from 192.168.33.222 using esphome API
INFO Successfully connected to wm-bus @ 192.168.33.222 in 0.312s
INFO Successful handshake with wm-bus @ 192.168.33.222 in 0.192s
[12:16:34][I][app:100]: ESPHome version 2025.2.2 compiled on Mar 20 2025, 11:16:33
[12:16:34][C][wifi:600]: WiFi:
[12:16:34][C][wifi:428]:   Local MAC: 40:22:D8:EA:23:8C
[12:16:34][C][wifi:433]:   SSID: [redacted]
[12:16:34][C][wifi:436]:   IP Address: 192.168.33.222
[12:16:34][C][wifi:440]:   BSSID: [redacted]
[12:16:34][C][wifi:441]:   Hostname: 'wm-bus'
[12:16:34][C][wifi:443]:   Signal strength: -44 dB ▂▄▆█
[12:16:34][C][wifi:447]:   Channel: 6
[12:16:34][C][wifi:448]:   Subnet: 255.255.255.0
[12:16:34][C][wifi:449]:   Gateway: 192.168.33.1
[12:16:34][C][wifi:450]:   DNS1: 0.0.0.0
[12:16:34][C][wifi:451]:   DNS2: 0.0.0.0
[12:16:34][C][logger:177]: Logger:
[12:16:34][C][logger:178]:   Max Level: DEBUG
[12:16:34][C][logger:179]:   Initial Level: DEBUG
[12:16:34][C][logger:181]:   Log Baud Rate: 115200
[12:16:34][C][logger:182]:   Hardware UART: UART0
[12:16:34][C][captive_portal:089]: Captive Portal:
[12:16:34][C][sntp:042]: SNTP Time:
[12:16:34][C][sntp:045]:   Server 0: '0.pool.ntp.org'
[12:16:34][C][sntp:045]:   Server 1: '1.pool.ntp.org'
[12:16:34][C][sntp:045]:   Server 2: '2.pool.ntp.org'
[12:16:34][C][mdns:116]: mDNS:
[12:16:34][C][mdns:117]:   Hostname: wm-bus
[12:16:34][C][esphome.ota:073]: Over-The-Air updates:
[12:16:34][C][esphome.ota:074]:   Address: 192.168.33.222:3232
[12:16:34][C][esphome.ota:075]:   Version: 2
[12:16:34][C][esphome.ota:078]:   Password configured
[12:16:34][C][safe_mode:018]: Safe Mode:
[12:16:34][C][safe_mode:020]:   Boot considered successful after 60 seconds
[12:16:34][C][safe_mode:021]:   Invoke after 10 boot attempts
[12:16:34][C][safe_mode:023]:   Remain in safe mode for 300 seconds
[12:16:34][C][api:140]: API Server:
[12:16:34][C][api:141]:   Address: 192.168.33.222:6053
[12:16:34][C][api:143]:   Using noise encryption: YES
[12:16:34][C][wmbus:338]: wM-Bus v4.1.4-1.17.1-b8f4a945:
[12:16:34][C][wmbus:340]:   Clients:
[12:16:34][C][wmbus:347]:     wmbusmeters: 10.0.0.22:7227 TCP [rtl-wmbus]
[12:16:34][C][wmbus:351]:   LED:
[12:16:34][C][wmbus:352]:     Pin: GPIO2
[12:16:34][C][wmbus:353]:     Duration: 1000 ms
[12:16:34][C][wmbus:356]:   Chip ID: 8C23EAD82240
[12:16:34][C][wmbus:358]:   CC1101 frequency: 868.950 MHz
[12:16:34][C][wmbus:359]:   CC1101 SPI bus:
[12:16:34][C][wmbus:363]:     MOSI Pin: GPIO23
[12:16:34][C][wmbus:364]:     MISO Pin: GPIO19
[12:16:34][C][wmbus:365]:     CLK Pin:  GPIO18
[12:16:34][C][wmbus:366]:     CS Pin:   GPIO5
[12:16:34][C][wmbus:367]:     GDO0 Pin: GPIO17
[12:16:34][C][wmbus:368]:     GDO2 Pin: GPIO4
[12:16:34][C][wmbus:374]:   Available drivers: unknown, amiplus
[12:16:34][C][wmbus:388]:   Meter:
[12:16:34][C][wmbus:389]:     ID: 56821948 [0x036308BC]
[12:16:34][C][wmbus:390]:     Type: amiplus
[12:16:34][C][wmbus:391]:     Key: '32001568219480000000000000000000'
[12:16:34][C][wmbus:393]:     Field: 'current_power_consumption'
[12:16:34][C][wmbus:394]:      Name: 'my current power consumption in Watts'
[12:16:34][C][wmbus:394]:        Device Class: 'power'
[12:16:34][C][wmbus:394]:        State Class: 'measurement'
[12:16:34][C][wmbus:394]:        Unit of Measurement: 'w'
[12:16:34][C][wmbus:394]:        Accuracy Decimals: 1
[12:16:34][C][wmbus:394]:        Icon: 'mdi:transmission-tower-import'
[12:16:34][C][wmbus:393]:     Field: 'current_power_production'
[12:16:34][C][wmbus:394]:      Name: 'my current power production in Watts'
[12:16:34][C][wmbus:394]:        Device Class: 'power'
[12:16:34][C][wmbus:394]:        State Class: 'measurement'
[12:16:34][C][wmbus:394]:        Unit of Measurement: 'w'
[12:16:34][C][wmbus:394]:        Accuracy Decimals: 1
[12:16:34][C][wmbus:394]:        Icon: 'mdi:transmission-tower-import'
[12:16:34][C][wmbus:393]:     Field: 'total_energy_consumption_tariff_1'
[12:16:34][C][wmbus:394]:      Name: 'total energy on T1'
[12:16:34][C][wmbus:394]:        Device Class: 'energy'
[12:16:34][C][wmbus:394]:        State Class: 'total_increasing'
[12:16:34][C][wmbus:394]:        Unit of Measurement: 'kwh'
[12:16:34][C][wmbus:394]:        Accuracy Decimals: 3
[12:16:34][C][wmbus:394]:        Icon: 'mdi:transmission-tower-import'
[12:16:34][C][wmbus:393]:     Field: 'total_energy_production_tariff_1'
[12:16:34][C][wmbus:394]:      Name: 'total energy production on T1'
[12:16:34][C][wmbus:394]:        Device Class: 'energy'
[12:16:34][C][wmbus:394]:        State Class: 'total_increasing'
[12:16:34][C][wmbus:394]:        Unit of Measurement: 'kwh'
[12:16:34][C][wmbus:394]:        Accuracy Decimals: 3
[12:16:34][C][wmbus:394]:        Icon: 'mdi:transmission-tower-import'
[12:16:34][C][wmbus:393]:     Field: 'voltage_at_phase_1'
[12:16:34][C][wmbus:394]:      Name: 'voltage_at_phase_1'
[12:16:34][C][wmbus:394]:        Device Class: 'voltage'
[12:16:34][C][wmbus:394]:        State Class: 'measurement'
[12:16:34][C][wmbus:394]:        Unit of Measurement: 'v'
[12:16:34][C][wmbus:394]:        Accuracy Decimals: 0
[12:16:34][C][wmbus:394]:        Icon: 'mdi:sine-wave'
[12:16:34][C][wmbus:397]:     Text field: 'current_power_consumption'
[12:16:34][C][wmbus:398]:      Name: 'my current power consumption in Watts'
[12:16:34][C][wmbus:398]:        Icon: 'mdi:transmission-tower-import'
[12:16:44][D][mbus:035]: Received T1 A frame
**[12:16:47][E][wmbus:283]: Can't connect via TCP to 10.0.0.22:7227** <--- tu chyba jest problem dlaczego nie dekoduje....
[12:16:47][I][wmbus:104]: amiplus [0x56821948] RSSI: -61dBm T: DE4401064819825601027A6F00D0051E04C19438E7469C9408480E72AE44302F9C84A37378D3A3A83C1D7D34BC31E52C7159051B7B52D45968B50CD4B9D5CEEB63A6E9372A030116E8DD3D5BD2D4FE252A325FB7750FBBBE61557A71D9B257F7F2206F60043FED025884126E3E3C92FE8B097E3E2CE39D6EE731F1E503ECD97BA6F52F74691ADB7AE2C5EE376651B4F01F413AA446D58BFE465F4CC4471447A9EBAF1C38BCC036A3CA02403B17582EE6C5DF38BE583A3A855BA5AA134844BBE7E20F2078E64F718851251199C57445C58D3ADC5711D4F6E620E981BCD70DAC (223
[12:16:47][W][component:237]: Component wmbus took a long time for an operation (3100 ms).
[12:16:47][W][component:238]: Components should block for at most 30 ms.
[12:17:44][D][mbus:035]: Received T1 A frame
[12:17:47][E][wmbus:283]: Can't connect via TCP to 10.0.0.22:7227
[12:17:47][I][wmbus:104]: amiplus [0x56821948] RSSI: -61dBm T: DE4401064819825601027A7000D005852C6C86153861805A61383A178F0F97931CB2B3AB4FBAEC5D71752A3AE6D638B38EFCA03097407FD049B34E0F977EE05A8CAAE73EDEE064E903754B1FA2948B7A32F81032BB8D5F66C7DAC2A28CEAE0542B1545486E5A0AB8D111E45F46328F764F3C8507C14FD4F55554B447F617A1067ADA10884BD9F6D41A81B6847604CDB6F5241D15C91C7291FFA8B0D806E36425820246E1D48DCEAAD2F03069E677CE5C93C5DFCBAC05A503C5EF82EA25817C2321D86FB7D53CE4BA507823408355357F7C0B2602E7FB276629CD1ADB468EB9 (223
[12:17:47][W][component:237]: Component wmbus took a long time for an operation (3099 ms).
[12:17:47][W][component:238]: Components should block for at most 30 ms.
[12:20:44][D][mbus:035]: Received T1 A frame
[12:20:47][E][wmbus:283]: Can't connect via TCP to 10.0.0.22:7227
[12:20:47][I][wmbus:104]: amiplus [0x56821948] RSSI: -61dBm T: DE4401064819825601027A7300D005015DFC6BA08799002A97BC465525C8F6DBD854C8C8CDEE452B44E8CCDE4B5B3AF5CCCD52A233906A6262ACFCA38719AD6664DBAB47033C9BDD3DE506EC95E1D83DA04B38FFD0F47477CBA6268D84A354E68C0FFF3256C4523CDFE03B2A6EC4D053ABEBC57D1639C0A25C9F5ECF0C40A235F1F3DF6F3DE7ED52452D04941C2BEAFBF041E443BBDB7F994A7AAA83463C27A3C0F8D0AA0DBC1EC76DC20B21D1821C077206E187D399183A2840541F9C317037EA07776B60155436AFE3C0095BE4C75DC3F6E3A63746B3C6EB9B5A4625DF8A (223
[12:20:47][W][component:237]: Component wmbus took a long time for an operation (3100 ms).
[12:20:47][W][component:238]: Components should block for at most 30 ms.

Log z terminala rs połączenie po kablu usb- niekompletny telegram.

///////  A to z terminala RS ////

rst:0x1 (POWERON_RESET),boot:0x13 (SP__FAdrv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13132
load:0x40080400,len:3036
entry 0x400805e4
[0;32m[I][logger:171]: Log initialized[0m
[0;35m[C][safe_mode:079]: There have been 0 suspected unsuccessful boot attempts[0m
[0;36m[D][esp32.preferences:114]: Saving 1 preferences to flash...[0m
[0;36m[D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed[0m
[0;32m[I][app:029]: Running through setup()...[0m
[0;35m[C][wifi:048]: Setting up WiFi...[0m
[0;35m[C][wifi:061]: Starting WiFi...[0m
[0;35m[C][wifi:062]:   Local MAC: 40:22:D8:EA:23:8C[0m
[0;36m[D][wifi:482]: Starting scan...[0m
[0;33m[W][component:157]: Component wifi set Warning flag: scanning for networks[0m
:313]: WiFi Connecting to 'GPONWIFI_BBD8'...[0m
[0;32m[I][wifi;- '32m[0m[0m
[0;36m[D][wifi:542]:     Channel: 6[0m
[0;36m[D][wifi:543]:     RSSI: -40 dB[0m
[0;36m[D][wifi:546]: - [5m''[6m [5m(02:09:B0:09:2F:01) [6m[0;33m[0;37m[0m[0m
[0;36m[D][wifi:546]: - [5m'TP-Link_C000':313]: WiFi Connecting to 'GPONWIFI_BBD8'...[0m
[0;36m[D][esp-idf:000][1;31m[wifi][0;36m: E (15044) wifi:[0m
[0;36m[D][esp-idf:000][1;31m[wifi][0;36m: Association refused temporarily, comeback time 1048 mSec[0m
[0;36m[D][esp-idf:000][1;31m[wifi][0;36m: 
[0m
[0;33m[W][wifi_esp32:569][1;31m[arduino_events][0;33m: Event: Disconnected ssid='GPONWIFI_BBD8' bssid=[5m54:DB:A2:3E:E3:99[6m reason='Association Failed'[0m
[0;33m[W][wifi:653]: Error while connecting to network.[0m
[0;33m[W][wifi_esp32:569][1;31m[arduino_events][0;33m: Event: Disconnected ssid='GPONWIFI_BBD8' bssid=[5m54:DB:A2:3E:E3:99[6m reason='Authentication Failed'[0m
[0;33m[W][wifi:669]: Connecting to WiFi network failed. Are the credentials wrong?[0m
+jm%um313]: WiFi Connecting to 'GPONWIFI_BBD8'...[0m
[0;[0;33m: Event: Disconnected ssid='GPONWIFI_BBD8' bssid=[5m54:DB:A2:3E:E3:99[6m reason='Association Leave'[0m
[0;33m[W][wifi:674]: WiFi Unknown connection status 0[0m
[0;32m[I][wifi:313]: WiFi Connecting to 'GPONWIFI_BBD8'...[0m
[0;32m[I][wifi:617]: WiFi Connected![0m
[0;35m[C][wifi:428]:   Local MAC: 40:22:D8:EA:23:8C[0m
[0;35m[C][wifi:433]:   SSID: [5m'GPONWIFI_BBD8'[6m[0m
[0;35m[C][wifi:436]:   IP Address: 192.168.33.222[0m
[0;35m[C][wifi:440]:   BSSID: [5m54:DB:A2:3E:E3:99[6m[0m
[0;35m[C][wifi:441]:   Hostname: 'wm-bus'[0m
[0;35m[C][wifi:443]:   Signal strength: -40 dB [0;32m[0m[0m
[0;35m[C][wifi:447]:   Channel: 6[0m
[0;35m[C][wifi:448]:   Subnet: 255.255.255.0[0m
[0;35m[C][wifi:449]:   Gateway: 192.168.33.1[0m
[0;35m[C][wifi:450]:   DNS1: 0.0.0.0[0m
[0;35m[C][wifi:451]:   DNS2: 0.0.0.0[0m
[0;36m[D][wifi:626]: Disabling AP...[0m
[0;35m[C][sntp:018]: Setting up SNTP...[0m
[0;35m[C][api:026]: Setting up Home Assistant API server...[0m
[0;36m[D][rxLoop:031]: Set CC1101 frequency to 868.950MHz [21 6B D0][0m
[0;36m[D][rxLoop:043]: CC1101 version '20'[0m
[0;36m[D][rxLoop:045]: CC1101 initialized[0m
[0;32m[I][app:062]: setup() finished successfully![0m
[0;33m[W][component:170]: Component wifi cleared Warning flag[0m
[0;33m[W][component:157]: Component api set Warning flag: unspecified[0m
[0;32m[I][app:100]: ESPHome version 2025.2.2 compiled on Mar 20 2025, 11:16:33[0m
[0;35m[C][wifi:600]: WiFi:[0m
[0;35m[C][wifi:428]:   Local MAC: 40:22:D8:EA:23:8C[0m
[0;35m[C][wifi:433]:   SSID: [5m'GPONWIFI_BBD8'[6m[0m
[0;35m[C][wifi:436]:   IP Address: 192.168.33.222[0m
[0;35m[C][wifi:440]:   BSSID: [5m54:DB:A2:3E:E3:99[6m[0m
[0;35m[C][wifi:441]:   Hostname: 'wm-bus'[0m
[0;35m[C][wifi:443]:   Signal strength: -40 dB [0;32m[0m[0m
[0;35m[C][wifi:447]:   Channel: 6[0m
[0;35m[C][wifi:448]:   Subnet: 255.255.255.0[0m
[0;35m[C][wifi:449]:   Gateway: 192.168.33.1[0m
[0;35m[C][wifi:450]:   DNS1: 0.0.0.0[0m
[0;35m[C][wifi:451]:   DNS2: 0.0.0.0[0m
[0;35m[C][logger:177]: Logger:[0m
[0;35m[C][logger:178]:   Max Level: DEBUG[0m
[0;35m[C][logger:179]:   Initial Level: DEBUG[0m
[0;35m[C][logger:181]:   Log Baud Rate: 115200[0m
[0;35m[C][logger:182]:   Hardware UART: UART0[0m
[0;35m[C][captive_portal:089]: Captive Portal:[0m
[0;35m[C][sntp:042]: SNTP Time:[0m
[0;35m[C][sntp:045]:   Server 0: '0.pool.ntp.org'[0m
[0;35m[C][sntp:045]:   Server 1: '1.pool.ntp.org'[0m
[0;35m[C][sntp:045]:   Server 2: '2.pool.ntp.org'[0m
[0;35m[C][mdns:116]: mDNS:[0m
[0;35m[C][mdns:117]:   Hostname: wm-bus[0m
[0;35m[C][esphome.ota:073]: Over-The-Air updates:[0m
[0;35m[C][esphome.ota:074]:   Address: 192.168.33.222:3232[0m
[0;35m[C][esphome.ota:075]:   Version: 2[0m
[0;35m[C][esphome.ota:078]:   Password configured[0m
[0;35m[C][safe_mode:018]: Safe Mode:[0m
[0;35m[C][safe_mode:020]:   Boot considered successful after 60 seconds[0m
[0;35m[C][safe_mode:021]:   Invoke after 10 boot attempts[0m
[0;35m[C][safe_mode:023]:   Remain in safe mode for 300 seconds[0m
[0;35m[C][api:140]: API Server:[0m
[0;35m[C][api:141]:   Address: 192.168.33.222:6053[0m
[0;35m[C][api:143]:   Using noise encryption: YES[0m
[0;35m[C][wmbus:338]: wM-Bus v4.1.4-1.17.1-b8f4a945:[0m
[0;35m[C][wmbus:340]:   Clients:[0m
[0;35m[C][wmbus:347]:     wmbusmeters: 10.0.0.22:7227 TCP [rtl-wmbus][0m
[0;35m[C][wmbus:351]:   LED:[0m
[0;35m[C][wmbus:352]:     Pin: GPIO2[0m
[0;35m[C][wmbus:353]:     Duration: 1000 ms[0m
[0;35m[C][wmbus:356]:   Chip ID: 8C23EAD82240[0m
[0;35m[C][wmbus:358]:   CC1101 frequency: 868.950 MHz[0m
[0;35m[C][wmbus:359]:   CC1101 SPI bus:[0m
[0;35m[C][wmbus:363]:     MOSI Pin: GPIO23[0m
[0;35m[C][wmbus:364]:     MISO Pin: GPIO19[0m
[0;35m[C][wmbus:365]:     CLK Pin:  GPIO18[0m
[0;35m[C][wmbus:366]:     CS Pin:   GPIO5[0m
[0;35m[C][wmbus:367]:     GDO0 Pin: GPIO17[0m
[0;35m[C][wmbus:368]:     GDO2 Pin: GPIO4[0m
[0;35m[C][wmbus:374]:   Available drivers: unknown, amiplus[0m
[0;35m[C][wmbus:388]:   Meter:[0m
[0;35m[C][wmbus:389]:     ID: 56821948 [0x036308BC][0m
[0;35m[C][wmbus:390]:     Type: amiplus[0m
[0;35m[C][wmbus:391]:     Key: '32001568219480000000000000000000'[0m
[0;35m[C][wmbus:393]:     Field: 'current_power_consumption'[0m
[0;35m[C][wmbus:394]:      Name: 'my current power consumption in Watts'[0m
[0;35m[C][wmbus:394]:        Device Class: 'power'[0m
[0;35m[C][wmbus:394]:        State Class: 'measurement'[0m
[0;35m[C][wmbus:394]:        Unit of Measurement: 'w'[0m
[0;35m[C][wmbus:394]:        Accuracy Decimals: 1[0m
[0;35m[C][wmbus:394]:        Icon: 'mdi:transmission-tower-import'[0m
[0;35m[C][wmbus:393]:     Field: 'current_power_production'[0m
[0;35m[C][wmbus:394]:      Name: 'my current power production in Watts'[0m
[0;35m[C][wmbus:394]:        Device Class: 'power'[0m
[0;35m[C][wmbus:394]:        State Class: 'measurement'[0m
[0;35m[C][wmbus:394]:        Unit of Measurement: 'w'[0m
[0;35m[C][wmbus:394]:        Accuracy Decimals: 1[0m
[0;35m[C][wmbus:394]:        Icon: 'mdi:transmission-tower-import'[0m
[0;35m[C][wmbus:393]:     Field: 'total_energy_consumption_tariff_1'[0m
[0;35m[C][wmbus:394]:      Name: 'total energy on T1'[0m
[0;35m[C][wmbus:394]:        Device Class: 'energy'[0m
[0;35m[C][wmbus:394]:        State Class: 'total_increasing'[0m
[0;35m[C][wmbus:394]:        Unit of Measurement: 'kwh'[0m
[0;35m[C][wmbus:394]:        Accuracy Decimals: 3[0m
[0;35m[C][wmbus:394]:        Icon: 'mdi:transmission-tower-import'[0m
[0;35m[C][wmbus:393]:     Field: 'total_energy_production_tariff_1'[0m
[0;35m[C][wmbus:394]:      Name: 'total energy production on T1'[0m
[0;35m[C][wmbus:394]:        Device Class: 'energy'[0m
[0;35m[C][wmbus:394]:        State Class: 'total_increasing'[0m
[0;35m[C][wmbus:394]:        Unit of Measurement: 'kwh'[0m
[0;35m[C][wmbus:394]:        Accuracy Decimals: 3[0m
[0;35m[C][wmbus:394]:        Icon: 'mdi:transmission-tower-import'[0m
[0;35m[C][wmbus:393]:     Field: 'voltage_at_phase_1'[0m
[0;35m[C][wmbus:394]:      Name: 'voltage_at_phase_1'[0m
[0;35m[C][wmbus:394]:        Device Class: 'voltage'[0m
[0;35m[C][wmbus:394]:        State Class: 'measurement'[0m
[0;35m[C][wmbus:394]:        Unit of Measurement: 'v'[0m
[0;35m[C][wmbus:394]:        Accuracy Decimals: 0[0m
[0;35m[C][wmbus:394]:        Icon: 'mdi:sine-wave'[0m
[0;35m[C][wmbus:397]:     Text field: 'current_power_consumption'[0m
[0;35m[C][wmbus:398]:      Name: 'my current power consumption in Watts'[0m
[0;35m[C][wmbus:398]:        Icon: 'mdi:transmission-tower-import'[0m
[0;36m[D][mbus:035]: Received T1 A frame[0m
mponent:238]: Components should block for at most 30 ms.[0m
coSm
I: -60dBm T: DE4401064819825601027A9A00D005C656F28CF454E7F600453EBDE8E64D434D1B430868F40C91D5D600894D9D53098428E677E1632A0817F4F33985618B90CABD1A917BBC20FB8B293610F44216E6B733A5F6D232F12F176C359523C1936886EBC0D0A4DC41E97048534159B28D94A868DF493D2C12035mponent:238]: Components should block for at most 30 ms.[0m
+jm%um}041]: Boot seems successful; resetting boot 4oop]: Saving 1 preferences to flash...[0m
[0;36m[D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed[0m
+jmum035]: Received T1 A frame[0m
mponent:238]: Components should block for at most 30 ms.[0m
coSm
I: -60dBm T: DE4401064819825601027A9B00D005862BD3837D9886265C5A956655FEA8079A6A8EF160EB10CDC96EC781E287DF1C812348FB0D4D69F9AE5F90504D408FC8738B143787442A861EBA8F4552482829F4AD6A645DF55B50162A90EBBF240A11A1E6BAA9A6D5691E4CD1EA4E9918ED4F274A723F3B79F2EA8mponent:238]: Components should block for at most 30 ms.[0m

Dane są odczytane prawidłowo, po rozkodowaniu ręcznie są wszystkie wartości z licznika.
Czy da się te dane wysłać na zewnętrzny serwer mqtt, swój lub w sieci?

2

Da się, choć pewnie nie ma takiej konieczności (ESPHome się świetnie integruje bezpośrednio z HA po API, swoją drogą skonfigurowałeś sensory, więc nie wiem czemu z tego nie korzystasz), możesz też bezpośrednio wysyłać do własnego serwera wmbusmeters (dostępnego też w postaci Dodatku do HA)

To wszystko zgodnie z dokumentacją (nie wiem na ile aktualną, bo nie używam w ten sposób - ESP32 i EPS32-Sx są w sumie wystarczające do dekodowania już na poziomie MCU, ale nie mam licznika takiego jak twój, gdzie być może istotnie to się może do czegoś przydać…).

Nawet powiem więcej ten wpis w logu

wynika z faktu, że w konfiguracji YAML z której tworzysz firmware skonfigurowałeś sobie serwer wmbusmeters

którego najwyraźniej nie posiadasz, ponadto jest on w innej adresacji niż twoja sieć, więc czuję w kościach, że poniższy fragment był skopiowany skądś (dokumentacji?) bez zrozumienia po co on jest…

to może wynikać z ograniczeń terminala którego używasz do podglądania logów z portu szeregowego (wygląda jakby jakaś sekwencja znaków sterowała terminalem).

3

Tak zgadza się, cupłem go na żywca z przykładu do Komponentu. Przyznaje że jestem zielony w tej dziedzinie. Coś mi tam zaświtało że mam inną adresacje, i dlatego mi to nie chce śmigać. Będę próbował dalej. Na chwilę obecną dzięki za sugestie. Na pewno będę miał jeszcze pytania. Pozdro.

4

Wywal zbędne rzeczy i zacznij po API.
Jeśli nie tak to wysyłając dane do wmbusmeters bezpośrednio.
MQTT w ostateczności, bo kojarzę wiele postów z problemami.

5

A po API to znaczy jak?

6

Tak “po prostu” - za domyślną Integrację z HA odpowiada właśnie API
dzięki temu zdefiniowane i działające sensory (i aktory) ze sprzętu z firmware ESPHome masz dostępne od ręki w HA.

Jak widać masz to uruchomione

Wiec jeśli tylko coś odbierasz, dekodujesz i masz poprawnie zdefiniowane sensory, to one są dostępne w HA natychmiastowo w Integracji tego urządzenia.

O ile je dodałeś do HA.

bo jak widać z jakiegoś powodu zdefiniowałeś TCP/IP statycznie (więc autodiscovery może nie działąć).

7

Ok, dogram brakujące elementy i zobaczę co mi pokaże.

8

Co tam chcesz dogrywać? usuń zbędny balast.

9

No właśnie, problemem jest to że widzę HA od paru dni dosłownie, poruszam się po omacku, nie znam tego środowiska. Całe życie w Basic, Pascal, Bascom a ostatnio dla ESP Annex rds WiFi. Próbowałem Arduino ale zalałem się łzami. Jeszcze podgórę z Linuxem. Chciałem odbierać dane z licznika na zasadzie modułu bramki, konfiguruję z poziomu strony web i śmiga ale widocznie się myliłem. Dlatego czeka mnie długa droga, muszę poznać HA dobrze. Pozytyw że moduł odbiera telegram. Pewnie bym zrobił na chłopski rozum, podłączył drugi ESP po rs i zdekodował w mim telegram z poziomu Annex Basic i wysłał na swój mqqt, ale to tylko opcja.