core: LG Soundbar is triggered by media player

The problem

my home assistant keeps my soundbar on and i can’t turn it of anymore. When i push the powerbutton on the remote it says goodbye and restarts itself immediately.

Environment

  • Home Assistant Core release with the issue: 0.115.6
  • Last working Home Assistant Core release (if known): /
  • Operating environment (OS/Container/Supervised/Core): HassOS 4.13 on Raspi 4
  • Integration causing this issue: media player
  • Link to integration documentation on our website:

Problem-relevant configuration.yaml


Traceback/Error logs

2020-10-03 11:10:20 WARNING (MainThread) [homeassistant.helpers.entity] Entity media_player.lg_soundbar_e797e6bc_013a_41c4_8df7_38516a852e9c is incorrectly being triggered for updates while it is disabled. This is a bug in the lg_soundbar integration

Additional information

The soundbar is not integrated as a device. It always gets an entity. I can deactivate the entity and will get the warning in the logs:

When i push the turn off button ot the switch long, the soundbar turns off. But when i’m using it again, home assistent detects it again as a new entity - with another number behind lg_soundbar_…

I tried: discovery: ignore: - lg_soundbar - lg - media_player

that didn’t work

also tried:

discovery: ignore: - google_cast

media_player:

  • platform: lg_soundbar

that didn’t work either

I’m not using the soundbar with ha so i just would love to remove it fully to have a chance to switch it of again

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 16 (4 by maintainers)

Most upvoted comments

@patatman both (this and your) issue should be fixed with my pull request #42044. If you want you can test it (via custom_component). But it is currently stuck because of a unique id problem (see pr). Nothing we can do for now if nobody has a satisfying idea.

@bernimoses I have used hostname (self._host) I also tested the name (self._name) but the expected result did not return.

There are two problems here:

  1. The soundbar uses a different uuid when announcing itself via zeroconf which leads to multiple entities
  2. The current component uses polling which wakes the soundbar from standby and is not necessary with python-temescal version > 0.2 anymore

As unique id i am testing the hostname since that should not change unless the user does so. And so far it looks ok. What did you @amonhk use as unique id for homeassistant?