Suggestions

[PianSom]

A couple of things that I'd like to see:

• above the table the time - if any - at which the battery will get depleted
• A heavy line (or some other demarkation) at midnight, so I can easily see when a new day begins
• A running total of costs from that future midnight

And although I run the risk of being further publicly shamed as an alignment obsessive, it'd be nice if the digits of the SoC column aligned even if no up or down arrow is present :)

EDIT - also - I like Trefor's "time of plan's last update" field above the table

[pacemaker82]

And although I run the risk of being further publicly shamed as an alignment obsessive, it'd be nice if the digits of the SoC column aligned even if no up or down arrow is present :)

This is how I am planning to address this. It will be an optional config item for those that like or dont like the empty space

[pacemaker82]

1.0.4 is out which tackles the alignment and "day break" in the table.

[PianSom]

The alignment isn't working here yet ...

(But thanks!)

[pacemaker82]

Please set the card YAML per release notes:

fill_empty_cells: true

then you should be good

[PianSom]

oh der, sorry. Didn't notice.

[pacemaker82]

Version 1.0.8 is out which supports the last plan updated time at the top of the table.

[PianSom]

Looking good here.

Small, odd thing - the width of the Import Cost label varies (see green 7.5p is smaller than orange/blue 31p and 0p).

[gcoan]

I like the look and feel of the new card, but am concerned about how much screen real-estate (i.e. length) the card occupies.

Trefor's original card for example, occupies 2 and a bit screen heights to scroll top to bottom. This plan card its 4 and a half. And in debug mode to show the prices with losses (which is what I normally use), it's even longer.

This makes it harder to get an overview of prices and battery Soc over the remainder of the day as there's so much scrolling to do

[pacemaker82]

might need help with understanding your issue. When I look at the predbat card, vs my one, I see the same amount of rows when not in HTML debug mode:

I can see your point in terms of html debug mode on, you're missing 4-5 half hour slots.

Am I understanding the issue correctly?

What I can look at is "if" there is wide enough space, the import + import incl. losses pills could go on same level rather than stacked, that would bring it inline with the first comparison images above.

Its tough because trying to also make it work for iPhone without horizontal scrolling, so will need to figure out how to get it to wrap the pills on width changes.

[PianSom]

Here are my two, starting at the same blue bar and ending at the bottom of my current screen

[pacemaker82]

@PianSom yes so yours is same as mine, missing ~4 half hour slots when using the custom card. @gcoan seems to be saying its much worse than that though, but maybe screenshots will help

[gcoan]

Here's the predbat plan, viewing on the HA companion app on my ipad

I can see from now to 4:30am on a single screen, including seeing the last updated time and header rows

By comparison, the predbat plan card, deliberately scrolling the headers and last updated off the screen, I can only see from now to 23:30. If I show these as well (to be comparable to the predbat view, I can only see to 22:30)

[pacemaker82]

Please try 1.1.5 - I've compacted things a little to get more data on screen.

[gcoan]

New header looks better thanks

Auto light/dark mode is working perfectly 👍

[pacemaker82]

what if there was a YAML option to show effective rates only?

[pacemaker82]

@gcoan I decided it was a nice feature to add actually (to only show debug adjusted prices). They will display in brackets (price) in the same way they already do. I am also ensuring the special symbols appear (=, ?, $ etc...).

You can set debug_prices_only to true to force it. Out now in 1.1.7

Example"

[gcoan]

Did you see my suggestion about vertical/horizontal stacking option of the rates+effective rates?

Cheers

[pacemaker82]

I'll implement a stack_pills true/false (true being default) type config I think, and that will just put the pills side by side (aka horizontal). Then there should be complete control. Please hold...

[pacemaker82]

@gcoan please download 1.2.0

use stack_pills: false in your YAML and import/export and import & export columns will organise the pills horizontally only. Default is to stack. (true)

[gcoan]

Much more compact now, thank you

Everything fits on one row again

BTW the stack_pills hasn't made it into the readme

[pacemaker82]

BTW the stack_pills hasn't made it into the readme

Thanks, fixed that.

[gcoan]

I don't know if people consider this important or not, but I've noticed that the forced charge/discharge/idle (upside down F) doesn't make it into the Predbat plan card:

[pacemaker82]

OK. see 1.2.4

Actually I see discharge is also supported so need to add that in.

[pacemaker82]

@gcoan should work in 1.2.5, supports charge, discharge and idle states. My presumption is "idle" state as mentioned in the docs is where the column shows ↘ ↗ → only (plus the upside down F for forced idle).

[gcoan]

Hmm, I still don't see it in 1.2.5

Same forced charge, discharge and idle set in predbat (as above from 23:00) and the plan card looks the same, blank in each case.

I was assuming that the forced charge and discharge would show with a battery+ and battery- icon and there would be some annotation that these 3 slots were forced activities (upside down F in Trefor's plan)

Don't feel its a major issue as I don't use forced activities all that often, I put one in yesterday to see if I could improve on the Predbat plan - and couldn't - hence noticed that they don't appear in your plan card

[pacemaker82]

Fixed it properly in 1.2.6 which is available now. I was using the incorrect upside down F unicode character (surprisingly there are multiples). Not sure the hand is the right icon here, I will keep looking through the MDI library to see if there is a better fit.

[gcoan]

@pacemaker82 this works perfectly now, thanks.

If you look at the predbat Python code, Trefor uses &#8526

As said before, if Predbat output in a structured format then would be easier to parse than reading and decoding the HTML

[pacemaker82]

Another bug @gcoan - I never see that on my plan - wondering what difference really is between 2.00 and 2.30 charge types (functionally wise). But I've had that confusion since day 1 and I suppose they mean something to trefor. Anyway I'll fix this.

[PianSom]

Although it pains me to say it, I am still being drawn to Trefor's table.

I MUCH prefer the payout of your card @pacemaker82 , especially the ability to have SoC front and centre as the leftmost column (after day+time). But what I like more about Trefor's is the big blocks of colour in the Status column. It's just much easier to see at a glance what is going on with the battery.

I admit I am somewhat hazy about what exactly the difference is between "Freeze Discharge", "Discharge" and a down arrow, but I do like being able to see easily if I am importing (ie big green area) or exporting. I miss the big colour blocks. I find the icons are too similar and actually quite hard to interpret.

Any thoughts on this? It's not you, it's me ...

[gcoan]

I too am undecided.

I have an 'Agile' tab with SoC's, current import rate and some templates to work out when its cheapest to put the washing machine and dishwasher on at the top. Then underneath I have Trefor's html plan and then the Predbat plan card.

I was expecting that I'd get to the point that I'd swap the two cards round and use the new card as my primary but that hasn't happened.
I like the colouring (especially in day-mode), the little icons and the ability to move the SoC column nearer to the start, but I'm still finding that Trefor's card gives me a quicker overview of what's happening.

I don't tend to look at Predbat's calculations, trusting it to get it right, but I do skim down the table to see when its charging and discharging and when the battery will run out.

Like @PianSom I find the big green and yellow charging/discharging blocks are easier to scan

[pacemaker82]

@PianSom its a fair point in terms of the colours and being drawn to them. I guess it depends on what people find is important information. For me, I look at it as informational and dont much care about the colours, I am trusting predbat to do whats right, and no amount of red or green is going to change that for me personally. But I expect there are folks that come at it from a position of fear and want to be drawn to certain aspects (discharge is important to them, or charge, or low SOC or whatever...) It will be hard to have a one size fits all I expect. Maybe trefor should just update his so folks can change the columns around :)

[pacemaker82]

FWIW I think the dark mode version does a pretty good job in terms of bringing the colours out. Maybe just making the text bold so the colours stand out a bit more might help

[PianSom]

Ummm - not sure I agreee

[pacemaker82]

well for some reason you have a seriously ugly alternative row colour there :) Here is my comparison. Are you overriding the row colours?

I feel like the defaults below work well honestly...

[PianSom]

Yes, not sure how I stuffed up the colours quite so spectacularly, but your defaults are better. I also like your single line layout, so I will move to that.

[PianSom]

How do you get the day/time to go on one line? Mine seems to be stuck on two ...

[pacemaker82]

It will squash itself if its container is thinner than the number of columns total width (it can only squash so much before the content has no more room to shrink). I have a full page template where the table has enough width to be all on one line.

You can set the width property to try force the issue or reduce your columns. Ultimately there is too much info to display perfectly

[PianSom]

I'll have a look later when it goes dark (can't be bothered to change it by hand!) but here's a direct comparison of what I'm seeing. Trefor's has WAY too much colour going on. But the yellow/green Status blocks do make for immediate impact. I do like your column customisation very much.

[pacemaker82]

@gcoan I guess I dont understand about the stacking ask. Why not just use import-column and export-column? You get everything on a single line which I think is what you want no? The whole point of the import/export column is to collapse the two into one to reduce width.

[gcoan]

@gcoan I guess I dont understand about the stacking ask. Why not just use import-column and export-column? You get everything on a single line which I think is what you want no? The whole point of the import/export column is to collapse the two into one to reduce width.

The bit about horizontal vs vertical stacking with the old skool set was more an observation that it didn't work whereas when old skool was set, it did align horizontally.
So yes I swapped back to the two separate columns. I had it on the combined column with pills not stacked just because it looked best to me. Maybe same screen size as two columns, I didn't measure it

[pacemaker82]

@gcoan @PianSom how's this for choice? You can do it with any column you choose, I just chose SOC and Status

[gcoan]

that would be perfect thanks @pacemaker82
As I said I probably only was looking for SoC and Status to be old skool as they are the fields I like to stand out.

Need to wean myself off having the export column shown as I'm now on the fixed 15p rate I don't really need to see it all the time

[PianSom]

Looks great - thanks!

Yeah, I just turned it off too @gcoan

[gcoan]

Heads up @pacemaker82

[pacemaker82]

Thank yeah all seems fine. Will ship this latest version with custom columns tomorrow.

[gcoan]

I wasn't sure what the changes were. The new predbat Seems to be working ok for me with the plan card

[pacemaker82]

something to do with iBoost - but I didnt see any change. Will keep fingers crossed.

[pacemaker82]

@gcoan @PianSom Check out version 1.4.0

Supports custom column override for the original plan. Example YAML is in the readme. Using the old_skool setting is ignored if you only override specific columns with the new feature.

[pacemaker82]

i'll see whats happening there with the row height - can you send me your YAML?

The readme looks updated to me (last update was 1 hr ago) https://github.com/pacemaker82/PredBat-Table-Card/blob/main/README.md

[pacemaker82]

@gcoan nevermind I found the issue - that octopus agile card was somehow overriding the padding setting. I've ensured that's now overridden by my CSS to 0px and it fixed it.

Release 1.4.1 is available now.

[gcoan]

I put 1.4.1 in and it looks the same.

Heres my yaml. I tried it on a dashboard with only the new card and same thing

type: custom:predbat-table-card
entity: predbat.plan_html
columns:
  - time-column
  - import-column
  - soc-column
  - state-column
  - limit-column
  - pv-column
  - load-column
  - cost-column
  - total-column
old_skool_columns:
  - soc-column
  - state-column
odd_row_colour: '#181f2a'
even_row_colour: '#2a3240'
table_width: 100
fill_empty_cells: true
stack_pills: false

It must be that HACS is caching the readme in HA because the readme was unchanged. I went back in to get a screen shot and its just updated!

[pacemaker82]

hmm ok. Are you testing this in the app on iPad or via browser?

[gcoan]

HA companion app on an ipad

Here's the card on the same dashboard as octopus and Trefor's:

And its slightly better if its on a dashboard on its own, but still raised a bit above the single line of Trefor's.

I thought it might be the PV or limit icons, but changing those to old skool didn't make any noticeable difference

[pacemaker82]

@gcoan I have pushed 1.4.2

This has adjusted the LIMIT iconography canvas size to allow for a row height of 28px. That is the minimum I'm comfortable going with. If I match trefor at 26px, the limit icons have no row padding and it looks naff. To make them smaller looks bad / hard to read. So I'm gonna stick with 28px as minimum.

Side by side when I compare trefor's and mine, I lose 2 half hours slot at the page break... the cost of doing business I'll put that down to :)

[PianSom]

I am a big fan of the old-skool column options and I am happy to report that I now use your card by default. I actually find Trefor's less easy to use now.

Couple of small things on my iPhone (old-skool cols being social, PV, state and import):

• no gap between total cost and import when import is at its widest
• "Discharge" creeps into yellow when there is a joint spot

(All fine on laptop btw.)

I wonder whether it might be better to contract "Charge" and "Discharge" to "Chg" and "Dchge" for a phone screen?

[gcoan]

@gcoan I have pushed 1.4.2

This has adjusted the LIMIT iconography canvas size to allow for a row height of 28px. That is the minimum I'm comfortable going with. If I match trefor at 26px, the limit icons have no row padding and it looks naff. To make them smaller looks bad / hard to read. So I'm gonna stick with 28px as minimum.

That's a lot better @pacemaker82, happy with that now

[pacemaker82]

Couple of small things on my iPhone (old-skool cols being social, PV, state and import):

• no gap between total cost and import when import is at its widest
• "Discharge" creeps into yellow when there is a joint spot

@PianSom I published Version 1.4.3 which fixes these. It will force the width of the table to be a little bit wider on mobile phone but makes it more readable.

[pacemaker82]

@gcoan @PianSom what are your thoughts on replacing the horrible arrows in trefor's plan (that appear on phone/tablet) with mdi:icon library? So keeping the coloured style you like but replacing the ↘↗→ arrows with something less ugly

Effectively replace these:

With these:

[PianSom]

SO much better.

Why are the double headed horizontal arrows grey? Is that a feature or a bug?

[pacemaker82]

it was a feature, as they are basically meaning "nothing is happening", similar to the "-" where there is no data.

I have ramped the opacity down on them. This is what it looks like at same opacity:

[PianSom]

Me, I prefer the same opacity. The shape says it all

[pacemaker82]

OK will go with it. V 1.4.4. is available now

[gcoan]

I definitely prefer these new mdi arrows. Think maybe just an arrow to the right for no change rather than the double header arrows might look less fussy

[gcoan]

The conditional card is a useful trick, now got a narrower version of the card for use on my mobile with the wider for iPad / PC

The mobile screen is formatting though on 2 rows now whereas yesterday it wasn't. It must be very close on the row width because if I delete pv for example it goes back to single height row (yesterday pv was shown ok on the single row)

I wonder if the sun symbol could be omitted on mobiles or the space between sun and pv figure reduced
And if space between the cost arrow and total cost reduced?

I have defaulted to this being my primary plan card for predbat 👍

[pacemaker82]

I've tightened up the icons in the current new release 1.4.7

The cost column is impacted (so is anywhere an mdi:icon is used). However @gcoan you are seeing a lot of width there because further down the content is filling it up. Usually around 23:30 there is a big cost incl standing charge which makes the entire column wide. Not much I can do about that. What I have done is remove any white space in the costs so "+5 p" is now "+5p", as well as bringing the icons in tighter too.

[pacemaker82]

as I said above, the time is being forced to shrink to two lines because the columns are too wide for the screen in portrait. Landscape they fit within the screen so no need for the time column to squash and force it to two lines.

[pacemaker82]

my own card version in portrait. I have enough width with the columns I use to keep it all on one line.

[gcoan]

I'm just being greedy in wanting to see more...

I fixed it, now all on one line in portrait with the same columns

I changed the predbat code to replace the space between day and time (which is where it was line breaking) with  

Hack but it worked

[pacemaker82]

Hah, thats one way. I added a secret YAML for you:

force_single_line: true

https://github.com/pacemaker82/PredBat-Table-Card/releases/tag/v1.4.9.1 available now

[gcoan]

The secret hack works. I reverted the predbat code and put 1.4.9.1 in and it displays perfectly on one line now.

Can't see anything obviously squashed either 👍

[gcoan]

@pacemaker82 I've added details of the Predbat table card to the Predbat documentation

Draft here https://github.com/gcoan/batpred/blob/main/docs/predbat-plan-card.md

[pacemaker82]

Thanks @gcoan - i was wondering if that was something that could be done, but not sure how trefor feels about such things! Anyway, thanks for adding it, will see if the PR gets accepted :)

[gcoan]

I thought it should be signposted.

Trefor seems quite relaxed about changes I make to the documentation

[pacemaker82]

@gcoan looks like Trefor made his own addition in the latest predbat release: springfall2008/batpred@a3c5a1d

Either way its great to be linked up

[gcoan]

Yes I saw that in the release, great recognition.
👍

[PianSom]

Here's a thought - would it be possible to turn the time/day field into a button, clicking of which would cycle between

• charge for this slot
• discharge for this slot
• idle for this slot
• reset

So must a new implementation of the manual over-ride functionality, on a slot by slot basis.

[pacemaker82]

you want it to actually control predbat and set manual overrides?

[PianSom]

I want it to use the Predbat manual overrides - https://springfall2008.github.io/batpred/customisation/#manual-control

So still Predbat, but a more intuitive selection method

[gcoan]

I want it to use the Predbat manual overrides - https://springfall2008.github.io/batpred/customisation/#manual-control

So still Predbat, but a more intuitive selection method

that would be nice, the current approach if you want to set multiple overrides is a bit clunky.

I've also noticed if you set say two overrides one after another than predbat misses the second override and you have to select another then cancel another to get it to notice the change. This is probably just due to the way predbat is triggered on a control change though

[pacemaker82]

@PianSom

It took a while, but I have now supported this ask in Version 1.7.2 using the options-column in columns. Check out the readme for more. Enjoy!!!

[gcoan]

I don't see the tooltips working when viewing the card on my ipad in the companion app. Using old school for soc and status, new style for everything else.

Pressing on Charge, Discharge and FreezeDis, nothing happens 🤷‍♂️

[pacemaker82]

Tooltips dont appear on iPad or iPhone because they are expecting mouse over event, not a press (its using the HTML "title" tag). Tooltips appear on hover over which you cant do with a finger on touch device.

[PianSom]

All gone horribly badly with the latest update ...

[pacemaker82]

bit dramatic :) but yes, not ideal - am pushing a fix now

[PianSom]

New suggestion (asking for a friend!) - if Holiday days left > 0 then it would be good to have Holiday days left displayed at the top of the table (alongside last update time). Useful reminder

[robyholmes]

Just come across this card after reading back some of the release notes on Predbat. Really liking the card, but my only thing I'm missing currently (As mentioned above) is the blocks of colour for states. I don't really want to use the old school columns setting if I can help it, as the icons and width of the new column is much better.

So would it be possible to colour the background of the state cell? So green for charging for example, with the icon still shown in the cell itself. This would then create the blocks of colour as found on the old plan, but only in the narrow states column.

[gcoan]

Change Predbat and Predbat table card to use a dedicated plan data entity

At the moment the Predbat table card reuses the predbat html output that is really designed for easy display on a dashboard.
This means a lot of re-processing of the data (e.g. unpacking combined rows) and as has been demonstrated with the recent Predbat 8.1.0 upgrade, is fragile to any changes Trefor makes.

It was raised as a feature request on Predbat previously but didn't go anywhere, but I think we ought to put effort in to creating a dedicated data structure of the data plan, that Predbat writes and the table card can read.

Was thinking that a json structure would be a good structure that could stop this fragility, that could be extendable with new attributes if ever wanted but would mean that such extensions didn't break the existing working card.

Something like:

{ "header":
 [ {"date-time": "2024-01-25 12:34:00",
    "version": "v8.2.0",
    ...
   } ]
  "data-block":
 [ {"row":
   [ {"time": "11:00",
      "import": "10.02",
      "import-loss": "11.35",
      "export": ....
     ...
      } ]
    {"row":
    [ {"time": "11:30",
     ....
      } ]
  ]
}

Would probably want to shorten the tag names to reduce the object size. Whether this is written as an additional attribute to the existing predbat_plan object, or to a file, TBD.
Wouldn't be any formatting in the data structure, just content, all formatting done by the table card or any other front end component.

Don't know whether JSON is the right structure but whatever is easier to write, re-read, and must be extensible without breaking.

What do people think? Anyone fancy coding this up?

[divenal]

I can have a look at whether I can work out how to do this, or if someone can give a starter for 10. I understand enough of the Predbat code and can insert it in, it's just the mechanics of creating and streaming json objects in python I don't have the experience of...

I think you just construct it as a (nested) python dictionary, and then the JSON module can turn that into a JSON string.

[magicmonkey]

I've opened a PR for the start of this : springfall2008/batpred#1288

[gcoan]

I've opened a PR for the start of this : springfall2008/batpred#1288

Great news, I was thinking about this the other day and how I might go about tackling it. Do you have an example of the json it produces?

[magicmonkey]

Good point! I've added an example in the PR comments. There are definitely improvements which could be made, but I wanted to get the ball rolling.

[magicmonkey]

I've been pulling out a single entry from it using something like this curl command:

curl -s -H 'Authorization: Bearer <REDACTED>' http://<IP>:8123/api/states/predbat.plan_json | jq -r '.attributes.json' | jq '.slots[] | select(.rate.start == "Sun 13:00")'

[Tangiers2020]

Just wondering, is it possible to think about adding a 12hr clock, not that i cannot read the time, but my brain works better with 12hr :-) also it will then match my agile card :-)

[gcoan]

I like the new options-column that has been introduced @pacemaker82 but have some suggestions for further improving it ....

Instead of a row of icons which fills up quite a bit of screen real estate, could we have a single icon that then pops out to the list/row of individual controls? Appreciate this is more complex Java scripting but would mean the option could more readily be incorporated on small displays

The two controls I tend to use the most are not included (possibly due to the above space constraints). Freeze export during the day when I have enough in my batteries and want predbat to export the remainder, and freeze charge (less often this one) overnight to hold the SoC at a particular level and run off grid import. I do use force demand, but force charge/force export I tend to leave it to predbat to control these

[pacemaker82]

Thanks - I got some whack-a-mole to take care of for now:

springfall2008/batpred#2740

But will consider :)

[pacemaker82]

I put in battery_capacity but couldn't get it to work. It was only when I noticed I had soc-column in old-skool-columns and removed it did I get it to work. (Der.)

This will be fixed next time to work in old skool too.

[pacemaker82]

Latest 1.9.x is out now. It's a major refactor of the cell creation code, so there might be bugs.

However, battery % vs kWh should work in both old skool and non. Also, for now I added the battery % as a mouseover of the battery icon - until I think of something else.

I haven't undertaken anything related to "bulk" actions yet, where you select multiple slots and apply a single override to all. TBH I feel like using options-column lets you do that already in the table. It's the same amount of clicks/presses. Maybe there is something where I can show/hide that column from a trigger button somewhere in the header...

[gcoan]

(about half an hour go before I swapped to Cosy for the winter, and its now not so relevant) I'd have liked to have a multiple select on rows to change their action,

but from a UI perspective I can't see how this would easily work

what I did request and @pacemaker82 included, is you can don't have to click the close icon on the popup to then select another time period

so click time period, choose mode
click anywhere on the screen
click next time period, choose mode
click anywhere

etc

its not that many more clicks than a bulk time select and then mode select

[PianSom]

Happy to be out-voted here.

But here's my case: even for a 2 slot choice there is a less-click advantage (which grows as the number of slots chosen increases); though I concede there is a 1-more-click disadvantage for 1 slot. Plus there's the fact that the Predbat re-calc would also only start once and so the result would arrive quicker.

Current 2-slot clicks: select time slot 1, select mode, click away, select time slot 2, select mode, click away = 6 (3n)
Proposed 2-slot clicks: select time slot 1, select time slot 2, click action button, select mode, click away = 5 (n+3)

[gcoan]

I was looking at the plan just now, and considering that rather than SoC %, the plan would in many respects be easier to read if it were in kWh.

We have PV, Load and Clipping all in kWh but SoC as a % and sometimes I have found myself trying to convert in my head to kWh; which isn't easy with 13.5kWh battery capacity.

Obviously to be able to convert from SoC% to SoC kWh you'd need a parameter specifying of the battery capacity.

Does this have legs? Interest with anyone else?

[pacemaker82]

A user could add a card YAML value of their full battery capacity (in kWh) then could do the maths on the presence of that, converting the % to kWh?

e.g. battery_capacity: 13.5

Let me take a look at how easy that might be - seems like it would be a small change.

[pacemaker82]

@gcoan OK I added that to main too. Pretty quick change.

Just add battery_capacity to the card YAML, use a number/float, not a string otherwise it will fail... e.g mine is:

battery_capacity: 9.523

Result:

[pacemaker82]

My only thought is whether to scrap the "kWh" from the labelling like the other columns. Its obvious its not a % I think...

[gcoan]

My only thought is whether to scrap the "kWh" from the labelling like the other columns. Its obvious its not a % I think...

Agreed, it doesn't add and takes up screen estate.

I was wondering about the precision as well. Is 9.5kWh enough accuracy, do you need to know it's only on 9.51 currently?

[pacemaker82]

I've left it as 2 decimals for now in line with the rest of the columns. Published the release v1.8 as I think we're pretty solid. I might consider a decimal setting for the entire card at some point though so user has choice.