To correctly process the data from the different load sessions, information is visibly provided in the API which gives the number of the load session, this number is incremented with each new load.
In the integration (or plugin) of other home automation boxes, this information is reported, it was not taken into account on Home Assistant.
Could you see if you can add this information? This would be very interesting for the future.
Can you give me an example of the field you are looking for in the API output? Also, what do you want to use it for? If its in the API response I can probably add it, it should however have a functional goal for all users.
Here is the widget of Jeedom’s MyWallbox plugin.
“Sessions de charge 22” = Charging session number 22
=> have a functional objective for all users, it’s obvious, the session number is very important, it changes (+1) with each session and therefore it allows the sessions to be recorded.
Hi, I just had a quick look at your example and the API output. For your information, we are using this python package to import the data: wallbox · PyPI, from this package we use the getChargerStatus to show the different sensors. This functions response does not contain the information you are looking for. I believe that the getSessionList function does contain the relevant number, however, we are not currently using this function in the integration.
This means that 1. the effort of adding this information to the integration would be quite high and 2. the relative load of this addtitional field would be also high (as it would be the 1 field that would require an additional (more complex) function call).
Because of this, and as I still don’t really see the usecase, I’m currently not going to invest any time in potentially adding this info to the integration.
To do this and then to process this data, it is necessary to divide the charging sessions and this is done using the charging session number.
if I understand correctly the getChargerStatus function gives the status of the Wallbox while getSessionList allows you to retrieve information on the charging sessions, this is particularly interesting if you want to know your consumption per week, per month. Estimate the cost of charges…
it’s you who decide to invest time on your integration or not but I think that being able to process information from charging sessions is a real bonus for integration and HA
thank you for taking the time to study my proposal
hi @sigalou, I think you can export that list directly from the API, no need to create it. However, homeassistant isn’t the right place to store this kind of data, it doesn’t works with lists of data. If you just want averages, you can use the built-in energy dashboard of Home Assistant, you could even create a new sessionnumber in Home Assistant by counting when the kWh number resets to 0 (or when the cable is unplugged from the wallbox). Hope this helps.
hi @hesselonline
Thank you for your explanations, very interesting.
Before asking you the question, I did a lot of research on how to be able to create the session number in the API retrieval, I did a lot of tests but it’s very complicated. The Wallbox (with the powerboost) sometimes cuts the load to give priority to heating or hot water for example, so we cannot rely on the kwh.
I also tried with state changes (from: Charging for example) but there are plenty of exceptions.
I have extensively documented my tests (in French) on my blog:
I contacted several developers from other platforms, all of whom finally resolved these difficulties by recovering the charging session number, it appears at the same time as the last charge such as the last power consumed, the number of km added or the cost of the last charge.
If it’s too complex, give up but I assure you that the usefulness is real.
Thank you for this dialogue on this point, friendly.
There is a larger thread here on the forum of people using the integration, maybe somebody there has some ideas on how to create the overview you want. I will keep your idea / requirement in mind, I might add it later on.