-
Notifications
You must be signed in to change notification settings - Fork 39
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
Equalizer - Main Fuse Limit #576
Comments
I think you should look at the service action easee.set_surplus_charging instead. Anyway, you can call the action like this:
I think the API you pointed to might anyway be the correct one for changing the setting you want, but I would think it is better to leave it alone since it is a setting that is probably stored in flash, and use the surplus charging setting instead which is more aimed for temporary limiting the current of the site. |
Ah, thanks for the advice, even if surplus charging seems aimed for those producing energy via solar or wind. But if the the result is the same I guess it could be used. An alternative would be to add a schedule and a weekly plan with the limits I want. But, that is also not possible when having smartcharging enabled. I have asked Easee support about it but no response yet. |
I am not sure I understand why it would be necessary to use Easee as operator for that. Do you not have the option to turn on surplus charging in your app then or? |
https://support.easee.com/hc/en-gb/articles/11554316308625-Surplus-charging "Surplus charging is only available if Easee is listed as the site operator." You're right, I can't turn surplus charging on since I have tibber as operator (smart charging) :( |
Hi @newlund, This should work, independent which operator you define. |
I can't use easee.set_charger_dynamic_limit since that is used by tibber to start/stop charging. |
I would still think you can use easee.set_circuit_dynamic_limit, just call the service once per minute or once per 10 seconds or whatever. If tibber sets it to 40A once in a while wont matter. The API is only called if the values are different than the service parameters, so you can call it as often as you like as long as the values are not idifferent every time. As I mentioned above, if the limit you set in main fuse limit is reached, charging will stop, it will wait 10 minutes and then retry. Of course easee.set_circuit_dynamic_limit knows nothing about the other consumers in the house so you have to intelligently control it to a value that makes sense. |
Yes, that is how I solved it before but then I changed ISP one night which caused my ongoing charging session to max out my main fuses. :) |
Yes, the fact that we have to go through cloud is a general problem when it comes to reliability... |
Well, the API does not change that limit, in the app it corresponds to the "equailizer limit" that you can see on the charger page if you click the limits button and expand the limits. |
Feature request
Is it possible to set the Equalizer Main Fuse Limit using this integration in HA?
https://support.easee.com/hc/en-gb/articles/8056639384977-Getting-started-Equalizer
"Under Main fuse limit you can set a limit for charging. The charger will not operate unless the building power consumption is below this limit. This is particularly useful if your energy provider changes rates based on the time of day.
When the consumption drops below the Main fuse limit, the Equalizer will wait 10 minutes before allowing the charger to increase charging power. This is to make sure the power is actually available."
Perhaps it is not available to set via Easee API?
I found this "configure-max-allocated-current" but it seems to set the "e-mobility fuse". What is that? :)
https://developer.easee.com/reference/post_api-equalizers-equalizerid-commands-configure-max-allocated-current
I would like to adjust the main fuse limit at 6:00 and 22:00 due to different power tariffs (Ellevio)
What version of the integration are you using?
0.9.68
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: