Komponent wM-Bus do ESPHome (SzczepanLeon) - liczniki gazu

Urządzenia Urządzenia inteligentnego domu
,
1

mod-edit: Ten wątek jest dedykowany dla liczników gazu.

Tematy ogólne proszę poruszać w źródłowym wątku…
Na pozostałe rodzaje liczników zostały też wydzielone osobne wątki podlinkowane w powyższym.

Niestety jeśli w danym poście jest poruszanych kilka osobnych tematów nie sposób tego potem podzielić moderacyjne na osobne wątki - stąd musiała tu pozostać wstawka o wodomierzach…

Przesiadłem się na cały komponent, skoro czyta Apatora i Izara, to jest to o co mi chodziło:)
Widzę, że się biblioteka rozbudowuje. Dostępne już dodatkowo apator08, evo868 i unismart ?

2

W teorii tak. Chyba nikt jeszcze nie testował tego z fizycznym wodo/gazo-mierzem. Jedynie puściłem parę testów na telegramach znalezionych w internecie.

1 polubienie
3

Jak pisałem wcześniej mam Apatory-08 więc obiecuję test (nie wiem jeszcze kiedy), madaleny nie mam, unismarta też nie (chyba nie jest zbyt popularny, ostatnio miałem wymianę gazomierza, ale przy śladowym zużyciu - mam tylko kuchenkę gazową - PSG nie instaluje zdalnego odczytu).

4

I Tak i Nie… do kuchenki gazowej nieopłacalna zabawa tym bardziej że PSG w telemetrii poszło w innym kierunku niż wodociągi. Nie widziałem w PSG żadnego UNISMARTA zamontowanego na gazomierzu.

1 polubienie
5

Działa :smiley: AT-WMBUS-08 , AT-WMBUS-G-01

[23:04:34][I][wmbus:049]: Using driver 'apator08' for ID [0x00033CAB] T: 10441486AB3C03000303A030250000304A (17)
[23:04:34][D][sensor:126]: 'Licznik wody': Sending state 3.17333 m³ with 3 decimals of accuracy
[23:06:30][I][wmbus:049]: Using driver 'unismart' for ID [0x00021290] T: 5E44B8059012020001037AA10050A52E36D467DECB62D6CE322793D121EBB3A1F708367E43AC8389C03E000018F7C5D31FBF78247690B8DA2823ACFA0838F9233F349D984D253E86B2DB83B69BA3E5C219FA653A1B64AACBA2E9738F000453 (95)
[23:06:30][D][sensor:126]: 'Licznik gazu': Sending state 813.27002 m³ with 3 decimals of accuracy
[23:08:45][I][ota:113]: Boot seems successful, resetting boot loop counter.
[23:08:50][I][wmbus:049]: Using driver 'apator162' for ID [0x00111252] T: 6E4401065212110005077A9C006085C91F2C8AB33F7ED93281A9547FF2671DF0D4C2C0C4780EB04C2DB52549E7454A2DAB9CC4746FB6A85477DD1807D8FF5B5C9260775C1A0BCB79413F84D605B8CBCFC7694558214181C5FB9CD5FC3EA92951AD29050E967D5098FD15AADB8447C3 (111)
[23:08:50][D][sensor:126]: 'Licznik wody 162': Sending state 171.83800 m³ with 3 decimals of accuracy
1 polubienie
6

Z pomocą @Mariusz_Woszczyński zacząłem zaczytywać liczniki izar i unismart.
Mam prośbę do @_Szczepan. Liczniki unismart są do gazu, a Device Class i Icon mają jako woda.

[13:13:51][C][wmbus_sensor:015]: wM-Bus Sensor 'Licznik wody główny ESP'
[13:13:51][C][wmbus_sensor:015]:   Device Class: 'water'
[13:13:51][C][wmbus_sensor:015]:   State Class: 'total_increasing'
[13:13:51][C][wmbus_sensor:015]:   Unit of Measurement: 'm³'
[13:13:51][C][wmbus_sensor:015]:   Accuracy Decimals: 3
[13:13:51][C][wmbus_sensor:015]:   Icon: 'mdi:water'
[13:13:51][C][wmbus_sensor:016]:   Type: izar
[13:13:51][C][wmbus_sensor:017]:   ID: 552054541 [0x20E7AF0D]
[13:13:51][C][wmbus_sensor:015]: wM-Bus Sensor 'Licznik gazu góra ESP'
[13:13:51][C][wmbus_sensor:015]:   Device Class: 'water'
[13:13:51][C][wmbus_sensor:015]:   State Class: 'total_increasing'
[13:13:51][C][wmbus_sensor:015]:   Unit of Measurement: 'm³'
[13:13:51][C][wmbus_sensor:015]:   Accuracy Decimals: 3
[13:13:51][C][wmbus_sensor:015]:   Icon: 'mdi:water'
[13:13:51][C][wmbus_sensor:016]:   Type: unismart
[13:13:51][C][wmbus_sensor:017]:   ID: 274580 [0x00043094]
[13:13:51][C][wmbus_sensor:015]: wM-Bus Sensor 'Licznik gazu dół ESP'
[13:13:51][C][wmbus_sensor:015]:   Device Class: 'water'
[13:13:51][C][wmbus_sensor:015]:   State Class: 'total_increasing'
[13:13:51][C][wmbus_sensor:015]:   Unit of Measurement: 'm³'
[13:13:51][C][wmbus_sensor:015]:   Accuracy Decimals: 3
[13:13:51][C][wmbus_sensor:015]:   Icon: 'mdi:water'
[13:13:51][C][wmbus_sensor:016]:   Type: unismart
[13:13:51][C][wmbus_sensor:017]:   ID: 268425 [0x00041889]
7

Nadpisz w konfiguracji ESPHome ich ikonke i co tam potrzebujesz – tak chyba będzie najłatwiej.

1 polubienie
8

A z ciekawości z czego zliczasz ilość gazu ? Z kotła czy licznika ? I jak zliczasz za pomocą czego ?

9

Sczytuje bezpośrednio z nakładki do licznika (fotka poniżej) no i za pomocą ESP’ka + CC1101 i repozytorium @_Szczepan za co wszyscy (a przynajmniej ja na pewno) mu niezmiernie dziękujemy. Choć zalążek zaczął się u @Mariusz_Woszczyński i gdyby nie oni dalej wnerwiał bym się na DVB-T :stuck_out_tongue:

image
image952×1087 77.3 KB

A może ktoś wie czemu mój licznik gazu wysyła takie krótkie pakiety.

16:49:09	[D]	[text_sensor:067]	
'wmBus Uptime': Sending state '4d 5h 7m 54s'
16:49:11	[I]	[wmbus:043]	
Using driver 'unismart' for ID [0x00021290] T: 0E47B8059012020001038A26000080 (15)
16:49:11	[D]	[wmbus:049]	
Decrypted T : 0E47B8059012020001038A26000080 (15)
16:49:11	[E]	[wmbus:070]	
Can't get value from telegram for ID [0x00021290] 'unismart'
16:49:11	[E]	[wmbus:071]	
T : 0E47B8059012020001038A26000080 (15)
16:49:24	[D]	[sensor:126]	
'wmBus WiFi Signal dB': Sending state -66.00000 dBm with 0 decimals of accuracy
16:49:25	[D]	[sensor:126]	
'wmBus WiFi Signal Percent': Sending state 68.00000 Signal % with 0 decimals of accuracy
10

Zawsze czy też naprzemiennie z ramkami zawierającymi dane możliwe do odkodowania?

11

a gdzie kupiłeś at-wmbus-g-01

1 polubienie
12

Mam dokładnie taki sam licznik. Taki już mi montowali z tą nakładką.

13

Dodając swój licznik wody, znalazłem “w eterze” liczniki gazu, dodałem z ciekawości licznik sąsiadów i ciekawą rzecz znalazłem. Myślę, że należałoby się temu przyjrzeć, bo widzę, że ten licznik nadaje te komunikaty co jakiś czas.
W konfiguracji, sensor jest tako:

  - platform: wmbus
    type: unismart
    meter_id: 0x00002652
    key: "00000000000000000000000000000000"
    add_prefix: false 
    lqi:
      name: "gaz lqi"
    rssi:
      name: "gaz RSSI"
    total_gaz_m3:
      name: "gaz"

Odczyty pięknie spływały, a w logach takie coś - czyli wszystko prawidłowo:

[05:45:56][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -85 dBm LQI: 138 Mode: T1 T: 5E44B8055226000001037AC70050A5BA6A19342BA52A97EEA16708940FB9D8824CEAAF87BD85A294F64CCB47D39922EFD7E405CA675D27E7BFE594346E24D89496EBA71B778F8B489C5B92B853B4DB23BA759F1A8559C047FB03AFF73D2908 (95)
[05:45:56][D][wmbus:090]: Decrypted T : 5E44B8055226000001037AC70050A52F2F0C7844801201046D0026EC2B0C943A63576400446D0026E12B4C943A0836640001FD670002FD74A3050DFD0C06559496EBA71B778F8B489C5B92B853B4DB23BA759F1A8559C047FB03AFF73D2908 (95)
[05:45:56][V][sensor:043]: 'gas lqi': Received new state 138.000000
[05:45:56][D][sensor:094]: 'gas lqi': Sending state 138.00000  with 0 decimals of accuracy
[05:45:56][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[05:45:56][V][json:058]: Size after shrink 68 bytes
[05:45:56][V][sensor:043]: 'gas RSSI': Received new state -85.000000
[05:45:56][D][sensor:094]: 'gas RSSI': Sending state -85.00000 dBm with 0 decimals of accuracy
[05:45:56][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[05:45:56][V][json:058]: Size after shrink 72 bytes
[05:45:56][V][sensor:043]: 'gas': Received new state 6457.629883
[05:45:56][D][sensor:094]: 'gas': Sending state 6457.62988 m³ with 3 decimals of accuracy
[05:45:56][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[05:45:56][V][json:058]: Size after shrink 72 bytes
[05:45:56][W][component:214]: Component wmbus took a long time for an operation (0.13 s).
[05:45:56][W][component:215]: Components should block for at most 20-30ms.

aż licznik, przysłał to:

[05:48:04][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -86 dBm LQI: 142 Mode: T1 T: 0E47B8055226000001038AC7000080 (15)
[05:48:04][E][wmbus:311]: CI unknown
[05:48:18][D][api:102]: Accepted 192.168.0.143
[05:48:18][V][api.connection:1032]: Hello from client: 'Home Assistant 2023.11.2' | 192.168.0.143 | API Version 1.9
[05:48:19][D][api.connection:1050]: Home Assistant 2023.11.2 (192.168.0.143): Connected successfully

Wygląda to tak, że nie wiedział co zrobić z odebraną ramką, co finalnie spowodowało zerwanie połączenia z HA, a wtedy encja w HA zmieniła się na “nieznany”, co się potwierdza na historii w HA.
image
Również dla stanu wodomierza:
image

z racji, że testuje te odczyty to loguje wszystko z esp jako debug do pliku, to sprawdziłem jak to wyglądało w czasie gdy była “dziura” rano:

[05:45:56][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -85 dBm LQI: 138 Mode: T1 T: 5E44B8055226000001037AC70050A5BA6A19342BA52A97EEA16708940FB9D8824CEAAF87BD85A294F64CCB47D39922EFD7E405CA675D27E7BFE594346E24D89496EBA71B778F8B489C5B92B853B4DB23BA759F1A8559C047FB03AFF73D2908 (95)
[05:45:56][D][wmbus:090]: Decrypted T : 5E44B8055226000001037AC70050A52F2F0C7844801201046D0026EC2B0C943A63576400446D0026E12B4C943A0836640001FD670002FD74A3050DFD0C06559496EBA71B778F8B489C5B92B853B4DB23BA759F1A8559C047FB03AFF73D2908 (95)
[05:45:56][V][sensor:043]: 'gas lqi': Received new state 138.000000
[05:45:56][D][sensor:094]: 'gas lqi': Sending state 138.00000  with 0 decimals of accuracy
[05:45:56][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[05:45:56][V][json:058]: Size after shrink 68 bytes
[05:45:56][V][sensor:043]: 'gas RSSI': Received new state -85.000000
[05:45:56][D][sensor:094]: 'gas RSSI': Sending state -85.00000 dBm with 0 decimals of accuracy
[05:45:56][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[05:45:56][V][json:058]: Size after shrink 72 bytes
[05:45:56][V][sensor:043]: 'gas': Received new state 6457.629883
[05:45:56][D][sensor:094]: 'gas': Sending state 6457.62988 m³ with 3 decimals of accuracy
[05:45:56][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[05:45:56][V][json:058]: Size after shrink 72 bytes
[05:45:56][W][component:214]: Component wmbus took a long time for an operation (0.13 s).
[05:45:56][W][component:215]: Components should block for at most 20-30ms.
[05:48:04][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -86 dBm LQI: 142 Mode: T1 T: 0E47B8055226000001038AC7000080 (15)
[05:48:04][E][wmbus:311]: CI unknown
[05:48:18][D][api:102]: Accepted 192.168.0.143
[05:48:18][V][api.connection:1032]: Hello from client: 'Home Assistant 2023.11.2' | 192.168.0.143 | API Version 1.9
[05:48:19][D][api.connection:1050]: Home Assistant 2023.11.2 (192.168.0.143): Connected successfully
[05:53:04][I][ota:117]: Boot seems successful, resetting boot loop counter.
[05:53:04][D][esp32.preferences:114]: Saving 1 preferences to flash...
[05:53:04][V][esp32.preferences:126]: sync: key: 233825507, len: 4
[05:53:04][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[05:54:28][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -87 dBm LQI: 135 Mode: T1 T: 0E47B8055226000001038AC7000080 (15)
[05:54:28][E][wmbus:311]: CI unknown
[05:54:59][D][api:102]: Accepted 192.168.0.143
[05:54:59][V][api.connection:1032]: Hello from client: 'Home Assistant 2023.11.2' | 192.168.0.143 | API Version 1.9
[05:54:59][D][api.connection:1050]: Home Assistant 2023.11.2 (192.168.0.143): Connected successfully
[05:58:44][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -87 dBm LQI: 137 Mode: T1 T: 0E47B8055226000001038AC7000080 (15)
[05:58:44][E][wmbus:311]: CI unknown
[06:01:05][D][wmbus:184]: Meter ID [0x00001139] RSSI: -91 dBm LQI: 146 Mode: T1 not found in configuration T: 5E44B8053911000001037AC600508555D72B3C4E09FA58DA72D43C83393EF24217E390155BD00B578FAA53352B9C7E41247B6287ABF9A40B5416CE99319DD8BF76FD0527BB51A23881DDCFBAF1B69D9A4FCE39EBC4A5CEDA57888B4309CFC5 (95)
[06:03:07][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -87 dBm LQI: 151 Mode: T1 T: 0E47B8055226000001038AC8000080 (15)
[06:03:07][E][wmbus:311]: CI unknown
[06:03:39][D][api:102]: Accepted 192.168.0.143
[06:03:39][V][api.connection:1032]: Hello from client: 'Home Assistant 2023.11.2' | 192.168.0.143 | API Version 1.9
[06:03:39][D][api.connection:1050]: Home Assistant 2023.11.2 (192.168.0.143): Connected successfully
[06:08:08][I][ota:117]: Boot seems successful, resetting boot loop counter.
[06:08:08][D][esp32.preferences:114]: Saving 1 preferences to flash...
[06:08:08][V][esp32.preferences:126]: sync: key: 233825507, len: 4
[06:08:08][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[06:08:11][D][wmbus:184]: Meter ID [0x00044213] RSSI: -89 dBm LQI: 146 Mode: T1 not found in configuration T: 0E47B8051342040001038A97000080 (15)
[06:15:05][D][sntp:078]: Synchronized time: 2023-11-12 06:15:05
[06:20:19][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -85 dBm LQI: 142 Mode: T1 T: 0E47B8055226000001038AC9000080 (15)
[06:20:19][E][wmbus:311]: CI unknown
[06:22:53][D][wmbus:184]: Meter ID [0x00044213] RSSI: -88 dBm LQI: 147 Mode: T1 not found in configuration T: 0E47B8051342040001038A98000080 (15)
[06:24:35][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -86 dBm LQI: 143 Mode: T1 T: 0E47B8055226000001038AC9000080 (15)
[06:24:35][E][wmbus:311]: CI unknown
[06:25:08][D][api:102]: Accepted 192.168.0.143
[06:25:08][V][api.connection:1032]: Hello from client: 'Home Assistant 2023.11.2' | 192.168.0.143 | API Version 1.9
[06:25:08][D][api.connection:1050]: Home Assistant 2023.11.2 (192.168.0.143): Connected successfully
[06:25:36][I][wmbus:084]: Using driver 'apator162' for ID [0x06335627] RSSI: -54 dBm LQI: 128 Mode: T1 T: 3E4401062756330605077A830030850097D4E33C22673F51C63A3106993BA428C18BD61577BC420DCF87BE1BC69A8AE86669E25401200D8217E55B3A17B0BD (63)
[06:25:36][D][wmbus:090]: Decrypted T : 3E4401062756330605077A830030852F2F0F992CEB97180200432500830018FAA988EB01F0150210B405000071013100000000000000A0C7FFB704FFFFF0D1 (63)
[06:25:36][V][sensor:043]: 'lqi': Received new state 128.000000
[06:25:36][D][sensor:094]: 'lqi': Sending state 128.00000  with 0 decimals of accuracy
[06:25:36][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[06:25:36][V][json:058]: Size after shrink 64 bytes
[06:25:36][V][sensor:043]: 'RSSI': Received new state -54.000000
[06:25:36][D][sensor:094]: 'RSSI': Sending state -54.00000 dBm with 0 decimals of accuracy
[06:25:36][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[06:25:36][V][json:058]: Size after shrink 68 bytes
[06:25:36][V][sensor:043]: 'water': Received new state 1.460000
[06:25:36][D][sensor:094]: 'water': Sending state 1.46000 m³ with 3 decimals of accuracy
[06:25:36][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[06:25:36][V][json:058]: Size after shrink 72 bytes
[06:25:36][W][component:214]: Component wmbus took a long time for an operation (0.14 s).
[06:25:36][W][component:215]: Components should block for at most 20-30ms.
[06:29:35][I][ota:117]: Boot seems successful, resetting boot loop counter.
[06:29:35][D][esp32.preferences:114]: Saving 1 preferences to flash...
[06:29:35][V][esp32.preferences:126]: sync: key: 233825507, len: 4
[06:29:35][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[06:36:55][D][sntp:078]: Synchronized time: 2023-11-12 06:36:55
[06:51:55][D][sntp:078]: Synchronized time: 2023-11-12 06:51:55
[06:58:52][D][wmbus:184]: Meter ID [0x00044213] RSSI: -88 dBm LQI: 134 Mode: T1 not found in configuration T: 5E44B8051342040001037A9A00508535FE944A18237C98F448C31444389424ACC42C3C11E5CF40E2E2FCE2092C308CF70B48E249E8AD08253ED4105989E3FB52BCE9D6E7043E39851CDD7498FAE131188A936F54B3342D374CB2308E4BEF8B (95)
[07:06:55][D][sntp:078]: Synchronized time: 2023-11-12 07:06:55
[07:08:25][I][wmbus:084]: Using driver 'apator162' for ID [0x06335627] RSSI: -55 dBm LQI: 128 Mode: T1 T: 3E4401062756330605077A85003085368AE174818A78DF1B17EE06CE72525FE27838B13A5AFF2CD572BC1124BE710C164EEDFBD6B5632D9211D5A6133C96BC (63)
[07:08:25][D][wmbus:090]: Decrypted T : 3E4401062756330605077A850030852F2F0FC82CEB97180200432500830018FAA988EB01F0150210B805000071013100000000000000A0C7FFB704FFFF862E (63)
[07:08:25][V][sensor:043]: 'lqi': Received new state 128.000000
[07:08:25][D][sensor:094]: 'lqi': Sending state 128.00000  with 0 decimals of accuracy
[07:08:25][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[07:08:25][V][json:058]: Size after shrink 64 bytes
[07:08:25][V][sensor:043]: 'RSSI': Received new state -55.000000
[07:08:25][D][sensor:094]: 'RSSI': Sending state -55.00000 dBm with 0 decimals of accuracy
[07:08:25][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[07:08:25][V][json:058]: Size after shrink 68 bytes
[07:08:25][V][sensor:043]: 'water': Received new state 1.464000
[07:08:25][D][sensor:094]: 'water': Sending state 1.46400 m³ with 3 decimals of accuracy
[07:08:25][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[07:08:25][V][json:058]: Size after shrink 72 bytes
[07:08:25][W][component:214]: Component wmbus took a long time for an operation (0.15 s).
[07:08:25][W][component:215]: Components should block for at most 20-30ms.
[07:16:23][D][wmbus:184]: Meter ID [0x00001139] RSSI: -89 dBm LQI: 134 Mode: T1 not found in configuration T: 5E44B8053911000001037ACB00508551889A4EF43AD3CD352534B1C15DE74BD439F4BD10BDF293ECFDDBC193E10B164AA567429CFB9CE8B85247337B7296FD4F8CBE71B4AE541CEBA2C8D2EC98FCBC96C4D9884E3C8F4F604A9ABE6E1C8CA5 (95)
[07:20:21][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -86 dBm LQI: 146 Mode: T1 T: 5E44B8055226000001037ACD0050859259EFE0C8D6493703B9E591BE4B9453C39DB5BD22EEC7121EE94239990C2F56726A84325AA8E21D48D69A106B550359D81815BFD5FE255634F9705C46AB43AEDE875D1952F0D321AD16ABC3A782C2C1 (95)
[07:20:21][D][wmbus:090]: Decrypted T : 5E44B8055226000001037ACD0050852F2F0C7844801201046D2227EC2B0C943A63576400446D0026E12B4C943A0836640001FD670002FD74A3050DFD0C0655D81815BFD5FE255634F9705C46AB43AEDE875D1952F0D321AD16ABC3A782C2C1 (95)
[07:20:21][V][sensor:043]: 'gas lqi': Received new state 146.000000
[07:20:21][D][sensor:094]: 'gas lqi': Sending state 146.00000  with 0 decimals of accuracy
[07:20:21][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[07:20:21][V][json:058]: Size after shrink 68 bytes
[07:20:21][V][sensor:043]: 'gas RSSI': Received new state -86.000000
[07:20:21][D][sensor:094]: 'gas RSSI': Sending state -86.00000 dBm with 0 decimals of accuracy
[07:20:21][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[07:20:21][V][json:058]: Size after shrink 72 bytes
[07:20:21][V][sensor:043]: 'gas': Received new state 6457.629883
[07:20:21][D][sensor:094]: 'gas': Sending state 6457.62988 m³ with 3 decimals of accuracy
[07:20:21][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[07:20:21][V][json:058]: Size after shrink 72 bytes
[07:20:21][W][component:214]: Component wmbus took a long time for an operation (0.14 s).
[07:20:21][W][component:215]: Components should block for at most 20-30ms.
[07:21:21][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -86 dBm LQI: 137 Mode: T1 T: 5E44B8055226000001037ACD005085C615666A3420BE00D0DE6F50B6D1CFFEE3C4C25CCFD0EC4FFACC7D25CF2183C98951AF895ACAC893B618A8154B131C97278A5E4B1A5249E48969F41C3A72E50D00DCCAD5B5B308A2D6F34A99E731861F (95)
[07:21:21][D][wmbus:090]: Decrypted T : 5E44B8055226000001037ACD0050852F2F0C7844801201046D2327EC2B0C943A63576400446D0026E12B4C943A0836640001FD670002FD74A3050DFD0C0655278A5E4B1A5249E48969F41C3A72E50D00DCCAD5B5B308A2D6F34A99E731861F (95)
[07:21:21][V][sensor:043]: 'gas lqi': Received new state 137.000000
[07:21:21][D][sensor:094]: 'gas lqi': Sending state 137.00000  with 0 decimals of accuracy
[07:21:21][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[07:21:21][V][json:058]: Size after shrink 68 bytes
[07:21:21][V][sensor:043]: 'gas RSSI': Received new state -86.000000
[07:21:21][D][sensor:094]: 'gas RSSI': Sending state -86.00000 dBm with 0 decimals of accuracy
[07:21:21][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[07:21:21][V][json:058]: Size after shrink 72 bytes
[07:21:21][V][sensor:043]: 'gas': Received new state 6457.629883
[07:21:21][D][sensor:094]: 'gas': Sending state 6457.62988 m³ with 3 decimals of accuracy
[07:21:21][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[07:21:21][V][json:058]: Size after shrink 72 bytes
[07:21:21][W][component:214]: Component wmbus took a long time for an operation (0.15 s).
[07:21:21][W][component:215]: Components should block for at most 20-30ms.
[07:21:55][D][sntp:078]: Synchronized time: 2023-11-12 07:21:55

To według mnie wygląda to tak, że jak dostaje wiadomość, której nie może zdekodować się wysypuje - na szczęście tylko dla dodanego sensora - pozostałe liczniki z eteru pomija (prawidłowo).
Cały log z esp za 24h - jako zip bo forum nie pozwala dodać jako log.
wodomierz_esp.zip (20,9 KB)

Edit:
Dzisiaj taka sama sytuacja licznik gdy wyśle tą ramkę:

[16:32:00][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -80 dBm LQI: 138 Mode: T1 T: 0E47B8055226000001038A50000080 (15)
Wygląda to tak jakby zerwane zostawało połączenie do HA - wartość zapisana do bazy jest pewnie niepoprawna i wysypuje się.
Zmienne z tego esp przyjmują stan nieznany (tak samo jak po starcie), a że ten licznik nadaje stosunkowo rzadko gdy nie zmienia mu się wskazanie to można zobaczyć dziurę w danych.

[16:32:00][I][wmbus:084]: Using driver ‘unismart’ for ID [0x00002652] RSSI: -80 dBm LQI: 138 Mode: T1 T: 0E47B8055226000001038A50000080 (15)
[16:32:00][E][wmbus:311]: CI unknown
[16:32:34][D][api:102]: Accepted 192.168.0.143
[16:32:34][V][api.connection:1032]: Hello from client: ‘Home Assistant 2023.11.2’ | 192.168.0.143 | API Version 1.9
[16:32:34][D][api.connection:1050]: Home Assistant 2023.11.2 (192.168.0.143): Connected successfully
[16:33:02][I][wmbus:084]: Using driver ‘apator162’ for ID [0x06335627] RSSI: -50 dBm LQI: 128 Mode: T1 T: 3E4401062756330605077ABA0030852F59861716F3855C450FF89EB715F0DF95248BF5A00BE6F2A740930305BC3FDBADD03FFFD79424F117E2199588047D45 (63)
[16:33:02][D][wmbus:090]: Decrypted T : 3E4401062756330605077ABA0030852F2F0F208D2B97180200432600841569EB626CEB042A0000106008000071013100000000000000A0C7FFB704FFFF56CE (63)
[16:33:02][V][sensor:043]: ‘lqi’: Received new state 128.000000
[16:33:02][D][sensor:094]: ‘lqi’: Sending state 128.00000 with 0 decimals of accuracy
[16:33:02][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[16:33:02][V][json:058]: Size after shrink 64 bytes
[16:33:02][V][sensor:043]: ‘RSSI’: Received new state -50.000000
[16:33:02][D][sensor:094]: ‘RSSI’: Sending state -50.00000 dBm with 0 decimals of accuracy
[16:33:02][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[16:33:02][V][json:058]: Size after shrink 68 bytes
[16:33:02][V][sensor:043]: ‘water’: Received new state 2.144000
[16:33:02][D][sensor:094]: ‘water’: Sending state 2.14400 m³ with 3 decimals of accuracy
[16:33:02][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[16:33:02][V][json:058]: Size after shrink 72 bytes
[16:33:02][W][component:214]: Component wmbus took a long time for an operation (0.14 s).
[16:33:02][W][component:215]: Components should block for at most 20-30ms.

14

Dariusz zerknij do tego posta:

15

Zainstaluj nowszą wersję, 2.2.32 i daj znać czy się poprawiło.

17

Teraz gorzej niż było bo popsuło wodę.

[16:57:28][I][wmbus:084]: Using driver 'apator162' for ID [0x06335627] RSSI: -50 dBm LQI: 128 Mode: T1 T: 3E4401062756330605077AEB003085C855025764E7A525B69FB27F7DE4ADBD35D3E72343E2E67AD7EF83C9E6E605755EE7C960756C096F8945D810C7710BE0 (63)
[16:57:28][E][wmbus:105]: Something was not OK during decrypting telegram for ID [0x06335627] 'apator162' key: '00000000000000000000000000000000'
[16:57:28][E][wmbus:106]: T : 3E4401062756330605077AEB003085C855025764E7A525B69FB27F7DE4ADBD35D3E72343E2E67AD7EF83C9E6E605755EE7C960756C096F8945D810C7710BE0 (63)
[16:57:28][E][wmbus:107]: T': 3E4401062756330605077AEB003085C855025764E7A525B69FB27F7DE4ADBD35D3E72343E2E67AD7EF83C9E6E605755EE7C960756C096F8945D810C7710BE0 (63)
[16:57:28][W][component:214]: Component wmbus took a long time for an operation (0.07 s).
[16:57:28][W][component:215]: Components should block for at most 20-30ms.
[16:58:01][I][wmbus:084]: Using driver 'apator162' for ID [0x06335627] RSSI: -50 dBm LQI: 128 Mode: T1 T: 3E4401062756330605077AEC003085D62F5B259C28AEC66153DD2570DFACE103C358523955A3819DA7D133A4157548240005CC3F31AE29187E29554B1CA620 (63)
[16:58:01][E][wmbus:105]: Something was not OK during decrypting telegram for ID [0x06335627] 'apator162' key: '00000000000000000000000000000000'
[16:58:01][E][wmbus:106]: T : 3E4401062756330605077AEC003085D62F5B259C28AEC66153DD2570DFACE103C358523955A3819DA7D133A4157548240005CC3F31AE29187E29554B1CA620 (63)
[16:58:01][E][wmbus:107]: T': 3E4401062756330605077AEC003085D62F5B259C28AEC66153DD2570DFACE103C358523955A3819DA7D133A4157548240005CC3F31AE29187E29554B1CA620 (63)
[16:58:01][W][component:214]: Component wmbus took a long time for an operation (0.07 s).
[16:58:01][W][component:215]: Components should block for at most 20-30ms.
[16:58:23][I][wmbus:084]: Using driver 'apator162' for ID [0x06335627] RSSI: -50 dBm LQI: 128 Mode: T1 T: 3E4401062756330605077AED0030851C92C918D601D08DF450C72A6A1D80C756C36972E6C81D621E83AF290D0C836C1AA1E73A0B1FF8E89348D15BE91E8C50 (63)
[16:58:23][E][wmbus:105]: Something was not OK during decrypting telegram for ID [0x06335627] 'apator162' key: '00000000000000000000000000000000'
[16:58:23][E][wmbus:106]: T : 3E4401062756330605077AED0030851C92C918D601D08DF450C72A6A1D80C756C36972E6C81D621E83AF290D0C836C1AA1E73A0B1FF8E89348D15BE91E8C50 (63)
[16:58:23][E][wmbus:107]: T': 3E4401062756330605077AED0030851C92C918D601D08DF450C72A6A1D80C756C36972E6C81D621E83AF290D0C836C1AA1E73A0B1FF8E89348D15BE91E8C50 (63)
[16:58:23][W][component:214]: Component wmbus took a long time for an operation (0.07 s).
[16:58:23][W][component:215]: Components should block for at most 20-30ms.
[16:59:19][I][wmbus:084]: Using driver 'apator162' for ID [0x06335627] RSSI: -51 dBm LQI: 128 Mode: T1 T: 3E4401062756330605077AEF0030854630EB24FDED7020CC6AB0511CA4EF43BEBB393413D03947758E55F4624AF6E44B9DBC067E1B0E19CFBAC37AC76889AA (63)
[16:59:19][E][wmbus:105]: Something was not OK during decrypting telegram for ID [0x06335627] 'apator162' key: '00000000000000000000000000000000'
[16:59:19][E][wmbus:106]: T : 3E4401062756330605077AEF0030854630EB24FDED7020CC6AB0511CA4EF43BEBB393413D03947758E55F4624AF6E44B9DBC067E1B0E19CFBAC37AC76889AA (63)
[16:59:19][E][wmbus:107]: T': 3E4401062756330605077AEF0030854630EB24FDED7020CC6AB0511CA4EF43BEBB393413D03947758E55F4624AF6E44B9DBC067E1B0E19CFBAC37AC76889AA (63)
[16:59:19][W][component:214]: Component wmbus took a long time for an operation (0.08 s).
[16:59:19][W][component:215]: Components should block for at most 20-30ms.
[17:00:01][I][wmbus:084]: Using driver 'apator162' for ID [0x06335627] RSSI: -50 dBm LQI: 128 Mode: T1 T: 3E4401062756330605077AF0003085D53FF2424C81D0B57BF611FFE1039583E2B0266F6F262E941DFD486DE5C659EC8673F35A3CB7E1CBAF7779ED8501BBA7 (63)
[17:00:01][E][wmbus:105]: Something was not OK during decrypting telegram for ID [0x06335627] 'apator162' key: '00000000000000000000000000000000'
[17:00:01][E][wmbus:106]: T : 3E4401062756330605077AF0003085D53FF2424C81D0B57BF611FFE1039583E2B0266F6F262E941DFD486DE5C659EC8673F35A3CB7E1CBAF7779ED8501BBA7 (63)
[17:00:01][E][wmbus:107]: T': 3E4401062756330605077AF0003085D53FF2424C81D0B57BF611FFE1039583E2B0266F6F262E941DFD486DE5C659EC8673F35A3CB7E1CBAF7779ED8501BBA7 (63)
[17:00:01][W][component:214]: Component wmbus took a long time for an operation (0.07 s).
[17:00:01][W][component:215]: Components should block for at most 20-30ms.
[17:00:24][I][wmbus:084]: Using driver 'apator162' for ID [0x06335627] RSSI: -50 dBm LQI: 128 Mode: T1 T: 3E4401062756330605077AF1003085A86C910F122E0B0882B008E5E661D41485B98989F8AF965CF74765CDA54643B910EE33AECA2CFD148286A75C94940C83 (63)
[17:00:24][E][wmbus:105]: Something was not OK during decrypting telegram for ID [0x06335627] 'apator162' key: '00000000000000000000000000000000'
[17:00:24][E][wmbus:106]: T : 3E4401062756330605077AF1003085A86C910F122E0B0882B008E5E661D41485B98989F8AF965CF74765CDA54643B910EE33AECA2CFD148286A75C94940C83 (63)
[17:00:24][E][wmbus:107]: T': 3E4401062756330605077AF1003085A86C910F122E0B0882B008E5E661D41485B98989F8AF965CF74765CDA54643B910EE33AECA2CFD148286A75C94940C83 (63)
[17:00:24][W][component:214]: Component wmbus took a long time for an operation (0.07 s).
[17:00:24][W][component:215]: Components should block for at most 20-30ms.
[17:00:57][I][wmbus:084]: Using driver 'apator162' for ID [0x06335627] RSSI: -50 dBm LQI: 128 Mode: T1 T: 3E4401062756330605077AF2003085B94693546E50C5ACF8D0BB7DC7F767566391F9A6EC597AFB713CFF7E818100F8B73537786475D839705E8A2EC04149FE (63)
[17:00:57][E][wmbus:105]: Something was not OK during decrypting telegram for ID [0x06335627] 'apator162' key: '00000000000000000000000000000000'
[17:00:57][E][wmbus:106]: T : 3E4401062756330605077AF2003085B94693546E50C5ACF8D0BB7DC7F767566391F9A6EC597AFB713CFF7E818100F8B73537786475D839705E8A2EC04149FE (63)
[17:00:57][E][wmbus:107]: T': 3E4401062756330605077AF2003085B94693546E50C5ACF8D0BB7DC7F767566391F9A6EC597AFB713CFF7E818100F8B73537786475D839705E8A2EC04149FE (63)
[17:00:57][W][component:214]: Component wmbus took a long time for an operation (0.08 s).
[17:00:57][W][component:215]: Components should block for at most 20-30ms.
[17:01:10][I][ota:117]: Boot seems successful, resetting boot loop counter.
[17:01:10][D][esp32.preferences:114]: Saving 1 preferences to flash...
[17:01:10][V][esp32.preferences:126]: sync: key: 233825507, len: 4
[17:01:10][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed

Z gazem taki sam błąd, aktualnie wróciłem do 2.2.31

18

Tak to jest jak się człowiek spieszy. Zaciągnij 2.2.34 – man nadzieję że już będzie OK.

19

Dzięki, na tej wersji działa odczyt z apator162 i unismart - te dziwne ramki przychodzą między 14, a 17, a czasem w nocy lub nad ranem, także dodam aktualizację jutro.

Przyszedł pierwszy telegram, z którym poprzednio sobie nie radził, teraz jest ok, info w logu, że nie może odszyfrować, ale nie rozłączył. Także działa.

[16:14:32][I][wmbus:084]: Using driver 'unismart' for ID [0x00002652] RSSI: -82 dBm LQI: 141 Mode: T1 T: 0E47B8055226000001038AB0000080 (15)
[16:14:32][E][wmbus:311]: CI unknown
[16:14:32][E][wmbus:105]: Something was not OK during decrypting telegram for ID [0x00002652] 'unismart' key: '00000000000000000000000000000000'
[16:14:32][E][wmbus:106]: T : 0E47B8055226000001038AB0000080 (15)
[16:14:32][E][wmbus:107]: T': 0E47B8055226000001038AB0000080 (15)
[16:14:55][I][wmbus:084]: Using driver 'apator162' for ID [0x06335627] RSSI: -50 dBm LQI: 128 Mode: T1 T: 3E4401062756330605077A5900308509CA2AF498858785F7842407829A3A33A4A0746ED535FB104BAA1C45E95063AB08FEF8876A91F0E15F542C3C77199107 (63)
[16:14:55][D][wmbus:090]: Decrypted T : 3E4401062756330605077A590030852F2F0F0E8E4B97180200432700830018FAA988EB01F01502100C09000071013100000000000000A0C7FFB704FFFF6619 (63)
[16:14:55][V][sensor:043]: 'lqi': Received new state 128.000000
[16:14:55][D][sensor:094]: 'lqi': Sending state 128.00000  with 0 decimals of accuracy
[16:14:55][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[16:14:55][V][json:058]: Size after shrink 64 bytes
[16:14:55][V][sensor:043]: 'RSSI': Received new state -50.000000
[16:14:55][D][sensor:094]: 'RSSI': Sending state -50.00000 dBm with 0 decimals of accuracy
[16:14:55][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[16:14:55][V][json:058]: Size after shrink 68 bytes
[16:14:55][V][sensor:043]: 'water': Received new state 2.316000
[16:14:55][D][sensor:094]: 'water': Sending state 2.31600 m³ with 3 decimals of accuracy
[16:14:55][V][json:038]: Attempting to allocate 512 bytes for JSON serialization
[16:14:55][V][json:058]: Size after shrink 72 bytes
[16:14:55][W][component:214]: Component wmbus took a long time for an operation (0.13 s).
[16:14:55][W][component:215]: Components should block for at most 20-30ms.
1 polubienie