AndroidAPS icon indicating copy to clipboard operation
AndroidAPS copied to clipboard

Issue with boluswizard Combo Combov2 driver

Open Gosee1960 opened this issue 2 years ago • 5 comments
trafficstars

Reporting bugs

  • Note the precise time the problem occurred and describe the circumstances and steps that caused the problem
  • Note the Build version (found in the About dialog in the app, when pressing the three dots in the upper-right corner).
  • Obtain the app's log files, which can be found on the phone in /storage/emulated/0/Android/data/info.nightscout.androidaps/ See https://wiki.aaps.app/en/latest/Usage/Accessing-logfiles.html
  • Open an issue at https://github.com/nightscout/AndroidAPS/issues/new

Time accident 09.43

With the boluswizard , 15 gr carbs for 40 min later, it says 1,4 bolus. I dit OK Then AAPS give a warning to me so i must check if bolus was given. I did that, and bolus was given. I checked in aaps the bolus/smb historie and also in the pump. They were both oke and the same

But the carbs in future was not registrated. I waited and check again but still no carbs in future, soa i manually at only 15 carbs.

I try to put the logs and some printscreens, maybe this will help

AndroidAPS.log Screenshot_20231117-094655_AAPS Screenshot_20231117-094727_AAPS Screenshot_20231117-094747_AAPS Screenshot_20231117-094803_AAPS Screenshot_20231117-095005_AAPS Screenshot_20231117-100817_AAPS

Thanx in advance

Greetz Jose

Gosee1960 avatar Nov 17 '23 09:11 Gosee1960

@dv1 the bolus failed (success = false reported to AAPS) thus carbs were not recorded. But the bolus record was written to DB later. can you check why?

MilosKozak avatar Dec 06 '23 10:12 MilosKozak

Yes, this is a known error. It also happens to me. I am trying to fix this.

dv1 avatar Dec 06 '23 22:12 dv1

Just had the exact same problem yesterday evening and I was confused - funny reading this now..

Added carbs manually then.

blaqone avatar Dec 12 '23 06:12 blaqone

regularly getting the same problem (bolus failure) bolus is given and appears in database at next connect log shows: ]18:07:20.510 [DefaultDispatcher-worker-5] E/PUMPCOMM: [PumpIO$startCMDPingHeartbeat$2.invokeSuspend():2067]: [PumpIO] Error caught when attempting to transmit CMD ping packet - stopping CMD ping heartbeat 18:07:20.514 [DefaultDispatcher-worker-5] E/PUMPCOMM: [PumpIO$startCMDPingHeartbeat$2.invokeSuspend():2070]: [PumpIO] Error: info.nightscout.comboctl.base.ApplicationLayer$IncorrectPacketException: Incorrect packet: expected CMD_PING_RESPONSE packet, got CMD_READ_DATE_TIME_RESPONSE one at info.nightscout.comboctl.base.PumpIO$sendPacketWithResponse$4$1.invokeSuspend(PumpIO.kt:1456) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:793) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:697) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:684)

full log available.

NicoAAPS avatar Apr 02 '24 15:04 NicoAAPS