AndroidAPS
AndroidAPS copied to clipboard
nightscout
Feature Request: Setting 100% Profile (without having to specify duration) via Automation
Currenlty, in order to make an automation which restores profile percentage to 100%, you should use the "change profile to" action. However, this may be problematic if you use different profiles for different days, since the automation can't know which profile should be used (see issues #3024 and #3025). Trying to make a "set profile percentage to 100%" action produces nonsense, since it requires to set a duration and besides requires the profile to be already 100% as a precondition.
Background: I have a weekday_profile for weekdays and a weekend_profile for weekends Automation A: when bg rises set 130% profile percentage Automation B: when bg stops rising/begins falling, restore profile to 100% Now notice that neither of the automations has any way of checking which profile am I currently using (weekday_profile or weekend_profile) (see #3024 and #3025), therefore automation B can't use an action such as "change profile to weekday_profile".
Automation A: when bg rises set 130% profile percentage
Automation B: when bg stops rising/begins falling, restore profile to 100%
That is not the most secure way to use automations. Better to set them for a duration of 10-15 minutes. If the triggering situation persists, then the same automation will kick in a second, third... time.
Yes, I always do set a duration but still prefer to set an additional counter-automation
Your set profile to 100% will NOT work. When you set a profile % change, automatically AAPS adds a corrolary looking if the profile is at 100%. If it is not100%, the set profile to x% will not kick in.
This is percisely my point... That's the problem I'm referring to - you can't set the profile back to 100% via automation. If it weren't so I wouldn't have created this issue...
I think this is a valuable feature to add, and one that I note has been requested multiple times over recent months in Discord - most recently by me! :-)
I understand the argument that automations should be set for short periods, and reapply for as long as necessary. But I don't agree with it. In principle, I think that anything that can be set by automation, should also be able to be reversed. Currently, there is an option to stop temp target, so why can't there be a similar option to stop temp profile percentage? And profile percentage changes every 10-15 minutes would create a very messy and hard to read graph on the AAPS home screen.
As far as use cases, I'm sure there are many. In my specific example, I was trying to use step count to measure whether I was having an active or sedentary day, and adjust the profile percentage accordingly. If I turn up the profile because I have done almost no steps for the last 3 hours, then I want to be able to turn it down as quickly as possible when that activity level increases (as well as set a high TT, assuming I've forgotten the ideal, which is to make the adjustments an hour before the exercise!). I know that Autosens is meant to do some of this, but does not respond quickly enough to this type of activity change.
I am trying to think of how this is best implemented. When you set a timed temporary profile change, either manually or via automation, it does not reset Autosens. When you manually set the profile percentage back to 100%, with no timed value, it does reset the Autosens. I could argue either way on whether Autosens should be reset, or used at all, in the example use that I've given. But I think that for consistency, if a timed profile % change does not reset Autosens, then there should be a way to stop that, both manually and via automation, that does not reset Autosens.
I'd also like to extend this suggestion further, and make it possible for an automation to override an existing temporary % profile. But I understand that this could interfere with existing users' automations that relied on this NOT being possible, so to implement that, there would have to be some sort of choice available on whether you wanted to allow this to happen or not. I'm not sure how hard that would be to implement. I also have noted when experimenting manually, if a timed percentage profile is in effect, and you enter a second timed % profile with a shorter time span, then when that time elapses, the profile does not change back to 100%, but rather falls back to the previous percentage! I was not expecting that, but that is okay, and automations could/should work the same way, providing it is documented and the user knows to expect this.
I welcome thoughts/discussions on this
