Sensors "Battery (dis)charge limit current" no longer available since 0.9.x (3phase)
Issue related to
Sunsynk / solarman Home Assistant Add-On
Describe the issue/bug
Since update from 0.8.2 (where it worked fine) to newer 0.9.2 version the writable sensors:
- Battery charge limit current
- Battery discharge limit current
Are no longer available (3 phase configuration)
Expected behavior
These writable sensors should be available as they were on version 0.8.2
Your environment
- Home Assistant version: 2025.9.4
- Addon:
- Name: sunsynk-multi
- Version: 0.9.2
- Inverter:
- Make: Deye
- Model: Sun 12k EU
- Firmware: __
- Adaptor details:
- solarman
You configuration
I have the same experience on the installations were the update was made. On other Installations 0.8.2 is still running fine, I switched off update. Now I need to find out how to downgrade the one installation that causes the problem now.
Exactly the same issue, I had to roll back. However I am on a single phase inverter.
I’m on latest and can’t see the following values
- battery_max_charge_current
- battery_max_discharge_current
Have they been renamed?
Have a look at the docs. Are you sure you have them in your config?
I’ve just used the defaults do I need to do anything else to get these values?
If you don’t configure them they probably wont be there.
Defaults would include sensors for the power flow card
Thank you, that worked
So, did something change in the code or is it configuration that brings back the writable attributes?
As i see in documentation these attributes are only available in single phase configuration. (Is this correct.)
As i remember i didn't re-configure to 3-phase from single-phase even inverter is 3-phase by hardware. (Maybe auto discovery now?)
But as one user has the same issue having a single-phase...
Is the solution something we users can do by configuration?
So, did something change in the code or is it configuration that brings back the writable attributes?
As i see in documentation these attributes are only available in single phase configuration. (Is this correct.)
As i remember i didn't re-configure to 3-phase from single-phase even inverter is 3-phase by hardware. (Maybe auto discovery now?)
But as one user has the same issue having a single-phase...
Is the solution something we users can do by configuration?
Hi! You can read the docs here: https://kellerza.github.io/sunsynk/reference/definitions#battery In summary, add "battery" sensor/group to your sensors list and you shall have all battery sensors and config entities.
So, did something change in the code or is it configuration that brings back the writable attributes?
As i see in documentation these attributes are only available in single phase configuration. (Is this correct.)
As i remember i didn't re-configure to 3-phase from single-phase even inverter is 3-phase by hardware. (Maybe auto discovery now?)
But as one user has the same issue having a single-phase...
Is the solution something we users can do by configuration?
Yes that’s what I would like to know. Been using the integration for well over 12 months and never had any issues updating prior to this. I also use time /date and a few other none standard ones which all disappeared…..
Regarding to documentation -battery-charge-current and -batter-discharge-current
Is not available at 3 phase inverters. But it did work great on version 0.82 on a physical 3 phase inverter (falsly) configured as a single phase one.
Is the inverter type now automatically resolved and therefore no longer worked?
Or can you officially support those 2 current sensors?
Or does it work if we manually add them in the yaml file?
Many things change over such a long time, you are welcome to have a look at the git history and try to blame someone.
I would rather spend my time on:
- Fixing your config
- Adding custom sensors if you believe they are/were valid
See https://kellerza.github.io/sunsynk/reference/mysensors - you are free to add any register you wish. If they work well, feel free to suggest an addition in a PR
There is no automatic resolution of inverter type, so if you need it wrongly configured, feel free to keep doing it. Other sensors might be wrong
btw, if you ask for help, but not willing to share your config or proper logs there is really not much we can do for you