-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Total energy (today, yesterday) statistical error in three pzem-004t #7301
Comments
Problem solved |
Updat: Is it possible that too much accumulation is not handled here? ` // 0 1 2 3 4 5 6 7 8 9 = ModBus register
In the beginning, everything is normal, but after a period of time (maybe an hour or more), the total value will become the data from which to supplement, and the value is the same as that without opt72. 11:40:41 DMP: 03 04 14 09 6A 03 9A 00 00 03 E3 00 00 2E F9 00 00 01 F3 00 2D 00 00 8C DD |
what is the difference between setoption 72 enabled and disabled? |
The setoption72 works only in hardware with total energy counter like sdm120, ddsu666, etc. The reported value is used to update tasmota internal counter and be in sync both counters. If enabled, tasmota use the reported value as total energy counter. |
This issue seems to be the same as #7155 Closing this one in order to have just one thread for the same issue |
Same here, the value from the pzem doesn't match the tasmota value in the console, with SetOption72 is ON . |
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
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
:(Please use
weblog 4
for more debug information)TO REPRODUCE
Steps to reproduce the behavior:
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
![p](https://user-images.githubusercontent.com/84192/71335195-7d810000-257c-11ea-80bb-b4fb3247c8e1.png)
ADDITIONAL CONTEXT
Add any other context about the problem here.
At first it looked very normal.
But recently, I found that the energy statistics seem to violate the normal values I actually use. So I opened the log and found out. The statistical energy is actually higher than the total energy sent back by three 004ts. And today, yesterday and total energy refresh is slow
The data are as follows:
11:45:02 DMP: 02 04 14 09 54 00 C7 00 00 00 89 00 00 14 1C 00 00 01 F4 00 1D 00 00 C5 47
11:45:03 DMP: 01 04 14 09 52 05 47 00 00 0A 4B 00 00 47 5D 00 00 01 F4 00 52 00 00 9A 8C
11:45:04 DMP: 03 04 14 09 60 03 48 00 00 02 EA 00 00 1E 31 00 00 01 F4 00 25 00 00 F5 AD
2=14 1C = 5148Wh
1= 47 5D = 18269Wh
3=1E 31 = 7729Wh
total = 31146Wh =31.146kWh
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: