Inability of Home to display a sensor value, but the sensor can be displayed as secondary value

[EPeterE]

Hi
I am not sure what I am doing wrong. I have created a sensor value "Home consumption" which is the power generated by the PV system subtracting the power from the battery. I require this since my invertor and controller uses power which is not recorded. So I would like the primary "Home" value to reflect the value of this sensor. However, the flow card doesn't display the value. The sensor can be displayed as a secondary value, but then the flow chart is incorrect since I assume it is based on the primary value. Is there anyway to correct this?

So in the evening, the PV generated is zero and the battery is discharging so the value for the Home Consumption sensor is 0--466W=466W and not the displayed value of 0. Due to the display showing 0, the flow card flow lines are wrong too.

The secondary value is showing the sensor value correctly.

And the sensor is created as a helper

Thanks

[gcoan]

In my use of this card I don't create a home sensor, I let the card work out what the home consumption is based upon the other sensors. I have grid, battery and solar defined and the home is worked out automatically.

I also think your home sensor is wrong as its not taking account of any grid import or export. If you want to create a template home sensor then it should be:
import - export + battery discharge - battery charge + solar generation

import - export might be a single grid sensor and battery discharge - battery charge again might be a single battery power sensor

But as I said, you shouldn't need to do this for the card to work correctly. I'd also caution about creating a sensor like this because you will end up with an awful lot of (not very useful) data stored in your home assistant database. Every single watt of power change for your battery charge/discharge, grid import/export or solar generation will result in a change of state of the template sensor and a new record in the HA database. You'll bloat your database unnecessarily.

[EPeterE]

On Wed, 23 Oct 2024 at 19:35, Geoffrey Coan ***@***.***> wrote: In my use of this card I don't create a home sensor, I let the card work out what the home consumption is based upon the other sensors. I have grid, battery and solar defined and the home is worked out automatically.

Unfortunately, my Victron system doesn't create a total home consumption value since it forgets to account for the losses of running the inverter and associated Victron system (typically 100-200W). Hence the reason for the sensor which I have created.

I also think your home sensor is wrong as its not taking account of any grid import or export. If you want to create a template home sensor then it should be: import - export + battery discharge - battery charge + solar generation

I am off grid so GRID is always = 0, so my proposed sensor gives me the correct value. The power-flow-card draws the GRID and the line from the BATTERY to the GRID should not exist since there is no path there. The battery is discharging and should be recorded as consumption under HOME, and the line should be drawn from the BATTERY to HOME, not from BATTERY to GRID. I assume if the primary HOME value recorded the value of my sensor, the flow would be correctly plotted.

import - export might be a single grid sensor and battery discharge - battery charge again might be a single battery power sensor But as I said, you shouldn't need to do this for the card to work correctly. I'd also caution about creating a sensor like this because you will end up with an awful lot of (not very useful) data stored in your home assistant database. Every single watt of power change for your battery charge/discharge, grid import/export or solar generation will result in a change of state of the template sensor and a new record in the HA database. You'll bloat your database unnecessarily.

So how do I get the HOME icon to use my sensor value as the primary input?? That is really what I need to know. I take your point ref the data. I didn't realise it was stored and I know no other way of subtracting PV-BATTERY as I require without using a sensor. Thanks

…

— Reply to this email directly, view it on GitHub <#719 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFINAWBH4RXB5IB7QHD43PLZ47M6HAVCNFSM6AAAAABQPJYUFSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBTGIZTEOA> . You are receiving this because you authored the thread.Message ID: <flixlix/power-flow-card-plus/repo-discussions/719/comments/11032328@ github.com>

[gcoan]

So how do I get the HOME icon to use my sensor value as the primary input?? That is really what I need to know.

I'm sorry I don't know how to do what you want. It might be that the card doesn't anticipate off grid connections which is why it's drawing unnecessary lines.

I take your point ref the data. I didn't realise it was stored and I know no other way of subtracting PV-BATTERY as I require without using a sensor. Thanks

It does unfortunately and I've been finding myself just how much data does get held in the state and state attribute tables.
One way to reduce the volume of data is to use a time based trigger template. Trigger say every minute to calculate the sensor value rather than trigger on every single underlying state change. This is the approach I've taken to reduce my data storage of a similar home consumption sensor I have in HA