-
Notifications
You must be signed in to change notification settings - Fork 159
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
Signature doesn't match request #775
Comments
Accept the new legal stuff in the Thinq app.
Op do 11 jul 2024 20:16 schreef 4ronse ***@***.***>:
… *Describe the bug*
Unable to connect to my account. I tried both the redirect method and the
username/password methods.
It never worked, but I did succeed one time by changing the request params
order so that it's organized alphabetically but I can't get it to work this
time...
*Expected behavior*
It should work idk lol
*Screenshots*
image.png (view on web)
<https://github.com/ollo69/ha-smartthinq-sensors/assets/24609051/d1a0b957-6c79-4b16-9f23-b06c8e037af6>
image.png (view on web)
<https://github.com/ollo69/ha-smartthinq-sensors/assets/24609051/7bd375d5-b088-44bf-8114-32a4afe6a41a>
*Environment details:*
- Environment (HASSIO, Raspbian, etc): HassIO
- Home Assistant version installed: 2024.7.1
- Component version installed: v0.39.2
- Last know working version: v0.39.2
- LG device type and model with issue: API
- LG devices connected (list): API
*Output of HA logs*
There isn't any
*Additional context*
The signature request matches the Lgemp-X-Signature header on the
empsession request
—
Reply to this email directly, view it on GitHub
<#775>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFCKJFKNOQQ3MWEQQJTSXWTZL3DYZAVCNFSM6AAAAABKXPX6W6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYDGOBQGI3DKMA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
How do I accept the legal stuff? |
in the Thinq app. |
#776 (comment)
Op vr 12 jul 2024 00:25 schreef 4ronse ***@***.***>:
… Accept the new legal stuff in the Thinq app. Op do 11 jul 2024 20:16
schreef 4ronse *@*.
*>: … <#m_1944813543855830961_> Describe the bug Unable to connect to my
account. I tried both the redirect method and the username/password
methods. It never worked, but I did succeed one time by changing the
request params order so that it's organized alphabetically but I can't get
it to work this time... Expected behavior It should work idk lol
Screenshots image.png (view on web)
https://github.com/ollo69/ha-smartthinq-sensors/assets/24609051/d1a0b957-6c79-4b16-9f23-b06c8e037af6
<https://github.com/ollo69/ha-smartthinq-sensors/assets/24609051/d1a0b957-6c79-4b16-9f23-b06c8e037af6>
image.png (view on web)
https://github.com/ollo69/ha-smartthinq-sensors/assets/24609051/7bd375d5-b088-44bf-8114-32a4afe6a41a
<https://github.com/ollo69/ha-smartthinq-sensors/assets/24609051/7bd375d5-b088-44bf-8114-32a4afe6a41a>
Environment details: - Environment (HASSIO, Raspbian, etc): HassIO - Home
Assistant version installed: 2024.7.1 - Component version installed:
v0.39.2 - Last know working version: v0.39.2 - LG device type and model
with issue: API - LG devices connected (list): API Output of HA logs There
isn't any Additional context The signature request matches the
Lgemp-X-Signature header on the empsession request — Reply to this email
directly, view it on GitHub <#775
<#775>>, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFCKJFKNOQQ3MWEQQJTSXWTZL3DYZAVCNFSM6AAAAABKXPX6W6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYDGOBQGI3DKMA
<https://github.com/notifications/unsubscribe-auth/AFCKJFKNOQQ3MWEQQJTSXWTZL3DYZAVCNFSM6AAAAABKXPX6W6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYDGOBQGI3DKMA>
. You are receiving this because you are subscribed to this thread.Message
ID: @.*>
How do I accept the legal stuff?
—
Reply to this email directly, view it on GitHub
<#775 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFCKJFMZUUPR6HQFSE2VMALZL4A7BAVCNFSM6AAAAABKXPX6W6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRUGA2TMOBXGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Bruh there is nothing to accept I couldn't find anything but the promotional stuff |
Same thing here.. It was working for several months, but now nothing to accept and dont connect |
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
Describe the bug
Unable to connect to my account. I tried both the redirect method and the username/password methods.
It never worked, but I did succeed one time by changing the request params order so that it's organized alphabetically but I can't get it to work this time...
Expected behavior
It should work idk lol
Screenshots
Environment details:
Output of HA logs
There isn't any
Additional context
The signature request matches the Lgemp-X-Signature header on the empsession request
The text was updated successfully, but these errors were encountered: