-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
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
Solax daily / total sensors mixed up and incorrectly marked as total_increasing #130742
Comments
Hey there @squishykid, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) solax documentation |
I suspect
The initial issue might be from reverse engineered API data here
The Daily reset sensors for feed-in and consumed energy seem to miss |
Attempt to fix: |
The problem
Four sensor values are wrong on Solax X3-Hybrid-G4 - I don't have other solax inverters to compare.
Both Consumed energy and Feed in energy:
a)
_consumed_energy_total
and_feed_in_energy_total
- this is not actually a total value, it's reset daily - daily value, wrong name.b)
_consumed_energy_total
and_feed_in_energy_total
- as daily reset, it'sstate
is market incorrectly astotal_increasing
.c) _consumed_energy
and
_feed_in_energy- lack a
_totalsuffix, but actually this is a total increasing sensor.
state**correctly** marked as
total_increasing`.Summary - total and daily are swapped, and both incorrectly
state: total_increasing
I'll try to find this in the code and open a PR if time allows.
What version of Home Assistant Core has the issue?
core-2024.11.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
solax
Link to integration documentation on our website
https://www.home-assistant.io/integrations/solax
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: