Comments (8)
@RGx01 If it helps, I have worked around this with the sensor config below. It's far from ideal, but has been reasonably accurate.
- name: "EV Charger CT Power Corrected"
unique_id: ev_charger_ct_power_corrected
state_class: measurement
unit_of_measurement: W
device_class: power
state: >
{% if (states("switch.hypervolt_charging") == "on") %}
{{ states("sensor.hypervolt_grid_power") | float(default=0) }}
{% else %}
{% set power = states("sensor.hypervolt_grid_power") | float(default=0) %}
{% set avg_session_current = states("sensor.ev_charger_session_current") | float(default=0) %}
{% set avg_session_voltage = states("sensor.ev_charger_session_voltage") | float(default=0) %}
{% set avg_session_power = avg_session_current * avg_session_voltage %}
{% if (avg_session_power > 0 and power > avg_session_power) %}
{{ power - avg_session_power }}
{% else %}
{{ power }}
{% endif %}
{% endif %}
- name: "EV Charger Session Voltage"
unique_id: ev_charger_session_voltage
state_class: measurement
unit_of_measurement: V
device_class: voltage
state: >
{% set last_voltage = states("sensor.ev_charger_session_voltage") | float(default=0) %}
{% if (states("switch.hypervolt_charging") == "on") %}
{% set voltage = states("sensor.hypervolt_voltage") | float(default=0) %}
{{ voltage if last_voltage == 0 else ((voltage + last_voltage)/2) }}
{% else %}
{{ last_voltage }}
{% endif %}
- name: "EV Charger Session Current"
unique_id: ev_charger_session_current
state_class: measurement
unit_of_measurement: A
device_class: current
state: >
{% set last_current = states("sensor.ev_charger_session_current") | float(default=0) %}
{% if (states("switch.hypervolt_charging") == "on") %}
{% set current = states("sensor.hypervolt_charger_current") | float(default=0) %}
{{ current if last_current == 0 else ((current + last_current)/2) }}
{% else %}
{{ last_current }}
{% endif %}
from home-assistant-hypervolt-charger.
Integration: v1.3.1
Home Assistant:
- Core: 2024.3.0
- Supervisor: 2024.02.1
- Operating System: 12.0
- Frontend: 20240306.0
from home-assistant-hypervolt-charger.
@gndean I did more testing today, and I'm reasonably confident this is something in the integration code.
As my session was coming to an end, I've watched the Hypervolt Android app to check if the data remains misreported there as well. And it was reported correctly as soon as the session ended.
The HS entity displayed the tell-tale 1s blip at the end of the session, and then the data was misreported for the exact same length of time as the session itself.
I have a workaround in place, where I have a secondary entity that tracks the last charge session's average voltage and current, and then subtracts the power value from the reported CT clamp value if no charge session is in progress.
I'll try and check if I can debug this further at code level.
Here's an overlay of correct/incorrect data:
from home-assistant-hypervolt-charger.
Thanks for the issue report.
The CT Power
sensor is just a report of a raw field from the Hypervolt APIs. There is no processing that the integration does with it.
Since I moved from a HV 2.0 charger to a HV 3.0 charger, I no longer see this field populated at all, whereas it was with my HV 2.0 charger.
I suspect its meaning has changed internally within the HV API spec. But that's just a guess.
I appreciate your report and investigation however I am going to close this as a "won't fix" because the integration is just reporting what the HV servers supply and without any documentation, I'm not confident to make any further inferences to its precise meaning.
from home-assistant-hypervolt-charger.
OK, understood.
On my HV3 charger the CT clamp data is used internally to grid load balance, and - assuming it's installed as per manual - reports the full house load, which enables the charger to manage the different boost and eco modes appropriately, especially if there's other heavy loads active during the charge session, or PV production.
Interesting that you say this data is not populated with your charger at all. Firmware differences?
Mine's at 2627.0
from home-assistant-hypervolt-charger.
I've just reread previous posts - I'll report to Hypervolt.
I have a similar issue. But not sure if it's a problem with the charger firmware or integration. When my charge session ends, grid power remains at the session end power and house power jumps to the grid power value. The curious thing is... it's like Schrödinger's API, as soon as you look it returns to normal... I'm just not sure if it was opening the hypervolt app or opening home assistant that triggers the values to return. It happens at leat once a month and very frustrating.
Happy to report to Hypervolt if it's impossible that it's the integration. Just let me know.
from home-assistant-hypervolt-charger.
Thanks @ptashek I'll give it try and see what happens when it occurs again.
from home-assistant-hypervolt-charger.
Happened again @ptashek. Observed the same behaviour of opening the Hypervolt app and it suddenly showing the correct values in HA. I was using your sensor config with a small modification to only correct power when the avg_session_power > 50 rather than 0. But I think my logic was flawed and it didn't catch it so again the stats are messed up. Frustrating.
I'm changing it for a Zappi next month for other reasons (energy supplier integration) so hopefully I don't see the issue again.
from home-assistant-hypervolt-charger.
Related Issues (20)
- Schedule helper
- CT power entity no longer reports data in v2.0.2 HOT 5
- Support viewing the configured rate for Energy Tariff and updating it HOT 2
- Hypervolt Charge Mode changes not applied HOT 2
- How can I unpause when charger becomes paused? HOT 1
- The refresh token is not stored or used HOT 6
- No reconnect following connection error(s) HOT 1
- v2.2.6 misbehaving on HASS restart, incorrectly changes to Plug and Charge HOT 1
- AttributeError: TIME HOT 2
- HASS warning: Detected blocking call to 'open' inside the event loop by custom integration 'hypervolt_charger' HOT 1
- Not able to load charger data
- Setup issue following the recent update (V2.3.0) HOT 4
- Several minutes delay to synchronise the schedule following a token refresh HOT 1
- Issues since 2024.7 HOT 2
- Missed commands HOT 2
- Octopus Energy v12 breaks set schedule
- Boost, Eco & Super Eco HOT 1
- Octopus Intelligent GO integration HOT 4
- Error with set schedule service. HOT 3
- Not working with V2.0 HOT 2
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 home-assistant-hypervolt-charger.