openhab-addons: [lgwebos] OLED77C29 can not be turned on from "always ready"

In advance

  • This was working before
  • I do not know the WebOS version from that time
  • Since the last two updates i have this problem
  • Somewhere i read that the lgwebos-binding does not support the power on from “always ready” but due to the fact that it was working in my case i opened up this issue

Expected Behavior

  • LG TV is off in “always ready” mode (LED flashing white)
  • Switch-Item connected to lgwebos:WebOSTV:id:power can activate the TV

Current Behavior

  • LG WebOS v 03.21.45
  • Switch-Item is turned on
  • LG stays in “always ready” and is not turned on
  • See extended log below
==> /var/log/openhab/openhab.log <==

2023-01-08 13:23:01.311 [DEBUG] [ebos.internal.handler.LGWebOSHandler] - handleCommand(lgwebos:WebOSTV:24e9a24f88:power,OFF)

2023-01-08 13:23:01.312 [DEBUG] [g.lgwebos.internal.PowerControlPower] - Received OFF - TV is already off.

==> /var/log/openhab/events.log <==

2023-01-08 13:23:02.399 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'dLgTv1_Power' received command ON

2023-01-08 13:23:02.400 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'dLgTv1_Power' predicted to become ON

2023-01-08 13:23:02.401 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'dLgTv1_Power' changed from OFF to ON

==> /var/log/openhab/openhab.log <==

2023-01-08 13:23:02.410 [DEBUG] [ebos.internal.handler.LGWebOSHandler] - handleCommand(lgwebos:WebOSTV:24e9a24f88:power,ON)

Possible Solution

  • Fixing the binding?

Steps to Reproduce (for Bugs)

As described in “Current Behavior”

Context

  • Turning on my “Cinema Scene” via Google Home Assistant through Google Home Mini

Your Environment

  • Docker running on ProxMox
runtimeInfo: version: 3.4.0 buildString: Release Build locale: en-US systemInfo: configFolder: /openhab/conf userdataFolder: /openhab/userdata logFolder: /openhab/userdata/logs javaVersion: 11.0.17 javaVendor: Alpine osName: Linux osVersion: 5.15.64-1-pve osArchitecture: amd64 availableProcessors: 4 freeMemory: 155674776 totalMemory: 731906048 startLevel: 100 bindings: - airq - amazondashbutton - astro - chromecast - habspeaker - http - ipcamera - lgwebos - luxtronikheatpump - miio - mqtt - network - ntp - openweathermap - pushbullet - shelly - somfytahoma - sony - telegram - wifiled - wled clientInfo: device: ios: false android: false androidChrome: false desktop: true iphone: false ipod: false ipad: false edge: false ie: false firefox: false macos: false windows: false cordova: false phonegap: false electron: false nwjs: false webView: false webview: false standalone: false pixelRatio: 1 prefersColorScheme: dark isSecureContext: false locationbarVisible: true menubarVisible: true navigator: cookieEnabled: true deviceMemory: N/A hardwareConcurrency: 4 language: de-DE languages: - de-DE onLine: true platform: Linux x86_64 screen: width: 3440 height: 1440 colorDepth: 24 support: touch: false pointerEvents: true observer: true passiveListener: true gestures: false intersectionObserver: true themeOptions: dark: dark filled: true pageTransitionAnimation: default bars: light homeNavbar: default homeBackground: default expandableCardAnimation: default userAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 timestamp: 2023-01-08T12:57:39.008Z

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 26 (12 by maintainers)

Most upvoted comments

@SHU-red : you can’t do anything, the problem is an incompatibility between the binding and the new TV firmware. Someone has to enhance the binding, that’s all.

Are you sure your problem is not simply #14309 ? What is your TV firmware?