-
Notifications
You must be signed in to change notification settings - Fork 52
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 Nightscout 0.9.x #16
Comments
It works for me - after I spotted this in 0.9.x release notes:
Works a treat now. |
Great hint. I think this uploader should be enhanced to support the latest nightscout version, but at least this seems to be a workaround! Thanks for sharing this ;-) |
Nightscout versions 0.9.0 and above support both the old-style API KEY authentication, but also a new authentication token system where you can create multiple tokens with different permissions. The above workaround is for clients that don't implement the new token system, which require global permission to uploading treatments to work properly. |
The workaround worked for me, too. I added the change to my raspberry docker image: |
I'll take a look at this newer API key need, I am working in my own fork of the uploader which I'm happy to share and continue to work with, as this repository seems to have been abandoned. |
That sounds great. Let me know if I can test a new version! |
I have just published a release from my fork. This does not fix the need to use the workaround above, but there are a lot of changes in the backend to make maintenance of this project easier. NOTE: I have enabled logging of internal Logcat messages to help me debug this in day to day use - these are uploaded to app.bugfender.com - if you don't want me to see the log messages from the app, do not install it. Please feel free to use the release and report any issues direct to my repository. |
I've published another big set of changes to this in my fork - and asked for a pull. There is another Release also, looking for feedback if it works. |
This version works fine for me on the nightscout 0.8.x backend.
But using nightscout 0.9.x it seems that the hashing algorithm of the api secret
has been changed to SHA1.
Am I missing something or is 0.9 not supported anymore?
The text was updated successfully, but these errors were encountered: