Core: WebOS TV Integration doesn't save more than 1 instance

[TimothyLeeAdams]

Home Assistant release with the issue:
0.101.3

Last working Home Assistant release (if known):
not known

Operating environment (Hass.io/Docker/Windows/etc.):
Docker on unRaid Host

Integration:
https://www.home-assistant.io/integrations/webostv/

Description of problem:
After adding a second WebOS TV instance (I have two LG TVs) to my configuration.yaml, I am able to complete the pairing process and successfully control both TVs. However, this doesn't survive a restart of Home Assistant because the paring process simply overwrites the webostv.conf file and doesn't save previous entries. This results in having only the most recently paired TV remain paired, and the other prompting a pairing request after each restart of Home Assistant.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

media_player:
  - platform: webostv
    name: Lunch Room TV
    host: 172.16.4.86
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: "48:8D:36:64:39:B5"
  - platform: webostv
    name: E&E TV
    host: 172.16.4.89
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: "00:51:ED:BE:03:50"

Traceback (if applicable):

Additional information:
Contents of webostv.conf BEFORE pairing second tv:
{"172.16.4.86": "b0c4be0e40c94a2c40345c178f8ddf98"}
Contents of webostv.conf AFTER pairing second tv:
{"172.16.4.89": "b60c2e12781d2ac64643d67f5be5d7a9"}

[AlexeyUkolov]

You should add different filenames where the pairing key with the TV should be stored:

media_player:
  - platform: webostv
    name: Lunch Room TV
    filename: webostv.conf
    host: 172.16.4.86
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: "48:8D:36:64:39:B5"
  - platform: webostv
    name: E&E TV
    filename: webostv1.conf
    host: 172.16.4.89
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: "00:51:ED:BE:03:50"

[TimothyLeeAdams]

Thanks for the tip, that works! I see now that the documentation describes the "filename" field, but it wasn't quite clear to me that you could create multiple configs and name them as desired. It definitely seems to be a serviceable workaround. I do think that the integration should be updated to handle multiple TVs when setting up through the config flow to make it friendlier for new users.

I guess this is a low priority, but something that would contribute to the user-friendliness goals of the project. I'm going to leave this open unless someone else disagrees.

You should add different filenames where the pairing key with the TV should be stored:

media_player:
  - platform: webostv
    name: Lunch Room TV
    filename: webostv.conf
    host: 172.16.4.86
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: "48:8D:36:64:39:B5"
  - platform: webostv
    name: E&E TV
    filename: webostv1.conf
    host: 172.16.4.89
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: "00:51:ED:BE:03:50"

[springstan]

integration should be updated to handle multiple TVs when setting up through the config flow to make it friendlier for new users.

@TimothyLeeAdams completely agree with you on this! Please open a feature request for that functionality here.

Please close this issue since your problem has been solved and github issues should only contain issues and not feature requests. Thank you very much! :)

[TimothyLeeAdams]

integration should be updated to handle multiple TVs when setting up through the config flow to make it friendlier for new users.

@TimothyLeeAdams completely agree with you on this! Please open a feature request for that functionality here.

Please close this issue since your problem has been solved and github issues should only contain issues and not feature requests. Thank you very much! :)

Done! Thanks for the suggestion - I'll go create a feature request for this.

[hjkss]

When I add the filename in the config.yaml it gives and error