Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Libre 2 serial numbers can be misrepresented #2725

Open
PhilTU opened this issue Mar 9, 2023 Discussed in #2716 · 5 comments
Open

Libre 2 serial numbers can be misrepresented #2725

PhilTU opened this issue Mar 9, 2023 Discussed in #2716 · 5 comments

Comments

@PhilTU
Copy link

PhilTU commented Mar 9, 2023

Discussed in #2716

Originally posted by PhilTU March 3, 2023
Someone said to me that UK/EU Libre 2 serial numbers start with a 3. Right now my sensor is reported by xDrip+ classic status page as ABBOTT0MH00.... whereas when it was working via the patched app it was reported there as ABBOTT3MH00....

I have seen at least one post where the status page didn't match the sensor box (someone posted a screenshot and a photo together).

Is this a bug ? If the 3 does indicate a Libre 2 (?) it could be a useful diagnostic as sometimes the wrong type is issued.

@PhilTU
Copy link
Author

PhilTU commented Aug 12, 2023

Was this fixed in #2845 ? I have seen serial numbers starting with a 3.....

@Navid200
Copy link
Collaborator

Navid200 commented Sep 4, 2023

Do you mind closing this issue as it sounds like a question. We can use discussions for questions.
Thanks

@PhilTU
Copy link
Author

PhilTU commented Sep 5, 2023

I can edit the title to "serial numbers are misrepresented" if this would be preferable.

The issue is not resolved. I had observed some correct reporting of 3MH serial numbers but my last sensor misreported as 0MH when it should have been 3.

It is possible the issue was fixed for the C5 sensor type in May revisions to OOP2 but it persists for "standard" L2 sensors.

@Navid200
Copy link
Collaborator

Navid200 commented Sep 5, 2023

OK,

It's just that usually, we have a discussion where we talk about something until it may become clear that we need to fix something, we can fix it in xDrip, and there are developers who believe there is no conflict between fixing it and the operation logic.
I cannot find the discussions where this judgement was made.

I occasionally have to go over issues and get updates to make sure we don't have issues that should be closed and if we do, close them.

If we have 20 open issues and a new one is opened, the developers can see that something needs their attention.
If we have hundreds of open issues and new one opens, no one may have a clue that anything needs their attention.

@PhilTU
Copy link
Author

PhilTU commented Sep 5, 2023

"PhilTU opened this issue on Mar 9 Discussed in https://github.com/NightscoutFoundation/xDrip/discussions/2716· 4 comments"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants