2021.8.0: Feel the energy ⚡️

ianfretwell · August 30, 2021, 2:28pm

The issue isn’t the QNap firmware. It’s the 2.4.0 build of Container Station. If you just install the 2.3.5 build over the top you’ll find you have full functionality again.

To get the older build go to Qnap website, go to the apps section of the download centre and search for your model, but in the version tab change this to 4.5.2 - then you’ll be able to download v2.3.5.1708.

Just install it and you’ll be good to go again. I have an open ticket with QNap regarding this but their grasp of English is incredibly poor when you’re trying to explain something like this to them.

Joel_Marambaia · August 30, 2021, 3:56pm

is that possible to remove labels from statistics-graph card upper part? for me its just waste of space on the card, as hovering mouse you get the entity name. if you enable max, min, average there are even more labels above the graphs… i tried get name: null but doesn’t work for this card.

nickrout · August 30, 2021, 8:31pm

So who writes container station?

Prodigyplace · August 30, 2021, 8:50pm

QNAP, apparently

solarccd · September 24, 2021, 1:09am

Hi.
I’m trying to make the Energy Dashboard work with the integrated Kostal Integration, but there’s a problem with the “Return to Grid” option. There’s no useful value from the integration available to select here. The closest ist “scb Energy Yield Total”, but that isn’t what the energy dashboard expects, as it gives all the PV production, not the production minus the home consumption, aka the amount of energy returned to the grid.
However, there is also no other value the kostal can supply that would give exactly that data. There is one reading, “scb Grid Power”, (which can’t be selected in the energy dashboard), which however returns either negative (return to grid) or positive (from grid) values, depending on the direction of the total energy flow (to/from Grid). So what I think the energy dashboards needs, is “scb Grid Power”, but only the negative values (unsigned). 'm too much of a noob to be able to do that myself (yet). Any tips?

VDRainer · September 24, 2021, 7:08am

solarccd · September 24, 2021, 9:00am

I understand thisis supposed to be a reply to me, thanks. I figure I could make that work for me with a few hours of digging, but I’m positive this isn’t what HA is about, but rather that this should be possible quickly and easily for everybody without having to first understand what a riemann integration and a template sensor is. It’s not like I’m talking about some exotic third party integration, but rather an integrated one that supplies everything that’s needed for the energy dashboard straightaway, just not in the format that HA expects, and apparently this isn’t even the only integration with that issue.

And while I’m at it, the integrated Homematic integration needs to be updated to support energy sensors too. None of the homematic or homematic IP energy sensors can currently be selected in the energy dashboard.

lars86 · September 24, 2021, 2:01pm

Hi don’t know if this is the right place but i always get a error when restarting homeassistant…

2021-09-24 15:56:03 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140445153147056] Received invalid command: energy/info

2021-09-24 15:56:04 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140445152428192] Received invalid command: mobile_app/push_notification_channel

Anybody knows where to look to fix this?

Greetings!

nickrout · September 25, 2021, 6:23am

I expect what you meant was: thanks for your help @VDRainer

solarccd · October 2, 2021, 2:39pm

Here’s my solution. Use the modbus integration to get the necessary sensor not from the Kostal integration and the inverter, but from the Kostal Smart Meter (KSEM). In this example, it’s the last sensor “netzeinspeisung_energie_ksem” Thanks to to ANTON_H in photovoltaikforum.com https://www.photovoltaikforum.com/thread/154961-kostal-in-home-assistant-integrieren/?postID=2378153#post2378153

modbus:
  - name: "KSEM"
    type: tcp
    host: xxx.xxx.xxx.xxx
    port: 502

    sensors:
    - name: netzbezug_leistung_ksem
      slave: 1
      device_class: power
      state_class: measurement
      unit_of_measurement: W
      scale: 0.1
      address: 0
      scan_interval: 10 # Defines the update interval of the sensor in seconds.
      count: 2 # Anzahl zu lesenden Register
      input_type: holding
      data_type: uint32

    - name: netzeinspeisung_leistung_ksem
      slave: 1
      device_class: power
      state_class: measurement
      unit_of_measurement: W
      scale: 0.1
      address: 2
      scan_interval: 10 # Defines the update interval of the sensor in seconds.
      count: 2 # Anzahl zu lesenden Register
      input_type: holding
      data_type: uint32

    - name: netzbezug_energie_ksem
      slave: 1
      scale: 0.0001 # wegen kWh (0.1/1000)
      precision: 3
      address: 512
      scan_interval: 60 # Defines the update interval of the sensor in seconds.
      count: 4 # Anzahl zu lesenden Register
      input_type: holding
      data_type: uint64
      device_class: energy
      state_class: total_increasing
      unit_of_measurement: kWh

    - name: netzeinspeisung_energie_ksem
      slave: 1
      scale: 0.0001 # wegen kWh (0.1/1000)
      precision: 3
      address: 516
      scan_interval: 60 # Defines the update interval of the sensor in seconds.
      count: 4 # Anzahl zu lesenden Register
      input_type: holding
      data_type: uint64
      device_class: energy
      state_class: total_increasing
      unit_of_measurement: kWh

AleXSR7001 · October 6, 2021, 6:15pm

Love the new energy integration!

I raised an issue on github because I cannot see all entities that record power consumption (aka kWh). Just If you find the time, would be great if that worked

Apart from that: where/how does one assign colors to individual devices? Almost all devices are black, so impossible to see any distinctions in the graph.

sparkydave · October 6, 2021, 10:15pm

Have you ensured they have all the require attributes as documented and discussed in this thread?

AleXSR7001 · October 7, 2021, 5:51am

Ah, then probably some attribute in the tasmota integration is wrong. I will check which thread to request a fix.

nickrout · October 7, 2021, 6:05am

You don’t request fixes in threads. You post an issue to github. Or read this thread and work it out.

sparkydave · October 7, 2021, 8:13am

Edit the entity attributes via the GUI, Configuration → Customisations

AleXSR7001 · October 7, 2021, 6:18pm

Thank you very much! Never knew that I could make the override there. Noobie me…

AleXSR7001 · October 8, 2021, 8:58pm

So, I was wondering: does the Energy integration use the data recorded by the Recorder integration?

I assume it does not because data is only displayed from the moment you add an entity to the Energy monitoring. If it were to use the data recorded by Recorder it should have access to old data.

The reason why this is relevant is because I want to limit what the Recorder tracks and stores in the database. If I only wanted to track energy consumption and this data is stored by Energy itself (without being able to use the data from Recorder) I might as well disable all entities in Recorder.

So, is my assumption correct or does Energy need Recorder data despite not accessing old recordings?

nickrout · October 8, 2021, 9:08pm

It does use recorder, or more particularly the database that recorder feeds.

AleXSR7001 · October 8, 2021, 9:10pm

So it uses the same database or also the data? Because if the latter then it should be able to display data from before the new integration was introduce. If the first, then deactivating the Recorder should have no impact as the database remains available.

seanomat · October 9, 2021, 9:26am

The data from the recorder is aggregated and persisted in one hour intervalls into the statistics tables in the same database.
The data in the statistics tables is not purged Like the regular recorder data.