Skip to content

Releases: pacemaker82/PredBat-Table-Card

1.8.0.2

10 Oct 08:30
c89c98a

Choose a tag to compare

Bug Fix Release v1.8.0.2

  • Console.log cleanup

Bug Fix Release v1.8.0.1

  • Fixed issue where certain timeslots in the plan should not allow override settings.
  • Fixed issue where options-column and options-popup-column broke the plan when using oldskool settings.

Previous Release v1.8

Battery Capacity as kWh

Screenshot 2025-10-09 at 09 36 58

Now you can add battery_capacity to your card YAML to provide your total battery capacity. When doing this, the soc-column will show your battery capacity in kWh, rather than in percentage.

This should be set as a float value, e.g.

battery_capacity: 9.532

Manual Overrides for timeslots

Screenshot 2025-10-09 at 09 31 04

Building on the recent release to allow time-slot overrides, a number of enhancements have taken place to give more flexibility and usage. Overrides allow you to force Predbat to behave in the way you want, rather than the way it wants, like force a charge for a time slot, or export.

Supports the following Predbat overrides:

  • Manual Force Demand
  • Manual Force Charge
  • Manual Force Export
  • Manual Freeze Charge
  • Manual Freeze Export

There are a number of ways you can use these manual override settings, choose your favoured option below:

  1. By default, the time-column is now clickable. On click/tap, a pop up will appear allowing you to manage the override settings for that timeslot.
  2. Add options-column to the columns YAML settings to show a new column on the plan, giving you all the options in line.
  3. Add options-popup-column to the columns YAML settings, this will display a single icon that you can click to show the same pop up in option (1). Useful if you dont want the time-column to be clickable, and want the placement of that column to be somewhere else in your plan.

Icons (or the time-column) will turn GREEN when a timeslot has had a manual override set on it.

REMEMBER: You need to wait for the plan to do a re-run before your settings take hold. Selecting multiple settings at once may not necessarily get planned in by Predbat straight away. Be patient... this is the nature of Predbat and how it handles the manual override changes.

1.8.0.1

10 Oct 08:25
cbaeec7

Choose a tag to compare

Bug Fix Release v1.8.0.1

  • Fixed issue where certain timeslots in the plan should not allow override settings.
  • Fixed issue where options-column and options-popup-column broke the plan when using oldskool settings.

Previous Release v1.8

Battery Capacity as kWh

Screenshot 2025-10-09 at 09 36 58

Now you can add battery_capacity to your card YAML to provide your total battery capacity. When doing this, the soc-column will show your battery capacity in kWh, rather than in percentage.

This should be set as a float value, e.g.

battery_capacity: 9.532

Manual Overrides for timeslots

Screenshot 2025-10-09 at 09 31 04

Building on the recent release to allow time-slot overrides, a number of enhancements have taken place to give more flexibility and usage. Overrides allow you to force Predbat to behave in the way you want, rather than the way it wants, like force a charge for a time slot, or export.

Supports the following Predbat overrides:

  • Manual Force Demand
  • Manual Force Charge
  • Manual Force Export
  • Manual Freeze Charge
  • Manual Freeze Export

There are a number of ways you can use these manual override settings, choose your favoured option below:

  1. By default, the time-column is now clickable. On click/tap, a pop up will appear allowing you to manage the override settings for that timeslot.
  2. Add options-column to the columns YAML settings to show a new column on the plan, giving you all the options in line.
  3. Add options-popup-column to the columns YAML settings, this will display a single icon that you can click to show the same pop up in option (1). Useful if you dont want the time-column to be clickable, and want the placement of that column to be somewhere else in your plan.

Icons (or the time-column) will turn GREEN when a timeslot has had a manual override set on it.

REMEMBER: You need to wait for the plan to do a re-run before your settings take hold. Selecting multiple settings at once may not necessarily get planned in by Predbat straight away. Be patient... this is the nature of Predbat and how it handles the manual override changes.

1.8

09 Oct 08:40
5e3ea96

Choose a tag to compare

1.8

Major Release v1.8

Battery Capacity as kWh

Screenshot 2025-10-09 at 09 36 58

Now you can add battery_capacity to your card YAML to provide your total battery capacity. When doing this, the soc-column will show your battery capacity in kWh, rather than in percentage.

This should be set as a float value, e.g.

battery_capacity: 9.532

Manual Overrides for timeslots

Screenshot 2025-10-09 at 09 31 04

Building on the recent release to allow time-slot overrides, a number of enhancements have taken place to give more flexibility and usage. Overrides allow you to force Predbat to behave in the way you want, rather than the way it wants, like force a charge for a time slot, or export.

Supports the following Predbat overrides:

  • Manual Force Demand
  • Manual Force Charge
  • Manual Force Export
  • Manual Freeze Charge
  • Manual Freeze Export

There are a number of ways you can use these manual override settings, choose your favoured option below:

  1. By default, the time-column is now clickable. On click/tap, a pop up will appear allowing you to manage the override settings for that timeslot.
  2. Add options-column to the columns YAML settings to show a new column on the plan, giving you all the options in line.
  3. Add options-popup-column to the columns YAML settings, this will display a single icon that you can click to show the same pop up in option (1). Useful if you dont want the time-column to be clickable, and want the placement of that column to be somewhere else in your plan.

Icons (or the time-column) will turn GREEN when a timeslot has had a manual override set on it.

REMEMBER: You need to wait for the plan to do a re-run before your settings take hold. Selecting multiple settings at once may not necessarily get planned in by Predbat straight away. Be patient... this is the nature of Predbat and how it handles the manual override changes.

1.7.2

06 Oct 12:13
72bf720

Choose a tag to compare

Added

  • New options-column which gives button options to control Predbat

Details

By adding the options-column as a column in your card YAML, you can display a column of buttons that help you control Predbat for that timeslot.

Screenshot 2025-10-06 at 13 03 52

This column currently supports the following capabilities:

  • Force Demand / Idle
  • Force Battery Charge
  • Force Battery Export

Clicking these buttons within the timeslot is the same as selecting them from the Predbat dropdown options. It will trigger a plan rebuild, which will reflect the actual status in the status-column once calculated.

1.7.1.2

20 Sep 09:25
b9a139d

Choose a tag to compare

NEW

  • Added path_for_click YAML configuration item.

In combination with the "mini" Predbat card options released in 1.7.1.1, this new config item allows you to configure the entire plan to be clickable, and navigate to another dashboard view.

Useful if you want your mini Predbat plan to click through (or tap through) to another dashboard with the full plan.

path_for_click: /my-dashboard/predbat-plan

1.7.1.1

18 Sep 07:57
def74bd

Choose a tag to compare

NEW

  • Use row_limit in your YAML config to limit the number of rows the plan returns. Any rows that total up the columns will be based on the row limit set.

This is super useful for creating a quick-look "mini" version of the plan that you can show on a dashboard with other cards.

See here for more: https://github.com/pacemaker82/PredBat-Table-Card?tab=readme-ov-file#creating-a-mini-predbat-card

Screenshot 2025-09-18 at 09 10 49

1.7.1.0

26 Aug 14:18
660f121

Choose a tag to compare

Added

  • Use rain-column to see the percent chance of rain for the time slot. Must also have a weather entity set in the card YAML
  • Plan generation duration is now added with the last updated time, so you can see visually how long its taking.
Screenshot 2025-08-26 at 14 12 42

1.7.0.9

18 Aug 15:39
0d229c6

Choose a tag to compare

FIXED

  • Broken plan when using the new override for load feature in Predbat 8.24.2

1.7.0.8

14 Aug 07:10
cbaf1c4

Choose a tag to compare

FIXED

  • "Plan Last Updated" time - removed the AM/PM label
  • Removed bunch of legacy code

1.7.0.7

12 Aug 06:41
46cf0cc

Choose a tag to compare

FIXED

  • "Plan Last Updated" time now appears as 24 hour clock inline with the plan time format.