Contribution - LG ThinQ Binding

I might be able to answer. I have an LG Washer and dryer also with remote start, unsure if it’s the same model though.

The “smart course” are either downloaded program (we have 1 selection that is for downloaded cycle) or those that are using sensor in the wash. In my app,. I see small load as downloaded but I don’t see the other you said. I’ve checked in the dryer also and can’t find them so it might be for his model.

I’m unsure also for his model, mine is very stupid. For remote start to work, the machine must be turned on (not just plug-in) and have remote start button pressed (and repressed after each cycle!). It’s very stupid. I’m not even sure I can select the cycle remotely (never tried the feature since it’s pointless for me, I’m in front of it loading it, I’ll just start it while I’m there).

Still can’t wait to see that add-on pop into openhab!

This happens when the binding try to list the devices of your account, but doesn’t have success. To know about the problem, you have to see the OpenHab log about the detailed error threw.
Can you share here? You can reproduce it disabling and enabling the bridge.

Me too :smiley: . But, until there, I’m very close to finish WM fully support and you guys will be able to remotely WasherDryers through OpenHab. I hope to delivery it before Christmas !

1 Like

I’m using OH 3.4 with the jar linked in your post #1
235 x Active x 80 x 3.3.0.202212012353 x openHAB Add-ons :: Bundles :: LG Thinq Binding

Scanning my network does not find any device (I have a LG cloud gateway connected via Ethernet I guess it should be found ?).

So I manually added the bridge.
But the bridge thing stays offline and I keep seeing this message every 10 secs:

2022-12-21 20:30:11.609 [ERROR] [internal.handler.LGThinQAirConditionerHandler] - Error stopping LG Device monitor
java.lang.UnsupportedOperationException: Not supported in V2 API.
        at org.openhab.binding.lgthinq.lgservices.LGThinQACApiV2ClientServiceImpl.stopMonitor(LGThinQACApiV2ClientServiceImpl.java:151) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.stopDeviceV1Monitor(LGThinQAbstractDeviceHandler.java:313) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getSnapshotDeviceAdapter(LGThinQAbstractDeviceHandler.java:357) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.updateThingStateFromLG(LGThinQAbstractDeviceHandler.java:253) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]
2022-12-21 20:30:11.615 [ERROR] [internal.handler.LGThinQAirConditionerHandler] - Error updating thing /undef from LG API. Thing goes OFFLINE until next retry.
org.openhab.binding.lgthinq.internal.errors.LGThinqApiException: Error starting device monitor in LG API for the device:undef
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getSnapshotDeviceAdapter(LGThinQAbstractDeviceHandler.java:358) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.updateThingStateFromLG(LGThinQAbstractDeviceHandler.java:253) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.lang.UnsupportedOperationException: Not supported in V2 API.
        at org.openhab.binding.lgthinq.lgservices.LGThinQACApiV2ClientServiceImpl.startMonitor(LGThinQACApiV2ClientServiceImpl.java:145) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getSnapshotDeviceAdapter(LGThinQAbstractDeviceHandler.java:342) ~[?:?]
        ... 7 more

A bundle restart is giving this:

2022-12-21 20:26:01.349 [ERROR] [nq.lgservices.LGThinQAbstractApiClientService] - Error reading resource from URI:
java.net.MalformedURLException: no protocol:
        at java.net.URL.<init>(URL.java:645) ~[?:?]
        at java.net.URL.<init>(URL.java:541) ~[?:?]
        at java.net.URL.<init>(URL.java:488) ~[?:?]
        at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.loadDeviceCapability(LGThinQAbstractApiClientService.java:114) [bundleFile:?]
        at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.getCapability(LGThinQAbstractApiClientService.java:248) [bundleFile:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getCapabilities(LGThinQAbstractDeviceHandler.java:192) [bundleFile:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAirConditionerHandler.updateChannelDynStateDescription(LGThinQAirConditionerHandler.java:130) [bundleFile:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.initializeThing(LGThinQAbstractDeviceHandler.java:207) [bundleFile:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAirConditionerHandler.initialize(LGThinQAirConditionerHandler.java:86) [bundleFile:?]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
        at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
        at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:154) [bundleFile:?]
        at org.openhab.core.internal.common.Invocation.call(Invocation.java:52) [bundleFile:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]
2022-12-21 20:26:01.350 [ERROR] [internal.handler.LGThinQAirConditionerHandler] - Error updating channels dynamic options descriptions based on capabilities of the device. Fallback to default values.
org.openhab.binding.lgthinq.internal.errors.LGThinqApiException: Error reading IO interface
        at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.loadDeviceCapability(LGThinQAbstractApiClientService.java:120) ~[bundleFile:?]
        at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.getCapability(LGThinQAbstractApiClientService.java:248) ~[bundleFile:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getCapabilities(LGThinQAbstractDeviceHandler.java:192) ~[bundleFile:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAirConditionerHandler.updateChannelDynStateDescription(LGThinQAirConditionerHandler.java:130) ~[bundleFile:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.initializeThing(LGThinQAbstractDeviceHandler.java:207) [bundleFile:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAirConditionerHandler.initialize(LGThinQAirConditionerHandler.java:86) [bundleFile:?]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
        at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
        at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:154) [bundleFile:?]
        at org.openhab.core.internal.common.Invocation.call(Invocation.java:52) [bundleFile:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.net.MalformedURLException: no protocol:
        at java.net.URL.<init>(URL.java:645) ~[?:?]
        at java.net.URL.<init>(URL.java:541) ~[?:?]
        at java.net.URL.<init>(URL.java:488) ~[?:?]
        at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.loadDeviceCapability(LGThinQAbstractApiClientService.java:114) ~[bundleFile:?]
        ... 15 more
2022-12-21 20:26:01.728 [ERROR] [nq.lgservices.LGThinQAbstractApiClientService] - Error reading resource from URI:
java.net.MalformedURLException: no protocol:
        at java.net.URL.<init>(URL.java:645) ~[?:?]
        at java.net.URL.<init>(URL.java:541) ~[?:?]
        at java.net.URL.<init>(URL.java:488) ~[?:?]
        at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.loadDeviceCapability(LGThinQAbstractApiClientService.java:114) ~[?:?]
        at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.getCapability(LGThinQAbstractApiClientService.java:248) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getCapabilities(LGThinQAbstractDeviceHandler.java:192) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAirConditionerHandler.updateChannelDynStateDescription(LGThinQAirConditionerHandler.java:130) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.initializeThing(LGThinQAbstractDeviceHandler.java:207) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.bridgeStatusChanged(LGThinQAbstractDeviceHandler.java:247) ~[?:?]
        at org.openhab.core.thing.internal.ThingManagerImpl.lambda$13(ThingManagerImpl.java:1047) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]
2022-12-21 20:26:01.738 [ERROR] [internal.handler.LGThinQAirConditionerHandler] - Error updating channels dynamic options descriptions based on capabilities of the device. Fallback to default values.
org.openhab.binding.lgthinq.internal.errors.LGThinqApiException: Error reading IO interface
        at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.loadDeviceCapability(LGThinQAbstractApiClientService.java:120) ~[?:?]
        at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.getCapability(LGThinQAbstractApiClientService.java:248) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getCapabilities(LGThinQAbstractDeviceHandler.java:192) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAirConditionerHandler.updateChannelDynStateDescription(LGThinQAirConditionerHandler.java:130) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.initializeThing(LGThinQAbstractDeviceHandler.java:207) ~[?:?]
        at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.bridgeStatusChanged(LGThinQAbstractDeviceHandler.java:247) ~[?:?]
        at org.openhab.core.thing.internal.ThingManagerImpl.lambda$13(ThingManagerImpl.java:1047) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.net.MalformedURLException: no protocol:
        at java.net.URL.<init>(URL.java:645) ~[?:?]
        at java.net.URL.<init>(URL.java:541) ~[?:?]
        at java.net.URL.<init>(URL.java:488) ~[?:?]
        at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.loadDeviceCapability(LGThinQAbstractApiClientService.java:114) ~[?:?]

Hummm… sounds for me like you are using the last version of the binding with older device’s configuration. I suggest you to remove the thing & bridge, remove the $OH_USERDATA/thinq folder and add the Bridge again from the scratch and see if this solve the problem.

Hmm, some progress but the error remains the same.
I had to create the thinq/ directory for this to work. Seeing 3 json files in there now but the thing is still offline.

2022-12-22 00:17:38.617 [DEBUG] [nternal.handler.LGThinQBridgeHandler] - Initializing LGThinq bridge handler.
2022-12-22 00:17:39.790 [DEBUG] [internal.api.OauthLgEmpAuthenticator] - encrypted_pw=SElrGJXh82AaBkui0E3gn5s56CQwkH+GVGCN9yT1lGNbCFJFwkx+P9WNcBMEphwDhDEwDsy0QxoWexg06os9Mx5daZE70bD2kbXX6VypfhzR1q9c8/W9LZlSAxvo0sCjq2JdS61TrHU+ioCfE0cPg0r30Uh+seKsXLQn70oTB78VwevIlTD3VxwIqIsu8ygC, signature=cl08TzT9tPC83M+k+cXT1QF9d08dpvK8uEsTErHiZOE=, tStamp=1671664659
2022-12-22 00:17:40.412 [DEBUG] [internal.api.OauthLgEmpAuthenticator] - Secret found:fefe3620d403d67b4a2a2384c021a414
2022-12-22 00:17:40.416 [DEBUG] [internal.api.OauthLgEmpAuthenticator] - ===> Localized timestamp used: [Wed, 21 Dec 2022 23:17:40 +0000]
2022-12-22 00:17:40.418 [DEBUG] [internal.api.OauthLgEmpAuthenticator] - ===> signature created: [UB1NgvP2cxUZbQRp7RGY5j8NNvY=]
2022-12-22 00:17:41.077 [DEBUG] [nternal.handler.LGThinQBridgeHandler] - Successful getting token from LG API
2022-12-22 00:17:41.612 [DEBUG] [nternal.handler.LGThinQBridgeHandler] - Adding new LG Device to things registry with id:72cb9207-186a-18b0-a940-747a908300b7
2022-12-22 00:17:41.881 [DEBUG] [al.discovery.LGThinqDiscoveryService] - Discovered unsupported LG device of type 'UNKNOWN'(603) and model 'CGW_017401_WW' with id 72cb9207-186a-18b0-a940-747a908300b7
2022-12-22 00:17:41.884 [DEBUG] [nternal.handler.LGThinQBridgeHandler] - Adding new LG Device to things registry with id:72cb9207-186a-18b0-a940-747a908300b7:10

This is the expected behavior. Can you provide me the thinq*-cap.json file here ? With it, I can registry your device to the Binding recognize as a supported device, since 603 is really an unknown device for the binding.

Regards !

Sure, thanks for checking into.

thinq-72cb9207-186a-18b0-a940-747a908300b7:10-cap.json (67.1 KB)
thinq-72cb9207-186a-18b0-a940-747a908300b7-cap.json (477 Bytes)

@nemer are these jsons helpful or is there anything else I can do to help you ?

Thanks for your efforts and have a nice new year.

Hi @nemer !

I get these error messages every 10 seconds lately:

2023-01-03 15:51:48.237 [ERROR] [es.LGThinQAbstractApiV2ClientService] - Error returned by LG Server API. The reason is:{“resultCode”:“9006”,“result”:“”}
2023-01-03 15:51:48.238 [ERROR] [handler.LGThinQAirConditionerHandler] - Error updating thing Játszószoba/2963124d-1028-1d98-9690-24e8536d5d4c from LG API. Thing goes OFFLINE until next retry.
org.openhab.binding.lgthinq.internal.errors.LGThinqApiException: Error returned by LG Server API. The reason is:{“resultCode”:“9006”,“result”:“”}
at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiV2ClientService.handleGenericErrorResult(LGThinQAbstractApiV2ClientService.java:74) ~[?:?]
at org.openhab.binding.lgthinq.lgservices.LGThinQACApiV2ClientServiceImpl.beforeGetDataDevice(LGThinQACApiV2ClientServiceImpl.java:167) ~[?:?]
at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.getDeviceData(LGThinQAbstractApiClientService.java:356) ~[?:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getSnapshotDeviceAdapter(LGThinQAbstractDeviceHandler.java:338) ~[?:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.updateThingStateFromLG(LGThinQAbstractDeviceHandler.java:253) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]

Is there anything to do with it? Is this a local Wifi communication issue?

And also with 3.4.0 setting speed and operations type is based on numbers. There is no textual definition displayed in Main UI.


It is in hungarian but you can see the controls.
Do I need to define State definition for all items?

@nemer I hope you are alive and well.
Have you had a chance to look at my heat pump’s JSON to add it to your binding ?

Dear @nemer, I just found your binding for my LG Washer and Dryer and installed it, but when I try to create the bridge, I get the error: Generic Error in the LG API communication process.
What did I do wrong?

Yes, I’m alive and well :grin:. Just finishing my vacation. Next week I will come back.

3 Likes

Hi @nemer are there news?
Have you had a chance to look at my heat pump’s JSON to add it to your binding ?

Hi @nemer!

I hope you’re back and provide some support for us. :smiley:

I have a lot of the following in my logs:

2023-02-09 15:01:16.329 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Nappali/d0000000-1111-2222-3333-abbbbff22010. No data available yet ?
2023-02-09 15:01:33.655 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:01:59.645 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Nappali/d0000000-1111-2222-3333-abbbbff22010. No data available yet ?
2023-02-09 15:02:35.204 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:03:08.581 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:03:52.147 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Nappali/d0000000-1111-2222-3333-abbbbff22010. No data available yet ?
2023-02-09 15:04:07.150 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:04:53.621 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Nappali/d0000000-1111-2222-3333-abbbbff22010. No data available yet ?
2023-02-09 15:06:03.190 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:07:00.953 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:07:33.408 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:07:44.762 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Nappali/d0000000-1111-2222-3333-abbbbff22010. No data available yet ?
2023-02-09 15:08:49.545 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:09:22.185 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:09:30.393 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Nappali/d0000000-1111-2222-3333-abbbbff22010. No data available yet ?
2023-02-09 15:09:48.526 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Nappali/d0000000-1111-2222-3333-abbbbff22010. No data available yet ?
2023-02-09 15:10:50.430 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:11:08.470 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:11:20.327 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Nappali/d0000000-1111-2222-3333-abbbbff22010. No data available yet ?
2023-02-09 15:11:41.118 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:12:07.725 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Nappali/d0000000-1111-2222-3333-abbbbff22010. No data available yet ?
2023-02-09 15:12:26.011 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Nappali/d0000000-1111-2222-3333-abbbbff22010. No data available yet ?
2023-02-09 15:13:26.578 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:14:43.885 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Nappali/d0000000-1111-2222-3333-abbbbff22010. No data available yet ?
2023-02-09 15:15:08.014 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:15:26.142 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:15:44.216 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:17:47.228 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?
2023-02-09 15:18:45.049 [WARN ] [handler.LGThinQAirConditionerHandler] - LG API returns null monitoring data for the thing Garázs/d0000011-2130-2226-3333-abbbbff22010. No data available yet ?

Can you help to solve this? Or can I help you with that? Any hint what can cause this?

Thank you for your great work. I hope you can finish your pull request…

Hi @nemer , did you had any time to check this

Sorry, folks. I was on vacation and came bake last week. I’m reviewing these points and let you know soon.

nemer you r the man!very nice job with the binding mate.What is the status of the remote start?I got the latest jar ,removed my washer and discovered it again.I dont see a remote start channel.I ve got 2 new channels,Delay Time and Standby Mode.

Remote start is almost done. The problem is it was in the same branch I’m doing a refactoring to get the binding more modular. LG Thinq has (potentially) more than 20 devices and I’m doing a better design to introduce easier new devices. I will try to commit only the new features in the current main branch to do not hold the new features for a long period.