-
Notifications
You must be signed in to change notification settings - Fork 78
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
Help with def_current_state #352
Comments
I'm also struggling with the def_current_state parameter on runtime. even if I set it to true it will be ignored in the current period. the result is sensor.p_deferrable2 = 0.0.
|
This is a hard one to debug. |
In your case is maybe more explainable. |
Hi In my post there are logs. Is there another log you think of? |
Yes the logger changed a bit now with the guicorn integration. |
Hi @davidusb-geek you might have overseen, that I have passed two "true" states whereas just one is thermal load. the def2 (Wasching Maschine) is what I'm struggling with... here is a further example where def 1 (dishwasher) behaves as expected and def 2 (wasching maschine) not.
last week, I tried to solve it by giving a penalty per start of def load but without success. |
Hi
I'm trying to use the "def_current_state" function but can't make it work. Would appreciate some help. My understanding is that if you set "def_current_state" = true the def load will be running in the current period, even if it's not optimal. Typically to not turn off a load thats running. Is this correct?
I have an example below. I set "def_current_state" = true but the result is sensor.p_deferrable0 = 0.0.
The text was updated successfully, but these errors were encountered: