-
Notifications
You must be signed in to change notification settings - Fork 56
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
Can't get 1-minute data from the application #185
Comments
Is the file completely empty or does it contain the header ("Sensorid nr UnixTime YYYY-mm-dd-HH:MM:SS TZ Min mmol/L Rate ChangeLabel")? What happens when you turn on left menu->Settings->Web server and go to http://127.0.0.1:17580/x/stream?header&days=1 in chrome on the same phone as Juggluco is running? (You need to use http not https, which sometimes is used despite that http is specified). |
Yes, the file is completely empty. |
If you can't access the webserver, you probably didn't turn it on. Did you set [x] Active? What about the other commands from https://www.juggluco.nl/Juggluco/webserver.html?urlstart=http://127.0.0.1:17580 ? |
|
Cancelled can only come from pressing left menu->Sibionics with the Export dialog open followed by the back button. |
I don't use Sibionics at all... |
Can I put another version of the app and connect an already activated sensor (6 days out of 14) to it? Or could this cause the sensor to fail? |
You don't need to use Sibionics sensors to press on Left menu->Sibionics. |
I mean that I don't press Left menu->Sibionics at all. The question is could i connect my activated Libre3 to another phone with another version of Juggluco? |
That is a totally different issue. The answer is that you can as long as Juggluco uses the same Libreview account id number. |
I’ve updated version of Juggluco (8.0.4 ->8.1.5) and all is ok |
I have successfully activated the Libre3 sensor with juggluco, get glucose values in the app every minute. But when I try to export the data in tsv format, I get an empty file. what could be the problem?
The text was updated successfully, but these errors were encountered: