WebOS TV component not working

Configuration
1

Hi,
I have an LG WebOS TV which I’d like to connect to my system. If I do not set the IP address explicitly, it can’t find my TV, when I add the IP, then I have the setup card. When I click the setup card, I send the pairing request, but I see nothing on my TV and I find the following in the HA logs:

register failed to connect to ws://192.168.xx.xx:3000
components/media_player/webostv.py (ERROR)
(When I open the IP address and port above, I get a “Hello world” page)

Then after some minutes I have a webos media player entity, but it says off and does nothing even when the TV is on.

What can be the issue behind? I have an LG 49LH630V TV, running the latest available software. It is connected via cable (TV says it is connected to internet and apps can download), I have LG connected apps and mobile TV turned on. The TV was shipped with WebOS 3.0. HA and the TV are on the same wired network. I can connect via the LG Android app to the TV. The IP is DHCP but reserved.

I am running currently 0.84.6, however I had this problem before also on 0.80 (last time I gave it a try). I have Hassio in Docker running on Ubuntu Server 18.04 LTS.

This is my relevant config.yaml entry:

media_player:

  • platform: webostv
    host: 192.168.xx.xx
    timeout: 60
    mac: xxxxxxxx
    filename: webostv.conf

I also tried without specifying mac address with same results. I do have webostv.conf in my config directory, however it has a size of 0 bytes.

2

You’ve never been able to connect the WebOS TV to HA before? Not even on version 0.80? I ask because if someone hasn’t been able to get it working initially, then it is more likely a user error, or maybe it’s a TV issue.

I made sure to follow these instructions exactly. Did you do these steps on your TV before adding the configuration in Home Assistant? This is required to do first. Then you add to the media_player section of your configuration.yaml. Mine looks like this:

- platform: webostv  
  host: 192.168.1.100
  turn_on_action:
    service: wake_on_lan.send_magic_packet
    data:
      mac: !secret lg_mac_address

Following the remaining instruction on the Home Assistant UI is pretty straightforward. Your webostv.conf should have your token stored in it if it paired successfully. This is what my webostv.conf looks like:

{"192.168.1.100": "aaaaaaaaaaaaaaaaaatokenhere"}

The WebOS component has been working for me since version 0.79 to 0.89.

3

I can’t remember the setting (i’m not in front of my tv right now) but you have allow outside connections. i think it’s something to do with turning on remote connections via wifi (even though i don’t have wifi turned on that setting still has to be set to yes.)
I’ll look it up when i get home

4

@dwinn: I did follow these steps and the LG app (that LG suggests to suse on a phone to control the TV) does connect to my TV and gives the pairing request, however, HA can not. It did not connect neither with 0.80 nor 0.84. I add it to HA, then I get the card where I can send the pairing request to my TV, but it never happens, and I get the error that the websocket connection is failed

@ghvader: I turned on basically anything that has the slightest relation with connections, and the LG app on my phone does connect, however HA can not…

5

That’s weird then. I would revisit the network/firewall settings of your server that hosts your Home Assistant instance and see if something is wrong there. I’ve connected to the TV using Hassio on a Raspberry Pi 3 and Asus Tinkerboard S and it’s been fine for the past several releases.

7

I went and looked at my tv again tonight.
go to your settings menu and then go to general and then look for “mobile tv on”
go in there and enable the wifi settings (even if you are using a lan instead of wifi)
also try to go in that screen it says remove pairings… do that and then restart everything and see if it will re-pair with HA

edit: also make sure you are running on the “states” page, i have not done a ton of setup on my lovelace ui yet, so my media players (i.e. tv) don’t show up on that page. but does on my states page.

8

thanks for your help, but I guess, I’ll just give it up and maybe try again in a few months time
I couldn’t make it work, and I don’t really understand why, but I can probably live without it, so I don’t need the headache :smiley: