core: WebOS Error 0.109.0b0

The problem

Environment

Home Assistant Core release with the issue:
Last working Home Assistant Core release (if known):
Operating environment (Home Assistant/Supervised/Docker/venv):
Integration causing this issue:
Link to integration documentation on our website:

Problem-relevant `configuration.yaml`

# LG TV
webostv:
  host: !secret weboslgtv
  name: LG-TV Lounge Room

Traceback/Error logs

Log Details (ERROR)
Logger: homeassistant.components.media_player
Source: components/webostv/media_player.py:119
Integration: Media player (documentation, issues)
First occurred: 8:24:50 AM (1 occurrences)
Last logged: 8:24:50 AM

Error while setting up webostv platform for media_player
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 178, in _async_setup_platform
    await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
    return fut.result()
  File "/usr/src/homeassistant/homeassistant/components/webostv/media_player.py", line 78, in async_setup_platform
    entity = LgWebOSMediaPlayerEntity(client, name, customize, on_script)
  File "/usr/src/homeassistant/homeassistant/components/webostv/media_player.py", line 119, in __init__
    self._unique_id = client.software_info["device_id"]
TypeError: 'NoneType' object is not subscriptable

Additional information

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 19 (9 by maintainers)

Most upvoted comments

Yeah sure, will do 👍

timmo001 on Apr 24, 2020

Same problem here. Three TVs in my home automation system. Two disappeared from home assistant (and there is no way to make them “reappear”) and one is still visible but not available. I wonder: Is it ever possible that almost every update the LG Webos plugin will break? It is quite boring and frustrating.

giustanca on Apr 24, 2020

Submitted a PR to make it less annoying.

jjlawren on Apr 29, 2020

Looks like @ludeeus beat me to it. Cheers 🍻

timmo001 on Apr 24, 2020

Updated to .109.0b1 with the same error occuring. Turned my TV on and restarted HA and the error goes away.

silfa718 on Apr 24, 2020

@DavidFW1960 I saw this same issue last night when I first loaded the the beta. This morning I restated and had the TV on, and the error is gone. Not sure which cleared it up.

silfa718 on Apr 23, 2020