Failed to call service script/hyperhdr. [Errno 113] Host is unreachable. [LG WebOS, Picap v0.5.0, RP2040)

[Nerdpol-droid]

Version of the custom_component

v0.0.7

Configuration

2025-01-27 16:54:41.487 WARNING (MainThread) [hyperhdr.client] Connection to HyperHDR lost (192.168.178.56:19444) ...
2025-01-27 16:54:41.487 WARNING (MainThread) [hyperhdr.client] Could not close connection cleanly for HyperHDR (192.168.178.56:19444): ConnectionResetError(104, 'Connection reset by peer')

[...]

2025-01-27 18:03:52.399 WARNING (MainThread) [hyperhdr.client] Failed HyperHDR (192.168.178.56:19444) command: {'command': 'componentstate', 'error': 'Errors during specific message validation, please consult the HyperHDR Log', 'success': False, 'tan': 0}

[...]

2025-01-28 20:43:45.269 WARNING (MainThread) [hyperhdr.client] Could not write data for HyperHDR (192.168.178.56:19444): ConnectionResetError('Connection lost')
2025-01-28 20:43:45.270 WARNING (MainThread) [hyperhdr.client] Connection to HyperHDR lost (192.168.178.56:19444) ...
2025-01-28 20:43:45.270 WARNING (MainThread) [hyperhdr.client] Could not close connection cleanly for HyperHDR (192.168.178.56:19444): ConnectionResetError(104, 'Connection reset by peer')

Describe the bug

I am running HyperHDR (21.0.0.0beta1) on LG OLED with Picap 0.5.0 using a Adafruit Itsybitsy RP2040 as driver, following another common guide on GitHub. I have installed the custom integration using HACS.

I am facing an issue where HyperHDR Home Assistant integration is unable to re-establish connection once the TV has been turned off for a while, therefore disconnecting from Wifi, rendering HyperHDR, RP2024 plugged in the USB etc. unavailable through the network.

Error is: "Failed to call service script/hyperhdr. [Errno 113] Host is unreachable."

The only way to re-establish connection when TV was turned off a while is to restart Home Assistant completely. Turning on the TV only will not bring back the entities in Home Assistant. Reloading the integration config does not solve it and requests a full Home Assistant reboot to take effect.

Is there any way to fix or work around this behaviour?

Debug log

  File "/usr/local/lib/python3.13/site-packages/hyperhdr/client.py", line 1013, in async_send_clear
    return await self._async_send_json(data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/hyperhdr/client.py", line 463, in _async_send_json
    await self._writer.drain()
  File "/usr/local/lib/python3.13/asyncio/streams.py", line 374, in drain
    raise exc
  File "/usr/local/lib/python3.13/site-packages/hyperhdr/client.py", line 568, in _receive_task_loop
    while await self._async_receive_once():
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/hyperhdr/client.py", line 608, in _async_receive_once
    resp_json = await self._async_safely_read_command(use_timeout=False)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/hyperhdr/client.py", line 485, in _async_safely_read_command
    resp = await asyncio.wait_for(future_resp, timeout=timeout_secs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/tasks.py", line 507, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/streams.py", line 562, in readline
    line = await self.readuntil(sep)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/asyncio/streams.py", line 677, in readuntil
    await self._wait_for_data('readuntil')
  File "/usr/local/lib/python3.13/asyncio/streams.py", line 539, in _wait_for_data
    await self._waiter
  File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 1005, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
OSError: [Errno 113] Host is unreachable
<!-- To enable debug logs check this https://www.home-assistant.io/components/logger/ -->

[Nerdpol-droid]

I figured this was a configuration issue on my end. I set everything up with the TV conntected through Wifi and later changed it to LAN to enable WoL, without fixing the configuration to the new (LAN) IP address.

[Nerdpol-droid]

Have to reopen as this was not the root cause. Not sure why it worked the other night, today same issue appeared again.

[NeeeeB]

Well it looks like I have a somewhat similar problem.
HA integration worked ok last night.
After the night (so this morning), led instance is reported as switched off in the integration, although they are actually working.
If I switch them on, they go full white and I'm forced to reboot the TV so they can work correctly again (but they are still reported as off in HA).
There is definitely something wrong with the integration.
(full reinstall of integration did not solve the problem).

@mjoshd would be nice if you could investigate, and if you need testers I think we can both do it.

[mjoshd]

@Nerdpol-droid I don't have a rooted LG TV and have no way to know what complications may be introduced by running the HyperHDR server in that way. It sounds like the connection between the HyperHDR instance and Home Assistant is being lost at some point after the TV is turned off. Are you certain the HyperHDR server on the TV is getting the same IP/port every time it is powered on? Assuming your IP address issues are, hopefully, solved maybe try using the reload button in Home Assistant after you are sure the HyperHDR server running within the TV is fully back up and available. If that works then you can make an automation perform the reload automatically when the TV is detected as running (maybe with a delay to account for time reqired for the HyperHDR server to be fully up and running/available).
I use a Raspberry Pi 4 to host HyperHDR with HyperSPI controlling the lights and it has been working perfectly for several years.

@NeeeeB I only have one idea for your issue. It sounds like you may not have followed the Post Setup Advice on the Wiki. Give that a try; hopefully it helps.

I'm not a python or HA developer so I'm not going to be able to troubleshoot on your behalf.

In 2021 I put in a reqest on the HA forums for someone to create a proper HyperHDR integration. Nobody seemed to care or have any interest but I wanted one so I fought and fought with code and a couple months later came up with what you see today.

This integration was cobbled together back when HyperHDR v17 was the newest release and it has worked pretty well over the years with, thankfully, very little required in the way of 'fixes' (especially since I have no idea how python works).

At some point there will be a breaking change in HyperHDR or Home Assistant and that's going to be the end of this integration as I no longer have the time to spend fighting with python.

My hope is that someone who understands this stuff better than me will decide to make a fork and be capable of making the improvements folks would like and able to troubleshoot issues if/when they arrise.

[NeeeeB]

@mjoshd my problem is exactly the same as @Nerdpol-droid , and it has nothing to do with the post-setup advice.
Connection is lost on my side too, this is why it does strange things/strange behavior regarding led instance.

I totally understand that you can't help with fixing this problem.
I've been running your integration for a couple years too, and my previous installation, with HyperHDR running on a Pi, had zero problem with your integration.
And I suspect this is because it was running 24/7
Now on WebOS, as you stated, when TV is off, HyperHDR is off too, and the integration does not seem to be able to "reconnect" when HyperHDR is back online.

FYI, @Nerdpol-droid and I have static IPs on TV, so it does always have the same IP Address, so the problem is not in here.
Reloading HA when TV is online is a workaround, but a bit heavy unfortunately, because it can have side effects if other things are actually running when HA reboots (reload is not enough to make things work again, reboot is needed).