amb8465 [ALARM DeviceFailure] too many protocol errors(20)

[LarsBorris]

Hello,

Just wanted to know if this was normal behaviour I have attached the wmbusmeters.log and the latest metering log files. I can see that the last reset was at 07:52, but the last metering entry was at 05:59 Has my dongle stopped working?

TEST-Device_2021-10-01.log wmbusmeters.log

Thanks!

[weetmuts]

Thanks! What version of wmbusmeters are you running? Are you running on a raspberry pi? Does this occur after the reboot of the pi? If you stop the daemon and start it again, does it work then? If you stop the daemon and start wmbusmeters manually does it work then? Can you enable loglevel=debug and capture the problem again?

Thanks!

[LarsBorris]

Hello,

It looks like it is still running. I let it run for a few days and I had data for every day. I am running it on a Rpi. So I do think that the problem was not a problem at all.

However I have noticed this: When running the wmbusmeters with no meters configured, I get a crash. I use this method to see how many meters I can detect, then afterwards I can add the meters and decrypt the telegram.

I start the program using this command (with no meters configured so I can see how far it reaches): sudo wmbusmeters /dev/ttyUSB0:amb8465:c1,t1 Started config amb8465[00000000] on /dev/ttyUSB0 listening on c1,t1 No meters configured. Printing id:s of all telegrams heard!

It will output telegrams and work fine for 10 minutes then show this:

[ALARM DeviceFailure] too many protocol errors(20) resetting /dev/ttyUSB0 amb8465 (wmbus) resetting /dev/ttyUSB0 Warning! Did not get confirmation on set link mode for amb8465 (wmbus) successfully reset wmbus device

It will recover and start outputting telegrams again After 10 minutes or so it will crash:

[ALARM DeviceFailure] too many protocol errors(20) resetting /dev/ttyUSB0 amb8465 (wmbus) resetting /dev/ttyUSB0 wmbusmeters: src/wmbus.cc:3852: bool WMBusCommonImplementation::waitForResponse(int): Assertion `waiting_for_response_id_ == 0 && id != 0' failed. Aborted

The full log is attached. Thanks! wmbusmeters-scan.txt

[Baggerfahrer]

exactly the same issue here, as well in the same situation. i want to scan for all the devices and, after a specific time, the software crashes. I use it with home assistant and the official addon via the supervisor repository https://github.com/weetmuts/wmbusmeters/

---

Received telegram from: 01011361 manufacturer: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x80) ver: 0x69 device: amb8465[00000000] rssi: -55 dBm driver: fhkvdataiii Received telegram from: 01173957 manufacturer: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x80) ver: 0x69 device: amb8465[00000000] rssi: -62 dBm driver: fhkvdataiii Received telegram from: 24262133 manufacturer: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x80) ver: 0x69 device: amb8465[00000000] rssi: -84 dBm driver: fhkvdataiii Received telegram from: 24262096 manufacturer: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x80) ver: 0x69 device: amb8465[00000000] rssi: -82 dBm driver: fhkvdataiii Received telegram from: 24262139 manufacturer: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x80) ver: 0x69 device: amb8465[00000000] rssi: -80 dBm driver: fhkvdataiii Received telegram from: 01011282 manufacturer: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x80) ver: 0x69 device: amb8465[00000000] rssi: -84 dBm driver: fhkvdataiii Received telegram from: 60900641 manufacturer: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x80) ver: 0x69 device: amb8465[00000000] rssi: -63 dBm driver: fhkvdataiii Received telegram from: 01011362 manufacturer: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x80) ver: 0x69 device: amb8465[00000000] rssi: -114 dBm driver: fhkvdataiii Received telegram from: 60900641 manufacturer: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x80) ver: 0x69 device: amb8465[00000000] rssi: -63 dBm driver: fhkvdataiii [ALARM DeviceFailure] too many protocol errors(20) resetting /dev/ttyUSB1 amb8465 (wmbus) resetting /dev/ttyUSB1 Warning! Did not get confirmation on set link mode for amb8465 (wmbus) successfully reset wmbus device (wmbus) Unknown tpl-ci-field 80 Received telegram from: 17834150 manufacturer: (ZCH) Zhejiang Chaorong Electric Technology, China (0x6868) type: Unknown (0x69) ver: 0x01 device: amb8465[00000000] rssi: -66 dBm driver: unknown! (wmbus) Unknown tpl-ci-field 80 Received telegram from: 01136250 manufacturer: (ZCH) Zhejiang Chaorong Electric Technology, China (0x6868) type: Unknown (0x69) ver: 0x01 device: amb8465[00000000] rssi: -73 dBm driver: unknown! (wmbus) Unknown tpl-ci-field 80 Received telegram from: 01128250 manufacturer: (ZCH) Zhejiang Chaorong Electric Technology, China (0x6868) type: Unknown (0x69) ver: 0x01 device: amb8465[00000000] rssi: -73 dBm driver: unknown! [ALARM DeviceFailure] too many protocol errors(20) resetting /dev/ttyUSB1 amb8465 (wmbus) resetting /dev/ttyUSB1 Assertion failed: waiting_for_response_id_ == 0 && id != 0 (src/wmbus.cc: waitForResponse: 3852) /run.sh: line 56: 226 Aborted (core dumped) /wmbusmeters/wmbusmeters --useconfig=$CONFIG_DATA_PATH [cmd] /run.sh exited 134 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal.

[weetmuts]

I am trying to reproduce this myself. It is indeed an odd behaviour.

[BIBOLV]

@weetmuts - were you able to reproduce issue?

[github-actions[bot]]

This issue is stale because it has been open for 2 month with no activity. Remove stale label or comment or this will be closed in 1 month.

[github-actions[bot]]

This issue is stale because it has been open for 2 month with no activity. Remove stale label or comment or this will be closed in 1 month.

[github-actions[bot]]

This issue was closed because it has been stalled for 1 month with no activity.