Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Homekit, deviceclass tv and webostv integration #24006

Closed
alternativ opened this issue May 20, 2019 · 7 comments
Closed

Homekit, deviceclass tv and webostv integration #24006

alternativ opened this issue May 20, 2019 · 7 comments

Comments

@alternativ
Copy link

alternativ commented May 20, 2019

Home Assistant release with the issue:

0.94.0.dev0

Last working Home Assistant release (if known):

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

  • Raspberry PI
  • LG OLED65C7V

Component/platform:

https://www.home-assistant.io/components/webostv/

Description of problem:

Not possible to use the newly introduced homekit tv class to control webOS tv. The logging shows as below.

Your configuration contains extra keys that the platform does not support (but were silently accepted before 0.88). Please find and remove the following.This will become a breaking change.

Offending data: {"device_class": "tv", "host": “redacted”, "platform": "webostv", "name": "webos", "customize": “redacted”, "turn_on_action": "redacted”}

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

# Discover some devices automatically
discovery:
  ignore:
    - apple_tv
    - philips_hue
    - plex_mediaserver

wake_on_lan:

media_player:
  - platform: webostv
    host: redacted
    name: webos
    device_class: tv
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: redacted
    customize:
      sources:
        - Set-Top Box
        - Apple Tv
        - Playstation
        - Game Console

homekit:
  filter:
    include_domains:
      - media_player
  entity_config:
    media_player.webos:
     name: tv
     feature_list:
        - feature: on_off
        - feature: play_pause
        - feature: play_stop
        - feature: toggle_mute
@Jc2k
Copy link
Member

Jc2k commented May 20, 2019

I don't think thats how you set device_class - looks like you can do it through the front end though - https://www.home-assistant.io/docs/configuration/customizing-devices/?

@ghost
Copy link

ghost commented May 20, 2019

Hey there @cdce8p, mind taking a look at this issue as its been labeled with a integration (homekit) you are listed as a codeowner for? Thanks!

This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people.

@cdce8p
Copy link
Member

cdce8p commented May 20, 2019

@alternativ Please move device_class: tv to the customize section for the entity. Next remove the feature_list parameter for the tv and lastly take a look at https://www.home-assistant.io/components/homekit#my-media-player-is-not-showing-up-as-a-television-accessory
You will need to temporarily exclude the tv via the filter option and then add it again. The documentation should help you with that.

@ik0adr
Copy link

ik0adr commented May 20, 2019

I got a very similar warning on 93.1 and a media_player custom component.
The component works.
[https://github.com/pkozul/ha-tts-bluetooth-speaker]

WARNING (MainThread) [homeassistant.helpers.config_validation] Your configuration contains extra keys that the platform does not support.
Please remove [address].  (See /home/homeassistant/.homeassistant/configuration.yaml, line 325). 
Offending data: {"platform": "tts_bluetooth_speaker", "address": "41:42:D6:FA:B2:EA", "volume": "<redacted>"}
media_player:
  - platform: tts_bluetooth_speaker
    address: 41:42:D6:FA:B2:EA  
    volume: 0.8

@snicker
Copy link

snicker commented May 20, 2019

@ik0adr that error has nothing to do with homekit, I would recommend contacting whomever created the tts_bluetooth_speaker custom component

@cdce8p cdce8p removed their assignment Jul 10, 2019
@JuanGrados
Copy link

JuanGrados commented Jul 15, 2019

Hi!

I have followed this instructions:

@alternativ Please move device_class: tv to the customize section for the entity. Next remove the feature_list parameter for the tv and lastly take a look at https://www.home-assistant.io/components/homekit#my-media-player-is-not-showing-up-as-a-television-accessory
You will need to temporarily exclude the tv via the filter option and then add it again. The documentation should help you with that.

I also set the auto_start to false and included the 5 min start automations, and no success so far.

My config is:

media_player:
  - platform: webostv
    host: 192.168.1.103
    name: living_room_tv
    timeout: 5
    filename: webostv.config
    turn_on_action:
      service: wake_on_lan.send_magic_packet
      data:
        mac: !secret LGwebOSTV_MAC_Wired

homekit:
  auto_start: False
  filter:
    include_domains:
      - media_player

customise:


media_player.living_room_tv:
  device_class: tv

and the automation:

- alias: 'Start HomeKit'
  trigger:
    platform: homeassistant
    event: start
  action:
    - delay: 00:05  # Waits 5 minutes
    - service: homekit.start

On the other hand if I do:

homekit:
  filter:
    include_entities:
      - media_player.living_room_tv
  entity_config:
    media_player.living_room_tv:
      feature_list:
        - feature: on_off
        - feature: play_pause
        - feature: play_stop
        - feature: toggle_mute

I can see the tv in the Home app but only as a switch, so no further features than On/Off.

Any suggestions?

Thanks for the help!

@stale
Copy link

stale bot commented Oct 14, 2019

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 14, 2019
@stale stale bot closed this as completed Oct 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants