Setting “Battery maximum power” to 0 ignores PV battery limits and forces max car charging

[cwack-letsdev]

Describe the bug
When the field “Battery maximum power” is set to 0, the maximum possible charging power of the PV battery is no longer detected correctly. Instead, the wallbox immediately charges the car with its maximum charging power (e.g. 11 kW), and only the remaining surplus is charged into the PV battery.

If a fixed maximum PV battery charging power is set, the adapter only charges part of the available power into the car, while the rest is unnecessarily fed into the public grid – even though the wallbox would be able to charge the car with more power.

This results in an inefficient use of PV surplus and battery capacity.

To Reproduce
Steps to reproduce the behavior:

Open the adapter configuration and set Battery maximum power to 0.

Enable PV automatic mode with battery support.

Observe charging behavior when both PV surplus and battery capacity are available.

The car starts charging with maximum charging power (e.g. 11 kW), and the PV battery only receives the remaining surplus.

Edge case:

If instead of 0, a fixed value (e.g. 3000 W) is entered for Battery maximum power, the car only charges partially, while the remaining energy is unnecessarily fed into the grid – although the wallbox could provide more charging power to the car.

Expected behavior

With Battery maximum power = 0, the adapter should automatically detect and respect the actual maximum charging power of the PV battery.

The car should charge with the maximum possible charging power, while the PV battery is charged in parallel as much as possible – without feeding unnecessary power into the public grid.

Screenshots & Logfiles

Screenshots of the configuration with Battery maximum power = 0

Debug log output during PV surplus charging with battery support

Versions:

Adapter version: 3.2.0

JS-Controller version: 7.6.17

Node version: <please fill with node -v>

Operating system: Docker

Type of wallbox: X-Series PV Edition

Brand and model of vehicle to be charged:

Used options: PV automatics, battery storage, 1p/3p switch (x2), do not use battery storage (prio on battery)

Additional context
The bug only occurs in connection with PV battery charging limits. It seems that setting the parameter to 0 disables the auto-detection instead of interpreting it as “use the actual maximum PV battery charging power”.

[Sneak-L8]

@cwack-letsdev just to be sure, I got it right: when speaking of "Battery maximum power" then you mean the value in the setting of the adapter (pv section, 2nd line)?
In this field the maximum possible power of the pv battery is expected. It's not a value to chose how much your pv battery should be charged or not. This value is needed to be able to calculate maximum charging power of your vehicle depending on battery strategies. If having a pv battery installed this value should never be 0.
On git there's also an enhanced version, if your pv battery can suplly more power to the house than it can be charged. In this case, there's an additional option to specify the maximum power with that pv battery can be charged. If left empty (or zero), the value of "Battery maximum power" will be assumed for charging and discharging of pv battery.
If you need this option please install ltest version from git.

If I got it wrong please correct me. Some debug logs would also be appriciated to be able to analyze situation.

[Sneak-L8]

@cwack-letsdev do you sill have problems with this issue?

[cwack-letsdev]

Yes the issue still exists. In the last versions this issue never occurred. I guess the problem is that the battery of my house is not always charging with the same speed. At the first 20% about 1.800KWH then more than 6.000kw/h and when almost full again with slower speed. What I want to achieve is when I set to „battery first“ then the vehicle should only be charged with PV surplus. And that is not happening. The vehicle is being charger with all the surplus and not any more the battery of the house. Am 05.10.2025 um 20:48 schrieb Sneak-L8 ***@***.***>: [https://avatars.githubusercontent.com/u/34042079?s=20&v=4]Sneak-L8 left a comment (iobroker-community-adapters/ioBroker.kecontact#486)<#486 (comment)> @cwack-letsdev<https://github.com/cwack-letsdev> do you sill have problems with this issue? — Reply to this email directly, view it on GitHub<#486 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAMDWBAUOG5QGFEVABUKXEL3WFRYJAVCNFSM6AAAAACEIH7E6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNRZGI2DSOJYGM>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Sneak-L8]

Ok, please share your config and debug log (config is included in debug log at startup).
Please also mention when (timestamp) the problem occurs, so I can check the logs.