I got the Binding up and running and it work really well.
Now, as I am putting all “running” things and items into files I have a feature request (or the question for a hint what I am missing):
It would be really cool to be able to add the Things via a .things-file. Therefore, it seems to be important to have the possibility to add the property “device-id” via the .things file. The Philips Hue Binding offers such a feature: it discovers all properties on it’s own except those set in the .things file…
As an example I would refer to the Hue Binding. In the things files you add a bridge thing an then all “device things”. The connection between the exposed thing one has to add a “resource-id” as a configuration parameter refering the “real” lamp so one can steer it. This configuration parameter is also a property of the thing.
So, far LqThinq does discover the “device-id” and sets other properties when in auto discovery mode. The “device-id” seems already to be settable via the config parameters in the things file (e.g. {device-id=“blabla”}. As far as I saw: this already sets a device-id property. BUT: Based on that hand-set device-id all other properties are not discovered which makes the things-file not work.
What should help: Check whether there is a hand-set “device-id”, use that device-id to get /discover all other properties. Then when all properties are there, start the working thing.
LG Changed his API and is identifying not official integration asking to move to the new official open API delivered:
Error calling device settings 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.
The bad new is that this Binding must the rewritten, but the good news is that now we supposed to have an open and official API to use, but I don’t know it has all the features and capabilities of the official older one.
I have already tried this for manual connection to the Thinq API server. It works, but as @nemer suspected i.e. for my 3xAC does not give the information about the “filter usege” and other options.
I start to hate Cloud API systems and for the future devices I would chose those with local access, through local protocols. Since I have many devices it looks like every week I have to rewrite the code to adopt to the changes made to some devices.
hi guys,from what i read ,if i get it right, LG broke this super usefull binding changing something?Is there a way to get it back?I dont have dev skills but if there is a fix i am willing to test with my washer/dryer/fridge…
great!i did download the latest version but i am still at 4.1.2 so it does not seem to work right…Is there a compatible jar or do i have to update to 4.3?
i think its time to update ,i did update to 4.3.3 with no issues (so far).Installed the binding from within and i just had to delete the old things and relink the items to the new things…no problems so far!Thnx @nemer
could anyone help me with a text-file based specification of a thing? Binding works well, I connect the bridge but I do not get a washing machine online via a text file based specification.
However: I can normally configure the washing machine via UI. SO, something seems wrong with my text file.
It seems like the device ID is undef. Did the label change?
2025-03-02 10:32:03.138 [ERROR] [al.handler.LGThinQWasherDryerHandler] - Error updating thing /undef from LG API. Thing goes OFFLINE until next retry: Error starting device monitor in LG API for the device:undef
Full log:
2025-03-02 10:32:14.821 [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) ~[bundleFile:?]
at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.stopMonitor(LGThinQAbstractApiClientService.java:513) ~[bundleFile:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.stopDeviceV1Monitor(LGThinQAbstractDeviceHandler.java:639) [bundleFile:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getSnapshotDeviceAdapter(LGThinQAbstractDeviceHandler.java:678) [bundleFile:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.updateThingStateFromLG(LGThinQAbstractDeviceHandler.java:491) [bundleFile:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler$UpdateThingStateFromLG.run(LGThinQAbstractDeviceHandler.java:484) [bundleFile:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
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:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:840) [?:?]
2025-03-02 10:32:14.822 [ERROR] [al.handler.LGThinQWasherDryerHandler] - Error updating thing /undef from LG API. Thing goes OFFLINE until next retry: Error starting device monitor in LG API for the device:undef
org.openhab.binding.lgthinq.lgservices.errors.LGThinqApiException: Error starting device monitor in LG API for the device:undef
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getSnapshotDeviceAdapter(LGThinQAbstractDeviceHandler.java:679) ~[bundleFile:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.updateThingStateFromLG(LGThinQAbstractDeviceHandler.java:491) [bundleFile:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler$UpdateThingStateFromLG.run(LGThinQAbstractDeviceHandler.java:484) [bundleFile:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
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:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: 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) ~[bundleFile:?]
at org.openhab.binding.lgthinq.lgservices.LGThinQAbstractApiClientService.startMonitor(LGThinQAbstractApiClientService.java:495) ~[bundleFile:?]
at org.openhab.binding.lgthinq.internal.handler.LGThinQAbstractDeviceHandler.getSnapshotDeviceAdapter(LGThinQAbstractDeviceHandler.java:668) ~[bundleFile:?]
... 8 more
,i did update to 4.3.3 with no issues (so far).Installed the binding from within and i just had to delete the old things and relink the items to the new things…no problems so far!Thnx