Releases: pacemaker82/PredBat-Table-Card
1.9.0.5
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:
- 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.
- Add
options-columnto thecolumnsYAML settings to show a new column on the plan, giving you all the options in line. - Add
options-popup-columnto thecolumnsYAML 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 thetime-columnto 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.4
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:
- 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.
- Add
options-columnto thecolumnsYAML settings to show a new column on the plan, giving you all the options in line. - Add
options-popup-columnto thecolumnsYAML 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 thetime-columnto 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.3
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:
- 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.
- Add
options-columnto thecolumnsYAML settings to show a new column on the plan, giving you all the options in line. - Add
options-popup-columnto thecolumnsYAML 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 thetime-columnto 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.2
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:
- 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.
- Add
options-columnto thecolumnsYAML settings to show a new column on the plan, giving you all the options in line. - Add
options-popup-columnto thecolumnsYAML 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 thetime-columnto 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.1
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:
- 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.
- Add
options-columnto thecolumnsYAML settings to show a new column on the plan, giving you all the options in line. - Add
options-popup-columnto thecolumnsYAML 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 thetime-columnto 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
Version v1.9
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:
- 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.
- Add
options-columnto thecolumnsYAML settings to show a new column on the plan, giving you all the options in line. - Add
options-popup-columnto thecolumnsYAML 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 thetime-columnto 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.5
Bug Fix Releases v1.0.8.5 - v1.8.0.1
- Fixed issue where certain timeslots in the plan should not allow override settings.
- Fixed issue where
options-columnandoptions-popup-columnbroke the plan when using oldskool settings. - Updated messaging when overrides are not available for the current time slot.
- Updated messaging text colour causing black on black clash
- Fixed weather colours
- Ensure
options-popup-columnhas a visual reference when the override is not allowed - Console.log cleanup
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:
- 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.
- Add
options-columnto thecolumnsYAML settings to show a new column on the plan, giving you all the options in line. - Add
options-popup-columnto thecolumnsYAML 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 thetime-columnto 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.4
Bug Fix Releases v1.0.8.4 - v1.8.0.1
- Fixed issue where certain timeslots in the plan should not allow override settings.
- Fixed issue where
options-columnandoptions-popup-columnbroke the plan when using oldskool settings. - Updated messaging when overrides are not available for the current time slot.
- Ensure
options-popup-columnhas a visual reference when the override is not allowed - Console.log cleanup
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:
- 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.
- Add
options-columnto thecolumnsYAML settings to show a new column on the plan, giving you all the options in line. - Add
options-popup-columnto thecolumnsYAML 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 thetime-columnto 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.3
Bug Fix Releases v1.0.8.3 - v1.8.0.1
- Ensure
options-popup-columnhas a visual reference when the override is not allowed - Console.log cleanup
- Fixed issue where certain timeslots in the plan should not allow override settings.
- Fixed issue where
options-columnandoptions-popup-columnbroke the plan when using oldskool settings.
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:
- 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.
- Add
options-columnto thecolumnsYAML settings to show a new column on the plan, giving you all the options in line. - Add
options-popup-columnto thecolumnsYAML 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 thetime-columnto 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.2
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-columnandoptions-popup-columnbroke the plan when using oldskool settings.
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:
- 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.
- Add
options-columnto thecolumnsYAML settings to show a new column on the plan, giving you all the options in line. - Add
options-popup-columnto thecolumnsYAML 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 thetime-columnto 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.