LG Webostv and Homekit

Hi…How can I see my LG TV in the Home app? I integrated the TV into HA with the new configuration, but I don’t know how to view it with homekit:

configuration.yaml

webostv:

    host: 192.168.1.215 # match with IP address of your TV
    name: LG TV
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: "XX:XX:XX:XX:XX:XX"
    customize:
      sources:
        - livetv
        - Youtube
        - Apple TV
        - Netflix

If you check Developer Tools > States, is the TV represented as a media_player?

When you configured the Homekit integration, did you list media_player in include_domains? Or list the specific media_player in include_entities?

I have not specified any entities or domains. So they are all visible

At the end of my homekit yaml file

entity_config:
  media_player.lounge_tv:
    name: TV
    feature_list:
      - feature: on_off
      - feature: play_pause
      - feature: play_stop
      - feature: toggle_mute

Then should appear as Apple TV remote in control center

Yes, but I need to see my TV in home app, not only as remote control in control center. Do u can see your tv in home app?

Yes it appears in the home app.

Ok…did it appears as TV or Switch in Home App? Can u share your configuration, HA version, etc? Thanks @subzero79

As a tv showing, on//off and source selection

homekit: !include homekit.yaml

filter:
  include_domains:
    - media_player
  exclude_entities:
    - media_player.bedroom_tv
    - media_player.kodi_bedroom
    - media_player.kodi_lounge
  include_entities:
    - light.masterbedroom
    - light.lounge
    - light.toilet
    - light.dining_table
    - light.front_entrance
    - light.living_room
    - light.ricardo_bed_light
    - switch.fish_pond
    - light.patio
    - light.garden
    - light.bathroom
    - switch.bathroom
    - light.desktop_fan
    - light.desktop_light
    - sensor.bathroom_temperature
    - sensor.masterbedroom_temperature
    - binary_sensor.bathroom_door
    - light.kitchen_lights
    - fan.masterbedroom
    - light.kitchen_fan
    - switch.lounge_side_table
entity_config:
  media_player.lounge_tv:
    name: TV
    feature_list:
      - feature: on_off
      - feature: play_pause
      - feature: play_stop
      - feature: toggle_mute

Ok, thx…but in configuration.yaml?

?

that is configuration.yaml but splitted

homekit: !include homekit.yaml

You don’t have webostv: in configuration.yaml?

Yes but we are talking about homekit. webos doesn’t do homekit

webostv:
  host: 10.10.0.17
  name: Lounge TV
  customize:
    sources:
      - livetv
      - youtube
      - netflix
      - kodi
  turn_on_action:
    service: wake_on_lan.send_magic_packet
    data:
      mac: "14:c9:13:32:67:a9"

Ok…now i understand. Thx for your help!

So in configuration.yaml I should have:

Media_player: 

Homekit: #with your configuration

Webostv: (for HA)

sure, try that but lowercase

Yes sure. Thx

unfortunately, I see TV as a switch

Do you have sources in your media player ? I only have sources And power button I don’t have mute button.

I have (configuration.yaml)

media_player:    #empty

homekit:
  filter:
    include_domains:
      - media_player
      - sensor
      - binary_sensor
      - switch
      - light
      - climate
      - fan
      - device_tracker
      - input_boolean
    exclude_domains:
      - automation
      - scene
    exclude_entities:
      - binary_sensor.tvcamera
      - binary_sensor.tvsoggiorno
      - switch.learner1
      - switch.learner
      - light.led_tv
      - device_tracker.ipad_pro_di_salsalove
  entity_config:
    media_player.tv:
      name: TV
      feature_list:
        - feature: on_off


homeassistant:
   customize: !include customize.yaml

webostv:
    host: 192.168.1.215
    name: tv
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: "74:40:be:0d:f2:c4"
    customize:
      sources:
        - livetv
        - youtube
        - Apple TV
        - netflix

And customize.yaml


media_player.tv:
  friendly_name: tv
  icon: mdi:television
  device_class: tv

Yes i think this might also be required. Forgot that but is documented