Ola Lidholm

The non-working sensors mentioned above are now removed in the latest release.

Most of the sensors are not polled at all, the data is pushed from the servers over signalr stream. The exception is the cost sensors and the schedule sensors. The...

Btw, what sensors are you thinking of when you say "but there are others behaving the same way"?

Both of those sensors use data pushed over signalr, so at least it is not a polling problem. My gut feeling is that what you saw there was a server...

Yes, I am seeing something strange too which is probably what you are seeing. The data is received, but sometimes the sensors does not update correctly. I am investigating.

Ok, I found the issue with state_eqAvailableCurrentP1/2/3. They are incorrectly defined in the library, so they never update, they just get the initial value. Easily fixed. This is however a...

@asyvan the latest release should solve your problem, please have a look and see if works for you.

What was your reason_for_no_current sensor showing during the ready_to_charge period? You can send the log file to olal (a) plea.se

That is good. I will anyway mention this to Easee to let them know that there are improvements needed.

It happens now and then for me too that the sensors stop updating, not often though. The connection to the servers has in these cases not disconnected, it is just...