Webos: No device after pairing tv

Configuration
1

Hello!
I had configured this integration working until I had to factory reset the tv for other problems. So, my config in configuration.yml it’s “working”.

I have been reading some threaths and I deleted th webostv.conf file to force pairing process again.

After restarting hassio, the notification has appeared. I started the process to sync with TV, the TV has asked me to give permission and after this, hassio showme a screen like this:
image

I tried to change the ip addres of my tv, change the name of the devie, but still not showing up on devices.

I have to “clear” something more? What can I do?

webostv:
  host: 192.168.0.xxx
  name: TV01
  turn_on_action:
    service: wake_on_lan.send_magic_packet
    data:
      mac: 64-xx-xx-xx-xx-xx
  customize:
    sources:
      - livetv
2

Do you have any related messages / errors in your log?

3

Hello!
If i find “webos” in my home-assistant.log:

2021-09-18 10:27:02 WARNING (MainThread) [homeassistant.components.webostv] LG webOS TV IP_TV needs to be paired
......
2021-09-18 20:49:20 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/aiopylgtv/webos_client.py", line 340, in ping_handler
    ping_waiter = await ws.ping()
  File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 657, in ping
    await self.ensure_open()
  File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 735, in ensure_open
    raise self.connection_closed_exc()
websockets.exceptions.ConnectionClosedOK: code = 1001 (going away), reason = server shutting down

The first line, it’s when I received the notification, the other error it’s 10 hours before i did the pair process.

4

Is your tv connected by cable or by wifi?

5

Yes, It’s connected by cable.

Things I have checked:

  • Connect by cable & wifi, now it’s only cable
  • Check that the LG connect apps option is activated on the TV
  • wake_on_lan: in configuration.yaml
6

Try deleting webostv.conf and redoing the pairing again. Maybe it was just a one-time error caused by waiting too long for pairing.

7

I have tried it several times, it is the way I have to start the pairing between the TV and Hassio again. When I try it, after accepting the pairing on TV I get the image in the first message.

Do you know if I have to clear/erase something more?

8

Clear your browser cache.

9

I have tried with different browsers, different computers, even from windows and mac with the same result, after finishing the pairing process I don’t see any device.

Another thing that I have tried today, has been to recover the webostv.conf file from an old backup and have the same content.

Something new in log in the first reboot after pairing process:

2021-09-20 20:17:23 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2021-09-20 20:17:23 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.tv01_9 is taking over 10 seconds
2021-09-20 20:17:33 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
10

OMG! sorry for my inexperiencie in Hassio…
I’m looking for a new device and it’s a new ENTITY. :cold_sweat:

It’s working!

I apologize for the time that I have lost you