hardbyte / hardbyte/python-evnex

Make distributionByTariff data available as totalCost value is not accurate with TimeOfUse

Ouverte
#129 0 commentaires 2 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Python
Étoiles
13
Forks
8
Merge moyen
5 h 58 min
PR mergées (30 j)
2

Description

The API totalCost value does not accurately represent the actual cost where time-of-use tarrifs are in use. Evnex describe this as a legacy value, one that appears to use a single tariff where that tariff lacks precision. In Home Assitant time-of-use tariff's can be added in a template as an example and with totalEnergyUsage we can calculate a more accurate cost. Except where there is a mix of solar and grid energy, as we don't know the mix of grid and solar energy. However this is contained in the get session response.

"totalEnergyUsage": {
"total": 1041.0,
"distributionByTariff": { -- If these values could be surfaced we could work out the true cost ourselves
"solar": 88.9, -- either including solar export as a percieved cost or just a zero value.
"flat": 11.1
},
"distributionByEnergySource": {
"cogeneration": 0.1,
"gas": 0.1,
"geothermal": 2.4,
"hydro": 7,
"localSolar": 88.9,
"solar": 0.2,
"wind": 1.3
}
},
"totalCost": {
"currency": "NZD",
"amount": 0.0348, -- This is not a correct value where time of use tariffs are used.
"distribution": {
"flat": 100
}

I am going to attempt this myself, but I am not a Dev so raising it here as a backstop.

Regards

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

Start by locating the get session response handling and the existing totalEnergyUsage and totalCost fields. Trace how response data is represented and exposed, then make totalEnergyUsage.distributionByTariff available alongside the other usage values. Done means callers can access the tariff distribution from a session response without relying on the inaccurate totalCost value.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
python
Domaine
api, backend
Type d'issue
Fonctionnalité
Difficulté
3/5
Temps estimé
1-2 jours
Activité
Active
Clarté
Plutôt claire
Accessibilité débutants
68/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.