PzemAc 1 error 9 - reading pzem values intermittently #19570
Replies: 3 comments 1 reply
-
If you haven't changed anything in Tasmota (firmware, version, setting) it could be a hardware problem |
Beta Was this translation helpful? Give feedback.
-
Well basically the problem solved itself today. Tasmota is reading correctly everytime. No more error 9 in the logs. Just something strange happened with Home Assistant that now is reporting two entity for each value (like pzem.energy0 / pzem.energy1). And now the two entity disappered, so now i just have pzem.energy_*... I can't really understand what's happening... And now.... the zeros reading are back. |
Beta Was this translation helpful? Give feedback.
-
I'm also struggling with two PZEM-017 modules that are not reading correctly. I thought they were working previously, but perhaps I damaged them. From the source code here are the error codes: Error 9 is a CRC error - I'm seeing 'random' decodes when I set the Weblog to 4. I'm also seeing Error 7 - not enough packets. Truly odd since they appear to be correct when I look at the D1mini pin with a scope with serial decode capabilities. I added a tantalum capacitor to the 5V rail but still get errors. I have a third PZEM-017 on the way. |
Beta Was this translation helpful? Give feedback.
-
PROBLEM DESCRIPTION
Tasmota with a PZEM016 Sensor is not reporting data correctly since yesterday. Rebooting the tasmota+pzem didn't change anything.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
Not really a way to reproduce. It just happend randomly.
EXPECTED BEHAVIOUR
Tasmota should read pzem values as always. Insted it randomly switches between reading values and reading 0 reporting "pzemac 1 error 9".
SCREENSHOTS
Here you can see the sensor reporting correct values until today. Today it started to measure uncorrectly.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
Beta Was this translation helpful? Give feedback.
All reactions