-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
Comments
I don't think thats how you set |
Hey there @cdce8p, mind taking a look at this issue as its been labeled with a integration ( This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people. |
@alternativ Please move |
I got a very similar warning on 93.1 and a media_player custom component.
|
@ik0adr that error has nothing to do with homekit, I would recommend contacting whomever created the |
Hi! I have followed this instructions:
I also set the auto_start to false and included the 5 min start automations, and no success so far. My config is:
customise:
and the automation:
On the other hand if I do:
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! |
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. |
Home Assistant release with the issue:
0.94.0.dev0
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
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.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):The text was updated successfully, but these errors were encountered: