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

Hmm wkładasz mi w usta jakieś rzeczy których nie napisałem.
Widziałeś wątki z ostatnich tygodni powiązane z Supervisorem?
Zakładam, że HA zrestartował się w twojej instalacji z innego powodu (w sumie restart może wywołać Supervisror albo, co jest najczęstszą przyczyną, niestandardowy komponent w HA, ale nie w ESPHome).

Skoro nie masz włączonych autoaktualizacji, to ja tu widzę “rękę Supervisora”…
Bo w ogóle zrestartowanie się HA z powodu wadliwego działania urządzenia ESPHome jest z kategorii zdarzeń nieprawdopodobnych biorąc pod uwagę komunikację po API lub tym bardziej przez MQTT.

Czy ESPHome nie jest przypadkiem takim “niestandardowym komponentem”?

Integracja ESPHome jest standardowym komponentem, a jeśli mówisz o IDE ESPHome (jako Dodatek) to jest w ogóle oddzielny kontener (jak każdy Dodatek), więc jest izolowany od wszystkich innych kontenerów w instalacji.

Generalnie IDE ESPHome (Dashboard ESPHome, Dodatek) nie jest potrzebne do zintegrowania urządzeń ESPHome z instalacją HA, natomiast bez niego nie będziesz w stanie aktualizować firmware w posiadanych urządzeniach (ale nie ma musu instalacji IDE ESPHome w tej samej instalacji, gdzie masz działające HA, można mieć instalację środowiska uruchomieniowego zupełnie osobno i też będzie działać, chociaż oczywiście nie będzie tak wygodnie).
To jest i tak całkowicie osobny serwer od HA, bo nawet w postaci kontenera/Dodatku jest w pełni izolowany od instalacji HA, więc nie widzę powodu do robienia sobie pod górkę i instalacji na osobnym sprzęcie.

Połączyłem się przez USB. To jednak chyba błąd kodowania:

wMBus-lib: CC1101 version '4'
wMBus-lib: CC1101 initialized
[VV][wmbus-drivers:028]: Added driver 'amiplus' with key ''
[VV][wmbus-drivers:028]: Added driver 'apator08' with key ''
[VV][wmbus-drivers:028]: Added driver 'apator162' with key ''
[VV][wmbus-drivers:028]: Added driver 'apatoreitn' with key ''
[VV][wmbus-drivers:028]: Added driver 'bmeters' with key ''
[VV][wmbus-drivers:028]: Added driver 'c5isf' with key ''
[VV][wmbus-drivers:028]: Added driver 'compact5' with key ''
[VV][wmbus-drivers:028]: Added driver 'dme07' with key ''
[VV][wmbus-drivers:028]: Added driver 'elf' with key ''
[VV][wmbus-drivers:028]: Added driver 'evo868' with key ''
[VV][wmbus-drivers:028]: Added driver 'fhkvdataiii' with key ''
[VV][wmbus-drivers:028]: Added driver 'hydrocalm3' with key ''
[VV][wmbus-drivers:028]: Added driver 'hydrus' with key ''
[VV][wmbus-drivers:028]: Added driver 'iperl' with key ''
[VV][wmbus-drivers:028]: Added driver 'itron' with key ''
[VV][wmbus-drivers:028]: Added driver 'izar' with key ''
[VV][wmbus-drivers:028]: Added driver 'mkradio3' with key ''
[VV][wmbus-drivers:028]: Added driver 'mkradio4' with key ''
[VV][wmbus-drivers:028]: Added driver 'qheat' with key ''
[VV][wmbus-drivers:028]: Added driver 'qwater' with key ''
[VV][wmbus-drivers:028]: Added driver 'sharky774' with key '51728910E66D83F851728910E66D83F8'
[VV][wmbus-drivers:028]: Added driver 'topaseskr' with key ''
[VV][wmbus-drivers:028]: Added driver 'ultrimis' with key ''
[VV][wmbus-drivers:028]: Added driver 'unismart' with key ''
[VV][wmbus-drivers:028]: Added driver 'vario451' with key ''
[I][app:062]: setup() finished successfully!
[VV][scheduler:226]: Running interval 'update' with interval=900000 last_execution=4293894944 (now=58446)
[I][app:102]: ESPHome version 2023.11.6 compiled on Nov 30 2023, 18:45:35
[C][wifi:559]: WiFi:
[C][wifi:391]:   Local MAC: 84:CC:A8:5E:A5:80
[C][wifi:396]:   SSID: '#################'[redacted]
[C][wifi:397]:   IP Address: 10.0.0.132
[C][wifi:399]:   BSSID: B6:B9:8A:5C:66:3C[redacted]
[C][wifi:400]:   Hostname: 'esp-wmbus'
[C][wifi:402]:   Signal strength: -61 dB ▂▄▆█
[V][wifi:404]:   Priority: -6.0
[C][wifi:406]:   Channel: 9
[C][wifi:407]:   Subnet: 255.255.255.0
[C][wifi:408]:   Gateway: 10.0.0.1
[C][wifi:409]:   DNS1: 0.0.0.0
[C][wifi:410]:   DNS2: 0.0.0.0
[C][logger:416]: Logger:
[C][logger:417]:   Level: VERY_VERBOSE
[C][logger:418]:   Log Baud Rate: 115200
[C][logger:420]:   Hardware UART: UART0
[C][captive_portal:088]: Captive Portal:
[C][sntp:053]: SNTP Time:
[C][sntp:054]:   Server 1: '0.pool.ntp.org'
[C][sntp:055]:   Server 2: '1.pool.ntp.org'
[C][sntp:056]:   Server 3: '2.pool.ntp.org'
[C][sntp:057]:   Timezone: 'CET-1CEST,M3.5.0,M10.5.0/3'
[C][mdns:115]: mDNS:
[C][mdns:116]:   Hostname: esp-wmbus
[V][mdns:117]:   Services:
[V][mdns:119]:   - _esphomelib, _tcp, 6053
[V][mdns:121]:     TXT: version = 2023.11.6
[V][mdns:121]:     TXT: mac = 84cca85ea580
[V][mdns:121]:     TXT: platform = ESP32
[V][mdns:121]:     TXT: board = esp32dev
[V][mdns:121]:     TXT: network = wifi
[V][mdns:121]:     TXT: api_encryption = Noise_NNpsk0_25519_ChaChaPoly_SHA256
[C][ota:097]: Over-The-Air Updates:
[C][ota:098]:   Address: 10.0.0.132:3232
[C][ota:101]:   Using Password.
[W][ota:107]: Last Boot was an unhandled reset, will proceed to safe mode in 7 restarts
[C][api:139]: API Server:
[C][api:140]:   Address: 10.0.0.132:6053
[C][api:142]:   Using noise encryption: YES
[C][wmbus:415]: wM-Bus v2.3.2:
[C][wmbus:417]:   Clients:
[C][wmbus:424]:     wmbusmeters: 10.0.0.111:7227 UDP [rtl-wmbus]
[C][wmbus:432]:   CC1101 SPI bus:
[C][wmbus:433]:     MOSI Pin: GPIO23
[C][wmbus:434]:     MISO Pin: GPIO19
[C][wmbus:435]:     CLK Pin:  GPIO18
[C][wmbus:436]:     CS Pin:   GPIO5
[C][wmbus:437]:     GDO0 Pin: GPIO25
[C][wmbus:438]:     GDO2 Pin: GPIO26
[C][wmbus:445]:   Available drivers:  amiplus, apator08, apator162, apatoreitn, bmeters, c5isf, compact5, dme07, elf, evo868, fhkvdataiii, hydrocalm3, hydrus, iperl, itron, izar, mkradio3, mkradio4, qheat, qwater, sharky774, topaseskr, ultrimis, unismart, vario451
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=4294966015 (now=58719)
[D][api:102]: Accepted 10.0.0.200
[VV][api.socket:696]: 10.0.0.200: Handshake complete!
[VV][api.service:522]: on_hello_request: HelloRequest {
  client_info: 'Home Assistant 2023.11.3'
  api_version_major: 1
  api_version_minor: 9
}
[V][api.connection:1071]: Hello from client: 'Home Assistant 2023.11.3' | 10.0.0.200 | API Version 1.9
[VV][api.service:013]: send_hello_response: HelloResponse {
  api_version_major: 1
  api_version_minor: 9
  server_info: 'esp-wmbus (esphome v2023.11.6)'
  name: 'esp-wmbus'
}
[VV][api.service:531]: on_connect_request: ConnectRequest {
  password: ''
}
[D][api.connection:1089]: Home Assistant 2023.11.3 (10.0.0.200): Connected successfully
[VV][api.service:019]: send_connect_response: ConnectResponse {
  invalid_password: NO
}
[VV][api.service:576]: on_device_info_request: DeviceInfoRequest {}
[VV][api.service:049]: send_device_info_response: DeviceInfoResponse {
  uses_password: NO
  name: 'esp-wmbus'
  mac_address: '84:CC:A8:5E:A5:80'
  esphome_version: '2023.11.6'
  compilation_time: 'Nov 30 2023, 18:45:35'
  model: 'esp32dev'
  has_deep_sleep: NO
  project_name: ''
  project_version: ''
  webserver_port: 0
  legacy_bluetooth_proxy_version: 0
  bluetooth_proxy_feature_flags: 0
  manufacturer: 'Espressif'
  friendly_name: ''
  voice_assistant_version: 0
  suggested_area: ''
}
[VV][api.service:585]: on_list_entities_request: ListEntitiesRequest {}
[VV][api.service:055]: send_list_entities_done_response: ListEntitiesDoneResponse {}
[VV][api.service:594]: on_subscribe_states_request: SubscribeStatesRequest {}
[VV][api.service:656]: on_subscribe_homeassistant_services_request: SubscribeHomeassistantServicesRequest {}
[VV][api.service:683]: on_subscribe_home_assistant_states_request: SubscribeHomeAssistantStatesRequest {}
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=58719 (now=118720)
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000ABFA4] RSSI: -42 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486A4BF0A000303A0BD4303009C4100182412051E0B17348F97D70305FF0AACBE02000300000000375106305047501F0000000020000000000000236202820C2436020E160A1527000000280000000000002C0009161207172F0000000000003100002100 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[W][component:214]: Component wmbus took a long time for an operation (0.05 s).
[W][component:215]: Components should block for at most 20-30ms.
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
**wMBus-lib: Processing T1 A frame**
**wMBus-lib:  Error during decoding '3 out of 6'**
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=118719 (now=178719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000ABFA4] RSSI: -40 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486A4BF0A000303A0C34303009C41003A2512051E0B17348F97D70305FF0AACBE02000300000000375106305047501F0000000020000000000000236202820C2436020E160A1527000000280000000000002C0009161207172F0000000000003100002100 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=178719 (now=238719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=238719 (now=298719)
[I][ota:117]: Boot seems successful, resetting boot loop counter.
[VV][esp32.preferences:040]: s_pending_save: key: 233825507, len: 4
[D][esp32.preferences:114]: Saving 1 preferences to flash...
[VV][esp32.preferences:123]: Checking if NVS data 233825507 has changed
[V][esp32.preferences:126]: sync: key: 233825507, len: 4
[D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=298719 (now=358719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=358719 (now=418719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=418719 (now=478719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=478719 (now=538722)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000ABFA4] RSSI: -40 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486A4BF0A000303A0D84303009C41003B2B12051E0B17348F97D70305FF0AACBE02000300000000375106305047501F0000000020000000000000236202820C2436020E160A1527000000280000000000002C0009161207172F0000000000003100002100 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=538719 (now=598719)
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000B9CE7] RSSI: -35 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486E79C0B000303A07DFC00009C40002F1812051E0B17346297D70305FF0A7DFC00000300000000375106304D454D1F0000000020000000000000238DFC810C2406340D160A1527000000280000000000002C0030151207172F0000000000003101000500 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=598719 (now=658719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000ABFA4] RSSI: -41 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486A4BF0A000303A0D84303009C4100212D12051E0B17348F97D70305FF0AACBE02000300000000375106305047501F0000000020000000000000236202820C2436020E160A1527000000280000000000002C0009161207172F0000000000003100002100 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[W][component:214]: Component wmbus took a long time for an operation (0.05 s).
[W][component:215]: Components should block for at most 20-30ms.
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=658719 (now=718719)
[VV][scheduler:226]: Running interval 'update' with interval=900000 last_execution=4294794944 (now=727648)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=718719 (now=778720)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000ABFA4] RSSI: -41 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486A4BF0A000303A0D84303009C41001D2F12051E0B17348F97D70305FF0AACBE02000300000000375106305047501F0000000020000000000000236202820C2436020E160A1527000000280000000000002C0009161207172F0000000000003100002100 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[W][component:214]: Component wmbus took a long time for an operation (0.05 s).
[W][component:215]: Components should block for at most 20-30ms.
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=778719 (now=838719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=838719 (now=898720)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000B9CE7] RSSI: -35 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486E79C0B000303A07EFC00009C4000271D12051E0B17346297D70305FF0A7DFC00000300000000375106304D454D1F0000000020000000000000238DFC810C2406340D160A1527000000280000000000002C0030151207172F0000000000003101000500 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[W][component:214]: Component wmbus took a long time for an operation (0.05 s).
[W][component:215]: Components should block for at most 20-30ms.
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=898719 (now=958721)
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000B9CE7] RSSI: -35 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486E79C0B000303A07DFC00009C4000271E12051E0B17346297D70305FF0A7DFC00000300000000375106304D454D1F0000000020000000000000238DFC810C2406340D160A1527000000280000000000002C0030151207172F0000000000003101000500 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[W][component:214]: Component wmbus took a long time for an operation (0.05 s).
[W][component:215]: Components should block for at most 20-30ms.
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=958719 (now=1018719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=1018719 (now=1078720)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=1078719 (now=1138719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000ABFA4] RSSI: -43 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486A4BF0A000303A0D84303009C4100253512051E0B17348F97D70305FF0AACBE02000300000000375106305047501F0000000020000000000000236202820C2436020E160A1527000000280000000000002C0009161207172F0000000000003100002100 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[W][component:214]: Component wmbus took a long time for an operation (0.05 s).
[W][component:215]: Components should block for at most 20-30ms.
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000B9CE7] RSSI: -35 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486E79C0B000303A07EFC00009C4000042212051E0B17346297D70305FF0A7DFC00000300000000375106304D454D1F0000000020000000000000238DFC810C2406340D160A1527000000280000000000002C0030151207172F0000000000003103000500 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[W][component:214]: Component wmbus took a long time for an operation (0.05 s).
[W][component:215]: Components should block for at most 20-30ms.
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=1138719 (now=1198720)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=1198719 (now=1258719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=1258719 (now=1318721)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000B9CE7] RSSI: -35 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486E79C0B000303A07DFC00009C40000E2512051E0B17346297D70305FF0A7DFC00000300000000375106304D454D1F0000000020000000000000238DFC810C2406340D160A1527000000280000000000002C0030151207172F0000000000003101000500 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[W][component:214]: Component wmbus took a long time for an operation (0.05 s).
[W][component:215]: Components should block for at most 20-30ms.
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=1318719 (now=1378719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000ABFA4] RSSI: -41 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486A4BF0A000303A0D84303009C41000D3A12051E0B17348F97D70305FF0AACBE02000300000000375106305047501F0000000020000000000000236202820C2436020E160A1527000000280000000000002C0009161207172F0000000000003100002100 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[W][component:214]: Component wmbus took a long time for an operation (0.05 s).
[W][component:215]: Components should block for at most 20-30ms.
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=1378719 (now=1438722)
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000B9CE7] RSSI: -34 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486E79C0B000303A07DFC00009C4000232612051E0B17346297D70305FF0A7DFC00000300000000375106304D454D1F0000000020000000000000238DFC810C2406340D160A1527000000280000000000002C0030151207172F0000000000003101000500 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[W][component:214]: Component wmbus took a long time for an operation (0.05 s).
[W][component:215]: Components should block for at most 20-30ms.
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=2038719 (now=2098719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
wMBus-lib: Processing T1 A frame
[VV][wmbus:056]: have data from CC1101 ...
[D][wmbus:187]: Meter ID [0x000B9CE7] RSSI: -35 dBm LQI: 128 Mode: T1 not found in configuration T: 66441486E79C0B000303A07EFC00009C4000313112051E0B17346297D70305FF0A7DFC00000300000000375106304D454D1F0000000020000000000000238DFC810C2406340D160A1527000000280000000000002C0030151207172F0000000000003103000500 (103)
[VV][wmbus:191]: will send telegram to clients ...
[VV][wmbus:246]: Will send RTLWMBUS telegram to 10.0.0.111:7227 via UDP
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=2098719 (now=2158720)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=2158719 (now=2218720)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
**wMBus-lib: Processing T1 A frame**
**wMBus-lib:  Error during decoding '3 out of 6'**
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=2218719 (now=2278719)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}

