-
-
Notifications
You must be signed in to change notification settings - Fork 86
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
Support for Libre 2 #903
Comments
We would love to support the Libre 2, but after some initial investigation it seems Abbott has made significant changes to the device protocol, so this will not be easy to implement. I hope that we'll get there eventually, but don't have any estimate on availability yet. |
Is there any way I could help? |
Do you have experience with decoding packets using Wireshark? |
Sorry for the late response! I am not very experienced but had a look at the communication and it looks like abbott is using the serial number of the device to do some sort of encryption of the packages |
@DreadRoberts Yeah, I looked into this myself last month, and while the Libre 2 reader appears to use the same HID protocol and initialization sequence as the Libre 1 reader, all communications after the initialization sequence appears to be encrypted. What makes you think they're using the serial number as an encryption key? |
The last and only message which is transmited unencrypted is the serial number. |
I commented on another project what my current findings are, if you are interested: |
I'll have a look on it. |
I've recently written an implementation of the encrypted protocol for a python library called freestyle-hid. I found this repo through that one because this issue was linked in one of the issues from that library that was also about the libre 2. While I don't have the time to get into this codebase, I'd be happy to provide some guidance if someone else wants to implement support. |
I have a libre 2 device and would like to upload my data in Tidepool. Do you have any plans to support the Libre 2?
The text was updated successfully, but these errors were encountered: