Just recently connected my first Dash pod to a Oneplus 8T device running aaps 3.0-rc3 (getting cgm data from BOYDA broadcast).
I had changed the standard Profile to run at 150% for a few hours but when the timer expired a communications error occured. At the same time AAPS stopped getting data from the BOYDA broadcast. This resulted in AAPS not getting any cgm data, while stuck in a loop trying to reconnect to Dash. I woke up at around 06.00 realising the pump had been going at 150% during the entire night.
Looking at the logs there is repeated connection retry pattern with exceptions occurring once every second. It appears as if the bluetooth device is being hammered with retries, possible preventing BOYDA to communicate on bluetooth with the cgm sensor? Shouldn't there be some sort of back off logic when trying to reconnect (1s, 5s, 30s, 90s, ..)?
I've uploaded my logs on my Google Drive and this error pattern can be found directly in AndroidAPS._2022-01-21_00-00-00_.1 The problems started sometime after midnight and was recovered when I manually reset the Profile at around 6am. The phone was well within range (1-1.5m) without obstacles in the way.
From what I can see in the logs, connect() failed to even start. This change will not fix the fact that connect() fails to start. It just retries less often.
Just recently connected my first Dash pod to a Oneplus 8T device running aaps 3.0-rc3 (getting cgm data from BOYDA broadcast).
I had changed the standard Profile to run at 150% for a few hours but when the timer expired a communications error occured. At the same time AAPS stopped getting data from the BOYDA broadcast. This resulted in AAPS not getting any cgm data, while stuck in a loop trying to reconnect to Dash. I woke up at around 06.00 realising the pump had been going at 150% during the entire night.
Looking at the logs there is repeated connection retry pattern with exceptions occurring once every second. It appears as if the bluetooth device is being hammered with retries, possible preventing BOYDA to communicate on bluetooth with the cgm sensor? Shouldn't there be some sort of back off logic when trying to reconnect (1s, 5s, 30s, 90s, ..)?
I've uploaded my logs on my Google Drive and this error pattern can be found directly in
AndroidAPS._2022-01-21_00-00-00_.1
The problems started sometime after midnight and was recovered when I manually reset the Profile at around 6am. The phone was well within range (1-1.5m) without obstacles in the way.https://drive.google.com/drive/folders/1ilK0hbdkXGnyXljvAw2iTELHuHSmL_pp