Ale ładnie odbiera jakieś ramki poprawie.
Więc wszystko działa.
Tymi błędami kodowania nie przejmuj się, jak radio jest zaśmiecone (dużo transmisji) to będą od czasu do czasu wyskakiwać.

Jak widać w wersji 2023.11.6 działa – tym samym zamykam temat :smiley:

Nie tak szybko :grinning:
To są ramki z dwóch niekodowanych apator08. Kodowanych z unismart’a nie ma. Zakładam, że te błędy kodowania, to właśnie ramki unimart’a. Śmię tak przypuszczać, ponieważ wyszedłem z modułem na zewnątrz do skrzynki z unismart’em. Straciłem zasięg z nakładkami wodomierza, a te błędne zaczęły się pojawiać częściej. Poniżej log, gdzie byłem 1,5m od unismarta:

wMBus-lib: CC1101 version '4'
wMBus-lib: CC1101 initialized
[VV][wmbus-drivers:028]: Added driver 'amiplus' with key ''
[VV][wmbus-drivers:028]: Added driver 'apator08' with key ''
[VV][wmbus-drivers:028]: Added driver 'apator162' with key ''
[VV][wmbus-drivers:028]: Added driver 'apatoreitn' with key ''
[VV][wmbus-drivers:028]: Added driver 'bmeters' with key ''
[VV][wmbus-drivers:028]: Added driver 'c5isf' with key ''
[VV][wmbus-drivers:028]: Added driver 'compact5' with key ''
[VV][wmbus-drivers:028]: Added driver 'dme07' with key ''
[VV][wmbus-drivers:028]: Added driver 'elf' with key ''
[VV][wmbus-drivers:028]: Added driver 'evo868' with key ''
[VV][wmbus-drivers:028]: Added driver 'fhkvdataiii' with key ''
[VV][wmbus-drivers:028]: Added driver 'hydrocalm3' with key ''
[VV][wmbus-drivers:028]: Added driver 'hydrus' with key ''
[VV][wmbus-drivers:028]: Added driver 'iperl' with key ''
[VV][wmbus-drivers:028]: Added driver 'itron' with key ''
[VV][wmbus-drivers:028]: Added driver 'izar' with key ''
[VV][wmbus-drivers:028]: Added driver 'mkradio3' with key ''
[VV][wmbus-drivers:028]: Added driver 'mkradio4' with key ''
[VV][wmbus-drivers:028]: Added driver 'qheat' with key ''
[VV][wmbus-drivers:028]: Added driver 'qwater' with key ''
[VV][wmbus-drivers:028]: Added driver 'sharky774' with key '51728910E66D83F851728910E66D83F8'
[VV][wmbus-drivers:028]: Added driver 'topaseskr' with key ''
[VV][wmbus-drivers:028]: Added driver 'ultrimis' with key ''
[VV][wmbus-drivers:028]: Added driver 'unismart' with key ''
[VV][wmbus-drivers:028]: Added driver 'vario451' with key ''
[I][app:062]: setup() finished successfully!
[VV][scheduler:226]: Running interval 'update' with interval=900000 last_execution=4293876244 (now=84283)
[I][app:102]: ESPHome version 2023.11.6 compiled on Nov 30 2023, 18:45:35
[C][wifi:559]: WiFi:
[C][wifi:391]:   Local MAC: 84:CC:A8:5E:A5:80
[C][wifi:396]:   SSID: '###################'[redacted]
[C][wifi:397]:   IP Address: 10.0.0.132
[C][wifi:399]:   BSSID: B6:B9:8A:5C:82:48[redacted]
[C][wifi:400]:   Hostname: 'esp-wmbus'
[C][wifi:402]:   Signal strength: -86 dB ▂▄▆█
[V][wifi:404]:   Priority: -9.0
[C][wifi:406]:   Channel: 9
[C][wifi:407]:   Subnet: 255.255.255.0
[C][wifi:408]:   Gateway: 10.0.0.1
[C][wifi:409]:   DNS1: 0.0.0.0
[C][wifi:410]:   DNS2: 0.0.0.0
[C][logger:416]: Logger:
[C][logger:417]:   Level: VERY_VERBOSE
[C][logger:418]:   Log Baud Rate: 115200
[C][logger:420]:   Hardware UART: UART0
[C][captive_portal:088]: Captive Portal:
[C][sntp:053]: SNTP Time:
[C][sntp:054]:   Server 1: '0.pool.ntp.org'
[C][sntp:055]:   Server 2: '1.pool.ntp.org'
[C][sntp:056]:   Server 3: '2.pool.ntp.org'
[C][sntp:057]:   Timezone: 'CET-1CEST,M3.5.0,M10.5.0/3'
[C][mdns:115]: mDNS:
[C][mdns:116]:   Hostname: esp-wmbus
[V][mdns:117]:   Services:
[V][mdns:119]:   - _esphomelib, _tcp, 6053
[V][mdns:121]:     TXT: version = 2023.11.6
[V][mdns:121]:     TXT: mac = 84cca85ea580
[V][mdns:121]:     TXT: platform = ESP32
[V][mdns:121]:     TXT: board = esp32dev
[V][mdns:121]:     TXT: network = wifi
[V][mdns:121]:     TXT: api_encryption = Noise_NNpsk0_25519_ChaChaPoly_SHA256
[C][ota:097]: Over-The-Air Updates:
[C][ota:098]:   Address: 10.0.0.132:3232
[C][ota:101]:   Using Password.
[W][ota:107]: Last Boot was an unhandled reset, will proceed to safe mode in 5 restarts
[C][api:139]: API Server:
[C][api:140]:   Address: 10.0.0.132:6053
[C][api:142]:   Using noise encryption: YES
[C][wmbus:415]: wM-Bus v2.3.2:
[C][wmbus:417]:   Clients:
[C][wmbus:424]:     wmbusmeters: 10.0.0.111:7227 UDP [rtl-wmbus]
[C][wmbus:432]:   CC1101 SPI bus:
[C][wmbus:433]:     MOSI Pin: GPIO23
[C][wmbus:434]:     MISO Pin: GPIO19
[C][wmbus:435]:     CLK Pin:  GPIO18
[C][wmbus:436]:     CS Pin:   GPIO5
[C][wmbus:437]:     GDO0 Pin: GPIO25
[C][wmbus:438]:     GDO2 Pin: GPIO26
[C][wmbus:445]:   Available drivers:  amiplus, apator08, apator162, apatoreitn, bmeters, c5isf, compact5, dme07, elf, evo868, fhkvdataiii, hydrocalm3, hydrus, iperl, itron, izar, mkradio3, mkradio4, qheat, qwater, sharky774, topaseskr, ultrimis, unismart, vario451
[D][api:102]: Accepted 10.0.0.200
[VV][api.socket:696]: 10.0.0.200: Handshake complete!
[VV][api.service:522]: on_hello_request: HelloRequest {
  client_info: 'Home Assistant 2023.11.3'
  api_version_major: 1
  api_version_minor: 9
}
[V][api.connection:1071]: Hello from client: 'Home Assistant 2023.11.3' | 10.0.0.200 | API Version 1.9
[VV][api.service:013]: send_hello_response: HelloResponse {
  api_version_major: 1
  api_version_minor: 9
  server_info: 'esp-wmbus (esphome v2023.11.6)'
  name: 'esp-wmbus'
}
[VV][api.service:531]: on_connect_request: ConnectRequest {
  password: ''
}
[D][api.connection:1089]: Home Assistant 2023.11.3 (10.0.0.200): Connected successfully
[VV][api.service:019]: send_connect_response: ConnectResponse {
  invalid_password: NO
}
[VV][api.service:576]: on_device_info_request: DeviceInfoRequest {}
[VV][api.service:049]: send_device_info_response: DeviceInfoResponse {
  uses_password: NO
  name: 'esp-wmbus'
  mac_address: '84:CC:A8:5E:A5:80'
  esphome_version: '2023.11.6'
  compilation_time: 'Nov 30 2023, 18:45:35'
  model: 'esp32dev'
  has_deep_sleep: NO
  project_name: ''
  project_version: ''
  webserver_port: 0
  legacy_bluetooth_proxy_version: 0
  bluetooth_proxy_feature_flags: 0
  manufacturer: 'Espressif'
  friendly_name: ''
  voice_assistant_version: 0
  suggested_area: ''
}
[VV][api.service:585]: on_list_entities_request: ListEntitiesRequest {}
[VV][api.service:055]: send_list_entities_done_response: ListEntitiesDoneResponse {}
[VV][api.service:594]: on_subscribe_states_request: SubscribeStatesRequest {}
[VV][api.service:656]: on_subscribe_homeassistant_services_request: SubscribeHomeassistantServicesRequest {}
[VV][api.service:683]: on_subscribe_home_assistant_states_request: SubscribeHomeAssistantStatesRequest {}
**wMBus-lib: Processing T1 A frame**
**wMBus-lib:  Error during decoding '3 out of 6'**
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=54428 (now=114428)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
**wMBus-lib: Processing T1 A frame**
**wMBus-lib:  Error during decoding '3 out of 6'**
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=114428 (now=174428)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=174428 (now=234431)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=234428 (now=294428)
[I][ota:117]: Boot seems successful, resetting boot loop counter.
[VV][esp32.preferences:040]: s_pending_save: key: 233825507, len: 4
[D][esp32.preferences:114]: Saving 1 preferences to flash...
[VV][esp32.preferences:123]: Checking if NVS data 233825507 has changed
[V][esp32.preferences:126]: sync: key: 233825507, len: 4
[D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=294428 (now=354428)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=354428 (now=414428)
[VV][api.service:558]: on_ping_request: PingRequest {}
[VV][api.service:043]: send_ping_response: PingResponse {}
**Bus-lib: Processing T1 A frame**
**Bus-lib:  Error during decoding '3 out of 6'**
[VV][scheduler:226]: Running interval '' with interval=60000 last_execution=414428 (now=474428)

Nasuwa się pytanie czy moduł ESP32 odbierał ramki częściej z powodu mniejszej odległości, czy dlatego że miał więcej czasu, bo nie przeszkadzały mu nakładki wodomierzy.

OFF TOPIC
@Grzegorz_Murach
Pociągnę offtopic o zamykaniu się kontenerów - w innym wątku widziałem, że prawdopodobnie masz instalację na RPi - czy monitorujesz zasoby sprzętu (przede wszystkim RAM i swap)?
Bo sytuacja jest taka, że Supervisor w sytuacji krytycznej zamyka/restartuje kontenery, a sytuacja krytyczna w postaci braku pamięci na sprzęcie o ograniczonych zasobach jest prawdopodobna.
Bywały sytuacje, że ludzie mieli problem z kompilacją na sprzęcie mającym mało RAMu (np. na RPi3B czy RPi4B w wersjach z mniejszą ilością RAMu, ewentualnie w sytuacji pracujących wielu Dodatków, w tym np. NR).

To nie mój przypadek. Mam 2,5GB wolnej pamięci, obciążenie procka 4%, 40GB wolnego na karcie.
Monitoruję stabilność zasilania. Pełny backup nie przekracza 200MB. RPI4 to w moim przypadku marnotrawstwo zasobów.
Nigdy wcześniej nie zrestartował mi się HA bez mojej ingerencji.

  1. Musimy rozróżnić, albo uściślić pojęcie kodowania. W przypadku ramek T1 mamy dwa poziomy kodowania:
    a) 3z6 - obecne zawsze, bardzo upraszczając można powiedzieć że dotyczy transmisji po radiu.
    b) kodowanie powiązane z kluczem z YAMLa, raczej nazywał bym to szyfrowaniem.

  2. Czy coś można poprawić, nie mam pojęcia (teraz).

Najprościej to przygotować sobie wkład do ESP bez ESPHome, tak aby odciąć się od jego schedulera i wszystko załatwiać tylko w arduinowej pętli (bez zbędnego narzutu / marnowania czasu). Wtedy powinno być widać czy jest jakaś poprawa czy nie.

Z drugiej strony transmisja wM-Bus nie jest super szybka i wbudowany bufor w CC1101 powinien wystarczyć.

Jest jeszcze jedna opcja – zabawa z parametrami konfiguracyjnymi CC1101 – to już jest hardcore i wątpię czy coś więcej można tam wykrzesać.

@_Szczepan 2 slowa komentarza? :slight_smile:

Mam jedno:
działa

Niedługo powinno pojawić się na masterze wraz z konfiguracją w YAML.
Jak zawsze zapraszam do testów itp.

Panowie, możecie trochę jaśniej?

1 polubienie

Pytam, bo kiedyś wspominałeś, że projekt nie ma szans działać na 433MHz. To będzie jakaś odrębną lista liczników na 433MHz?

Tak to jest odpisywać z komórki :frowning:

W tamtej wersji było tylko 868. Niedługo też 433 będzie. Co do listy to nie mam pojęcia co działa na 433. :wink:

Musicie sami potwierdzać i/lub dodawać do dokumentacji.

[edit - 11.12.2023]
Od wersji 2.4.4 wprowadziłem możliwość wyboru częstotliwości. Wystarczy do konfiga dodać:

wmbus:
  frequency: 345.678
2 polubienia

@_Szczepan mam problem z nakładką od bmeters.

|20:06:21|[I]|[wmbus:087]|Using driver 'bmeters' for ID [0x12055236] RSSI: -42 dBm LQI: 128 Mode: T1 T: 0C46B40936520512050778865D (13)|
| --- | --- | --- | --- |
|20:06:21|[E]|[wmbus:324]|CI unknown|
|20:06:21|[E]|[wmbus:109]|Something was not OK during decrypting telegram for ID [0x12055236] 'bmeters' key: '00000000000000000000000000000000'|
|20:06:21|[E]|[wmbus:110]|T : 0C46B40936520512050778865D (13)|
|20:06:21|[E]|[wmbus:111]|T': 0C46B40936520512050778865D (13)|
|20:06:21|[E]|[wmbus:111]|T': 0C46B40936520512050778865D (13)|

czasem jest taki telegram:
https://wmbusmeters.org/analyze/4944B4093652051205077A59180610B5779974F9E00F1F5E23230603000000470720211223D18600D18600D18600D18600D18600D28600D28600D28600D28600D28600D28600D1860000

nIe wiem co z tym zrobić…

co ciekawe mam też izar - widzi telegramy od bmeters i izar na sucho, a po dodaniu sensorów do skryptu ich wartości są puste

  1. z bmeters “0C46…” nic nie zrobisz (chyba że sam wymyślisz co tam w środku jest
  2. ten długi “4944…” podobnie – jak nie dopasujesz wskazań do telegramu to tylko forum/ticket na wmbusmeters pozostaje zgłosić – może ktoś już coś takiego miał …

Więcej informacji bo nic nie rozumiem.

  • podawaj wersję komponentu, którą aktualnie masz
  • dodawaj logi (odpowiednio je zaznaczając)
  • nie pisz dwóch postów jeden pod drugim (istnieje przycisk edit)

Mi to obojętne, najwyżej nie odpiszę. To Wam powinno zależeć żeby komplet danych dostarczać przy pytaniu.

Ten krótki telegram wygląda na jakąś ramkę z błędem/informacyjną:

Chcesz więcej informacji to musisz poczytać dokumentację do wMBus.

Tak czy inaczej nie ma tam danych wodomierza.

1 polubienie

@_Szczepan no to da się odczytać bmeters czy nie?

bo taki telegram też był:
https://wmbusmeters.org/analyze/4944B4093652051205077A59180610B5779974F9E00F1F5E23230603000000470720211223D18600D18600D18600D18600D18600D28600D28600D28600D28600D28600D28600D1860000

Nie wiem, czy mam lipną nakładkę, błąd w yaml, czy po prostu deklaracja, że bmeters działa jest na wyrost…

A dlaczego nie działa izar?

Skad wziąłeś ID Izara?