Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    infoneo
    @infoneo
    I'm wondering why I get "TBR CANCELLED alert" every time when I try to set bolus higher than 2U in my room (maybe I have some kind of rf noise). I have no problems with this alert on SMB-s (probably because SMS-ses are lower than 2U). I tried to use ruffy manually - I can set more than 2U without problems. Temporary solution is to set boluses partially or set directly via the pump buttons... is there a way to experiment with protocol timeouts etc?
    Mike
    @libxmike
    @infoneo was the 2U delivers? do you get the "TBR CANCELLED alert" AFTER 2U delivery? do you get the "TBR CANCELLED alert" EVERY time?
    infoneo
    @infoneo
    @libxmike I found that 2U is the amount that is delivered without problems. I have problems with values above 2U - bigger are worse... What I found - it is almost impossible to deliver my typical meal dose - 8U (in my room) maybe 1 of 20 tries works. Now I'm out of the city (no wifi nor BT noise) and I can set any amount without error.
    swissalpine
    @swissalpine
    @infoneo Probably it's necessary to change your phone.
    I can give boluses everywhere ...
    without any connection losses.
    Andy Rozman
    @andyrozman
    So I got my new phone Galaxy S9 and it seems that Samsung is stopping upgrades to 8.1 (they were planned for middle of the year, but it seems nothing is happening, or at least not as fast as I hoped). So my option would be to root device and to pairing with my VM (as I did for my Galaxy A5) and then transfer pairing again... I know that after I root device, I won't be able to upgrade anymore at least not until I reflash my phone with original image (if new Oreo 8.1) finally comes... Does perhaps anybody else uses AAPS/Combo with S9 here? What did you do?
    Mike
    @libxmike
    @andyrozman I did it with Galaxy S8, rooted, paired Combo with Galaxy S4 mini, transferred necessary info/files to S8 and worked flawless. Same procedure would be on S9, BUT for S9 there is LineageOS 15.1 so just install LOS and pair with S9
    Andy Rozman
    @andyrozman
    @libxmike This is my main (only) phone, and I am not so sure about running LineageOS on it...
    Mike
    @libxmike
    @andyrozman then you have no other option as root and transfer pairing info, but, LOS is better as OOTB system unless you relay on Samsung's proprietary software
    Andy Rozman
    @andyrozman
    I might try it out, I am just not sure about it.
    pedroll
    @pedroll
    Is there any work in progress to have autotune running with the combo?
    I was taking a look at the unrecognized TBRs and creating the missing fields on the autotune side.
    But I see a difference in the iob reported by aaps and the one calculated by autotune.
    I do not have data on a pump that works with the autotune to compare the difference between the treatments json
    Is there a place where I can get example treatments.json from a pump running on autotune?
    cranetim
    @cranetim
    Hello all. I have a combo pump that was given to me recently so I've sorry the last week reading up on AAPS with the combo. When I received the pump it was out of warranty but in good operating order. I turned it on again today and the bottom Almost half of lcd it's blank. Upper half is still readable and pump appears to still operate properly. The only reason I can find in docs that this might hang me up is during the initial pairing. Will I be able to see pump code in order to pair with phone (LG Nexus 5x)? Furthermore am I missing something obvious or am I correct that after pairing I will not need lcd access?
    Andy Rozman
    @andyrozman
    @cranetim You would need display when pairing, and when you change infusion set (you need to stop pump, change infusion set, prime pump and start pump). So if you can see the middle part you should be ok...
    kallnap
    @kallnap
    @cranetim I would assume pairing is the worst, because you need to be able to decypher the 10 digit code
    Johannes Mockenhaupt
    @jotomo
    You can try turning the display upside down via the configuration software, which might move the pairing key to the area still readable
    cranetim
    @cranetim
    @andyrozman
    cranetim
    @cranetim
    Wanted to ask you a few questions about your setup with the combo and Nexus 5x. Does the 5x not work with xdrip and G5? Or is it just intermittent as far as looping ability to connect to sensor? Also you mentioned using a Galaxy (ithink) for xdrip setup? Could you explain your combo/g5 setup with the Nexus 5x in a little more detail. Finally, with studio trying to build aaps from combo branch following the new wiki instruction pages. I get to the change to combo branch but after I complete that the "generate signed apk" option is not available from the build menu? Surely this is some rookie mistake on my part......
    Not sure why I typed the word 'looping' above. Please ignore...
    Andy Rozman
    @andyrozman
    @cranetim Like I wrote in PM, I don't have such setup. My setup is Galaxy A5 (now Galaxy S9) / Combo / G4 (xbridge+xdrip+) / AAPS (1.58)
    cranetim
    @cranetim
    My mistake I've confused a message from FB group with you somehow. Sorry about the mix up.
    Grégory Beloncle
    @gregorybel
    @all ist someone else getting "pump unreachable" issue? if yes, what do you do in this case? how often does it happen?
    Andy Rozman
    @andyrozman
    @gregorybel You need to be more specific. On which version are you getting this, and with which hardware? I got this error before (on 1.58 and on Galaxy A5 (rooted)). My solution was: 1. Force stop AAPS and Ruffy and restart (helped in 70% of cases), 2. Restart phone... How often it happened... in begining about every few days, they I got new ruffy and it happened less (once two weeks or even less)
    Grégory Beloncle
    @gregorybel
    @andyrozman thank you. I don't search for a solution, just want to know how many people has this issue and how they solved it. I already know how to proceed 😉
    th122
    @th122
    @gregorybel Rock stable as far as the pump connection is concerned. Even during the ca. 5 days while the battery is draining until failure. (Old combo/Moto g1)
    Andy Rozman
    @andyrozman
    @gregorybel Another note. I have been using S9 for last month, with LineageOS and here I don't get this error (at least I haven't so far). (Knocking on the wood)
    swissalpine
    @swissalpine
    @gregorybel Same here. Since I stay away from my formerly Sony Z3c with LineageOS I haven't seen the pump unreachable error.
    AdrianLxM
    @AdrianLxM
    @gregorybel I do have a branch of Ruffy that accepts a broadcast to kill the service. And there is a branch of AAPS that adds a button to the combo tab to kill Ruffy and recreate/reconnect. You would need to merge that into a current AAPS as it is based on a prior RC.
    If it helps, we can automate that. It helps on one of my phones.
    MasterPlexus
    @MasterPlexus
    @gregorybel , I've got it in the past, and my solution was to pine/lock the Ruffy and AAps in the recent Apps list. It looks like that this is a trigger to prevent killing the apps by the Energiemanagement of my OnePlus smartphone. After that no one unreachable error occurs.
    Tobias
    @T-o-b-i-a-s
    The pump unreachable alerts that used to be there and required a button press on the pump or a complete reboot of the phone are gone since months, I cannot tell which AAPS or ruffy version made the difference.
    bruno
    @bboi61
    @gregorybel My pump (2011) never had this error. A pump from 2012 about once a month. A quick restart from the smartphone helps me.
    Grégory Beloncle
    @gregorybel
    thanks to all of you, so this is almost not an issue. on my side I see it one or two times a day. often in the night. Currently I use a BT watchdog implemented by @jotomo works like a charm but I got it merged for rc4 but too complicated for rc7. @AdrianLxM if I could get your branch with automatic restart it would be great. This needs to run automatic otherwise it makes no fun at night to wake-up and restart Ruffy!
    I think root cause is phone killing aaps and or Ruffy. On my honor, no chance to get app protected against battery optimization even if I activated 4 options
    AdrianLxM
    @AdrianLxM
    @gregorybel test it. If the button helps, we can automate it.
    Lexsus
    @Lexsus
    @cranetim Nexus 5x with Android 8.1 does not work consistently with Dexcom G5. I install LineAgeOs and now there are no problems. P.S. I could not install the LineAgeOs for Nexus 5x, but I install Pixel 2 Lineage software to Nexus 5x.
    Grégory Beloncle
    @gregorybel
    @AdrianLxM ok !
    Mondelman
    @Mondelman
    Hi all. Some weird behavior with alarms. It's not possible to silence them, only rebooting phone. It's not xDrip alarm, as you can easily mute them, so it should be AndroidAPS. Any idea?
    Savek-CC
    @savek-cc
    I sometimes have alarms staying active even though I swiped them away. Have to open xDrip an go to the menu to "snooze alarm" again to silence it @Mondelman
    Lexsus
    @Lexsus
    With RC7 I have problems- aaps crashed when i use careportal or when I set custom temp target. what should I do? Create issue on github?
    Grégory Beloncle
    @gregorybel
    @Lexsus Look at current issues, I think some are already opened and maybe already fixed in dev
    Lexsus
    @Lexsus
    I not find issues.
    Joost Hart
    @hartlijn
    @Lexsus open log file and look for errors at that timestamp just before the crash.
    Mondelman
    @Mondelman
    Hi again. It was a careportal error, reporting a non uploadable value... quite weird. I removed it from the list and now it is peaceful...
    FlyRad
    @FlyRad
    @Lexsus a view month ago I also tried to install linageOS on my Nexus 5x. I think there was/is a problem because of different filesystem, therefore it was not possible to install. In a short time I have to chage from Libre to Dexcom G5 because of skin irritation. Does that mean I also have to update with lineageOS for Pixel 2? I use the Combo.
    Mike
    @libxmike
    @Lexsus if you have Android 8.1 then it is not necessary, the reason for LOS is pairing with Combo, pairing is possible from 7.1 /LOS 14.1 or very old Android version 4.4 or somthing