I have a strong mesh wifi of 4 nodes, so I have good reliability also with wifi. Zigbee network is very reliable too.
If monophase, you could also check the Aeotec energy meter, I use their products for zwave, and they’re rock solid.
Good luck.
I was thinking about how you describe the order of import, export and production. To be fair: when I look at how my utilities provider regards my production and consumption, they do exactly as my setup is now. They show me how much i provide to the grid and how much I take from it. In fact, i don’t necessarily consume the power generated by my own solar panels. That would only apply if i would store my power in batteries and use it, switch to grid when I have a shortage of power.
I am not trying to correct you, just explaining my train of though and checking whether my logic is correct. Is it? It might just be different in my country…
export is the energy produced not consumed locally.
import is the energy you buy from the utilities company
production is the energy produced by your PVI.
It’s like this everywhere. What changes in some countries are the incentivation schemes, not the definitions.
that sounds really clear 
thanks for the clarification
no problem, sorry if I’ve not been clear enough in my first reply. if you read it again, taking into account the definitions,maybe it will be more clear. 
My electricity meters send via MQTT and I also have the problem that “last_reset” is not accepted in MQTT.yaml but is required when creating the sensor.
I created the fake sensor but "last_reset_topic: ‘fake/last_reset’ " is not accepted in the energy board, there it wants last_reset…
What should I do?
It’s a drama! 
you should be using the correct classes for power and energy sensors, and not bother with the last_reset any longer
<<: &energy
unit_of_measurement: kWh
<<: &value
value_template: >
{{value|round(2,default=none)}}
device_class: energy
state_class: total_increasing
qos: 1
and
<<: &power
unit_of_measurement: W
<<: *value
device_class: power
state_class: measurement
qos: 1
should do it. you can take out the yaml anchors, but I use these to repeat that code easily, like
*power
and
*energy
Hello everyone,
Now, for the first time in my life, I have to post a question in a forum, but Home Assistant is forcing me to do so.
I currently have the following problem and I just can’t solve it:
I have a FENECON inverter.
This sends the data to HA via the Modbus interface.
Now I need the values of the producer and the consumer in kWh for the Energy Dashboard. For this I use the well-known Riemann sum integration.
The “new” sensors generated by this in kWh also worked at the beginning. After some time (possibly due to an update in HA) the sensors showed NAN kWh. I still can’t solve this error! Now, for the sake of simplicity, I simply copied the sensor and appended v22 as a suffix. Lo and behold, this sensor works too. Now I’m at my wits end.
Now i have read that you have to set the last reset attribute of the sensor. I just don’t know how to do that. it always produces a syntax error.
I also have sensors in the modbus interface, which are positive when loaded and negative when unloaded, for example. I divided this sensor into two individual sensors using a template. these individual sensors in turn go into a Rieman sum sensor. Surprisingly, these have worked flawlessly since the beginning without any problems. Do I have to label the behavior as a bug or is there actually a solution to my problem?
finally one more question:
the modbus interface also supplies accumulated values. For example, the generator output in kWh since installation. Totally increasing, so to speak. can i not use these sensors for the energy dashboard? I would have already tried that but it says: attribute last reset is missing
but how can I set the attribute in the modbus interface? there are always syntax errors here!
Here one more picture from the modbus sensor
Here the picture with the two Rieman sum integration sensors.
The one with v22 function. the other one dose not
Don’t mess with templates and +/- values of a single sensor. Since you have them available, use the accumulated sensors for the energy integration, but you have the wrong state_class for accumulated sensors (you have measurement). Accumulated sensors are TOTALS, and since the’re always increasing, use state_class: total_increasing
source docs: Sensor Entity | Home Assistant Developer Docs
Hey Alex,
thank you very much for your help! I set up the energy sensors from the modbus interface with total_increasing instead of measurement. Now the energy dashboard accept the sensors. I will wait a day to see if the values in the dashboard are the same like with the Rieman sum integral. If this works it will make my stuff much more easy.
Thank you for the very quick help.
glad to be helpful to you.
regarding the integral sensors utility meter sensors: I use them only to compute daily, weekly, monthly, yearly data, for the energy integration if you have the accumulated sensors keep using those, because it’s data coming from the device directly.
could you send me a example of those template sensor? Wy you do not use the utility meter?
sorry, when I said integral sensors, I meant utility meter sensors.
Here’s my example (the sensor.e4u_* are the cumulative sensors created by a Node-Red flow for my Elios4You three-phase energy meter):
# E4U Meter Sensors (Node-Red flow)
utility_meter:
total_energy_autoconsumption:
name: Total Energy Autoconsumption
source: sensor.e4u_energy_autoconsumption
hourly_energy_autoconsumption:
name: Hourly Energy Autoconsumption
source: sensor.e4u_energy_autoconsumption
cycle: hourly
daily_energy_autoconsumption:
name: Daily Energy Autoconsumption
source: sensor.e4u_energy_autoconsumption
cycle: daily
weekly_energy_autoconsumption:
name: Weekly Energy Autoconsumption
source: sensor.e4u_energy_autoconsumption
cycle: weekly
monthly_energy_autoconsumption:
name: Monthly Energy Autoconsumption
source: sensor.e4u_energy_autoconsumption
cycle: monthly
yearly_energy_autoconsumption:
name: Yearly Energy Autoconsumption
source: sensor.e4u_energy_autoconsumption
cycle: yearly
total_energy_consumption:
name: Total Energy Consumption
source: sensor.e4u_energy_consumption
hourly_energy_consumption:
name: Hourly Energy Consumption
source: sensor.e4u_energy_consumption
cycle: hourly
daily_energy_consumption:
name: Daily Energy Consumption
source: sensor.e4u_energy_consumption
cycle: daily
weekly_energy_consumption:
name: Weekly Energy Consumption
source: sensor.e4u_energy_consumption
cycle: weekly
monthly_energy_consumption:
name: Monthly Energy Consumption
source: sensor.e4u_energy_consumption
cycle: monthly
yearly_energy_consumption:
name: Yearly Energy Consumption
source: sensor.e4u_energy_consumption
cycle: yearly
total_energy_production:
name: Total Energy Production
source: sensor.e4u_energy_production
hourly_energy_production:
name: Hourly Energy Production
source: sensor.e4u_energy_production
cycle: hourly
daily_energy_production:
name: Daily Energy Production
source: sensor.e4u_energy_production
cycle: daily
weekly_energy_production:
name: Weekly Energy Production
source: sensor.e4u_energy_production
cycle: weekly
monthly_energy_production:
name: Monthly Energy Production
source: sensor.e4u_energy_production
cycle: monthly
yearly_energy_production:
name: Yearly Energy Production
source: sensor.e4u_energy_production
cycle: yearly
total_energy_export:
name: Total Energy Export
source: sensor.e4u_energy_export
hourly_energy_export:
name: Hourly Energy Export
source: sensor.e4u_energy_export
cycle: hourly
daily_energy_export:
name: Daily Energy Export
source: sensor.e4u_energy_export
cycle: daily
weekly_energy_export:
name: Weekly Energy Export
source: sensor.e4u_energy_export
cycle: weekly
monthly_energy_export:
name: Monthly Energy Export
source: sensor.e4u_energy_export
cycle: monthly
yearly_energy_export:
name: Yearly Energy Export
source: sensor.e4u_energy_export
cycle: yearly
total_energy_import:
name: Total Energy Import
source: sensor.e4u_energy_import
hourly_energy_import:
name: Hourly Energy Import
source: sensor.e4u_energy_import
cycle: hourly
daily_energy_import:
name: Daily Energy Import
source: sensor.e4u_energy_import
cycle: daily
weekly_energy_import:
name: Weekly Energy Import
source: sensor.e4u_energy_import
cycle: weekly
monthly_energy_import:
name: Monthly Energy Import
source: sensor.e4u_energy_import
cycle: monthly
yearly_energy_import:
name: Yearly Energy Import
source: sensor.e4u_energy_import
cycle: yearly
Hi, can anyone help me to get the Fenecon Inverter and Battery intergrated into HA?
THX Michael
Is it possible to customise the energy-devices-graph card, beyond limiting it to a maximum number of devices?
I would like to be able to specify a custom (shorter) name for each entity.
Hey Max
Did you find a solution for the inverter?
I have the same inverter
Hi! I have exactly the same, my inverter is Daxtrom-Power 10.2kW hybrid 2MPPT model. It uses the SmartESS app and have a website Dessmonitor
Can I somehow import the data automatically into HA?
My inverter has an ethernet port, there is connected the WIFI-Plug datalogger now.
I would be very-very thankful if you could help me out!
1 Like
I have the same question! But seems there is still no solution related to integration with “Smart ESS” / “dessmonitor.com” platform.