| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Codecov ReportAll modified and coverable lines are covered by tests ✅ Additional details and impacted files @@ Coverage Diff @@
## master #1349 +/- ##
=======================================
Coverage 92.13% 92.13%
=======================================
Files 122 122
Lines 7867 7867
Branches 810 810
=======================================
Hits 7248 7248
Misses 454 454
Partials 165 165 ☔ View full report in Codecov by Sentry. |
Sorry, something went wrong.
|
I agree with the setting to zero, but I’m not sure about the value of the rename. Whilst I get that it’s a bit confusing, we’re still left with consumption_today, consumption_this_month etc. It’s a lot of churn to deprecate all this, when updating the docstrings to make clearer this is what the device reports as power could suffice. |
Sorry, something went wrong.
|
Yeah I was starting to doubt the cost of the change relative to its’ value. I can see that it would cost the long term history graphs of the power draw metrics in home assistant, but from what I could tell it would leave the energy monitoring integration mostly intact since that uses the accumulated consumption metrics instead of the instantaneous demand values. I think the term just confuses me since it is current_consumption rather than consumption_current or consumption_now to match the pattern of the other metrics. I see that it is inherited from TPLink themselves though, so I suppose if you are trying to stay as close to the way TPLink phrased it, the current name makes sense (although I’m still not a fan of overloading the term current in this context). I’ll get the zero setting extracted into a separate PR, since there’s no use in holding that back for this PR. |
Sorry, something went wrong.
- Fix: Report `0` instead of `None` for current when current is zero. - Fix: Report `0` instead of `None` for voltage when voltage is zero (not that this was possible to see).
|
I've extracted the zero power reporting fix into PR #1483 |
Sorry, something went wrong.
- Note: This is a breaking change. - Fix: Rename `current_consumption` to `power` in energy modules, to deconflict and clarify.
|
We could still look into renaming while keeping the deprecated names available for the time being. The only one we cannot change that easily is the feature identifier (which is used as a unique key). |
Sorry, something went wrong.
|
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.