Comments (10)
The README mentions how to create your own additional sensors from the state of the main sensor exposed by this integration. However, isn't it a better idea to expose all values in the state as separate sensor by default? This would allow the integration in add the proper state_class
? Since I am not sure this is possible using the template integration as explained in the README.
An alternative Goodwe integration (which works via UDP, see: https://github.com/mletenay/home-assistant-goodwe-inverter) does exactly this.
from goodwe-sems-home-assistant.
Yes indeed. For the statistics to work, you need a separate sensor with the correct state_class
.
from goodwe-sems-home-assistant.
on core-2022.5.4
HACS 1.24.5
RaspberryPi4
GoodWe SEMS API Beta 3.7.0
Firstly- great work @TimSoethout . I was unable to use any of the local integrations with my Goodwe inverter because it upset the SEMS uploads (even if I set it to poll every 3 or 5 mins!) and none seem compatible with the GoodWe homekit.
I have a GoodWe inverter (GW10KAU-DT), plus GoodWe homekit (for three-phase power).
I have got the SEMS beta version installed which yeilds two devices (the homekit and the inverter). The Homekit device has three entities. Two of which I can put straight into the HA Energy page:
- sensor.homekit_XXX_ import
- sensor.homekit_XXX_export
both in kWh of what should be only increasing values of my total grid consumption (eg buying), and grid export (selling) respectively.
However every night, just after midnight I'm recording backwards values, followed by a 2:30am recovery for both the cumulative inport and export:
This affects the HA Energy page.
Has anyone got a work around or an explanation for the behaviour?
from goodwe-sems-home-assistant.
I've posted this elsewhere, but just in case it helps.
I have homekit and a non goodwe inverter.
I redefined the sensors using the new format
I found the HA docs quite painful in how exactly to do this, the change in syntax I found to be brainmelting.
I put this directly into my configuration.yaml
For the issue with the dip in values, I'm now trying to change the all time totals to total_increasing and see if that avoids the issue.
template:
- sensor:
- name: "PV Front"
state: '{{ states.sensor.solar_pv_91000hku21600330.attributes.pv }}'
unit_of_measurement: 'W'
state_class: "measurement"
- sensor:
- name: "Grid"
state: '{{ states.sensor.solar_pv_91000hku21600330.attributes.grid }}'
unit_of_measurement: 'W'
state_class: "measurement"
- sensor:
- name: "House Consumption"
state: '{{ states.sensor.solar_pv_91000hku21600330.attributes.load }}'
unit_of_measurement: 'W'
state_class: "measurement"
- sensor:
- name: "PV Status"
state: '{{ states.sensor.solar_pv_91000hku21600330.attributes.PowerFlowDirection }}'
unit_of_measurement: 'W'
- sensor:
- name: "PV generation total"
state: '{{ states.sensor.solar_pv_91000hku21600330.attributes.all_time_generation }}'
unit_of_measurement: 'kWh'
state_class: "total_increasing"
device_class: "energy"
- sensor:
- name: "PV export total"
state: '{{ states.sensor.solar_pv_91000hku21600330.attributes.Totals_sell }}'
unit_of_measurement: 'kWh'
state_class: "total_increasing"
device_class: "energy"
- sensor:
- name: "PV import total"
state: '{{ states.sensor.solar_pv_91000hku21600330.attributes.Totals_buy }}'
unit_of_measurement: 'kWh'
state_class: "total_increasing"
device_class: "energy"
- sensor:
- name: "PV generation today"
state: '{{ states.sensor.solar_pv_91000hku21600330.attributes.Charts_sum }}'
unit_of_measurement: 'kWh'
state_class: "measurement"
device_class: "energy"
- sensor:
- name: "PV export today"
state: '{{ states.sensor.solar_pv_91000hku21600330.attributes.Charts_sell }}'
unit_of_measurement: 'kWh'
state_class: "measurement"
device_class: "energy"
- sensor:
- name: "PV import today"
state: '{{ states.sensor.solar_pv_91000hku21600330.attributes.Charts_buy }}'
unit_of_measurement: 'kWh'
state_class: "measurement"
device_class: "energy"
- sensor:
- name: "PV Self Use Today"
state: '{{ states.sensor.solar_pv_91000hku21600330.attributes.Charts_selfUseOfPv }}'
unit_of_measurement: 'kWh'
state_class: "measurement"
device_class: "energy"
from goodwe-sems-home-assistant.
This seems closely related to #73 and #71, all of which might be addressed with the latest release.
from goodwe-sems-home-assistant.
This seems closely related to #73 and #71, all of which might be addressed with the latest release.
Let you know in 12 hours or so! 🙏
from goodwe-sems-home-assistant.
Let you know in 12 hours or so! 🙏
I hope it fixes your issue!
I didn't think the PR would be merged so quickly or really at all so I didn't get a chance to mention that when switching from Totals to Charts data you'll see a new kind of spike in your graph - but it's only once off.
Luckily most people with this issue have broken graphs already and the next day should have a fixed graph.
For my own sake I'm also writing a tool to repopulate all available sems data to give me clean historical graphs.
from goodwe-sems-home-assistant.
Let you know in 12 hours or so! 🙏
I hope it fixes your issue!
I didn't think the PR would be merged so quickly or really at all so I didn't get a chance to mention that when switching from Totals to Charts data you'll see a new kind of spike in your graph - but it's only once off.
Luckily most people with this issue have broken graphs already and the next day should have a fixed graph.
For my own sake I'm also writing a tool to repopulate all available sems data to give me clean historical graphs.
Thanks so much @Denifia everything is working! Yes I had the one-off spike at midnight (reverse to the usual one) and it is good since.
I'd love access to your tool to clean up my old data as well, if that is possible.
Thanks again for your effort.
Now, the 🌞 just has to shine!
from goodwe-sems-home-assistant.
@gemmaker glad the fix worked for you!
I'll share my cleanup tool when it's working for me but I don't get a lot of time to work on it so it could be a few weeks away.
from goodwe-sems-home-assistant.
@gemmaker I've put up my first cut of a Sems HomeKit importer at https://github.com/Denifia/goodwe-sems-history-home-assistant but in some weird turn of fate that has a bug where recalculated days that were not imported have the daily data spike.
I've run out of time to work on it but hopefully someone else in the community will be able to contribute.
from goodwe-sems-home-assistant.
Related Issues (20)
- Energy template in HA incorrect HOT 3
- HomeKit reading dips to 0 during the day
- Max retries exceeded with url: xxx HOT 4
- How to change/check config
- Version 5.0.0 is making my GoodWe inverter offline HOT 10
- Docs / list attributes HOT 2
- Seems like some value are not corret?
- Import data inconsistent HOT 13
- Deprecation warning in 2024.7.0
- Component not starting - TypeError: 'NoneType' object is not subscriptable HOT 1
- turn off invertor via api HOT 13
- Error while setting up sems platform for sensor HOT 4
- Feedback on moving from extra_state_attributes to sensors. HOT 4
- GoodWe Sems Api HOT 1
- Expose "powerflow" metrics: real time power import / export in watts HOT 8
- Error adding entities for domain sensor with platform sems HOT 1
- Sems Portal Nightly Midnight Zero is double dipping upsetting HA Recorder HOT 34
- STATE_CLASS_TOTAL_INCREASING was used from sems, this is a deprecated constant which will be removed in HA Core 2025.1 HOT 1
- depreciated constants HA Core 2025.1 HOT 4
- HomeKit withtout sn HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from goodwe-sems-home-assistant.