-
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
Missing basic_schedule sensor, and basic_schedule service often fails to set the service #229
Comments
Ah, found this in the logs now:
Any way to increase the polling interval? |
In the next release we will change the polling of the schedules such that the schedules are only polled when there is an actual change. (Which we can know because of data that is pushed over signalr). Worth knowing is that if you are seeing that /api/chargers/{self.id}/state poll failing it means that the intial state poll of the charger state failed. This polling normally only happens once after restart of HA, since all updated status information is transferred using signalr after that, but if the intial poll fails it will retry periodically until it succeds. Until then some things may be behaving strange since some of that data is missing and will cause strange and seemingly unrelated errors. In any case, I would recommend using the service for set_circuit_dynamic_limit instead of setting a schedule. When you set it to 5 or less the charger will pause and wait until set_circuit_dynamic_limit is called again and raised to 6 or more. |
Thanks, I tried using master but the same problem persists unfortunately. Could be that I've just been hammering the API so I'll try to disable the integration for a while and see if that helps. |
Well, maybe.
|
So there's a few thing I'm noticing:
Which is a bit odd I guess? Or does that just mean I don't have a weekly schedule set? Also this, is interesting to me because the DateTime format when calling the service is explicitly not localized, but when we are calling their API we are at UTC, is that intentional? Or rather, is that what the API expects?
Yeah, I've seen this mentioned a few times and it's probably the approach I'll end up with. I just had good experience using the schedule through Tibber, so I wanted to try to re-implement that with this integration. |
Yes, the API does return 404 when you do not have a schedule set, take it leave it that is how it works :) |
The problem
I've installed the latest version of easee_hass through HACS, running on the latest version of HA.
Everything seems to be working great except the basic schedule setup. First of all I can't get the binary_sensor for the basic schedule to work, it's always disabled even when there is a basic schedule set on the robot.
The reason I even want that sensor is to determine if my call to the 'set_basic_charge_plan' works. I currently have an automation that fetches price data from nordpool, converts the datetime format and updates the basic schedule with the next period where I'd like to block charging. The problem is that this works 1 out of 5 times with no error message, which I assume is problems with the easee cloud service, or just a delay between the cloud and the unit. But if I could only get the binary sensor to tell me if the schedule has been applied or not, it would at least compensate. Any tips on how to debug or get that sensor up and running?
Version of Easee integration having the issue?
0.9.45
Version of Home Assistant Core having the issue?
2022.10.4
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: