Energy Spikes #244

jupppo · 2022-11-28T14:56:53Z

jupppo
Nov 28, 2022

Hi everyone,

I am getting sometimes (1-2 times a week) an enormes energy spike in the data. First I thought is is a home assistant problem, but then I catched it in the mqtt stream.
Here is what I get:

['elocalload_tot']	429.496.730,3 kWh
Solar Total	429.496.730,3 kWh
Battery Discharged	429.496.729,7 kWh
Battery Charged	-429.496.730 kWh

Any idea how to prevent this or where its coming from?

Answered by jupppo

Jan 9, 2023

I finally solved the energy spike issue by filtering the mqtt message in the home assistant.
This should be accordingly applied to the templates for homeassistant for each used entity. As soon as I have some time, I will update these.

mqtt:
  sensor:
    - state_topic: energy/growatt
      value_template: "{{ value_json['values']['epvtotal'] | int(0) / 10 }}" 
      availability_template: "{{ value_json['values']['epvtotal'] | int(0) < 200000}}"
      availability_topic: energy/growatt
      payload_available: true
      payload_not_available: false        
      unique_id: growatt_generated_energy_total
      device_class: energy
      unit_of_measurement: "kWh"
      state_class: "total…

View full answer

johanmeijer · 2022-11-28T18:51:11Z

johanmeijer
Nov 28, 2022
Maintainer

Can you retrieve the Grott log information with this failure?

Which version of Grott do you use? The latest version has some code to prevent from processing invalid records.

1 reply

jupppo Nov 28, 2022
Author

Hey Johan,

thanks for the quick reply. Where do I find the logs? I used the lastest version from the beta.

Best
Thomas

johanmeijer · 2022-11-28T20:27:13Z

johanmeijer
Nov 28, 2022
Maintainer

How do you use grott (docker, stand alone)?

1 reply

jupppo Nov 29, 2022
Author

I use stand alone on Debian 11

jupppo · 2022-12-08T12:20:07Z

jupppo
Dec 8, 2022
Author

It looked like it was a firewall problem, when too many messages got out.

0 replies

johanmeijer · 2022-12-08T20:27:11Z

johanmeijer
Dec 8, 2022
Maintainer

/Ok. Are you able to prevent this? Can this being solved

0 replies

jupppo · 2022-12-09T09:58:59Z

jupppo
Dec 9, 2022
Author

so far it looks good. Since 1 week no spike

0 replies

jupppo · 2022-12-19T07:50:23Z

jupppo
Dec 19, 2022
Author

After two weeks my spikes are back :-)

1 reply

jupppo Dec 23, 2022
Author

I got another data spike yesterday. Here is the data from journald:

Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: Dez 22 19:18:15 grott grott[20337]: - Growatt new layout processing
- decrypt : True
- offset : 6
- record layout : T06NNNNXSPH
- Grott data record date/time processing started
- date-time: 2022-12-22T19:17:14
- Grott values retrieved:
- datalogserial : JPC6A296K7
- pvserial : OMCUCDV020
- pvstatus : 6
- pvpowerin : 429496729.5
- pv1voltage : 6553.5
- pv1current : 6553.5
- pv1watt : 429496729.5
- pv2voltage : 6553.5
- pv2current : 6553.5
- pv2watt : 429496729.5
- pvpowerout : -0.1
- pvfrequentie : 655.4
- pvgridvoltage : 6553.5
- pvgridcurrent : 6553.5
- pvgridpower : 429496729.5
- pvgridvoltage2 : 6553.5
- pvgridcurrent2 : 6553.5
- pvgridpower2 : 429496729.5
- pvgridvoltage3 : 6553.5
- pvgridcurrent3 : 6553.5
- pvgridpower3 : 429496729.5
- totworktime : 596523.2
- eactoday : 429496729.5
- pvenergytoday : 429496729.5
- eactotal : 429496729.5
- epvtotal : 429496729.5
- epv1today : 429496729.5
- epv1total : 429496729.5
- epv2today : 429496729.5
- epv2total : 429496729.5
- pvtemperature : 6553.5
- pvipmtemperature : 6553.5
- pvboosttemp : 6553.5
- bat_dsp : 6553.5
- eacharge_today : 429496729.5
- eacharge_total : 429496729.5
- batterytype : 65535
- uwsysworkmode : 65535
- systemfaultword0 : 65535
- systemfaultword1 : 65535
- systemfaultword2 : 65535
- systemfaultword3 : 65535
- systemfaultword4 : 65535
- systemfaultword5 : 65535
- systemfaultword6 : 65535
- systemfaultword7 : 65535
- pdischarge1 : 429496729.5
- p1charge1 : 429496729.5
- vbat : 6553.5
- SOC : 655.4
- pactouserr : 429496729.5
- pactousertot : 429496729.5
- pactogridr : 429496729.5
- pactogridtot : 429496729.5
- plocaloadr : 429496729.5
- plocaloadtot : 429496729.5
- spdspstatus : 6553.5
- spbusvolt : 6553.5
- etouser_tod : 429496729.5
- etouser_tot : 429496729.5
- etogrid_tod : 429496729.5
- etogrid_tot : 429496729.5
- edischarge1_tod : 429496729.5
- edischarge1_tot : 429496729.5
- eharge1_tod : 429496729.5
- eharge1_tot : 429496729.5
- elocalload_tod : 429496729.5
- elocalload_tot : 429496729.5

johanmeijer · 2022-12-24T20:34:38Z

johanmeijer
Dec 24, 2022
Maintainer

Hmm not oke. Maybe we can try to build in some kind of filter in Grott. Let me think about it.

0 replies

johanmeijer · 2022-12-24T20:39:17Z

johanmeijer
Dec 24, 2022
Maintainer

Kan you send the hex growatt original data from the log? pvstatus = 6 is not what I expect for a SPH (I think).

1 reply

jupppo Dec 25, 2022
Author

Merry Christmas Johann,
Unfortunatly I dont have the Hex Part anymore. I Just keep a few days of log. next time I save the whole Part.
PV Status 6 ist Battery Operation Mode in the SPH.

Best

gaoxuannuli · 2022-12-29T00:43:07Z

gaoxuannuli
Dec 29, 2022

这是来自QQ邮箱的假期自动回复邮件。您好，您发的邮件我已收到，我会尽快给您回复。祝好！

0 replies

jupppo · 2023-01-09T15:12:47Z

jupppo
Jan 9, 2023
Author

I finally solved the energy spike issue by filtering the mqtt message in the home assistant.
This should be accordingly applied to the templates for homeassistant for each used entity. As soon as I have some time, I will update these.

mqtt:
  sensor:
    - state_topic: energy/growatt
      value_template: "{{ value_json['values']['epvtotal'] | int(0) / 10 }}" 
      availability_template: "{{ value_json['values']['epvtotal'] | int(0) < 200000}}"
      availability_topic: energy/growatt
      payload_available: true
      payload_not_available: false        
      unique_id: growatt_generated_energy_total
      device_class: energy
      unit_of_measurement: "kWh"
      state_class: "total_increasing" 
      name: Growatt - Generated energy (Total)
      icon: mdi:solar-power

Important are these filters, they mark the payload as unavailable and it wont get recorded:

availability_template: "{{ value_json['values']['epvtotal'] | int(0) < 200000}}"
availability_topic: energy/growatt
payload_available: true
payload_not_available: false

0 replies

jupppo · 2023-01-10T08:40:11Z

jupppo
Jan 10, 2023
Author

Here is the sensors_grott.yaml file for home assistant. Can be either included in configuration.yaml or sensors.yaml (if used). It includes the sensors for grott, plus some customs calculation (like solar usage % per day).

The filter solution is tested from me and works perfectly from me.
@johanmeijer :Feel free to attach the file to the examples, if you like.

Best

sensors_grott.yaml.txt

3 replies

HaareistNase Jun 9, 2023

Thanks for this file.
As a complete Home-Assistant-Newbie it helps me a lot to get Sensordata from MQTT. I struggle for hours to figure out how to do it. (After I figure out how git works on raspi, how I get python installed on the pi, and that mosquitto has to be installed and configured tooo, that this functionallity is not from grott^^).

BUT ... Since HASS changed the Sensor-Format in YAMEL a short time ago, you have to rewrite the whole list.

I have done this today (I can provide the list, if needed), with alle the MQTT-Sensors, but I did not find out how the first part of the file translate to the new format.
Maybe you can help me out (again^^).

This part is not working anymore, and I do not get it done :-)

sensor:
#Grott Parameters
      growatt_inverter:
        unique_id: growatt_invertertype
        friendly_name: Growatt - Type
        # Please set the type of your inverter
        value_template: "XXX"
        icon_template: mdi:select-inverse
      growatt_datalogger_type:
        unique_id: growatt_datloggertype
        friendly_name: Growatt - Datalogger type
        # Please set the type of your datalogger
        value_template: "XXX"
        icon_template: mdi:select-inverse
      growatt_datalogger_serial:
        unique_id: growatt_datlogger_serial
        friendly_name: Growatt - Datalogger serienr
        # Please set the serial number of your datalogger
        value_template: "XXX"
        icon_template: mdi:select-inverse

#Growatt (grott) Custom Measurements
  - sensor:
      - name: "Growatt - Netto Energiebezug"
        unit_of_measurement: "W"
        unique_id: netto_energie_actual
        device_class: power
        state_class: "measurement"         
        state: >
          {% set fromgrid = states('sensor.growatt_energy_from_grid_actual_2') | float %}
          {% set togrid = states('sensor.growatt_energy_to_grid_actual') | float %}
          {{ (fromgrid - togrid) | round(1, default=0) }}
          
  - sensor:
      - name: "Growatt - PV Energy Calculated Today"
        unit_of_measurement: "kWh"
        unique_id: netto_energie_calc_today
        device_class: energy
        state_class: "measurement" 
        state: >
          {% set ETstr1 = states('sensor.growatt_total_enegry_usage_actual_3') | float %}
          {% set ETstr2 = states('sensor.growatt_total_enegry_usage_actual_5') | float %}
          {{ (ETstr1 + ETstr2) | round(1, default=0) }} 

  - sensor:
      - name: "Growatt - PV Energy Calculated Total (Actual)"
        unit_of_measurement: "W"
        unique_id: netto_energie_calc_actual
        device_class: power
        state_class: "measurement" 
        state: >
          {% set EAstr1 = states('sensor.growatt_string_1_watt') | float %}
          {% set EAstr2 = states('sensor.growatt_string_2_watt') | float %}
          {{ (EAstr1 + EAstr2) | round(1, default=0) }}                

  - sensor:
      - name: "Growatt - Batterieladeleistung"
        unit_of_measurement: "kW"
        unique_id: battnetto
        device_class: energy
        state_class: "measurement" 
        state: >
          {% set BatTo = states('sensor.growatt_energy_to_battery_actual') | float %}
          {% set BatFrom= states('sensor.growatt_energy_from_battery_actual') | float %}
          {{ (BatTo - BatFrom) | round(1, default=0) }}      

  - sensor:
      - name: "Eigenproduktion"
        unit_of_measurement: "%"
        state_class: "measurement" 
        unique_id: "223456789987654321"
        state: >
          {% set lgrid = states('sensor.growatt_total_enegry_load_today') | float %}
          {% set sepv = states('sensor.growatt_energy_from_grid_today_2') | float %}        
          {{ ((lgrid - sepv) * 100 / lgrid) | round(2, default=0) }} 
  - sensor:
      - name: "Total Solar Percent"
        unit_of_measurement: "%"
        state_class: "measurement" 
        unique_id: "233456789987654321"
        state: >
          {% set ltgrid = states('sensor.growatt_lifetime_load_consumption_3') | float %}
          {% set ltsepv = states('sensor.growatt_generated_energy_total') | float %}        
          {{ ((ltsepv * 100) / ltgrid ) | round(2, default=0) }} 
         
  - sensor:
      - name: "battery_effectiveness"
        unit_of_measurement: "%"
        state_class: "measurement" 
        unique_id: "993456789987654321"
        state: >
          {% set batin = states('sensor.growatt_battery_charged_total') | float %}
          {% set batout = states('sensor.growatt_battery_discharged_total') | float %}
          {{ (batout * 100 / batin) | round(2, default=0) }}

jupppo Jun 10, 2023
Author

The quoted first part are definitions (can be put under sensors: in the configuration.yaml)
The growatt customs are template sensors (can be also put under template: in the configuration.yaml or into a separte template file)

Hope that helps

HaareistNase Jun 10, 2023

The quoted first part are definitions (can be put under sensors: in the configuration.yaml) The growatt customs are template sensors (can be also put under template: in the configuration.yaml or into a separte template file)

Hope that helps

Thx for reaction. Its not about the "place".
Its about the syntax.

In your original zipfile a sensor is like this:

mqtt:
sensor:
- state_topic: energy/growatt
value_template: "{{ value_json['values']['epvtotal'] | int(0) / 10 }}"
availability_template: "{{ value_json['values']['epvtotal'] | int(0) < 200000}}"
availability_topic: energy/growatt
payload_available: true
payload_not_available: false
unique_id: growatt_generated_energy_total
device_class: energy
unit_of_measurement: "kWh"
state_class: "total_increasing"
name: Growatt - Generated energy (Total)
icon: mdi:solar-power

But since a update latey it has to be:

mqtt:
sensor:
- name: "Growatt - Generated energy (Total)"
state_"topic: energy/growatt"
value_template: "{{ value_json['values']['epvtotal'] | int(0) / 10 }}"
availability_template: "{{ value_json['values']['epvtotal'] | int(0) < 200000}}"
availability_topic: "energy/growatt"
payload_available: "true"
payload_not_available: "false"
unique_id: "growatt_generated_energy_total"
device_class: "energy"
unit_of_measurement: "kWh"
state_class: "total_increasing"
icon: "mdi:solar-power"

And for the Quoted Entrys, I am to dump to figure out the "new" Syntax.

johanmeijer · 2023-01-12T19:25:14Z

johanmeijer
Jan 12, 2023
Maintainer

Thanks. I am a little bit puzzled about what is the best way for configuring HA. There are different solutions / methods (static and automatic). I have HA container running but not yet played with it. Is on the todo list......

1 reply

jupppo Jun 10, 2023
Author

That Strange. I am on the latest 23.06 and its works flawless. Are you Sure the Syntax IS correct? The dash should be before the topic, because IT defines the Sensor. The Name ist Just an Attribute (Other way round as with Templates sensors .
I am on my mobile, so I cant See whether spaces are correct. I would assume that might bei also a Problem.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Energy Spikes #244

{{title}}

Replies: 12 comments 8 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Energy Spikes #244

jupppo Nov 28, 2022

Replies: 12 comments · 8 replies

johanmeijer Nov 28, 2022 Maintainer

jupppo Nov 28, 2022 Author

johanmeijer Nov 28, 2022 Maintainer

jupppo Nov 29, 2022 Author

jupppo Dec 8, 2022 Author

johanmeijer Dec 8, 2022 Maintainer

jupppo Dec 9, 2022 Author

jupppo Dec 19, 2022 Author

jupppo Dec 23, 2022 Author

johanmeijer Dec 24, 2022 Maintainer

johanmeijer Dec 24, 2022 Maintainer

jupppo Dec 25, 2022 Author

gaoxuannuli Dec 29, 2022

jupppo Jan 9, 2023 Author

jupppo Jan 10, 2023 Author

HaareistNase Jun 9, 2023

jupppo Jun 10, 2023 Author

HaareistNase Jun 10, 2023

johanmeijer Jan 12, 2023 Maintainer

jupppo Jun 10, 2023 Author

jupppo
Nov 28, 2022

Replies: 12 comments 8 replies

johanmeijer
Nov 28, 2022
Maintainer

jupppo Nov 28, 2022
Author

johanmeijer
Nov 28, 2022
Maintainer

jupppo Nov 29, 2022
Author

jupppo
Dec 8, 2022
Author

johanmeijer
Dec 8, 2022
Maintainer

jupppo
Dec 9, 2022
Author

jupppo
Dec 19, 2022
Author

jupppo Dec 23, 2022
Author

johanmeijer
Dec 24, 2022
Maintainer

johanmeijer
Dec 24, 2022
Maintainer

jupppo Dec 25, 2022
Author

gaoxuannuli
Dec 29, 2022

jupppo
Jan 9, 2023
Author

jupppo
Jan 10, 2023
Author

jupppo Jun 10, 2023
Author

johanmeijer
Jan 12, 2023
Maintainer

jupppo Jun 10, 2023
Author