search

UtilitechAS / amsreader-firmware

ESP8266 and ESP32 compatible firmware to read, interpret and publish data to MQTT from smart electrical meters, both DLMS and DSMR is supported
Other
379 stars 73 forks source link

Less stable HAN parsing lately #816

Closed StarkJohan closed 1 month ago

StarkJohan commented 3 months ago

Recently, I can't say exactly after what version update, I've noticed a lot more errors in the data parsing. I'm constantly seeing "Footer checksum error" and "Unknown data received, check meter config". Sometimes it's just one "red" error until the next 10s update, sometimes it takes multiple updates to clear the error, say 3-5 x 10s updates in a row is erroneous. I have not changed anything in my config and the parsing has been very consistent previously, say 99% hit ratio. Now it's more like 75% correct readouts. Not a big issue but I wanted to inform you in case there's been any recent software changes that might cause more errors than before.

Kamstrup Omnipower without adapter HAN-NVE configuration, DLMS output, no encryption Pow-K (old kit version). Currently on software v2.3.6 2400 / 8N1 / Buffer 256

Any idea on what might cause the increase in errors? Hardware/software issue?

ArnieO commented 3 months ago

We have received other feedback over the last week on issues with ESP8266-based devices, what you're seeing could be related.

A bug surfaced yesterday; please try the test firmware in this thread and give us your feedback! https://github.com/UtilitechAS/amsreader-firmware/issues/815#issuecomment-2199477693

gskjold commented 3 months ago

Please try the attached firmware to check if that makes any difference for you: esp8266.zip

StarkJohan commented 3 months ago

Thanks, currently testing. First 5 minutes looks promising. Will keep an eye on it and report back.

Update: After about 30 minutes only a few errors have appeared, and when they have it's only been for single 10s periods (mostly). A few errors have been 3x10s but that is hardly anything compared to 2.3.6.

Seems like I can confirm this version solves the issue. Excellent work as usual.

StarkJohan commented 2 months ago

Issue not completely solved but a lot better. It's at least not affecting the functionality too much. Once in a while I get 2 or 3 errors consecutively but most of the time it's just one and that's not too serious.

ArnieO commented 2 months ago

Issue not completely solved but a lot better. It's at least not affecting the functionality too much. Once in a while I get 2 or 3 errors consecutively but most of the time it's just one and that's not too serious.

Thank you for the update!