What do need to do to be able to add this to the new Energy feature in HA?
When I try to add “Grid consumption” I only get "No matching statistics found.
I read in the forums that I needed to add the following to my “Total Consumption” for HA to recognize it as an energy entity:
last_reset: '1970-01-01T00:00:00+00:00'
state_class: measurement
device_class: energy
But when I do I get the following error:
ERROR (MainThread) [homeassistant.config] Invalid config for [sensor.template]: [attributes] is an invalid option for [sensor.template]. Check: sensor.template->sensors->shelly_3em_power_total->attributes. (See /config/configuration.yaml, line 481). Please check the docs at Template - Home Assistant
wow that was fast, thanks!
However I get the following error now:
ERROR (MainThread) [homeassistant.config] Invalid config for [sensor.template]: [state_class] is an invalid option for [sensor.template]. Check: sensor.template->sensors->shelly_3em_power_total->state_class. (See /config/configuration.yaml, line 481). Please check the docs at Template - Home Assistant
Never tried that integration before. It works flawlessly! Thank you very much.
Now I just need to find a way to get a “Total” value too but I think I saw someone in the forums that did just that.
ah that’s where I saw it.
Just one last question then. Where do I put this?
If I put this in configuration.yaml it says: Setup failed for consumed_energy: Integration not found.
So I’m guessing I should put this under sensors: somehow but I can’t figure out how.
I’m now far from sure that you should divide with SQRT(3) to get the right consumption. Got an hourly .csv file from my electric company and it showed actually that just summing should be the way to go.
The difference is ~70% so it should be quite easy to see the right amount. In my case I’m a little bit worried that my Solar inverter might mess something up since I got very bad power factor values according to EM3 (as low as 25% on one phase).
I own a Shelly 3EM for about a month now and yesterday I had that spike problem.
The topic was discussed here and in some other threads but I think there are situations not taken into account.
Earlier here you talked about inconsistent connections but this also happens if I reboot the 3EM or if I have to reboot my WLAN APs because of a firmware update, which lead to my first meeting with this issue yesterday.
So in real life a stable connection is what you want but you have events where you have to disconnect the device.
There must be a better solution than switching to MQTT for example and take care of filtering that on your own or creating own sensors trying to do what a utility_meter does with just a few lines of code just to get rid of events that occur sooner or later in every installation.
I have to restart HA on every update, on some config changes, this is a living system. Also I have to update my APs or I have a power outage of an AP. And this will break all of my statistics?
Ok well I found a fairly simple solution for now based on all the threads.
I added one “filtered” template sensor to filter unwanted values from the Shelly 3EM real sensor:
template:
- sensor:
- name: nh_energy_channel_a_energy_filtered
unique_id: nh_energy_channel_a_energy_filtered
unit_of_measurement: kWh
device_class: energy
state_class: total_increasing
state: >
{% set state = states('sensor.nh_energy_channel_a_energy') %}
{% if (is_number(state)) and state | float(0) > 0 %}
{{ state }}
{% else %}
{{ None }}
{% endif %}
availability: >-
{{
is_number(states('sensor.nh_energy_channel_a_energy'))
}}
I created this for each channel. I am going to bind this “filtered” sensor now to my utility meters which should then compensate what happens when the 3EM get rebooted or something else happens…
