South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I added the helpers in the UI and then added device_class in my customizations YAML.What did you exactly do?
View attachment 1349598
I need to sit down and read @SauRoNZA post from a few days. I think I still have some other work to do first. Sucks not having enough time to read.
What did you exactly do?
View attachment 1349598
I need to sit down and read @SauRoNZA post from a few days. I think I still have some other work to do first. Sucks not having enough time to read.
sensor: !include sensors.yaml
- platform: integration
source: sensor.geyser_power (<<<<<< CBI Bathroom Geyser - Power)
name: geyser_energy
unit_prefix: k
round: 2
method: left
sensor.geyser_energy:
device_class: energy
GUI is crazy easy. Settings -> Devices and Services -> Helpers -> Create Helper -> integration - Riemann sum.What you have there is just the source of the sensor.
You need one that reads in kWh, as in consumption over time…not in real time.
So you'll need something like this in YAML (your on your own in the GUI I'm afraid)
configuration.yaml
sensors.yamlCode:sensor: !include sensors.yaml
customize.yamlCode:- platform: integration source: sensor.geyser_power ( name: geyser_energy unit_prefix: k round: 2 method: left
Code:sensor.geyser_energy: device_class: energy
GUI is crazy easy. Settings -> Devices and Services -> Helpers -> Create Helper -> integration - Riemann sum.
Exactly, last week I created 4 Riemann sum helpers for my four Astutes (Left, 2 decimal, hour). They then appeared for use inside Energy dashboard (without me needing to touch YAML).
What didn't happen was that it was not resetting on a daily basis. The kWh usage was increasing daily.
Today, I have deleted all the helpers, and created again with a different name. Also added them to the customisation.yaml file as recommended by @SauRoNZA . Now just waiting to see when the energy data pull through. Thanks so much!!
I used the same graphs I had for my sonoff - just changed sensor to the CBI one. But when it was using the sonoff sensor, it only showed for the day , hence I thought I did something wrong.It's normal for the sensor to do that, it doesn't reset daily it's always a total.
The Energy Dashboard should reset it and give you the stats breakdown as you like it.
My Geyser sensor is at 1,621.25 kWh, whereas my Energy Dashboard usage for the day is 10.4 kWh






@TedLasso Just to confirm, you did bridge the two mqtt brokers?
https://solar-assistant.io/help/home-assistant/broker-setup
Just had a quick look at my setup, I had to add a additional folder (conf.d) before the solar_assistant.conf
View attachment 1350044
View attachment 1350046


So did I add the file yesterday too following that guide (but never saw the conf.d reference) ... mines as it is now - > Mines is running the official image in a VM so perhaps there could be a slight difference
192.168.2.2 (is my HA box)
View attachment 1350066
The one difference is I never added the port after the IP (192.168.2.8 is the SolarAssistant Pi) like you did because the guide didn't mention it but now have done that and reboot the HA
View attachment 1350072
Will see if that works. If not, I will then add the conf.d folder before it.
Thanks for the extra hints!
Edit: I just noticed something else. In the guide they say the file is supposed to be called solar_assistant.conf . You also refer to it as such, but your screenshot has it as solar-assistant.conf ...


Just double check your mosquito broker in HA and remember to restart the broker. I dont think the file name makes a difference as long as it ends in ".conf"
View attachment 1350104
You can also try http://mqtt-explorer.com/ its a pretty nice free program
View attachment 1350112



It should be the one in addons, not the one in devices. The one in devices only acts a connector to the mqtt server (the one in addons).can't seem to find on the MQTT broker on HA is the customize button (where you see the folder name i.e. mosquitto/conf.d) <-- There seems to be no option to set that using this one
It should be the one in addons, not the one in devices. The one in devices only acts a connector to the mqtt server (the one in addons).
addons>mosquito broker>configuration





To me it looks like HA is showing more up to date values.So I noticed what I think is an oddity in Solar Assistant stats and what it sends to HA:-
From Solar Assistant: (Yes, bad PV Generation day)
View attachment 1350414
In Home Assistant:
View attachment 1350418
Load Energy is sum total for the day: 17.3kWh - I think. It probably is the net across Grid/Battery/PV - I guess it subtracts from when battery is used?
But "Grid In" is showing as 15.5 in HA but on solar assistant it is showing as 13.1 ? Surely Grid-In was supposed to show 13.1 too?
I understand Solar assistant does not count the power used by inverter, and efficiencies in battery charge/discharge but do you see the same discprepancy? I am trying to get HA to show me actual power used from Eskom. I assume it has to be the value as shown on the Solar Assistant site itself i.e. "Grid Used"
Cheers
maybe its covered by this?So I noticed what I think is an oddity in Solar Assistant stats and what it sends to HA:-
From Solar Assistant: (Yes, bad PV Generation day)
View attachment 1350414
In Home Assistant:
View attachment 1350418
Load Energy is sum total for the day: 17.3kWh - I think. It probably is the net across Grid/Battery/PV - I guess it subtracts from when battery is used?
But "Grid In" is showing as 15.5 in HA but on solar assistant it is showing as 13.1 ? Surely Grid-In was supposed to show 13.1 too?
I understand Solar assistant does not count the power used by inverter, and efficiencies in battery charge/discharge but do you see the same discprepancy? I am trying to get HA to show me actual power used from Eskom. I assume it has to be the value as shown on the Solar Assistant site itself i.e. "Grid Used"
Cheers

Is anyone using the Solcast forecast integration? I've managed to get the integration installed, but it doesn't pull in any data.
EDIT: found the issue. I was using the API url shown on solcast and not the key.
