Hey there @thecode, mind taking a look at this issue as it has been labeled with an integration (webostv) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

webostv documentation
webostv source
_{^{(message by IssueLinks)}}

I have the exact same issue, however on the newest HA release (I guess it's 2023.12.2 - I'm trying to configure it for the first time, so don't know if it works on other versions). I've tried the same options as mentioned in the main post. Pinging the IP works fine, however HA doesn't even detect my TV, neither does LG ThinQ app (I'll try to contact with support about that). I've tried adding different configurations to configuration.yaml file and also using LG's integration creator, but none of this options worked. TV is connected via LAN/WLAN. HA is working on HAOS which is setup up on QNAP's virtual machine.

I would suggest set fixed ip address on LG tv, turn-on pairing and then add via the LG integration the TV by ip-address. I have 3 LG (webos) tv's and they are all working fine ( must say since i ensured fixed ip-address )

@b00tsie I don't have an option to specify static IP in TV settings, however, I made it static in router settings. So my TV always gets the same IP address. Still, no difference.
LG ThinQ app works fine for me though (and always did). HA integration is the only problem.

Same issue with Home Assistant 2023.12 and a LG G3 TV. It looks like the 2023 models need special handling.

Please add the following to configuration.yaml, restart home assistant, try to add the TV by IP and attach the log.

logger:
  default: info
  logs:
    homeassistant.components.webostv: debug
    aiowebostv: debug

Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.

Thanks

@thecode here's what I've got in logs after doing that (attached)
Lines up to 28 were added after HAOS startup. Lines 29 and to the end were added when I attempted to connect to TV.

Also, WebOS was updated since my initial message, so currently I see this:

• WebOS 8.3.0-15
• Software Version is 03.30.70

home-assistant.log

Now I have made a few observations regarding this. There are a couple of open source control tools out there for WebOS and I have tried quite a few of them. None of them were able to connect to my LG G3!

So I looked at the source and it seems like most tools try to connect to port 3000. So I tried to connect to the port through IPv4:

$ telnet 192.168.20.24 3000
Connection refused.

Connection refused. Bam! This obviously cannot work. This means it's not the integration's fault as the integration obviously cannot connect to port 3000.

After this I have messed with the settings on my TV and did a few things (unfortunately I did multiple things at once):

• toggled IPv6 off and on again in network settings, set IPv4 address manually (no DHCPv4)
• installed LG ThinkQ app on my Android phone

Guess what? ThinQ was able to find my TV and could control it remotely.

And what's even stranger: After pairing my TV with my phone through ThinQ the TV accepted connections on port 3000:

telnet 192.168.20.24 3000
Trying 192.168.20.24...
Connected to 192.168.20.24.
Escape character is '^]'.
Connection closed by foreign host.

Yay. So the TV finally does not refuse connections any more.

Now I am also able to connect to the TV through Home Assistant. 🎉

In order to get this sorted out (and maybe fix the docs) it would be nice if someone could try things more methodically (one step at a time). Before doing anything, could you please state the following:

• What is your TV model and firmware version? (I am on a LG G3, FW 03.20.17)
• What is your WebOS version? (Settings -> Support -> TV information) (I am on 8.2.0-710)
• Could you please provide the output of telnet <your_tv_ip> 3000?
• For 2023 models: Have you enabled IP control in Support -> IP control? (for older models there is a different option)

Now go ahead and do one thing at a time (I did it wrong because I was desperate):

• Install the LG ThinkQ app and check if it finds your TV. If it does, try to pair it.
• Now check the output of telnet <your_tv_ip> 3000 again.
• If it's accepting connections now, try connecting through Home Assistant

If the telnet command still gives you a Connection refused message, go to your TV's network settings:

• If IPv4 is on DHCP, set an IP address manually/statically.
• Try turning IPv6 off (just for testing)
• Now check the output of telnet <your_tv_ip> 3000 again.
• If it's accepting connections now, try connecting through Home Assistant

Note: Don't forget to enable IPv6 again as you don't want to stick with legacy IP only.

• What is your TV model and firmware version? (I am on a LG G3, FW 03.20.17)
  LG G3, 03.30.70
• What is your WebOS version? (Settings -> Support -> TV information) (I am on 8.2.0-710)
  8.3.0-15
• Could you please provide the output of telnet <your_tv_ip> 3000?
  Connection to 192.168.xxx.xxx port 3000 [udp/hbci] succeeded!
  Note: it's important to connect using UDP: nc -vu 192.168.xxx.xxx 3000 as TCP connection cannot be established.
  Note 2: WebSockets use TCP connection though and as far as I understand, aiowebostv uses websockets to connect to 3000 port.
• For 2023 models: Have you enabled IP control in Support -> IP control? (for older models there is a different option)
  yes

Install the LG ThinkQ app and check if it finds your TV. If it does, try to pair it.
Now check the output of telnet <your_tv_ip> 3000 again.

LG ThinQ always worked fine

Try turning IPv6 off (just for testing)

it was off already

If IPv4 is on DHCP, set an IP address manually/statically.

Doesn't make any difference since the IP address was made static on a router side, but tried that too. No difference.

If it's accepting connections now, try connecting through Home Assistant

Nope :( HA logs has the same:

2024-02-15 00:14:54.744 DEBUG (MainThread) [aiowebostv] connect(192.168.xxx.xxx): uri: ws://192.168.xxx.xxx:3000
2024-02-15 00:14:56.745 DEBUG (MainThread) [aiowebostv] exception(192.168.xxx.xxx): TimeoutError()

• Note: it's important to connect using UDP: nc -vu 192.168.xxx.xxx 3000 as TCP connection cannot be established.

If TCP connection to port 3000/3001 cannot be established then that's the problem. As I said I was also facing this until I messed around with the TV's network settings and the ThinQ app.

If Telnet gives you a connection refused then my guess is that the Home Assistant integration cannot do anything about it. You may try bscpylgtv and check if the connection to your WebOS TV succeeds with it. If not, then that's the issue.

Note 2: WebSockets use TCP connection though and as far as I understand, aiowebostv uses websockets to connect to 3000 port.

Yeah, aiowebostv uses TCP. AFAIK UDP is for WebRTC. The Python websocket library, which aiowebostv uses, opens the socket in TCP mode and aiowebostv does not change this.

Since we are both using the same TV (with slightly different FW) I think you should somehow be able to work this out. Maybe reset/reinstall the ThinQ app again, pair again and check the status of TCP port 3000 directly after pairing with ThinQ. You may also try to toggle the IP control setting.

As a last resort you could also try to factory reset your TV. I was about to do that with my TV before I got this to work.

There was WebOS upgrade today (0.30.71) and finally tcp connection succeeds

nc -v 192.168.xxx.xxx 3000
Connection to 192.168.xxx.xxx port 3000 [tcp/hbci] succeeded!

So maybe there was a problem with the previous version. However, HA still cannot connect with the same error 🤔

2024-02-19 11:42:33.337 DEBUG (MainThread) [aiowebostv] connect(192.168.xxx.xxx): uri: ws://192.168.xxx.xxx:3000
2024-02-19 11:42:35.338 DEBUG (MainThread) [aiowebostv] exception(192.168.xxx.xxx): TimeoutError()

UPD: I solved the problem. HA and TV were in different subnetworks 192.168.AAA.xxx and 192.168.BBB.yyy. There's no routing problem, both networks have full access to each other, but apparently, TV banned connection from "non-native" subnetwork. I changed HA's IP and it finally works.