Contribution - LG ThinQ Binding

Add-ons Bindings
634

Yeah, that’s what I thought too. We’ll be waiting for the update!
Thank you so much!
By the way, it’s possible this isn’t just on RU servers; maybe LG uses similar options elsewhere.

I was really looking forward to version 5 of OH, just for this extension. Then, when I updated to version 5, the extension didn’t work… I waited for several months, thinking the problem would resolve itself…
…But I couldn’t wait any longer; my fingers were itching to do something, so I decided to do a little research :grinning_face:

635

Please try this new test version with the fix I implemented to check whether you can now connect to LG API in your region. Notice that the binding will only works in openhab >= 5.1.X (millestone trunk).

1 Like
636

Sorry for the long wait. I was on vacation.
I installed release 5.1.1 and the specified jar.

Very cool! Everything works!

2026-01-10 19:16:13.472 [WARN ] [ing.lgthinq.lgservices.api.RestUtils] - TLS handshake failed for POST https://ru.emp.lgsmartplatform.com/emp/v2.0/account/session/<redacted>. Retrying once with TLS compatibility profile (TLS1.2 + RSA ciphers).
2026-01-10 19:16:13.481 [WARN ] [ty.util.ssl.SslContextFactory.config] - Weak cipher suite TLS_RSA_WITH_AES_256_GCM_SHA384 enabled for Client@710bec97[provider=null,keyStore=null,trustStore=null]
2026-01-10 19:16:13.481 [WARN ] [ty.util.ssl.SslContextFactory.config] - Weak cipher suite TLS_RSA_WITH_AES_128_GCM_SHA256 enabled for Client@710bec97[provider=null,keyStore=null,trustStore=null]
2026-01-10 19:16:13.481 [INFO ] [ing.lgthinq.lgservices.api.RestUtils] - Initialized TLS fallback HttpClient (TLSv1.2 + RSA cipher suites).
2026-01-10 19:16:15.264 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'lgthinq:washer-201:*********:****-****-****-****-***********' to inbox.
1 Like