Closed garageboxnv closed 1 year ago
Thanks for reporting. CRC-errors should be caused by hardware issues, e.g. interference of your serial cable. It's very prone to errors. The CRC is a checksum for the P1-telegram and if a single byte differs, the telegram is unreliable and must be discarded.
Sometimes these errors are obvious to tell, like this user: https://github.com/dsmrreader/dsmr-reader/issues/1733#issuecomment-1297718318
In your sample the second line below is obviously wrong, as it starts with kW):
. Also the third line seems a bit off in the end: (23030.7.0(00.000*kW)
, missing a )
and probably more.
...
0-0:96.14.0(0001)
kW):1.4.0(01.875*kW)
0-0:98.1.0(3)(1-0:1.6.0)(1-0:1.6.0)(230101000000W)(221220170000W)(03.711*kW)(230201000000W)(230114133000W)(03.606*kW)(23030.7.0(00.000*kW)
...
So you should check if your cable has any interference, e.g. power cable crossing (near) it.
Thx, I was looking further into the configuration details, as nothing was changed near the cable. I use esphome with a serial interface toward dsmr-reader and I update this regurarly
After investigation the error dissapeared, now all is running fine again :) I suspressed all logging and changed the serial buffer to 1500 bytes
Thx
`api: logger: level: NONE hardware_uart: UART1 baud_rate: 0 ota:
external_components:
uart:
stream_server: uart_id: p1_bus port: 8088`
Description
I noticed that the updates of my values suddenly was change to once or twice every 10 minutes, while before it was almost every second. I wonder if it relates with me requesting that fluvius records the 15 minute values on their online portal, this change I enabled not so long ago.
Log output, attached below
DSMR-reader version
5.10.3
DSMR-reader platform
Native (e.g. manual installation)
Debug info dump