Closed rfletcher closed 2 years ago
I am looking for a fix to this. Right now, it appears that a removal of the integration and re-addition will fix this. I know this is not ideal right now, but I am not sure of the best way to fix this at the moment
I haven't entirely figured out what's going on yet, but removal and re-addition seems to work for a very short time, but that's it.
This should be resolved in 0.5.0-beta.3 https://github.com/bretterer/home-assistant-rivian/releases/tag/0.5.0-beta.3. Please give it a shot and let me know
So far so good
On Fri, Oct 7, 2022, 8:45 PM Brian Retterer @.***> wrote:
This should be resolved in 0.5.0-beta.3 https://github.com/bretterer/home-assistant-rivian/releases/tag/0.5.0-beta.3. Please give it a shot and let me know
— Reply to this email directly, view it on GitHub https://github.com/bretterer/home-assistant-rivian/issues/18#issuecomment-1272215714, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACQARWT7P4BTTZU25BCMYZ3WCDU5PANCNFSM6AAAAAAQ5SNWZQ . You are receiving this because you commented.Message ID: @.***>
This should be resolved in 0.5.0-beta.3
Looks good to me. I upgraded ~8 hours ago and my session is still alive. Thanks!
Resolved with 0.5.0
Rivian pushed out an update that signed many (all?) users out of the mobile app the other night, and I've had trouble with my HA Rivian sessions ever since.
It looks like something related to API authentication has changed. Here's a traceback: