Skip to content
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

Add entity for battery heating #187

Open
3 tasks done
HakunaMatata47 opened this issue Jan 13, 2025 · 4 comments
Open
3 tasks done

Add entity for battery heating #187

HakunaMatata47 opened this issue Jan 13, 2025 · 4 comments
Labels
dependencies Pull requests that update a dependency file enhancement New feature or request help wanted Extra attention is needed

Comments

@HakunaMatata47
Copy link

Checklist

  • I have filled out the template to the best of my ability.
  • This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
  • This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

In the Anker App you see in the Device section a temperature information.

It would be helpful to have that temperature information also in the Solix Integration.
I.e. to understand why the battery is not charged (usually temperatures below 2 degrees)
or to set a warning notification for the hotter days.

Describe the solution you'd like

sensor.solix_site_sb_akkutemperatur

  • just an idea

Describe alternatives you've considered

or similar

Additional context

I think it is missing right now as I don't find an entity with that information in the current Integration version

@thomluther
Copy link
Owner

Hi,
The device temperature is not available via Cloud Api at this time, see Add temperature entity.
There is a new heating power field in the Api scene info response, but I have no idea how it is used for solarbanks.
You will have to monitor the Api response from time to time, especially when you see the heating on in the App.

You can use the Action to get Anker System information to fetch that data from Api.

@thomluther thomluther added enhancement New feature or request dependencies Pull requests that update a dependency file help wanted Extra attention is needed labels Jan 13, 2025
@thomluther thomluther changed the title Add item for device system battery temperature Add entity for battery heating Jan 13, 2025
@thomluther
Copy link
Owner

@HakunaMatata47
Any success in getting System info via the service? Does it show values other than 0 in pei_heating_power field?
Here are the new solarbank fields that are unknown and needs interpretation and correlation to App values that might be shown...

    "other_input_power": "0",  => Unknown? Maybe DC input for battery charging when grid to battery is AC?
    "micro_inverter_power": "0",   => AC Output power for SB2? Should be lower than other output power values, if those are DC?
    "micro_inverter_power_limit": "0",   => Inverter output limit? Used for all SB2 models?
    "micro_inverter_low_power_limit": "0",  => Unknown
    "grid_to_battery_power": "0",   => DC or AC charging power?
    "pei_heating_power": "0"   => Total heating power for the batteries?

@HakunaMatata47
Copy link
Author

HakunaMatata47 commented Jan 17, 2025 via email

@thomluther
Copy link
Owner

"micro_inverter_power": "32" => all micro_inverter_* field were introduced with the AC model as well as the pei_heating_power field, Probably the inverter fields are all non-sense for any other SB2 model, e.g. micro_inverter_power power is always the same at PV channel 3 power, which does not make sense at all.
I never saw pei_heating power other than 0....maybe it will come some day, maybe just for certain models and with certain firmware levels....
Total charging power response from Api is wrong. The library recalculates and reuses that total field to reflect battery power (positive and negative)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants