-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Feature Request: Different DynISF Adjustment Factor for Different Hours of the Day #2861
Comments
DynISF with good parameters during the day used to be too much at night - something I've noticed, too. Putting the adjustment factor into the profile would also fill the existing gap of ISF-scaling at a precentual profile change. Currently DynISF is not affected by a profile change see #2892 - I hope this will be solved before a stable release. Further please consider adding an automation action to set the DynISF adjustment factor. Another approach as a sidenote: Reducing the time-windows had the effect to be less aggressive at night/dawn - which has been fine for me. |
this DynISF realization takes profile % into account (when 'Obey profile' knob is switched On).
Some people find circadian being enough to deal with daily sensitivity change |
Very Interesting. I will try to increase the influence of the last 8 hours a little bit. Is there a place where dynisf Ideas or changes are discussed? |
hmm, that can be moved to DynISF (extended) settings too, nice idea :) |
I find in the recent time that I need an adjustment factor >100% to effectivly balance the day, but at night it causes some hypos. Tryed to get over it with targets and automations without sucsess.
I think it would be great if the adjustment factor would be set similarly to profile parameters, so that different adjustment factors could be set for different hours of the day (somewhat like ISF in SMB) (e.g. 113% from 9:00 and 100% from 23:00). I believe it makes much sense given that it's the main parameter affecting DynISF's result.
The text was updated successfully, but these errors were encountered: