Add grid_to_battery to grid_consumption in kW display about tesla-style-solar-power-card

[reptilex]

This is an issue with your sensors. My sensor does this on it's own so if you are having this issue you might need a template sensor

[MindFreeze]

The thing is I often have grid_to_battery but 0 grid_consumption. This is just my use case. I can charge the batteries with the grid being otherwise cut off.
So if do the addition in my sensors, the lines wouldn't make sense.

[reptilex]

I think I did not understand your problem in the first place. What is wrong in the display currently? can you tell me your data and maybe post an image? I thought your icon was showing the wrong sum. This could be handled with a third sensor (template sum sensor) for that icon. But it seems I misunderstood

[MindFreeze]

https://pasteboard.co/JMdkvef.png
This is what I would get even though I have 1kw going to the battery. It is not calculated in the battery display or the grid display.
If I add that to grid_consumption, it would show proper kW for the grid. But if I my grid_consumption is otherwise 0, it would show a line going to the house which would be wrong.

You are right that the grid part can be handled with a new sensor like totoal_grid_consumption similar to solar_yield. But that would still leave the battery kW wrong.

[MindFreeze]

IMO the new sensor path is redundant and so it the solar_yield sensor. After all, it is just solar_consumption+battery_charging.
If we define the power over all the paths, we can easily calculate the kW that should be displayed in the icons.

[headbouyJB]

solar-yield may also include solar that you're exporting, as well as consumption and battery charging.
I spent far too long trying to work out the logic to calculate the required sensors based on the sensors I have available :-D

It looks like I have this working so far, the only thing I believe is missing is battery to grid.

[reptilex]

Well there is a battery to grid line, and if your consumption shows battery to grid, then you should be having that too.

[reptilex]

About the redundancy, you might be right. But I have them because my solar meter shows the actual yield without losses. But I'm thinking whether this should be left out in the next iteration.

[headbouyJB]

Well there is a battery to grid line, and if your consumption shows battery to grid, then you should be having that too.

Ah OK cool! - reading through your list of sensors, there didn't seem to be a battery-to-grid option.
Can the grid-to-battery be negative then?

[reptilex]

Done in beta! But you would need to either checkout the beta branch or at least the binary or try a beta installation through HACS. But it would be a great help if you could test it. As soon as a few people do this is going to become the main branch.

[headbouyJB]

OK so I thought I'd give the beta a go via HACS - but I'm not getting anything displayed at all.
Have restarted, everything is updated, and the badges display the correct values for the sensors I'm attempting to use.

Is there something simple I'm missing here?

[MindFreeze]

Open dev tools and look for errors in the console. I've never seen this behavior.
It could be a cache problem.

[headbouyJB]

I see the same result in Safari and Chrome, even after clearing caches and refreshing.
My logs only have normal HACS custom component warnings.

I haven't used the dev tools and console before - is there a quick guide available so I can be helpful please?

Also with the same configuration the card does display in the iOS app, but not all the values are coming in.

[reptilex]

strange, will do some more testing this evening and get back to you asap

[MindFreeze]

@reptilex I had a similar problem with the values after updating and it was caused by the new epsilon rounding. I have it commented on my install only, because I thought the problem was on my end, but maybe it isn't just me.

[reptilex]

If the problem with the rounding persist, please open a new issue. I tried replicating it, but although sometime I got really long float numbers I never had a 0 problem. The feature request is implemented in latest breaking config release. ;)