Integration shows only a single value from last month #97
Comments
|
Further information about the setup: |
|
I checked the log, and I've only on 2023-08-02 few |
Ludy87
added
bug
An update takes place every 24 hours, unless otherwise set.
|
|
Hello! Thank you for the fast response :-) The JSON: {
"consum_types": [
"heating"
],
"combined_data": null,
"total_additional_values": {
"heating": null,
"warmwater": null,
"water": null,
"ww": null,
"w": null,
"h": null
},
"total_additional_custom_values": {
"heating": null,
"warmwater": null,
"water": null,
"ww": null,
"w": null,
"h": null
},
"last_value": {
"heating": null,
"warmwater": null,
"water": null,
"month": 7,
"year": 2023,
"ww": null,
"w": null,
"h": null
},
"last_custom_value": {
"heating": null,
"warmwater": null,
"water": null,
"month": 7,
"year": 2023,
"ww": null,
"w": null,
"h": null
},
"all_dates": null,
"sum_by_year": {
"heating": {
"2023": 0.0
},
"warmwater": null,
"water": null,
"ww": null,
"w": null,
"h": "kWh"
},
"last_costs": {
"heating": 11.0,
"warmwater": null,
"water": null,
"month": 7,
"year": 2023,
"unit": "EUR"
}
}11€ is correct for July. The ista portal shows more data:
And if I use pyecotrend_ista.py from February, I get this result (only a part): {
"entity_id": "heating_2023_7_wzkefdjf4",
"year": 2023,
"month": 7,
"type": "heating",
"value": "37,0",
"valuekwh": null,
"unit": "kWh",
"unitkwh": "kWh",
"supportCode": "WZKEFDJF4",
"date": {
"month": 7,
"year": 2023
},
"exception": null
},
I checked it with this small python script: ecotrend = ista.PyEcotrendIsta(email="***@***", password="***")
raw = asyncio.run(ecotrend.consum_small())
print ("Raw:")
print (json.dumps(raw, indent=4, default=str)) |
|
Btw., I upgraded to the latest |
|
the latest version of the lib is 2.0.19 import asyncio
import json
import logging
from pyecotrend_ista.pyecotrend_ista import PyEcotrendIsta
_LOGGER = logging.getLogger(__name__)
asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())
EMAIL = "your mail"
PASSWORD = "your Pass"
async def main():
ecotrend: PyEcotrendIsta = PyEcotrendIsta(email=EMAIL, password=PASSWORD, logger=_LOGGER)
print(ecotrend.getVersion())
await ecotrend.getUA()
await ecotrend.login(forceLogin=True)
raw = await ecotrend.get_raw()
print("Raw:")
print(json.dumps(raw, indent=4, default=str))
if __name__ == "__main__":
asyncio.run(main())please execute and post the log here, thanks. |
|
Ok, got it (too old python version was the issue to run the script). The output is huge and contains a lot of private information, I reduce it to July only (consumption and costs). If needed, I can send the whole JSON via mail. {
"consumptionUnitId": "1e4ca141-f4d8-4352-975e-05ae374170d7",
"resident": {
"movedOut": false,
"moveOutDate": null,
"invalid": false,
"invalidDate": null
},
"consumptions": [
{
"date": {
"month": 7,
"year": 2023
},
"readings": [
{
"type": "heating",
"value": "37,0",
"unit": "kWh",
"additionalValue": null,
"additionalUnit": "kWh",
"estimated": false,
"comparedConsumption": {
"lastYearValue": 34.0,
"period": {
"month": 7,
"year": 2022
},
"smiley": "MAD",
"comparedPercentage": 9,
"comparedValue": "3,0"
},
"comparedCost": null,
"averageConsumption": null
},
{
"type": null,
"value": null,
"unit": null,
"additionalValue": null,
"additionalUnit": "kWh",
"estimated": false,
"comparedConsumption": null,
"comparedCost": null,
"averageConsumption": null
},
{
"type": null,
"value": null,
"unit": null,
"additionalValue": null,
"additionalUnit": "kWh",
"estimated": false,
"comparedConsumption": null,
"comparedCost": null,
"averageConsumption": null
},
{
"type": null,
"value": null,
"unit": null,
"additionalValue": null,
"additionalUnit": "kWh",
"estimated": false,
"comparedConsumption": null,
"comparedCost": null,
"averageConsumption": null
},
{
"type": null,
"value": null,
"unit": null,
"additionalValue": null,
"additionalUnit": "kWh",
"estimated": false,
"comparedConsumption": null,
"comparedCost": null,
"averageConsumption": null
}
],
"exception": null,
"documentNumber": null
},
],
"costs": [
{
"date": {
"month": 7,
"year": 2023
},
"exception": null,
"costsByEnergyType": [
{
"type": "heating",
"value": 11,
"unit": "EUR",
"estimated": false,
"comparedCost": {
"lastYearValue": 10.3,
"period": {
"month": 7,
"year": 2022
},
"smiley": "MAD",
"comparedPercentage": 5,
"comparedValue": "1"
}
},
{
"type": null,
"value": null,
"unit": null,
"estimated": false,
"comparedCost": null
},
{
"type": null,
"value": null,
"unit": null,
"estimated": false,
"comparedCost": null
}
]
},
],
"co2Emissions": null,
"consumptionsBillingPeriods": {
...
},
"costsBillingPeriods": {
...
},
"co2EmissionsBillingPeriods": {
"currentBillingPeriod": null,
"previousBillingPeriod": null
}
} |
|
Thanks for the log. I think I've found the error, I'll test it in the coming days - I'm actually on vacation Ista has a bad understanding of json objects, numbers are partial strings and elsewhere they are floats again. In your case it's - I think - due to |
Ludy87
added
Bug: Confirmed!
Ista has a bad understanding of running software in general (remembering the several months when the company collapsed after the ransomware attack). Great, thank you for your effort. I'm looking forward to the solution. Have a nice holiday! |
|
Hello @arittner, change the lib version in the package |
|
Hi! Unfortunately, no change. |
|
The current JSON (generated with the script and pyecotrend-ista-2.0.20): {
"consumptionUnitId": "1e4ca141-f4d8-4352-975e-05ae374170d7",
"resident": {
"movedOut": false,
"moveOutDate": null,
"invalid": false,
"invalidDate": null
},
"consumptions": [
{
"date": {
"month": 7,
"year": 2023
},
"readings": [
{
"type": "heating",
"value": "37,0",
"unit": "kWh",
"additionalValue": null,
"additionalUnit": "kWh",
"estimated": false,
"comparedConsumption": {
"lastYearValue": 34.0,
"period": {
"month": 7,
"year": 2022
},
"smiley": "MAD",
"comparedPercentage": 9,
"comparedValue": "3,0"
},
"comparedCost": null,
"averageConsumption": {
"averageConsumptionValue": "58,8",
"residentConsumptionValue": "37,0",
"averageConsumptionPercentage": 100,
"residentConsumptionPercentage": 63,
"additionalAverageConsumptionValue": "0",
"additionalResidentConsumptionValue": "0",
"additionalAverageConsumptionPercentage": 0,
"additionalResidentConsumptionPercentage": 0
}
},
{
"type": null,
"value": null,
"unit": null,
"additionalValue": null,
"additionalUnit": "kWh",
"estimated": false,
"comparedConsumption": null,
"comparedCost": null,
"averageConsumption": null
},
{
"type": null,
"value": null,
"unit": null,
"additionalValue": null,
"additionalUnit": "kWh",
"estimated": false,
"comparedConsumption": null,
"comparedCost": null,
"averageConsumption": null
},
{
"type": null,
"value": null,
"unit": null,
"additionalValue": null,
"additionalUnit": "kWh",
"estimated": false,
"comparedConsumption": null,
"comparedCost": null,
"averageConsumption": null
},
{
"type": null,
"value": null,
"unit": null,
"additionalValue": null,
"additionalUnit": "kWh",
"estimated": false,
"comparedConsumption": null,
"comparedCost": null,
"averageConsumption": null
}
],
"exception": null,
"documentNumber": null
},
],
"costs": [
{
"date": {
"month": 7,
"year": 2023
},
"exception": null,
"costsByEnergyType": [
{
"type": "heating",
"value": 11,
"unit": "EUR",
"estimated": false,
"comparedCost": {
"lastYearValue": 10.3,
"period": {
"month": 7,
"year": 2022
},
"smiley": "MAD",
"comparedPercentage": 5,
"comparedValue": "1"
}
},
{
"type": null,
"value": null,
"unit": null,
"estimated": false,
"comparedCost": null
},
{
"type": null,
"value": null,
"unit": null,
"estimated": false,
"comparedCost": null
}
]
},
],
"co2Emissions": null,
"consumptionsBillingPeriods": {
...
},
"costsBillingPeriods": {
...
},
"co2EmissionsBillingPeriods": {
"currentBillingPeriod": null,
"previousBillingPeriod": null
}
} |
|
sorry for using you as a tester. please change the version to pyecotrend_ista==2.0.21 |
No problem ;-)
Now, it looks fine :-) Great, thank you! |
|
Btw., it would be nice to have the other values as entities, but this is maybe something for another feature request, e.g.: "averageConsumption": {
"averageConsumptionValue": "58,8",
"residentConsumptionValue": "37,0",
"averageConsumptionPercentage": 100,
"residentConsumptionPercentage": 63,
and "comparedConsumption": {
"lastYearValue": 34.0,
"period": {
"month": 7,
"year": 2022
},
"smiley": "MAD",
"comparedPercentage": 9,
"comparedValue": "3,0"
},and "comparedCost": {
"lastYearValue": 10.3,
"period": {
"month": 7,
"year": 2022
},
"smiley": "MAD",
"comparedPercentage": 5,
"comparedValue": "1"
} |
Warum steht bei dir Warmwasser? Es ist doch die Heating entity 🤔 |
|
Fernwärme ;-) - da ist Heizung und Warmwasser zusammen und ich habe es dann so in HA umbenannt. Da es für ista auch keine Unterscheidung gibt, haben die wohl gelost, auf welche Stelle sie das schreiben. |
|
Wenn ich dran denke, werde ich dem Tribe Lead PM eine Nachricht schicken, dass das eventuell gefixt wird. |
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I had tested an old integration a long time ago, but it never really worked. I had tested the Python library manually once and the access worked, but in Home Assistant never any sensor was displayed.
Now I saw the latest update and the integration could be set up without further problems, sensors are displayed and I thought I finally had my long-awaited Home Assistant integration.
But alas, only one entity shows a value (last month as an estimated amount to pay) but no kWh values. Debugging is enabled and shows only that:
On my dashboard, I see only a single sensor entity with data:
I update my ecotrend data hourly (I know, ista provides the data only once a month) to get an update. But since days I see only this data from above.
Here more detail information:
The text was updated successfully, but these errors were encountered: