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
Problem Sibionics reading on app update #157
Comments
Juggluco test whether a value is valid:
Among which it checks that a value is below 502. Where did Juggluco display 1245? Have you found a place where this check is not made? Such large values will be displayed as missing values. |
On the juggluco app and it broadcasted it to aaps. I deleted it from aaps
for safety.
Also, I started another sensor because and it started displaying new values
since 1 min first was 45 then 180 and it jumped around for a little while,
now it seems stable, the problem is that this values where also
broadcasted, maybe it should have an option to disable broadcasts for x
time, while the new sensor warms up.
El jue, 9 de may de 2024, 4:15 p. m., Jaap Korthals Altes <
***@***.***> escribió:
… Juggluco test whether a value is valid:
https://github.com/j-kaltes/Juggluco/blob/be880bee5c243b554aa14001ca09f9b5bc1a5d6f/Common/src/main/cpp/SensorGlucoseData.h#L115
Among which it checks that a value is below 502. Where did Juggluco
display 1245? Have you found a place where this check is not made?
Such large values will be displayed as missing values.
—
Reply to this email directly, view it on GitHub
<#157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRKWDM6L3DDJH4FOS74MV3ZBPYQTAVCNFSM6AAAAABHPQJFWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBTGQ4TQMRZG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
El jue, 9 de may de 2024, 4:15 p. m., Jaap Korthals Altes <
***@***.***> escribió:
… Juggluco test whether a value is valid:
https://github.com/j-kaltes/Juggluco/blob/be880bee5c243b554aa14001ca09f9b5bc1a5d6f/Common/src/main/cpp/SensorGlucoseData.h#L115
Among which it checks that a value is below 502. Where did Juggluco
display 1245? Have you found a place where this check is not made?
Such large values will be displayed as missing values.
—
Reply to this email directly, view it on GitHub
<#157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRKWDM6L3DDJH4FOS74MV3ZBPYQTAVCNFSM6AAAAABHPQJFWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBTGQ4TQMRZG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I should have corrected it strait away, but I thought it didn't matter because of the reason I just mentioned. A few values that are 1080 mg/dL too large is every well possible. But after 5 minutes the values are normal. |
The bug should be fixed in 8.0.17: https://www.juggluco.nl/Juggluco/download.html |
The thing is that it never went back to normal, it settled on 236 while I
was 106 with a glucometer, before the update it was showing 116. I waited
like 30 mins to see if it went back to normal but it didn't and decided to
change the sensor for a new one.
It's weird that it was that off with the update, while using the same
sensor.
El jue, 9 de may de 2024, 4:29 p. m., Jaap Korthals Altes <
***@***.***> escribió:
… I should have corrected it strait away, but I thought it didn't matter
because of the reason I just mentioned. A few values that are 1080 mg/dL
too large is every well possible. But after 5 minutes the values are normal.
—
Reply to this email directly, view it on GitHub
<#157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRKWDMUD2DKGCJETMDW5WLZBP2D7AVCNFSM6AAAAABHPQJFWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBTGU2DQMJXGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
That is something of the sensors. If you have a Chinese telephone number you can run the Chinese Sibionics app and receive all past values. https://cgm-prod-public.oss-cn-shenzhen.aliyuncs.com/app/update/android/%E7%A1%85%E5%9F%BA%E5%8A%A8%E6%84%9F.apk When you press on Blood glucose device, followed by view data, you can view and save the individual values. |
I dont have one.
So its better to update the app when the sensor time is over?
…On Thu, May 9, 2024 at 5:23 PM Jaap Korthals Altes ***@***.***> wrote:
That is something of the sensors. If you have a Chinese telephone number
you can run the Chinese Sibionics app and receive all past values.
https://cgm-prod-public.oss-cn-shenzhen.aliyuncs.com/app/update/android/%E7%A1%85%E5%9F%BA%E5%8A%A8%E6%84%9F.apk
When you press on Blood glucose device, followed by view data, you can
view and save the individual values.
—
Reply to this email directly, view it on GitHub
<#157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRKWDPWHWLEJ27VPCB5IMTZBQAPDAVCNFSM6AAAAABHPQJFWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBTGU4TGNZZGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Ing. Raúl Abraham C.
Director General
DEPOSITOS ELECTRICOS DE MORELIA S.A. DE C.V.
|
If you update from Juggluco before version 8.0.9, you can better update with a new sensor. From a later version is doesn't matter. |
Hi, first of all thanks for your work on this app.
I've been using juggluco with Sibionics sensor and it was working great, until I updated the app. I was like 4 builds behind. I had a working sensor already when I updated, I had 115mg/dl but when I made the update it jumped to 1245 or something crazy like that, then it dropped to 250 and it settled somewhere around that number. I checked with a glucometer and I was 106.
What can I do? Sensor is like 20days old.
The text was updated successfully, but these errors were encountered: