LGE Washer: Invalid Login info! #3

katerry · 2020-03-28T02:28:09Z

I am receiving the following error in the log after I submit the access token:

Log Details (ERROR)
Logger: custom_components.smartthinq_washer.config_flow
Source: custom_components/smartthinq_washer/config_flow.py:67
First occurred: 10:23:30 PM (2 occurrences)
Last logged: 10:25:06 PM

LGE Washer: Invalid Login info!

ollo69 · 2020-03-28T02:35:51Z

Are you sure that your token is correct?
Did you put the right value for region and language associated to your account?

katerry · 2020-03-28T03:08:05Z

I am certain. Region US Language en-US. I am able to login just fine and once I submit the redirection URL I get a access token but one I submit it I get Invalid SmartThinQ credentials.

towerhand · 2020-03-28T03:33:58Z

I left the token empty on the first window when setting up the integration, then followed the directions on the next steps to get a new token and it worked for me.

ollo69 · 2020-03-28T09:25:47Z

This is strange and hard to investigate. Can you try, just for check, to save your generated token, than close the browser, re-open it and perform the configuration using the token previously saved?

katerry · 2020-03-28T13:30:17Z

I am not sure what the issue is. I followed your instructions but no change. I even reset the password and confirmed that when I sign into the APP they work. When I sing into the Smartthinq login URL I just get a blank screen. Is that normal?

ollo69 · 2020-03-28T13:41:40Z

Blank screen is normal, that login only redirect you to a page from where you can take a refresh token.
It is possible that the hardware where Home Assistant run have some internet connection limit or that some firewall are enabled?

katerry · 2020-03-28T13:54:49Z

I use pIhole but I just disabled it and tested again with the same result.

katerry · 2020-03-28T14:12:57Z

I am sure that the credential work because when I use wideq I get the following output:

ollo69 · 2020-03-28T14:33:45Z

Can you retry with my last commit? I increased timeout, maybe I set it it too low.
Should work because wideq call are the same you are using.

katerry · 2020-03-28T14:47:12Z

Just retried with the same result. Here is the build I am using:

ollo69 · 2020-03-28T14:53:50Z

The PC from where you are launching the test is the same where you run HA?
Can you attach here in a zip with the wideq version that you are using for test, just to be sure that there are no difference?

katerry · 2020-03-28T15:00:14Z

I run HA using a raspberry pi 3 under HASSIO. I am running wideq under Ubuntu on my pc. The wideq zip is from the following link:

https://github.com/sampsyo/wideq/archive/master.zip

ollo69 · 2020-03-28T15:07:50Z

Ah, ok HASSIO is the problem, it have some limitation and I think do not support request.
You should check this post or maybe search other info on the web to see if it is possible to enable it.
I revert timeout as original.
Please report here if you discover some solutions.

kenmaples · 2020-03-28T20:00:06Z

I am also running into this issue on Home Assistant (used to be called HASSIO). Does this code base support the thinq API v2?

towerhand · 2020-03-28T20:14:54Z

I’m running the latest version of Home Assistant, installed hassio VM container on proxmox and this custom integration is working for me. Installed it via HACS with a new token.

ollo69 · 2020-03-30T15:45:53Z

Can I close this issue? I have no way for the moment to manage the component working on HASSIO.

katerry · 2020-03-30T15:57:21Z

Thanks for your effort. FYI I created an X86 Docker Home Assistant and added HACS and your custom component with the same result so this issue is not limited to HASSIO. Maybe LG is setting up new accounts different? I just setup my Washer and Dryer last month.

ollo69 · 2020-03-30T16:08:21Z

Thanks, for closing issue. In any case I will do some test with an HASSIO installation to better understand if is the issue is in the component or related to LG account. I will keep you informed.

ollo69 · 2020-03-30T20:01:18Z

Hi,
I just finish to make a test now using HASSOS, I installed it from scratch, added HACS and then istalled the component. It works without any issue.
The point is that, if you are able to connect with the test program, you should also be able to connect with the component because they use the sami API call.
I reopen this issue, need to understand where is the problem.

katerry · 2020-03-30T21:24:05Z

I can email you my redirect URL If you would like.

ollo69 · 2020-03-30T21:39:01Z

This could help, but wait, before I want to do other tests.
I will ask you if I will don't find anything.

Thx.

kenmaples · 2020-03-30T21:47:24Z

There has been a good deal of conversation around the new API on the thread from the original source of wideq - sampsyo/wideq#46

ollo69 · 2020-03-30T22:49:41Z

Ok, i will analyze better this API v2, but I understand that katerry run test application with API v1 and is able to connect to the washer, am I right?
Who is already succesfully using API v2?

ollo69 · 2020-03-31T00:53:14Z

I did some test, creating a new LG account with language en-US. It was failing, but because there are no device associated. My suspect is that some error is preventing process to end, but at this point I need to try with your token.
If you can please e-mail me your redirect URL at "aolivero@gmail.com".

Thx.

katerry · 2020-03-31T00:58:16Z

I just emailed you my redirect.

daveonkels · 2020-03-31T01:10:33Z

I'm still in the same boat - fully auth'd but no devices being returned. Sending you my redirect as well @ollo69

AbsoluteMidnight · 2020-03-31T10:20:01Z

Hello! I have the same problem, i get "Invalid SmartThinQ credentials." following the UI. I tried editing configuration.yaml too, but after restarting Hassio warns me i have a new device in integrations page, but asks me to configure it and the link gets me to the same UI with the same error message.

- set SSL version to TLSv1 - added error log

tayanov · 2020-04-07T18:22:05Z

And good and bad. I am ready support test frige if you need this))

kenmaples · 2020-04-07T18:52:10Z

Any plans on sending PRs back to the original wideq (https://github.com/sampsyo/wideq) or ha component (https://github.com/sampsyo/hass-smartthinq)? That may help to expand the number of testers. Personally I have a washer and dryer on APIv2, and will help testing anyway I can.

towerhand · 2020-04-07T18:54:23Z

I have a dryer to help testing with. it should be a v1.

KrzysiekLegnica · 2020-04-07T18:58:18Z

I also have a washer and dryer for APIv2 and help with testing.

Logger: custom_components.smartthinq_washer.sensor
Source: custom_components/smartthinq_washer/sensor.py:446
First occurred: 20:57:56 (9 occurrences)
Last logged: 21:02:03

Generic Wideq Error - [('0009', '장치가 존재하지 않습니다.')]. Exiting

ollo69 · 2020-04-07T19:14:46Z

Any plans on sending PRs back to the original wideq (https://github.com/sampsyo/wideq) or ha component (https://github.com/sampsyo/hass-smartthinq)? That may help to expand the number of testers. Personally I have a washer and dryer on APIv2, and will help testing anyway I can.

Send PR to this 2 project from here is not possible for differerent reason:

this is not a fork, but is a new repository created from scratch. I created it after some experiment starting from many mods of the wideq original project and mostly reviewed by me
this project include both the wideq (API) and the HA (component) part to avoid the problem of manual installation of wideq. May be in the future will be splitted, but the wideq part have to be managed as py project.
the wideq part is quite different in the structure, this to better manage coexistence of the 2 API model abtracting the device concept and not the client
the HA part is written for the most part from scratch for managing config flow and HA registry.

Create a PR from here will do the owner of original repository crazy.

KrzysiekLegnica · 2020-04-07T20:13:35Z

Please enter your email, I'll send you logs.

ollo69 · 2020-04-07T20:18:47Z

Please enter your email, I'll send you logs.

aolivero@gmail.com

ollo69 · 2020-04-07T21:07:34Z

Message from log:

This device do not use APIv1

tayanov · 2020-04-08T08:04:00Z

i see something new in log.
I see example "remainTimeMinute': 49.0"
May be it later in log... but ...
i send email for you

ollo69 · 2020-04-08T08:05:47Z

Yes, I discovered some interesting information in your log, trying to understand. Stay tuned...
Can you send me a log file with some more data, having both the washer on and off, and provide me the period when it was on and when it was off?
Thx

tayanov · 2020-04-08T08:29:16Z

i dont now need launch full washing or toggle on off only?

tayanov · 2020-04-08T13:27:35Z

i compare api answer frige and washer
frige washer
'platformType': 'thinq1' 'platformType': 'thinq2'
guideType': 'TYPE1' 'guideType': 'TYPE2'
'deviceType': 101 'deviceType': '201'

obviously see what devices have diffrent smart platform
as if have diffrent endpoint to api

ollo69 · 2020-04-08T18:03:36Z

Just released a new version, may be I found a solution, please test and provide feedback.
If should work, please not start complaining that not all sessor attributes are managed.( for sure I'm not managing course name).
Wait your feedback,

daveonkels · 2020-04-08T18:10:59Z

Haven't run a load yet but it sees that the washer is on - so that's a great start.

tayanov · 2020-04-08T18:11:26Z

You a superman!!! Its great. I see on\off state. And many sensor. And no error in log

ollo69 · 2020-04-08T18:20:01Z

APIv2 should also be better from a performance point of view because do not require to poll every device.
Anyway is better wait for additional feedback.
When I'll have some more time I'll try to manage other states.

towerhand · 2020-04-08T18:42:55Z

Recreated the integration again with the new version. Everything still works as before.

daveonkels · 2020-04-09T00:15:37Z

Looks like you solved a few more states in v0.9.

kenmaples · 2020-04-09T01:50:08Z

Looking better on my side also

ollo69 · 2020-04-09T09:29:36Z

To fix missing state I need a piece of log in debug mode during washer run.

ollo69 · 2020-04-13T16:59:42Z

I just released Dryer support, test can start now. Please provide feed-back and send to me logs (possible debug), because not having Dryer I wasn't able to do any test.

tayanov · 2020-04-13T17:18:32Z

Good news. I not have dryer. But have frige. Ready to test in future

rwarner · 2020-04-16T17:57:03Z

So excited over here. Just thought I'd add in my 2 cents.

Just setup this integration in HACS and was able to go through the whole workflow with a standard LG account. Detected my Washer while it was running and showed all the correct states. Alerted all the run_completed attributes as expected and ran my automations.

Seems to be working great for the US LGE Washer I have.

KTibow · 2020-07-01T16:15:25Z

Just saying: 76 days old, time to close @ollo69?

tismofied · 2021-09-22T15:26:42Z

Just installed this integration in HACS, the documment says to "Simply add a new "integration" and look for "SmartThinQ LGE Sensors" among the proposed ones and follow setup worflow" I look in HA integrations and it's not showing up. how do I configure this component? please help

ollo69 · 2021-09-22T17:59:40Z

This is a closed issue, open a new one. Anyway try before cleaning your bowser cache.

katerry closed this as completed Mar 30, 2020

ollo69 reopened this Mar 30, 2020

ollo69 added a commit that referenced this issue Mar 31, 2020

Fix for invalid login (issue #3)

64631bf

- set SSL version to TLSv1 - added error log

ollo69 mentioned this issue Apr 7, 2020

The condition of the washing machine is not visible #8

Closed

canadaohcanada mentioned this issue Apr 16, 2020

Device list doesn't return Washer sampsyo/wideq#46

Open

katerry closed this as completed Jul 1, 2020

Repository owner locked as resolved and limited conversation to collaborators Sep 22, 2021

LGE Washer: Invalid Login info! #3

LGE Washer: Invalid Login info! #3

Comments

katerry commented Mar 28, 2020

ollo69 commented Mar 28, 2020

katerry commented Mar 28, 2020

towerhand commented Mar 28, 2020 • edited Loading

ollo69 commented Mar 28, 2020

katerry commented Mar 28, 2020

ollo69 commented Mar 28, 2020

katerry commented Mar 28, 2020

katerry commented Mar 28, 2020

ollo69 commented Mar 28, 2020

katerry commented Mar 28, 2020

ollo69 commented Mar 28, 2020

katerry commented Mar 28, 2020

ollo69 commented Mar 28, 2020

kenmaples commented Mar 28, 2020

towerhand commented Mar 28, 2020

ollo69 commented Mar 30, 2020

katerry commented Mar 30, 2020

ollo69 commented Mar 30, 2020

ollo69 commented Mar 30, 2020

katerry commented Mar 30, 2020

ollo69 commented Mar 30, 2020

kenmaples commented Mar 30, 2020

ollo69 commented Mar 30, 2020

ollo69 commented Mar 31, 2020

katerry commented Mar 31, 2020

daveonkels commented Mar 31, 2020

AbsoluteMidnight commented Mar 31, 2020

tayanov commented Apr 7, 2020

kenmaples commented Apr 7, 2020

towerhand commented Apr 7, 2020

KrzysiekLegnica commented Apr 7, 2020 • edited Loading

ollo69 commented Apr 7, 2020 • edited Loading

KrzysiekLegnica commented Apr 7, 2020

ollo69 commented Apr 7, 2020

ollo69 commented Apr 7, 2020

tayanov commented Apr 8, 2020

ollo69 commented Apr 8, 2020 • edited Loading

tayanov commented Apr 8, 2020

tayanov commented Apr 8, 2020

ollo69 commented Apr 8, 2020

daveonkels commented Apr 8, 2020

tayanov commented Apr 8, 2020 • edited Loading

ollo69 commented Apr 8, 2020

towerhand commented Apr 8, 2020

daveonkels commented Apr 9, 2020

kenmaples commented Apr 9, 2020

ollo69 commented Apr 9, 2020

ollo69 commented Apr 13, 2020

tayanov commented Apr 13, 2020

rwarner commented Apr 16, 2020

KTibow commented Jul 1, 2020

tismofied commented Sep 22, 2021

ollo69 commented Sep 22, 2021

towerhand commented Mar 28, 2020 •

edited

Loading

KrzysiekLegnica commented Apr 7, 2020 •

edited

Loading

ollo69 commented Apr 7, 2020 •

edited

Loading

ollo69 commented Apr 8, 2020 •

edited

Loading

tayanov commented Apr 8, 2020 •

edited

Loading