-
Notifications
You must be signed in to change notification settings - Fork 160
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
Adding Access Token to enable graph on apple watch #213
Comments
Why not? https://myhome?token=.... is what I am using. update-b4d96ed628b2e24f You should have the "careportal" role assigned. |
Thanks - got the token working but still have no working graph on the watch! Is there a workaround that I haven’t seen yet? |
If fact - there is no graph on NightGuard at all! |
Have tried all those things but no joy. Thanks for trying |
Did you check your TLS Certificate? What is your Rating?
Kloy40 ***@***.***> schrieb am Di. 6. Dez. 2022 um 19:51:
… Have tried all those things but no joy. Thanks for trying
—
Reply to this email directly, view it on GitHub
<#213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYPBFOKBBVJMHFWS73ATTLWL6DKZANCNFSM6AAAAAASVRS4SE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sorry - I don’t know what the TLS certificate is! How would I check that? |
Your can check your URI e.g. here: |
Thanks again - just checked that and rating came back as A. Nothing obviously wrong that i could see! |
You can send me your URI: I will have a look. |
Looks like you have configured your nightscout backend to be accessed by Api Secret. Just by entering your Api Token doesn't work for me. And that is what nightguard uses, too. |
This comment was marked as off-topic.
This comment was marked as off-topic.
You need to generate a token that can be used to access your site. Your Api
Secret shouldn’t be used for that.
Kloy40 ***@***.***> schrieb am Di. 6. Dez. 2022 um 21:46:
… Thanks Dirk,Apologies but I am not a techie, so not sure quite what you
are saying. My API secret is what I sent earlier - NorthBerwick. Is that
what I need to add to Nightguard to get it to access?I get readings etc on
Nightguard, just not the graph. RegardsKenSent from my iPhoneOn 6 Dec 2022,
at 20:38, dhermanns ***@***.***> wrote:
Looks like you have configured your nightscout backend to be accessed by
Api Secret. Just by entering your Api Token doesn't work for me. And that
is what nightguard uses, too.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because you authored the thread.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYPBFIFVA42RACBZIFCI43WL6Q3BANCNFSM6AAAAAASVRS4SE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I generated an access token for Nightguard and sent that to you earlier, as well as my API secret. Not sure what to do now! Should I generate another token and scrap the existing one that starts 9130?Sorry for being so stupid. RegardsKenSent from my iPhoneOn 6 Dec 2022, at 20:56, dhermanns ***@***.***> wrote:
You need to generate a token that can be used to access your site. Your Api
Secret shouldn’t be used for that.
Kloy40 ***@***.***> schrieb am Di. 6. Dez. 2022 um 21:46:
Thanks Dirk,Apologies but I am not a techie, so not sure quite what you
are saying. My API secret is what I sent earlier - NorthBerwick. Is that
what I need to add to Nightguard to get it to access?I get readings etc on
Nightguard, just not the graph. RegardsKenSent from my iPhoneOn 6 Dec 2022,
at 20:38, dhermanns ***@***.***> wrote:
Looks like you have configured your nightscout backend to be accessed by
Api Secret. Just by entering your Api Token doesn't work for me. And that
is what nightguard uses, too.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because you authored the thread.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYPBFIFVA42RACBZIFCI43WL6Q3BANCNFSM6AAAAAASVRS4SE>
.
You are receiving this because you commented.Message ID:
***@***.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Not sure whats wrong with your nightscout setup. Maybe you should ask there. Normally your logon screen should work with your token, too. But thats not the case. Only logon with Api-Secret is working. If you find out the reason for this, nightguard will work, too. |
Ok - I will see what I can find out. It does seem strange as everything was working fine until recently. Not sure whether it was upgrading Phone, watch or whatever. Or if it was moving from Heroku to google cloud. Somewhere along the line it has gone wrong. Thank for tryingKind regardsKenSent from my iPhoneOn 6 Dec 2022, at 21:12, dhermanns ***@***.***> wrote:
Not sure whats wrong with your nightscout setup. Maybe you should ask there. Normally your logon screen should work with your token, too.
But thats not the case. Only logon with Api-Secret is working. If you find out the reason for this, nightguard will work, too.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
My guess is it was the resetup of your nightscout backend in google cloud. At least it was for the user issues we had here. |
Thanks Dirk,Wasn’t aware that I had changed the setup when I migrated but will have a look and maybe ask Navid if this is common.Sent from my iPhoneOn 7 Dec 2022, at 07:17, dhermanns ***@***.***> wrote:
My guess is it was the resetup of your nightscout backend in google cloud.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hi Dirk - fixed it!!!
In NightGuard i needed to enter my URL as https://klnightscout.hopto.org?token=nightguard-90…. - ie, the format for entering it was wrong previously. Now has graph etc all showing. It seems to need the site reconfigured but i can sort that quickly i hope.
Thanks again for all your assistance and i hope that the above may be useful if anyone else has a similar issue.
Kind regards
Ken
…Sent from my iPad
On 6 Dec 2022, at 21:12, dhermanns ***@***.***> wrote:
Not sure whats wrong with your nightscout setup. Maybe you should ask there. Normally your logon screen should work with your token, too.
But thats not the case. Only logon with Api-Secret is working. If you find out the reason for this, nightguard will work, too.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
But you can’t still logon to your site with this token?
Kloy40 ***@***.***> schrieb am Mi. 7. Dez. 2022 um 11:35:
… Hi Dirk - fixed it!!!
In NightGuard i needed to enter my URL as
https://klnightscout.hopto.org?token=nightguard-90…. - ie, the format for
entering it was wrong previously. Now has graph etc all showing. It seems
to need the site reconfigured but i can sort that quickly i hope.
Thanks again for all your assistance and i hope that the above may be
useful if anyone else has a similar issue.
Kind regards
Ken
Sent from my iPad
> On 6 Dec 2022, at 21:12, dhermanns ***@***.***> wrote:
>
>
> Not sure whats wrong with your nightscout setup. Maybe you should ask
there. Normally your logon screen should work with your token, too.
>
> But thats not the case. Only logon with Api-Secret is working. If you
find out the reason for this, nightguard will work, too.
>
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you authored the thread.
—
Reply to this email directly, view it on GitHub
<#213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYPBFP7BYSWEE7MHXCSRFTWMBR5XANCNFSM6AAAAAASVRS4SE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Do i need to have that? I have always accessed my site with API secret! Happy to try to change it if you think there is merit in it, but everything seems to be working now.
…Sent from my iPad
On 7 Dec 2022, at 10:37, dhermanns ***@***.***> wrote:
But you can’t still logon to your site with this token?
Kloy40 ***@***.***> schrieb am Mi. 7. Dez. 2022 um 11:35:
> Hi Dirk - fixed it!!!
>
> In NightGuard i needed to enter my URL as
> https://klnightscout.hopto.org?token=nightguard-90…. - ie, the format for
> entering it was wrong previously. Now has graph etc all showing. It seems
> to need the site reconfigured but i can sort that quickly i hope.
>
> Thanks again for all your assistance and i hope that the above may be
> useful if anyone else has a similar issue.
>
> Kind regards
>
> Ken
>
> Sent from my iPad
>
> > On 6 Dec 2022, at 21:12, dhermanns ***@***.***> wrote:
> >
> >
> > Not sure whats wrong with your nightscout setup. Maybe you should ask
> there. Normally your logon screen should work with your token, too.
> >
> > But thats not the case. Only logon with Api-Secret is working. If you
> find out the reason for this, nightguard will work, too.
> >
> > —
> > Reply to this email directly, view it on GitHub, or unsubscribe.
> > You are receiving this because you authored the thread.
>
> —
> Reply to this email directly, view it on GitHub
> <#213 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAYPBFP7BYSWEE7MHXCSRFTWMBR5XANCNFSM6AAAAAASVRS4SE>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
I thought that that was the reason. But didn’t seem so. So you just entered
the token in a wrong format? How did you enter it before?
Kloy40 ***@***.***> schrieb am Mi. 7. Dez. 2022 um 11:39:
… Do i need to have that? I have always accessed my site with API secret!
Happy to try to change it if you think there is merit in it, but everything
seems to be working now.
Sent from my iPad
> On 7 Dec 2022, at 10:37, dhermanns ***@***.***> wrote:
>
>
> But you can’t still logon to your site with this token?
>
> Kloy40 ***@***.***> schrieb am Mi. 7. Dez. 2022 um 11:35:
>
> > Hi Dirk - fixed it!!!
> >
> > In NightGuard i needed to enter my URL as
> > https://klnightscout.hopto.org?token=nightguard-90…. - ie, the format
for
> > entering it was wrong previously. Now has graph etc all showing. It
seems
> > to need the site reconfigured but i can sort that quickly i hope.
> >
> > Thanks again for all your assistance and i hope that the above may be
> > useful if anyone else has a similar issue.
> >
> > Kind regards
> >
> > Ken
> >
> > Sent from my iPad
> >
> > > On 6 Dec 2022, at 21:12, dhermanns ***@***.***> wrote:
> > >
> > >
> > > Not sure whats wrong with your nightscout setup. Maybe you should ask
> > there. Normally your logon screen should work with your token, too.
> > >
> > > But thats not the case. Only logon with Api-Secret is working. If you
> > find out the reason for this, nightguard will work, too.
> > >
> > > —
> > > Reply to this email directly, view it on GitHub, or unsubscribe.
> > > You are receiving this because you authored the thread.
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
#213 (comment)
>,
> > or unsubscribe
> > <
https://github.com/notifications/unsubscribe-auth/AAYPBFP7BYSWEE7MHXCSRFTWMBR5XANCNFSM6AAAAAASVRS4SE
>
> > .
> > You are receiving this because you commented.Message ID:
> > ***@***.***>
> >
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you authored the thread.
—
Reply to this email directly, view it on GitHub
<#213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYPBFK3H4VHSKZAIEAH7HLWMBSODANCNFSM6AAAAAASVRS4SE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I also had an issue with Sugarmate a few weeks ago and it turned out to be that i needed to add a token on there to get it to work so i just added 9130cb5b41edb3de as the token and it worked fine. When i added the token to NightGuard i just entered the same ie https://klnightscout.hopto.org? 9130cb5b41edb3de
The correct format appears to be https://klnightscout.hopto.org?token=nightguard-9130cb5b41edb3de
All working fine now.
…Sent from my iPad
On 7 Dec 2022, at 10:47, dhermanns ***@***.***> wrote:
I thought that that was the reason. But didn’t seem so. So you just entered
the token in a wrong format? How did you enter it before?
Kloy40 ***@***.***> schrieb am Mi. 7. Dez. 2022 um 11:39:
> Do i need to have that? I have always accessed my site with API secret!
> Happy to try to change it if you think there is merit in it, but everything
> seems to be working now.
>
>
> Sent from my iPad
>
> > On 7 Dec 2022, at 10:37, dhermanns ***@***.***> wrote:
> >
> >
> > But you can’t still logon to your site with this token?
> >
> > Kloy40 ***@***.***> schrieb am Mi. 7. Dez. 2022 um 11:35:
> >
> > > Hi Dirk - fixed it!!!
> > >
> > > In NightGuard i needed to enter my URL as
> > > https://klnightscout.hopto.org?token=nightguard-90…. - ie, the format
> for
> > > entering it was wrong previously. Now has graph etc all showing. It
> seems
> > > to need the site reconfigured but i can sort that quickly i hope.
> > >
> > > Thanks again for all your assistance and i hope that the above may be
> > > useful if anyone else has a similar issue.
> > >
> > > Kind regards
> > >
> > > Ken
> > >
> > > Sent from my iPad
> > >
> > > > On 6 Dec 2022, at 21:12, dhermanns ***@***.***> wrote:
> > > >
> > > >
> > > > Not sure whats wrong with your nightscout setup. Maybe you should ask
> > > there. Normally your logon screen should work with your token, too.
> > > >
> > > > But thats not the case. Only logon with Api-Secret is working. If you
> > > find out the reason for this, nightguard will work, too.
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub, or unsubscribe.
> > > > You are receiving this because you authored the thread.
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> #213 (comment)
> >,
> > > or unsubscribe
> > > <
> https://github.com/notifications/unsubscribe-auth/AAYPBFP7BYSWEE7MHXCSRFTWMBR5XANCNFSM6AAAAAASVRS4SE
> >
> > > .
> > > You are receiving this because you commented.Message ID:
> > > ***@***.***>
> > >
> > —
> > Reply to this email directly, view it on GitHub, or unsubscribe.
> > You are receiving this because you authored the thread.
>
> —
> Reply to this email directly, view it on GitHub
> <#213 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAYPBFK3H4VHSKZAIEAH7HLWMBSODANCNFSM6AAAAAASVRS4SE>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
Great - and thanks for the feedback |
Graph hasn’t been working for a few weeks now and looks to be related to updates and the need to add an access token. Can someone please specify the format for adding the token please? The example on NightGuard app - http://Nightscout?token=mytoken doesn’t make any sense to me!
The text was updated successfully, but these errors were encountered: