Closed lyonsbt closed 1 year ago
Refresh token has been refreshed on multiple occasions / server restarted but with no change
You state this, but it doesn't match the logs you provided. Also, when you say the "server was restarted" what exactly did you do?
Apologies, I have refreshed the token multiple times over several days, but not during the period of those logs today - not overly helpful, I know.
I've just refreshed the token again, however, and below are the relevant logs:
2022-10-10T13:26:25.995Z ring-mqtt Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens 2022-10-10T13:26:43.296Z ring-mqtt Username/Password was accepted, waiting for 2FA code to be entered. 2022-10-10T13:26:45.998Z ring-mqtt Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens 2022-10-10T13:26:55.399Z ring-mqtt Attempting connection to Ring API using generated refresh token... 2022-10-10T13:26:56.080Z ring-mqtt Successfully established connection to Ring API using generated token 2022-10-10T13:26:56.081Z ring-mqtt Received updated refresh token 2022-10-10T13:26:56.081Z ring-mqtt Saving updated refresh token to state file 2022-10-10T13:26:57.096Z ring-mqtt Successfully saved updated state file: /data/ring-state.json 2022-10-10T13:27:06.000Z ring-mqtt Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens
In terms of restarting, I only mean restarting my HA instance on the Raspberry Pi.
Thanks,
Brad
Have you actually restarted the addon? The logs don't look like you have.
Apologies for wasting your time - I've specifically restarted the addon and everything is connected fine now. I didn't think of that because I restarted my HA instance earlier today without any change.
In any case, thanks for your work / support on this add-on - much appreciated
Restarting HA doesn't restart addons. HA runs in its own container and, when you use the restart from the system menu it only restarts this container, addon containers aren't restarted. This is why I asked specifically what restart method you used, in my opinion, it's very misleading and it seems to trip people up regularly because they think this is a full restart. It is possible to fully restart the system from the HA UI, but you have to go to hardware and choose the 3-dots menu and select restart system, which will before an actual reboot of the hardware.
However, in the end, it still indicates that there is a bug I need to look into because regenerating the token should work without requiring a restart of the addon so I'll need to find time to look at this at some point.
Describe the Bug
Entities are unavailable due to authentication issue with Ring servers
Steps to Reproduce
Refresh token has been refreshed on multiple occasions / server restarted but with no change
Expected Behavior
MQTT entities available
Log Output
Screenshots
No response
Config File
Install Type
Home Assistant Addon
Version
2022.10.02 of OS, 5.0.3 of add-on
Operating System
Home Assistant OS
Architecture
N/A
Machine Details
Raspberry Pi