-
Notifications
You must be signed in to change notification settings - Fork 638
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
POW energy_delta blank #258
Comments
The energy_delta topic reports energy consumption over the last minute in Joules. So, previous energy_total value plus current energy_delta should be current energy_total. |
Original comment by Chad Faurie (Bitbucket: ChadFaurie, GitHub: Unknown): I did see that, and it works really well This occurs after about an hour of up time |
Original comment by jcoertel (Bitbucket: jcoertel, GitHub: jcoertel): Hello,
Here is MQTT report (subscribe on .../energy_delta) : You can see that turning on rad01 sets the right level for the first report but after topic value is (null). Did the same with another equipment (rad02) with same result. After a while the values are still null. Not sure if the this is the same issue. Cheers |
Original comment by jcoertel (Bitbucket: jcoertel, GitHub: jcoertel): Hello again, Had a look to the code (file power.ino) and I did a test after increasing the buffer size of conversion buffers. Previous code was:
Changed code :
After that I did not experience the problem anymore. Maybe it can help to fix the issue. Cheers |
Original comment by Chad Faurie (Bitbucket: ChadFaurie, GitHub: Unknown): Awesome, I'll be honest I have not had the chance to look at it, I have been traveling the last 2 weeks. I'll test the fixes when I get back unless they get pulled into the latest release |
Changed in dev branch, will be released with 1.9.8 |
Released with 1.9.8 |
Removing milestone: 1.9.8 (automated comment) |
Originally reported by: Chad Faurie (Bitbucket: ChadFaurie, GitHub: Unknown)
Hi
After a while the POW reports nothing in the energy_delta topic on MQTT
The text was updated successfully, but these errors were encountered: