-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sensors slow to update or not updating at all #253
Comments
Most of the sensors are not polled at all, the data is pushed from the servers over signalr stream. The short answer is that we are aware of that the cost sensors behave strange and we will fix it as soon as we can figure out how. |
Btw, what sensors are you thinking of when you say "but there are others behaving the same way"? |
Thank you! :) Mostly cost sensors but I had the same problem with sensor.laddbox_dynamic_circuit_limit a while ago. Also laddbox status sensor. It locked on an old status until I reloaded the integration. Perhaps it was due to temporary issues with the Easee API. |
Both of those sensors use data pushed over signalr, so at least it is not a polling problem. Cost sensors is as I said above different though, so that is a real bug, if it is on the server side or in our code I can not tell right now :) |
Had problems this morning with sensors not updating. When I reloaded the integration they all updated to correct values. |
I am trying to use state_eqAvailableCurrentP1 (etc) from sensor.garage_equalizer_limit. |
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. This is however a problem with that specific data so it does not really apply to the original issue.
|
@olalid I have enabled debug logging. Will let you know when it happens again |
@asyvan the latest release should solve your problem, please have a look and see if works for you. |
Thank you. Will try tomorrow and let you know. |
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 |
This night all sensors updated the way they should. 👍 |
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 that the servers stops sending updates. As you say restarting the integration helps because a new connection to the servers seem to solve the problem. |
Note though that I am now talking about cases where all sensors stop updating, not only a specific one or a missed state change etc. |
Im not sure if sensor.xx_cost_per_kwh had a solution, but i just wanted to let you know that I am pushing new cost_per_kwh value to Easee every hour and see the change in the Easee-app but the value will not update in HA unless the sensor/integration is reloaded in HA. I have turned off the hourly "reload_config_entry" and the pre-heat works fine in the morning. Though, the sensor is not being updated hourly in HA. |
Yes, well, that is the behaviour I would expect since cost_per_kwh is not part of the data that the servers push out, so it will not update unless you reload the integration. It sounds very puzzling that reloading the integration would have that effect on the charger, I am sure we do not do anything apart from reading status when we start up, so I do not understand why that would change the behaviour of the charger. What was the state of your "reason_for_no_current" sensor during the "awaiting_start" mode? |
That sensor you are asking about was not enabled so i have no history of it when "something" happened to make the car not preheat. I enabled it after your reply here. I have no idea what/if the reloading caused the car not to preheat, but the reloading was the only deviation/new thing in a very well used and functional setup that I have been using for months. So i assumed it was the reloading-every-hour that did something to trip off the preheating. I might ofc be wrong for all i know. So for now its not reloading and I don't get the "cost_per_kwh" into my HA. That is less important than a preheated car in the early morning. |
It is not powersaver that pauses the charger at the end of that green period then? |
In my flow powersaver itself does not pause if in/outside the "low price" window. Powersaver just gives info for other nodes to start/stop charging. |
My suspicions were right and this worked without issues after the Easee-charger was restarted properly by flipping the fuse for 5 minutes. To circle back to my initial reason for commenting here; cost_per_kwh |
OK, that is good news. I have unfortunately no knowledge about how they calculate the cost for a charging session. It could be either way. |
According to Eease support the charging cost used is the price per kwh when you plugged the cable in. |
@olalid The answer I got was this: So, is it possible to make the integration to request information more often? If so, could this be addressed, please? " |
Well, I am pretty sure that when they answered you they did not mean "you can ask the guys developing the HA integration to make synchronised polls from more than 3000 clients at the exact same time to our servers". If they mean something else than polling, I need more info to understand what they mean. |
Thank you for the quick reply. Perhaps the integration could be configured to randomly select a time within, let's say, the 59th minute of each hour. Subsequently, it could provide a qualified estimation for usage during the remaining seconds of the hour. This way, the hourly consumption could be updated in time to align with the correct hour in the energy dashboard in Home Assistant. |
Exactly which sensor(s) do you actually mean? |
It's the Equalizer Import energy sensor I'm referring to. The response I received from Easee support led me to believe that it should be possible to poll this sensor at any given time to retrieve an updated value. However, your answer implies that polling is only meaningful after the hour mark. If this is the case, I understand why you're puzzled, and I realize that my preferences might not be fulfilled. |
It has been my understanding that it is not the servers that are delaying the data from being sent out, but rather the equalizers that are randomly delaying the data before sending it to the servers. I guess, if it is the server that has the delay, then we can check at random time in the interval between 3 and 4 minutes past the hour mark if we did receive an update, and if not we try to poll the data from the servers. |
It seems I just have to acknowledge that fulfilling my wish of getting the value into Home Assistant and placing it on the right hour probably is impossible. However, to overcome the issue of not receiving any value for a whole hour, if no new value is received in the current hour I think it will be useful to poll the server a few times leading up to the next hour mark. I can also add that the issue of "empty" hours has happened more frequently this passed week. I've had 5 empty hours the last month, the last 4 happened from the 14. to the 20. this month. |
I have been experimenting a bit with monitoring the equalizers energy sensors and polling if data has not been received a few minutes after the hour mark. There is however a problem in that the values are not pushed out from the server unless there is a change in the value. Which is not a problem for the import energy sensor since it usually updates every hour, but the export energy sensor keeps the same value for large parts of the day due to solar energy not producing (and in fact this time of the year where I live also nothing is really produced during daytime either since the panels are covered with snow). So this means the values are more or less being polled every hour, not only when actually needed... I will probably create a pull request in a few days so others can test too. |
Hard to say if it is really an improvement, but I made a PR which polls some time between 2 and 3 minutes after each hour mark. |
The latest release now does a poll of the equalizer energy sensors shortly at a random offset after the hour mark. In my installation I have not really seen any conclusive evidence, I can still see the occasional hour where there is a dropout of data. In those cases the poll just returns the old data from the previous hour. |
Question
Hi!
Sometimes I have to reload the integration to get the latest sensor updates.
For example sensor.laddbox_cost_day but there are others behaving the same way.
Is there a setting for how often the integration should poll the easee API?
BR/Nicklas
What version of the integration are you using?
0.9.46
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: