batpred icon indicating copy to clipboard operation
batpred copied to clipboard

Sensor sensor.predbat_lib_0_reserve changed from % to Wh in v8.25.9

Open ragg987 opened this issue 2 months ago • 1 comments

Describe the bug Hi, the battery sensor behaviour has changed from % to Wh in one of the 2 release v8.25.8 or .9

There have been no changes on my apps.yaml during this time so I'm not clear if there is any way for me to control this.

sensor.predbat_lib_0_reserve
input_number.predbat_lib_0_charge_limit_target_from_predbat

The _reserve sensor still shows units as % in the Developer view.

Image

The input number is a custom sensor I have created that predbat will write to with the target SOC required, then I have a custom automation that will write this value to the Libbi battery.

Expected behaviour Sensors should respect the % units.

Predbat version

v8.25.9

Environment details

  • Inverter and battery setup: Myenergi Libbi setup as a custom inverter
  • Standard HAOS installer

Screenshots

Image

Log file

58649 | 2025-10-14 16:05:55.872473: Warn: record_status Warn: Inverter 0 write to charge_limit failed
58648 | 2025-10-14 16:05:55.851039: Warn: Inverter 0 Trying to write 550 to charge_limit didn't complete got 4.0
58647 | 2025-10-14 16:05:53.847830: Warn: Service call input_number/set_value data {'value': 550, 'entity_id': 'input_number.predbat_lib_0_charge_limit_target_from_predbat'} failed with response None

Predbat debug yaml file This is important for any plan related issues.

Once you have captured the issue go to the Web UI, in the Dash tab click on predbat_debug.yaml and wait 30 seconds for it to download. Select 'keep' if your Web Browser thinks the file is dangerous.

Rename the download file to predbat_debug.yaml.txt and upload it to Github. This will allow your plan to be reproduced and also stores all your settings for review.

ragg987 avatar Oct 14 '25 15:10 ragg987

OK this is really odd, the values are correct now and (again) I have not made any changes to HA or predbat.

I suspect my install was hitting some code condition that messed up the value of the target... I'll leave this issue up here in case someone else comes across the same thing - I have no idea how to replicate the issue.

Image

ragg987 avatar Oct 15 '25 14:10 ragg987