You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@felixerdy Thanks for the hint, thats new to me. Would be good to let users know that boxes can only be updated when setting an access_token first.
You can go into your settings and generate a new access_token for your senseBox
But I don't want to (as then I have to reflash the sensebox, and currently have no access to the physical box) ;)
Also it's weird that the managing user-account would use a box-specific access token, and failing to provide that invalidates the user account access token? Something seems fishy there
You are right. There is definitely still an issue that came from the usage of the access_token. We only observed that issue with boxes that had been registered some years ago that don't have an access_token yet. We still have to do the migration of old boxes in the database (i.e. adding an access_token).
Don't worry, if you just generate a new access_token, you won't need to update your box as long as you don't enable the authentication feature in the checkbox above
Activity
ubergesundheit commentedon Nov 1, 2020
/cc @felixerdy @umut0
felixerdy commentedon Nov 2, 2020
You can go into your settings and generate a new access_token for your senseBox
noerw commentedon Nov 3, 2020
@felixerdy Thanks for the hint, thats new to me. Would be good to let users know that boxes can only be updated when setting an access_token first.
But I don't want to (as then I have to reflash the sensebox, and currently have no access to the physical box) ;)
Also it's weird that the managing user-account would use a box-specific access token, and failing to provide that invalidates the user account access token? Something seems fishy there
felixerdy commentedon Nov 3, 2020
You are right. There is definitely still an issue that came from the usage of the access_token. We only observed that issue with boxes that had been registered some years ago that don't have an access_token yet. We still have to do the migration of old boxes in the database (i.e. adding an access_token).
Don't worry, if you just generate a new access_token, you won't need to update your box as long as you don't enable the authentication feature in the checkbox above