Correct channel names for voice assistants about lghorizon

[Sholofly]

Where do you examine this logs?

[StevoNL]

The screenshot is from myactivity.google.com. It shows my voice prompt and the voice response from Google Assistant. It seems the channel names are passed to Google Assistant as "p NPO", "p VRT canv", "p RTL" etc.

Everything is executed perfectly by Home Assistant and there are no errors, the debug logs don't share any valuable information imo. For example: this is the log entry for a single request (key's removed):

2024-04-09 15:29:04.651 INFO (Thread-24 (_thread_main)) [lghorizon.lghorizon_api] Executing API call to https://spark-prod-nl.gnp.cloud.ziggogo.tv/eng/web/linear-service/v2/replayEvent/crid:~~2F~~2Fgn.tv~~[..........]returnLinearContent=true&language=nl

[Sholofly]

True, I don't think its an integration issue: In my account it's reporting no p:

[StevoNL]

Interesting. I'll try and remove the integration from Home Assistant and Google Home and then do a reinstall. Perhaps something is still lingering somewhere now. I'll come back with more information after I tried.

[StevoNL]

Allright, an update with high failure rate... Things I've tried:

• Remove LGHorizon integration, restarted Home Assistant, synced devices on Google Home to make sure TV is removed. Re-added LGHorizon integration, restarted Home Assistant again and installed integration, resynced devices on Google Home:
  Problem persists
• Tried voice promts via Google Nest mini, Google Home mini, Google Nest Hub and android Phone. Tried locally via Wifi (Local fulfillment) aswell as via 5G (Cloud fulfillment):
  Problem persists
• Redeployed Google Assistant testversion through actions.google.com:
  Problem persists

The channel names show correctly on device screens, even in Google Home, yet the voice responses remain truncated and with leading "P".
Sholofly's reply confirm my suspicion that the cause doesn't lie in the integration. I suspect it's probably caused by a cache lingering somewhere far far away, but I'm out of clues.

Thanks Sholofly for your quick response, if anyone else has the same problem, has an idea or know's the solution... I'd be happy to hear!