Ola Lidholm

I do not recall saying that, but it sounds reasonable. :) Within HA you could use the filter integration low-pass filter: https://www.home-assistant.io/integrations/filter/#low-pass Maybe time_constant = 2 would make sense.

All the different voltages are available as attributes in the voltage sensor. inVoltageT2T3 is voltage between terminal 2 and terminal 3. This is L1 voltage in a TN system. inVoltageT2T4...

In a template you can access an attribute like this: ``` {{ state_attr('sensor.j21_voltage', 'state_inVoltageT2T3') }} ```

There is no exact timing when sensors update, this is just how the easee cloud works, it does not push out updates to all connected clients at the same time...

Well, it seems like an interesting idea. I do not personally have access to a site with more than one user and it may be difficult to implement without being...

I tried calling the APIs you suggested, for the first one I get a user list, consisting of only myself of course. With the second API I get nothing, no...

So seems like it is similar to the https://api.easee.cloud/api/sessions/charger/{chargerId}/monthly API. And maybe identical to https://api.easee.cloud/api/sessions/user/{id}/monthly?

Yes, totalEnergyUsage seems to be the same, but there are some extra fields with cost and currency.

A guess is that there was an interrupt in the communication with the equalizer for some reason and the energy used during that hour was accumulated on the following hour...

If the problem is on the server side I think the timing of when data is missing or when a client disconnects can differ between the clients. But, anyway, there...