LG Thinq Binding

nemer · March 30, 2025, 1:58am

@Daniel77 , first of all, get the latest version of the binding in my repo (GitHub - nemerdaud/openhab-thinq-stuff: Some distribution binary, files and docs.) install it and if th e problem persists, let me know.

Daniel77 · April 6, 2025, 5:05pm

Hi, I installed the latest org.openhab.binding.lgthinq-4.3.0-SNAPSHOT.jar from your repo on an openbhab 4.3.4 installation. No issue to get the binding online, but the water heatpump (it is a water boiler with heatpump, not an air/water heat pump) can not be found. Are the LG WH27S.F5 / WH20S.F5 (difference is only 270l vs. 200l) devices among the supported devices?

nemer · April 6, 2025, 7:49pm

Your device is only supported if its supported by LG Thinq App.

Daniel77 · April 8, 2025, 12:11pm

Yes, I can control it over the LG Thinq App (operation mode, setpoint for temperature, current temperature, current power, enegry consumption and a timer)

Nirtsep · July 18, 2025, 8:20am

Hi Nemer, I have the following issue with my AC. Everything is working fine except for Autodry command ON / OFF (from OH). If I set Autodry ON /OFF from the remote, the AC setting correctly changes, also in OH switch status. If I set Autodry function from OH, the setting changes for some seconds then goes back to previous status (so nothing changes). When I send the command from OH swith the AC emits the usual beep, so some sort of command is received but it’s not changing autodry status. Can you please check it? If it helps, when I send the command from OH, it does not affect power status (instead, if I send Air clean command, it will turn on the AC)

nemer · August 11, 2025, 11:51am

I will take a look on it. Regards.

Norick · August 20, 2025, 4:39am

Hello

I tried to use your binding in version 4.3.0.202502232037 with OH5.0.0 (windows). What works is the LG gateway but when I use the LGThinQ Dryer thing, I get following error message:

COMMUNICATION_ERROR
Error starting device monitor in LG API for the device:undef

In the log file more detailed:

[ERROR] [al.handler.LGThinQWasherDryerHandler] - Error stopping LG Device monitor
org.openhab.binding.lgthinq.lgservices.errors.LGThinqApiException: LG API report error processing the request → resultCode=[null], message=[ ]
at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiV2ClientService.handleGenericErrorResult(LGThinQAbstractApiV2ClientService.java:123) ~[?:?]
at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.stopMonitor(LGThinQAbstractApiClientService.java:513) ~[?:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.stopDeviceV1Monitor(LGThinQAbstractDeviceHandler.java:639) ~[?:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getSnapshotDeviceAdapter(LGThinQAbstractDeviceHandler.java:678) ~[?:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.updateThingStateFromLG(LGThinQAbstractDeviceHandler.java:491) ~[?:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler$UpdateThingStateFromLG.run(LGThinQAbstractDeviceHandler.java:484) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.lang.Thread.run(Thread.java:1583) [?:?]

Do you have an idea what went wrong and how I can fix it?

Thank you

Kim_Andersen · October 3, 2025, 11:22am

I updated openhab from 4.3.3 to 4.3.7-1 today, hoping that I could get the LGthing binding to run again, which didnt work with 4.3.3 but used to work some time ago.

But it seems like I still have issues.I cant get the bridgde to connect. The return error is:

Error getting devices from LG API in scanner process.

Any idea what to do?

Both my dryer and my washingmachine is working fine in the LGthing app.

nemer · October 3, 2025, 8:03pm

I can´t identify this message in the source code. Can you put the binding in debug mode and attach here an excerpt from the log with that error ?

Kim_Andersen · October 4, 2025, 8:53am

EDIT:
I think I found the issue.. I had the 3.3. manually installed in the addons folder, and totally forgot about it.. I have now removed the 3.3 version and installed the repo version (4.3.0) and now the bridge came online just fine.. (my devices shows error handler.. But I guess I just need to search them again or something..).

Hey Nemer.
Which is the latest LGthing bundle?

I get this som the bundlelist:

openhab> bundle:list -s |grep -i LG
247 x Active x  80 x 3.3.0.202202150027    x org.openhab.binding.lgthinq
299 x Active x  80 x 4.3.7                 x org.openhab.binding.lgwebos
openhab>

This is after putting the logging into debug mode:

025-10-04 10:59:24.644 [DEBUG] [nternal.handler.LGThinQBridgeHandler] - Token authentication process has been already done. Skip first authentication process.
2025-10-04 10:59:24.647 [DEBUG] [internal.handler.LGThinQDryerHandler] - bridgeStatusChanged ONLINE
2025-10-04 10:59:24.647 [DEBUG] [nternal.handler.LGThinQWasherHandler] - bridgeStatusChanged ONLINE
2025-10-04 10:59:24.650 [DEBUG] [nternal.handler.LGThinQWasherHandler] - initializeThing LQ Thinq lgthinq:201:4bb559ca4d:592bd2a4-d3e7-16e9-a69f-44cb8b2e0c43. Bridge status ONLINE
2025-10-04 10:59:24.650 [DEBUG] [internal.handler.LGThinQDryerHandler] - initializeThing LQ Thinq lgthinq:202:4bb559ca4d:a6fc6dc7-34e8-147a-8f50-44cb8b0819e7. Bridge status ONLINE
==> /var/log/openhab/events.log <==
2025-10-04 10:59:24.653 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'lgthinq:bridge:4bb559ca4d' changed from OFFLINE: Error getting devices from LG API in scanner process. to ONLINE
2025-10-04 10:59:24.654 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'lgthinq:201:4bb559ca4d:592bd2a4-d3e7-16e9-a69f-44cb8b2e0c43' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2025-10-04 10:59:24.656 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'lgthinq:202:4bb559ca4d:a6fc6dc7-34e8-147a-8f50-44cb8b0819e7' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
==> /var/log/openhab/openhab.log <==
2025-10-04 10:59:24.680 [ERROR] [ices.LGThinQAbstractApiClientService] - Error reading resource from URI: https://objectcontent.lgthinq.com/3d4390db-ffc3-4585-a955-d7e2bdc6f884?hdnts=exp=1673404020~hmac=9ecd10b7f9b160bdcfa834dc6e506535bcca0facdc7e6a41929a629d823e7a51
java.io.IOException: Server returned HTTP response code: 403 for URL: https://objectcontent.lgthinq.com/3d4390db-ffc3-4585-a955-d7e2bdc6f884?hdnts=exp=1673404020~hmac=9ecd10b7f9b160bdcfa834dc6e506535bcca0facdc7e6a41929a629d823e7a51
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:2038) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1627) ~[?:?]
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224) ~[?:?]
	at java.net.URL.openStream(URL.java:1161) ~[?:?]
	at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.loadDeviceCapability(LGThinQAbstractApiClientService.java:117) ~[?:?]
	at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.getCapability(LGThinQAbstractApiClientService.java:232) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getCapabilities(LGThinQAbstractDeviceHandler.java:167) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQWasherHandler.updateChannelDynStateDescription(LGThinQWasherHandler.java:97) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.initializeThing(LGThinQAbstractDeviceHandler.java:182) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.bridgeStatusChanged(LGThinQAbstractDeviceHandler.java:218) ~[?:?]
	at org.openhab.core.thing.internal.ThingManagerImpl.lambda$11(ThingManagerImpl.java:822) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
	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:1136) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
	at java.lang.Thread.run(Thread.java:840) [?:?]
2025-10-04 10:59:24.682 [ERROR] [ices.LGThinQAbstractApiClientService] - Error reading resource from URI: https://objectcontent.lgthinq.com/f2266edf-b2aa-4a65-a010-350acfc6eb4a?hdnts=exp=1673503245~hmac=737662edeec4b1379bf5ee3c5f067e5b26b268cde8eb86d6eba88759f678be5c
java.io.IOException: Server returned HTTP response code: 403 for URL: https://objectcontent.lgthinq.com/f2266edf-b2aa-4a65-a010-350acfc6eb4a?hdnts=exp=1673503245~hmac=737662edeec4b1379bf5ee3c5f067e5b26b268cde8eb86d6eba88759f678be5c
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:2038) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1627) ~[?:?]
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224) ~[?:?]
	at java.net.URL.openStream(URL.java:1161) ~[?:?]
	at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.loadDeviceCapability(LGThinQAbstractApiClientService.java:117) ~[?:?]
	at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.getCapability(LGThinQAbstractApiClientService.java:232) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getCapabilities(LGThinQAbstractDeviceHandler.java:167) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQDryerHandler.updateChannelDynStateDescription(LGThinQDryerHandler.java:131) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.initializeThing(LGThinQAbstractDeviceHandler.java:182) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.bridgeStatusChanged(LGThinQAbstractDeviceHandler.java:218) ~[?:?]
	at org.openhab.core.thing.internal.ThingManagerImpl.lambda$11(ThingManagerImpl.java:822) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
	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:1136) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
	at java.lang.Thread.run(Thread.java:840) [?:?]
2025-10-04 10:59:24.686 [ERROR] [nternal.handler.LGThinQWasherHandler] - 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:123) ~[?:?]
	at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.getCapability(LGThinQAbstractApiClientService.java:232) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getCapabilities(LGThinQAbstractDeviceHandler.java:167) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQWasherHandler.updateChannelDynStateDescription(LGThinQWasherHandler.java:97) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.initializeThing(LGThinQAbstractDeviceHandler.java:182) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.bridgeStatusChanged(LGThinQAbstractDeviceHandler.java:218) ~[?:?]
	at org.openhab.core.thing.internal.ThingManagerImpl.lambda$11(ThingManagerImpl.java:822) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
	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:1136) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
	at java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL: https://objectcontent.lgthinq.com/3d4390db-ffc3-4585-a955-d7e2bdc6f884?hdnts=exp=1673404020~hmac=9ecd10b7f9b160bdcfa834dc6e506535bcca0facdc7e6a41929a629d823e7a51
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:2038) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1627) ~[?:?]
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224) ~[?:?]
	at java.net.URL.openStream(URL.java:1161) ~[?:?]
	at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.loadDeviceCapability(LGThinQAbstractApiClientService.java:117) ~[?:?]
	... 12 more
2025-10-04 10:59:24.687 [ERROR] [internal.handler.LGThinQDryerHandler] - 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:123) ~[?:?]
	at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.getCapability(LGThinQAbstractApiClientService.java:232) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getCapabilities(LGThinQAbstractDeviceHandler.java:167) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQDryerHandler.updateChannelDynStateDescription(LGThinQDryerHandler.java:131) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.initializeThing(LGThinQAbstractDeviceHandler.java:182) ~[?:?]
	at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.bridgeStatusChanged(LGThinQAbstractDeviceHandler.java:218) ~[?:?]
	at org.openhab.core.thing.internal.ThingManagerImpl.lambda$11(ThingManagerImpl.java:822) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
	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:1136) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
	at java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL: https://objectcontent.lgthinq.com/f2266edf-b2aa-4a65-a010-350acfc6eb4a?hdnts=exp=1673503245~hmac=737662edeec4b1379bf5ee3c5f067e5b26b268cde8eb86d6eba88759f678be5c
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:2038) ~[?:?]
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1627) ~[?:?]
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224) ~[?:?]
	at java.net.URL.openStream(URL.java:1161) ~[?:?]
	at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.loadDeviceCapability(LGThinQAbstractApiClientService.java:117) ~[?:?]
	... 12 more
2025-10-04 10:59:24.823 [ERROR] [ices.LGThinQAbstractApiClientService] - Error calling device list from LG Server API. The reason is:Please consider using the official API. Visit https://smartsolution.developer.lge.com/en/product/useCase11?s=1740015848379 for more details.
2025-10-04 10:59:24.826 [DEBUG] [internal.handler.LGThinQDryerHandler] - bridgeStatusChanged OFFLINE: @text/error.lgapi-getting-devices
==> /var/log/openhab/events.log <==
2025-10-04 10:59:24.826 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'lgthinq:bridge:4bb559ca4d' changed from ONLINE to OFFLINE: Error getting devices from LG API in scanner process.
==> /var/log/openhab/openhab.log <==
2025-10-04 10:59:24.826 [DEBUG] [nternal.handler.LGThinQWasherHandler] - bridgeStatusChanged OFFLINE: @text/error.lgapi-getting-devices
2025-10-04 10:59:24.827 [DEBUG] [nternal.handler.LGThinQWasherHandler] - Stopping LG thinq polling for device/alias: 592bd2a4-d3e7-16e9-a69f-44cb8b2e0c43/Frontbetjent vaskemaskine
2025-10-04 10:59:24.827 [DEBUG] [internal.handler.LGThinQDryerHandler] - Stopping LG thinq polling for device/alias: a6fc6dc7-34e8-147a-8f50-44cb8b0819e7/Tørretumbler
2025-10-04 10:59:24.829 [DEBUG] [nternal.handler.LGThinQWasherHandler] - initializeThing LQ Thinq lgthinq:201:4bb559ca4d:592bd2a4-d3e7-16e9-a69f-44cb8b2e0c43. Bridge status OFFLINE
2025-10-04 10:59:24.829 [DEBUG] [internal.handler.LGThinQDryerHandler] - initializeThing LQ Thinq lgthinq:202:4bb559ca4d:a6fc6dc7-34e8-147a-8f50-44cb8b0819e7. Bridge status OFFLINE

Phuong · October 4, 2025, 9:17am

You still on OH 4?

The latest version is 5.0.1 but assume this version also required OH 5 or higher.

Kim_Andersen · October 4, 2025, 9:21am

Yeah Im on openhab 4.3.7-1 atm.. Havnt got time to update to 5 yet.

nemer · October 6, 2025, 2:44pm

You are using a very old version of the binding (3.3.0). Currently the binding was added to the official openhab addson bundle. I suggest you:

backup your openhab data (openhabian-config utility is very useful for it).
Uninstall the currently lgthinq version (org.openhab.binding.lgthinq). If you installed the binding jar phisically at addson directory, remove it.
Remove all the things related to lg thinq binding (you can keep and reuse the items related to the channels). This procedure is necessary since the chances that was made in the name of the channels to be standardized to OpenHab.

Optional: you can remove the OH_USERDATA/lgthinq directory to ensure that no junk left behind will bother you.

Restart OpenHab and reinstall the binding by the “Adds On” menu option. If you are using OH >= 5.0.0, you can find the LogThinq Binding at “openHAB Distribution” session. If the version is < 5.0.0, you will find at “Community Marketplace” session.

Then you can proceed with the Bridge Installation and Discovery Process to get back all your things.

Kim_Andersen · October 7, 2025, 10:04am

Yeah, I alread did that, when I discovered I had the old 3.3.0 version installed.
Everything seems to work fine again, thank you!

Nodiaque · October 29, 2025, 2:30pm

Hello,

I just updated from openhab 4.3.6 to 5.0.2. Like always, even if I had installed the binding from market place, It didn’t reinstalled the binding. I removed my current gateway thing and installed the new official binding. I went and add the the gateway thing and it doesn’t work. There’s no option to say anything like user account and such:

edit: Ok, I don’t know why but I add to restart the server to see the proper screen.

If I may add, can you add Canada (CA) in the country list? Right now, I put Other and CA which solved the unable to connect. Thanks!

pleedell · October 31, 2025, 2:11pm

I noticed the same, if I clean cache now the LG ThinQ binding does not re-install and I have to do it manually. To be clear I’m using the marketplace version of the binding.

This is the only binding that I use that seems to require this.

nemer · October 31, 2025, 2:24pm

I don’t believe this behavior is related to the binding itself. The thing/bridge configuration UI is managed by openHAB and driven by the XML configuration descriptors - not by the binding logic.

One important note: between openHAB 4.3 and 5.x several configuration property names were changed as part of the requirements for this binding to become an official openHAB addon. These changes may affect how previously stored metadata is interpreted, and could explain any configuration inconsistencies after upgrading.

BTW I suggest you, if you are in the 5.X version, to install the official release available in AddsOn session.

Nodiaque · October 31, 2025, 3:20pm

Yeah I recreated everything from scratch when I switched to the new one. The weird thing is only because the gateway had no field. Reboot fixed it at least.

Gae_vb · December 11, 2025, 12:28pm

is there a way to have the in and outlet water temperature on the Heatpump? it’s LG Therma V R290.

i tried to install HA and there it works.

would be nice to have the possibility to change the requested heatingwater temperature by +/- 1 to 5 °C like in the LG Thinq app.

chuck2k · March 10, 2026, 12:01pm

The LG fridge, V1, will no longer work with binding. With the message

returnMsg: 등록되지 않은 모델입니다 (Unregistered/unsupported model)

Firmware update/chenges?

12:50:20.459 [TRACE] [ding.lgthinq.lgservices.api.RestUtils] - POST request to URI: ``https://eic.lgthinq.com:46030/api/rti/rtiResult
12:50:20.525 [TRACE] [ding.lgthinq.lgservices.api.RestUtils] - POST response: {“lgedmRoot”:{“returnCd”:“0000”,“returnMsg”:“OK”,“workList”:{“deviceId”:“<DEVICE_ID>”,“deviceState”:“E”,“format”:“B64”,“returnCode”:“0000”,“returnData”:“AgEBAQICBAABAAEA”,“stateCode”:“S”,“workId”:“<WORK_ID>”}}}
12:50:20.526 [TRACE] [ding.lgthinq.lgservices.api.RestUtils] - POST request to URI: ``https://eic.lgthinq.com:46030/api/rti/rtiMon
12:50:20.589 [TRACE] [ding.lgthinq.lgservices.api.RestUtils] - POST response: {“lgedmRoot”:{“returnCd”:“0000”,“returnMsg”:“OK”,“stateCode”:“S”,“workId”:“<WORK_ID>”,“deviceState”:“E”,“timestamp”:0}}
12:50:20.712 [DEBUG] [ces.LGThinQAbstractApiV1ClientService] - Prepare command v1: [1, 1, 1, 2, 255, 255, 255, 255, 255, 255, 255]
12:50:20.713 [DEBUG] [s.LGThinQFridgeApiV1ClientServiceImpl] - setControl Payload:[{cmd=Control, cmdOpt=Set, value=ControlData, data=AQEBAv////////8=, format=B64}]
12:50:20.714 [DEBUG] [ces.LGThinQAbstractApiV1ClientService] - URL: ``https://eic.lgthinq.com:46030/api/rti/rtiControl``, Post Payload:[{
“lgedmRoot” : {
“deviceId” : “<DEVICE_ID>”,
“workId” : “<WORK_ID>”,
“cmd” : “Control”,
“cmdOpt” : “Set”,
“value” : “ControlData”,
“data” : “AQEBAv////////8=”,
“format” : “B64”
}
}]
12:50:20.715 [TRACE] [ding.lgthinq.lgservices.api.RestUtils] - POST request to URI: ``https://eic.lgthinq.com:46030/api/rti/rtiControl
12:50:21.198 [TRACE] [ding.lgthinq.lgservices.api.RestUtils] - POST response: {“lgedmRoot”:{“returnCd”:“0011”,“returnMsg”:“등록되지 않은 모델입니다.”,“deviceId”:“<DEVICE_ID>”,“stateCode”:“S”,“workId”:“<WORK_ID>”,“format”:“B64”,“deviceState”:“E”,“timestamp”:0}}
12:50:21.199 [ERROR] [internal.handler.LGThinQFridgeHandler] - Error executing Command ON to the channel dashboard#ice-plus. Thing goes offline until retry
org.openhab.binding.lgthinq.lgservices.errors.LGThinqApiException: Status error executing endpoint. resultCode must be 0000, but was:0011
at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiV1ClientService.handleGenericErrorResult(LGThinQAbstractApiV1ClientService.java:175) ~[?:?]
at org.openhab.binding.lgthinq.lgservices.LGThinQFridgeApiV1ClientServiceImpl.setControlCommand(LGThinQFridgeApiV1ClientServiceImpl.java:128) ~[?:?]
at org.openhab.binding.lgthinq.lgservices.LGThinQFridgeApiV1ClientServiceImpl.setIcePlus(LGThinQFridgeApiV1ClientServiceImpl.java:109) ~[?:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQFridgeHandler.processCommand(LGThinQFridgeHandler.java:345) ~[?:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.lambda$0(LGThinQAbstractDeviceHandler.java:120) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.lang.Thread.run(Thread.java:1583) [?:?]
12:50:30.593 [TRACE] [ding.lgthinq.lgservices.api.RestUtils] - POST request to URI: ``https://eic.lgthinq.com:46030/api/rti/rtiMon