Open kzajac83 opened 11 hours ago
Hello, the same for apator08.
Everytime a frame from apator08 is received my ESP device crashes.
[21:31:36][V][Telegram.cpp:1131]: (wmbus) parseDLL @0103
[21:31:36][V][Telegram.cpp:1178]: (wmbus) parseELL @10 93
[21:31:36][V][Telegram.cpp:1333]: (wmbus) parseNWL @10 93
WARNING wmbus-reader @ 10.0.0.135: Connection error occurred: [Errno 104] Connection reset by peer
INFO Processing unexpected disconnect from ESPHome API for wmbus-reader @ 10.0.0.135
WARNING Disconnected from API
INFO Successfully connected to wmbus-reader @ 10.0.0.135 in 0.116s
INFO Successful handshake with wmbus-reader @ 10.0.0.135 in 0.091s
[21:32:14][D][api:102]: Accepted 10.0.0.200
[21:32:14][V][api.connection:1427]: Hello from client: 'Home Assistant 2024.9.2' | 10.0.0.200 | API Version 1.10
Full log attached: logs_wmbus-reader_run.txt
I can see and decode the fame from the log:
{
"media":"water",
"meter":"apator08",
"name":"",
"id":"000b9ce7",
"total_m3":61.097,
"timestamp":"2024-09-23T19:12:48Z"
}
Other device unismart is working well:
I removed configuration for apator08 and compiled, with no luck. Then, I removed configuration for unismart, it didn't help. At this stage only configuration of wmbus left, no sensors configured, still crashes. Finally, I commented out configuration for wmbus and the hang-ups have stopped.
I reverted to version 3 where everything is OK.
Well, seems you have right. Stay only hydroclima3
driver in my cause:
[22:21:33][C][wmbus:331]: Available drivers: hydrocalm3
and again the same
22:24:02][D][api.connection:1445]: Home Assistant 2024.9.2 (192.168.15.20): Connected successfully
[22:24:02][D][time:051]: Synchronized time: 2024-09-23 22:24:02
[22:24:05][D][mbus:035]: Received T1 A frame
WARNING wmbus-reader-v2 @ 192.168.13.108: Connection error occurred: [Errno 104] Connection reset by peer
INFO Processing unexpected disconnect from ESPHome API for wmbus-reader-v2 @ 192.168.13.108
WARNING Disconnected from API
WARNING Can't connect to ESPHome API for wmbus-reader-v2 @ 192.168.13.108: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.13.108', port=6053))]: [Errno 111] Connect call failed ('192.168.13.108', 6053) (SocketAPIError)
INFO Trying to connect to wmbus-reader-v2 @ 192.168.13.108 in the background
So problem is bigger in V4.0
Please try
external_components:
- source: github://SzczepanLeon/esphome-components@ana1
components: [ wmbus ]
refresh: 0d
INFO ESPHome 2024.9.1
INFO Reading configuration /config/esphome/wmbus-reader.yaml...
INFO Updating https://github.com/SzczepanLeon/esphome-components.git@ana1
...
....
....
[D][mbus:035]: Received T1 A frame
[V][mbus:046]: Frame: 6B271C58D59A3A5396B0E59659959366CD0B4E665A596696B19956B1998B94B38DD1A713C934CD66C94ECA36533724D3C5A98E3B1C9A69334E71A3A9D344ECCA64D398E9A5993B0B70B5A935AC9AC6969AB315AC2D99A659C5ACA56C4D38D6A673138BA71C4DA7438BA6C2E658D353D31A74A69C93A5CC665B23B4C59732C9638D2E394D6634CB8D9D1C69AD19693C59CA64F42E66A335C4EC723A72C4ED2558E2D9C533ACC4D65CA655B24CD59996336C369D0B4CD369C4DCA63964D370B5 (191) [RAW]
[V][mbus:053]: Frame: 6E44010629208200050758C37A560060859085A39321C647E7715892EB571E77D6A22DE66712462FCC78EA77A2A9A783430F16E6DF668D0835AA0408F0D1216A4D23FDD1FC23F83A0117CDFCFFE7F4DA0E2CD54EE0213B915B73B5C466C567D5EA7C3A6B14784BFED2C90235D728D154F90E71059B181FC3711FD1EA207743 (127) [with CRC]
[V][mbus:096]: Validating CRC for Block1
[V][crc:031]: calculated: 0x58C3, read: 0x58C3
[V][mbus:116]: Validating CRC for Block2
[V][crc:031]: calculated: 0xEB57, read: 0xEB57
[V][mbus:116]: Validating CRC for Block3
[V][crc:031]: calculated: 0xA783, read: 0xA783
[V][mbus:116]: Validating CRC for Block4
[V][crc:031]: calculated: 0x4D23, read: 0x4D23
[V][mbus:116]: Validating CRC for Block5
[V][crc:031]: calculated: 0xD54E, read: 0xD54E
[V][mbus:116]: Validating CRC for Block6
[V][crc:031]: calculated: 0x1478, read: 0x1478
[V][mbus:116]: Validating CRC for Block7
[V][crc:031]: calculated: 0x1FC3, read: 0x1FC3
[V][mbus:116]: Validating CRC for Block8
[V][crc:031]: calculated: 0x7743, read: 0x7743
[V][mbus:063]: Frame: 6E4401062920820005077A560060859085A39321C647E77158921E77D6A22DE66712462FCC78EA77A2A9430F16E6DF668D0835AA0408F0D1216AFDD1FC23F83A0117CDFCFFE7F4DA0E2CE0213B915B73B5C466C567D5EA7C3A6B4BFED2C90235D728D154F90E71059B18711FD1EA20 (111) [without CRC]
[V][Telegram.cpp:1131]: (wmbus) parseDLL @0 111
[V][Telegram.cpp:1178]: (wmbus) parseELL @10 101
[V][Telegram.cpp:1333]: (wmbus) parseNWL @10 101
[V][Telegram.cpp:1391]: (wmbus) parseAFL @10 101
[V][Telegram.cpp:2078]: (wmbus) parseTPL @10 101
[V][wmbus:063]: 01 - header przeparsowany
[V][wmbus:066]: 02 - driver wybrany
And disconnect:
After some time appear
WARNING wmbus-reader-v2 @ 192.168.13.108: Connection error occurred: [Errno 104] Connection reset by peer
INFO Processing unexpected disconnect from ESPHome API for wmbus-reader-v2 @ 192.168.13.108
WARNING Disconnected from API
INFO Successfully connected to wmbus-reader-v2 @ 192.168.13.108 in 0.014s
INFO Successful handshake with wmbus-reader-v2 @ 192.168.13.108 in 0.096s
the same for apator08.
@czesiu20 but on what HW? Please share full YAML.
HW is nodemcu esp32 and cc1101 from Mariusz Woszczynski.
My YAML:
substitutions:
name: "wmbus-reader"
friendly_name: "wmbus-reader"
esphome:
name: "${name}"
friendly_name: "${friendly_name}"
project:
name: esphome.wmbus_reader
version: "1.0"
# only for RPI
compile_process_limit: 1
esp32:
board: esp32dev
framework:
type: arduino
external_components:
- source: github://SzczepanLeon/esphome-components@main
components: [ wmbus ]
refresh: 0d
time:
- platform: sntp
id: time_sntp
# Enable logging
logger:
level: VERBOSE
# Enable Home Assistant API
api:
encryption:
key: !secret api_key
ota:
platform: esphome
password: !secret ota_password
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
power_save_mode: none
fast_connect: true
reboot_timeout: 10min
manual_ip:
static_ip: 10.0.0.135
gateway: 10.0.0.1
subnet: 255.255.255.0
web_server:
port: 80
wmbus:
mosi_pin: GPIO32
clk_pin: GPIO33
miso_pin: GPIO19
gdo2_pin: GPIO21
gdo0_pin: GPIO22
cs_pin: GPIO23
led_pin: GPIO2
led_blink_time: "1s"
sensor:
- platform: wmbus
meter_id: 0x000ABFA4
type: apator08
sensors:
- field: "rssi"
name: "Woda - Licznik główny - RSSI"
accuracy_decimals: 0
unit_of_measurement: "dBm"
device_class: "signal_strength"
state_class: "measurement"
entity_category: "diagnostic"
- field: "total"
id: "woda_licznik_glowny"
name: "Woda - Licznik główny"
icon: "mdi:water"
accuracy_decimals: 3
unit_of_measurement: "m3"
device_class: "water"
state_class: "total_increasing"
filters:
- offset: 83.078
- platform: wmbus
meter_id: 0x000B9CE7
type: apator08
sensors:
- field: "rssi"
name: "Woda - Licznik ogrodowy - RSSI"
accuracy_decimals: 0
unit_of_measurement: "dBm"
device_class: "signal_strength"
state_class: "measurement"
entity_category: "diagnostic"
- field: "total"
id: "woda_licznik_ogrodowy"
name: "Woda - Licznik ogrodowy"
icon: "mdi:water"
accuracy_decimals: 3
unit_of_measurement: "m3"
device_class: "water"
state_class: "total_increasing"
filters:
- offset: 60.457
- platform: wmbus
meter_id: 0x00058794
type: unismart
key: "00000000000000000000000000000000"
sensors:
- field: "rssi"
name: "Licznik gazu - RSSI"
accuracy_decimals: 0
unit_of_measurement: "dBm"
device_class: "signal_strength"
state_class: "measurement"
entity_category: "diagnostic"
- field: "total"
id: "licznik_gazu"
name: "Licznik gazu"
icon: "mdi:gas-burner"
accuracy_decimals: 3
unit_of_measurement: "m3"
device_class: "gas"
state_class: "total_increasing"
filters:
- offset: 4337.090
Seems that crash is somewhere below:
bool supported_link_mode{false};
if (drv_info.linkModes().empty()) {
supported_link_mode = true;
... ... ...
Hello
New driver Apator NA-1 cause disconnect after processing msg.
In logs telegram from Apator NA-1 however disconnect occur after every telegram with correct CRC and build in
apatorna1
driver.YAML