xDrip does not recognise new G7 sensor, despite correct code, and it working on Tandem T-slim pump

[shrewsdog]

Issue is xDrip not recognising a new sensor (which is working on Tandem T-Slim pump). System Status has correct TX ID for new sensor, but transmitter days and battery voltages are clearly for the old transmitter as days are 10, and voltage a 280 and b 176. Data source is shown as G6/G7/1/1+ Transmitter, and xDrip version is dfcbe80-20240917. Phone is Motorola Moto g(6) Play.

Catalogue of errors by me. Had G7 on day nine. Had been erratic, so inserted new one early. Then realised I needed to stop the first one. Used stop sensor which stopped both (at this point I believed I had not paired sensor 2). Then removed the 2 sensor TXs from bluetooth list on my phone and rebooted. Inserted sensor 3, paired it with pump which is receiving data correctly. New TX ID on phone is correct, but the status page is showing the old day nine sensor and battery data, and the main page records sensor error and 'Ends 7.48' tomorrow. I opted to put an incorrect TX ID in Xdrip, allowed it to try to connect, and when it failed reinputted the correct TX, but no change.

Both the expiring sensor and its replacement have been sat in microwave for hours. Applicator code for new sensor is correct.

It is as though the tx data for the first sensor is 'locked' on the phone.

[Navid200]

Please post a screenshot of the status page.

[Navid200]

Please leave the issue alone.
Please post the status page screenshot here in the discussion. To do that, please don't respond to an email.
Please log into GitHub and go to the discussions, respond to the post and tap on the paperclip symbol and choose the image file you want to attach.

[shrewsdog]

Latest status update

[shrewsdog]

First, thank you so much for your time. Second, the pump is tubed. I could disconnect the tube, and wrap the pump in tin foil, but could it go in the microwave instead? I have had my lunch bolus, so should manage being disconnected for a while. What time scale would you envisage?

[Navid200]

After you put the pump in the microwave, I expect that xDrip will connect in 20 minutes. When that happens, you will need to wait for 2-3 consecutive reads. This adds up to 35 minutes.

After that, you can bring the pump back out. Hopefully, it will reconnect. If it turns out that it doesn't, you can disable collection in xDrip as I explained before.

But, before doing any of this, make sure that you have disabled battery optimization for xDrip and for Bluetooth.
https://navid200.github.io/xDrip/docs/BatteryOpt.html
https://navid200.github.io/xDrip/docs/BluetoothBatteryOpt.html

[Navid200]

I am on my way out. I may or may not be able to respond occasionally for the next few hours.

[shrewsdog]

Noted, and thank you

[shrewsdog]

Sorry to report no resolution. Pump was suspended and in microwave for 60 minutes. It reconnected to the sensor within about 3 minutes. x-Drip did multiple scans, all timing out after 5 minutes. Phone was within a foot of the sensor for almost all that time.. Main screen still reporting 'G7 State not currently known'. Events log show nothing for the last three hours when last entry was 'switching to scan always on due to connect failures metric:0' As to battery optimisation, x-Drip was already set to not optimised. I have now reset the bluetooth battery to always optimised. Screenshot of status page attached, but I think nothing has changed.

[jamorham]

Please enable OB1 debugging - https://github.com/NightscoutFoundation/xDrip/wiki/Enabling-Debugging-for-OB1-collector then wait some time for it to gather data of failing to connect then use the event log upload feature and report back here something to provide a clue for the identity given when uploading the logs so I can find which are yours and I will take a look for what is happening.

If you haven't done so already, before doing that you may want to reboot your phone in case something is up with the bluetooth.

[shrewsdog]

Thank you so much. Phone was restarted, verbose mode on, and 30 minute log uploaded with AZAZAZAZ which will hopefully help you locate me.

[shrewsdog]

I appreciate we are probably in different time zones, but worry in case my reply on github (which I am not familiar with) was not correctly sent. Reply read - Thank you so much. Phone was restarted, verbose mode on, and 30 minute log uploaded with AZAZAZAZ which will hopefully help you locate me. From: JamOrHam ***@***.***> Sent: 28 September 2024 19:04 To: NightscoutFoundation/xDrip ***@***.***> Cc: shrewsdog ***@***.***>; Author ***@***.***> Subject: Re: [NightscoutFoundation/xDrip] xDrip does not recognise new G7 sensor, despite correct code, and it working on Tandem T-slim pump (Discussion #3687) Please enable OB1 debugging - https://github.com/NightscoutFoundation/xDrip/wiki/Enabling-Debugging-for-OB1-collector then wait some time for it to gather data of failing to connect then use the event log upload feature and report back here something to provide a clue for the identity given when uploading the logs so I can find which are yours and I will take a look for what is happening. If you haven't done so already, before doing that you may want to reboot your phone in case something is up with the bluetooth. — Reply to this email directly, view it on GitHub <#3687 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKHL5SZ3WJEY3CWBNURNRELZY3VQZAVCNFSM6AAAAABPALLMFKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZYGUZDENQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AKHL5SZZWEC3PAMSBE3DFKLZY3VQZA5CNFSM6AAAAABPALLMFKWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAUSI4U.gif> Message ID: ***@***.*** ***@***.***> >

[Navid200]

You clutter the thread every time you respond to an email in order to post here.
You just have to be patient. He is a volunteer like the rest of us with family and work and other obligations.