1.9.6

Added (1.9.6)

• Day and Plan totals now include the total-column.
• Cost and Total prices in the day/plan totals show green for credit, and red for debit.

Added (1.9.5)

• Use reset_day_totals and set to true in your card YAML to reset the total-column at midnight to £0.00

Fixed (1.9.6)

• Logic for reset_day_totals now reflects pricing logic of Predbat table.

1.9.5

Added

• Use reset_day_totals and set to true in your card YAML to reset the total-column at midnight to £0.00

1.9.4

FIXED

• Card now supports up to 48-hour manual overrides. This is only supported by Predbat v8.28.2 and above. Card will fall back to previous logic if you are on an older Predbat version.

1.9.3

Updates

Version 1.9.3 - New card configuration UI !

You can now edit nearly all of the card configuration within the card UI editor. Note: columns still need to be manually added as the built-in support from home assistant isn't flexible enough yet.

Version 1.9.2

• Cleaned up CSS for the table including last updated and version labels.

New Version Label Functionality

• When a new version of Predbat or the card is available, you can now click the label to upgrade right there.
• Use show_predbat_version: true to show a label at the bottom of the table of the current Predbat version
• Use show_tablecard_version: true to show a label at the bottom of the table of the current card version

Minor Updates

• Refactored code for the day and overall total rows
• Updated hide_empty_columns card YAML functionality: When set to true the card will hide ANY column that has no data in it for the entire length of the plan. Previously this was just car-column and iboost-column

Version v1.9.x

Major refactor of the cell generation code, which should massively simplify maintenance going forwards, and make table generation quicker. This was very logically complex code written over 1 year ago so I expect some bugs.

Refactor is enabled by default. If you find an issue and can't wait (but please log a bug on GitHub), use the following YAML for your card to bypass the refactor and use the old code:

bypassRefactor: true

Bypass will be removed in a future release once bugs are squashed. Thank you for enjoying the card!

1.9.2

Updates

Version 1.9.2

• Cleaned up CSS for the table including last updated and version labels.

New Version Label Functionality

• When a new version of Predbat or the card is available, you can now click the label to upgrade right there.
• Use show_predbat_version: true to show a label at the bottom of the table of the current Predbat version
• Use show_tablecard_version: true to show a label at the bottom of the table of the current card version

Minor Updates

• Refactored code for the day and overall total rows
• Updated hide_empty_columns card YAML functionality: When set to true the card will hide ANY column that has no data in it for the entire length of the plan. Previously this was just car-column and iboost-column

Version v1.9.x

Major refactor of the cell generation code, which should massively simplify maintenance going forwards, and make table generation quicker. This was very logically complex code written over 1 year ago so I expect some bugs.

Refactor is enabled by default. If you find an issue and can't wait (but please log a bug on GitHub), use the following YAML for your card to bypass the refactor and use the old code:

bypassRefactor: true

Bypass will be removed in a future release once bugs are squashed. Thank you for enjoying the card!

1.9.1.2

Updates

• Refactored code for the day and overall total rows
• Updated hide_empty_columns card YAML functionality: When set to true the card will hide ANY column that has no data in it for the entire length of the plan. Previously this was just car-column and iboost-column

Version v1.9.x

Major refactor of the cell generation code, which should massively simplify maintenance going forwards, and make table generation quicker. This was very logically complex code written over 1 year ago so I expect some bugs.

Refactor is enabled by default. If you find an issue and can't wait (but please log a bug on GitHub), use the following YAML for your card to bypass the refactor and use the old code:

bypassRefactor: true

Bypass will be removed in a future release once bugs are squashed. Thank you for enjoying the card!

1.9.1.1

Updates

• Added directional arrows to the state-column when just showing icons
• Fixed issues with state mouseover tooltips
• Updated Friendly Text for HoldChrg to "Maintain SoC to Limit"
• Tidied up some issues with refactor code

Version v1.9.x

Major refactor of the cell generation code, which should massively simplify maintenance going forwards, and make table generation quicker. This was very logically complex code written over 1 year ago so I expect some bugs.

Refactor is enabled by default. If you find an issue and can't wait (but please log a bug on GitHub), use the following YAML for your card to bypass the refactor and use the old code:

bypassRefactor: true

Bypass will be removed in a future release once bugs are squashed. Thank you for enjoying the card!

Previous Release v1.8

Battery Capacity as kWh

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

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.9.0.9

Updates

• Added directional arrows to the state-column when just showing icons
• Fixed issues with state mouseover tooltips
• Updated Friendly Text for HoldChrg to "Maintain SoC to Limit"

Version v1.9.x

Major refactor of the cell generation code, which should massively simplify maintenance going forwards, and make table generation quicker. This was very logically complex code written over 1 year ago so I expect some bugs.

Refactor is enabled by default. If you find an issue and can't wait (but please log a bug on GitHub), use the following YAML for your card to bypass the refactor and use the old code:

bypassRefactor: true

Bypass will be removed in a future release once bugs are squashed. Thank you for enjoying the card!

Previous Release v1.8

Battery Capacity as kWh

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

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.9.0.10

Updates

• Added directional arrows to the state-column when just showing icons
• Fixed issues with state mouseover tooltips
• Updated Friendly Text for HoldChrg to "Maintain SoC at Limit"

Version v1.9.x

Major refactor of the cell generation code, which should massively simplify maintenance going forwards, and make table generation quicker. This was very logically complex code written over 1 year ago so I expect some bugs.

Refactor is enabled by default. If you find an issue and can't wait (but please log a bug on GitHub), use the following YAML for your card to bypass the refactor and use the old code:

bypassRefactor: true

Bypass will be removed in a future release once bugs are squashed. Thank you for enjoying the card!

Previous Release v1.8

Battery Capacity as kWh

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

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.9.0.8

Updates

• Added directional arrows to the state-column when just showing icons
• Fixed issues with state mouseover tooltips

Version v1.9.x

Major refactor of the cell generation code, which should massively simplify maintenance going forwards, and make table generation quicker. This was very logically complex code written over 1 year ago so I expect some bugs.

Refactor is enabled by default. If you find an issue and can't wait (but please log a bug on GitHub), use the following YAML for your card to bypass the refactor and use the old code:

bypassRefactor: true

Bypass will be removed in a future release once bugs are squashed. Thank you for enjoying the card!

Previous Release v1.8

Battery Capacity as kWh

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

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.