@Mariusthvdb Your solar energy sensor should have a positive value. Maybe you did ‘solar_midnight_energy minus solar_actual_energy’ instead of ‘solar_actual_energy minus solar_midnight_energy’? If the value is positive (as it should), the icon will turn green and your home energy will have a higher value than your grid energy.
EDIT: You got the point already (saw your EDIT to late)
Going to let it rest for now, but also because I feel this card is heavy on the system. I’m experiencing sudden and long beachballs and the system log/error has returned…
clicking the i in the system tools has my HA instance wait and nothing happens, where that was rather immediate before.
Maybe this second functionality of the card takes a lot of resources ?
Request: please make this double meter sensitive… especially when future use will be calculating costs we need the discernabilty for high and low tariff.
Right now all consumption is added while in real life those tariffs are separated in calculations and costs. That’s why I now have such a long template adding it all together…
The card itself isn’t that heavy. And it’s running in your browser, not in your HA instance. But the set of sensors could be to heavy depending on the way they are configured. You could switch off the card (or the sensors) temporarily to see if it’s the card or the extra sensors. Then you get more information where to improve.
The tip I gave on recorder: will decrease database resources (and also network resources if your db isn’t local) because template sensors based on dsmr sensors will update the db every 10 seconds.
Could you elaborate on how your ‘daystart’ sensors are configured?
Okay, cool. And those sensors aren’t heavy. At least no db queries there.
My own DMSR doesn’t return them directly. I have an automation which saves the current meter counters into a series of input_numbers each midnight.
Aha, I see now. You use these as I use my daystart sensors. I don’t need these input_numbers for that. Luckily
I thought you wanted to save the daily usage/production somehow. Since we’ve disable the sensors_today in recorder, it would be possible to do the same to my sensor.grid_energy_total, save it automatically at midnight in a sensors/input/variable, and have recorder record these values once a day, instead of constantly during the day.
Hope this makes sense…
beware, this is a quick and dirty transplant of one of my other variable automations, so i must still check everything… especially the data_template, which seems a bit useless right now.
Added a quick input_number to it, so recorder can save that too …
I have one question. I’m using the plugin from hass for my solarpanel (sma). This gives values wh en the sun is up, and works fine. At night, the sma plugin gives the status: unknown. Because the power wheel gives with the solar NaN W, but also the home power is now NaN W. (see picture). It should be nice that if the solar is not working or unknown is that the power grid is the home power.
I’d like to keep the code as simple as possible. Instead of taking into account every situation that could occur for an individual sensor, there are some requirements in the readme. Otherwise the card becomes too heavy/slow and/or the code too complex. E.g. the value of the sensor always should be parsable as an int of float. The value ‘unknown’ doesn’t comply to that.
Maybe you already know how to fix this with a derived sensor, but then the explanation below can be useful for other people.
You can create a sensor based on your solarpanel sensor that is complying to the requirements:
Then use the sensor.better_sensor as input for the card. I expect that both solar value and home value in the power-wheel-card will be correct when you do this. It’s because the ‘unknown’ value will be replaced by a zero value.
If you don’t want to record both sensors in your database, you can exclude one in your recorder setting.
best would be when the original sensor wouldn’t return ‘unknown’ of course… maybe you should file an issue at the components GitHub. Even at night/dark the sensor should work correctly and show 0, if no energy was produced.