Spilling excess Diesel #2 heating oil into groundwater isn’t a punchline. To a lesser degree, freezing one’s butt off in an ambient temperature shower in a New England AirBNB in October also isn’t super-fun, even if one measures their heating oil at home in a superior system.
1 Like
Hi! I have reverted back to core-2021.7.4 as it seems to brake my Qees zware dimmer. As a NOOB how can I help trace the issue?
By logging and posting an issue on github.
OK, I hope I did it correctly: 2021.8.8 issue with QEES Dimmer US · Issue #55362 · home-assistant/core · GitHub
I’m experiencing the same problems and have tried a couple of workarounds with no success.
I guess we’re stuck with waiting for QNAP to push a new firmware?
There was a thread where someone had solved the QNAP problem, use the seach 
Here Can't install latest version on Docker Container station Qnap - #12 by diegot
That one seemed very promising to me and I was able to pull an image. I could however not create a container from it and my guess is that somehow Container Station doesn’t recognize what kind of image it has pulled. That it’s missing some metadata or that this Container Station version is simply flawed.
I’ve attached a screenshot of what it looks like to me. I simply don’t get any options to set up the container and to me this is still an unresolved issue.
Have you contacted qnap?
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.
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.
1 Like
So who writes container station?
QNAP, apparently
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?
1 Like
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.
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:03 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140445153147056] Received invalid command: energy/info
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:03 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140445153147056] Received invalid command: energy/info
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: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!
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
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.
Have you ensured they have all the require attributes as documented and discussed in this thread?