-
Notifications
You must be signed in to change notification settings - Fork 114
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
Sensors reading with a very small negative value #63
Comments
See this post in the discussion section: #59 |
Thanks for this link. I ended up resolving the issue using the advice. For anyone else who wants to know how I did it: Editing the ESPhome yaml for the energy-meter, towards the bottom, below the last
And if you want to have a "Totals" section for calculating total watts / kWh based upon the Positive values in the above-created templates, then you can add this section to the yaml just below the section above. Obviously change the
|
Hello, I am using your 6C main board to read the energy through four different lines in my power box. AC for upstairs, AC for downstairs, washing machine, and dryer. I've got everything configured and working well, except for one issue I cant seem to figure out.
When the appliances are currently "off", the 6C unit is sending a very small negative value in the watts sensor. I would ignore this except it gets amplified up to the kWh reading and therefore the energy cost reading in the Energy dashboard within Home Assistant.
I've triple checked my yaml within ESPHome and everything seems to be correct, it's mostly the same copied from your example file.
What can I do to make this value absolute?
I'm using all four "100A/50ma SCT-013-000" clamps. When the appliances turn on, I get a positive watt reading, so the issue is not that the clamps are on backwards (I've double checked that).
What is interesting is that when one of my AC units is running, all the values are in the positive. Image below:
But when no appliance is running, watt values are slightly negative.
The text was updated successfully, but these errors were encountered: