Home Assistant 2024.6.3 issued started : Failed updating jwt token #80
Comments
|
+1 |
|
@dcsim0n do you have a chance to take a look at this? |
|
It may be a couple days. I’ll add a reminder to take a look ASAP
Dana Simmons
https://linkedin.com/in/dcsimon
KN4BEV
…On Mon, Jun 24, 2024 at 9:56 AM Luke Lashley ***@***.***> wrote:
@dcsim0n <https://github.com/dcsim0n> do you have a chance to take a look
at this?
—
Reply to this email directly, view it on GitHub
<#80 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIKHAURGBD3DYBMR3VCAVYTZJAQPDAVCNFSM6AAAAABJVVJIQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWGY2DIMBSGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
|
Having the same problem here. "Failed updating jwt token" |
|
Any updates on this yet? |
|
I looked at it briefly in my dev environment. When sending the auth request
the jwt token isn’t found in the response. It seems likely that the
southern company website changed and HA needs to change to. I’ll spend
some more time looking at it later this week.
Dana Simmons
https://linkedin.com/in/dcsimon
KN4BEV
…On Sat, Jul 6, 2024 at 3:19 PM Chance Callahan ***@***.***> wrote:
Any updates on this yet?
—
Reply to this email directly, view it on GitHub
<#80 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIKHAUVONQVK7THAK35R5TTZLA7KZAVCNFSM6AAAAABJVVJIQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRHA4TAOBYHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
rixth
pushed a commit
to rixth/southern_company_api
that referenced
this issue
Jul 10, 2024
Couple things have broken/changed: * `LoginComplete` now 500s on a `null` being sent as the `ReturnUrl`. Send a valid value. * `LoginComplete` now returns a 302 on success. Cookies are only returned by `aiohttp` for the last request that was followed, so we need to disable following redirects. I confirmed that error handling for invalid username/password still works as expected. Resolves Southern-Company-HA/southern-company-hacs#80
rixth
pushed a commit
to rixth/southern_company_api
that referenced
this issue
Jul 17, 2024
Couple things have broken/changed: * `LoginComplete` now 500s on a `null` being sent as the `ReturnUrl`. Send a valid value. * `LoginComplete` now returns a 302 on success. Cookies are only returned by `aiohttp` for the last request that was followed, so we need to disable following redirects. I confirmed that error handling for invalid username/password still works as expected. Resolves Southern-Company-HA/southern-company-hacs#80
Lash-L
pushed a commit
to Southern-Company-HA/southern_company_api
that referenced
this issue
Jul 17, 2024
Couple things have broken/changed: * `LoginComplete` now 500s on a `null` being sent as the `ReturnUrl`. Send a valid value. * `LoginComplete` now returns a 302 on success. Cookies are only returned by `aiohttp` for the last request that was followed, so we need to disable following redirects. I confirmed that error handling for invalid username/password still works as expected. Resolves Southern-Company-HA/southern-company-hacs#80 Co-authored-by: Thomas Rix <[email protected]>
|
@Lash-L Has the HA integration been updated with this fix? There looks to be a failing build on the API repo, not sure if it went out or not. |
|
A new version should have been pushed now. |
|
I am getting this error running 1.0.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version of the custom_component
Latest versions
Describe the bug
Suddently stopped working, tried logging in again, credentials are accepted but getting
Failed updating jwt token
Debug log
Nothing in the debug log
The text was updated successfully, but these errors were encountered: