8000 Webos discovered but not added in the UI · Issue #4356 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Webos discovered but not added in the UI #4356

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

Closed
rofrantz opened this issue Nov 12, 2016 · 4 comments
Closed

Webos discovered but not added in the UI #4356

rofrantz opened this issue Nov 12, 2016 · 4 comments

Comments

@rofrantz
Copy link
Contributor
rofrantz commented Nov 12, 2016

Home Assistant release (hass --version):
0.33.0.dev0

Python release (python3 --version):
Python 3.5.2

Component/platform:
discovery, webos

Description of problem:
Although #4250 was merged and the updated netdisco 0.7.6 works and dicovers the TV when run with python3 -m netdisco, HA still fails to add it to the web interface unless I manually specify the IP.

Expected:
Add discovered WebOS TV to the UI interface

Problem-relevant configuration.yaml entries and steps to reproduce:

media_player LG_TV:
  platform: webostv
  name: LG TV Dormitor
  customize:
    sources:
      - livetv
      - youtube

Additional info:
I've tried to debug myself the issue by launching "hass --open-ui" cmd manually and this is what I saw in the logs:
1st I see in the logs "ERROR:homeassistant.components.media_player.webostv:No TV found in configuration file or with discovery"
And funny enough, later on I see "INFO:homeassistant.components.discovery:Found new service: webos_tv 192.168.4.118"

This makes me thing that the TV is discovered too late :(

OFF-TOPIC:
Now, as I've stated in earlier comments I'm not a python developer and I don't know how to debug myself HA issues, meaning I've tried to modify homeassistant/components/media_player/webostv.py by adding an extra log line but my change is not reflected; do I need to do anything else or how can I debug in general an issue in HA ?

@balloob
Copy link
Member
balloob commented Dec 19, 2016

This requires two steps:

@rofrantz
Copy link
Contributor Author

Indeed...right now there's a pr on netdisco mentioned to enhance the info from webos...and soon I'll submit also the code in HA to reuse webos info, as right now after debugging I've noticed that its missing and that's why autodiscovery was not working for webos

@balloobbot
Copy link

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 👍

@balloobbot
Copy link

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

@home-assistant home-assistant locked and limited conversation to collaborators Jul 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants
0