Giter Club home page Giter Club logo

Comments (11)

itm1960 avatar itm1960 commented on June 17, 2024 1

OK many thanks for your help.

from core.

home-assistant avatar home-assistant commented on June 17, 2024

Hey there @thecode, mind taking a look at this issue as it has been labeled with an integration (webostv) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of webostv can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign webostv Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


webostv documentation
webostv source
(message by IssueLinks)

from core.

thecode avatar thecode commented on June 17, 2024

Please enable Debug for LG webOS Smart TV integration, turn on the TV, wait until it shows on in HA, disable debug and attach the log.

Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.

Thanks

from core.

itm1960 avatar itm1960 commented on June 17, 2024

home-assistant.log

from core.

itm1960 avatar itm1960 commented on June 17, 2024

Log attached, as per your instructions - the TV was turned on at around 15:49 today

from core.

itm1960 avatar itm1960 commented on June 17, 2024

I should add that the state of the TV entity is shown as "off" in the HA UI, even after the TV has been turned on (and picked up by the Squeezebox/LMS integration as a media player).

from core.

thecode avatar thecode commented on June 17, 2024

According to the log HA was never connected to the TV.
There are two IPs in the log, 192.168.1.42 & 192.168.1.49 if the IP is correct than the network access is disabled on the TV.

from core.

itm1960 avatar itm1960 commented on June 17, 2024

The IP address of the TV is actually 192.168.1.128. It has connected to my Logitech Media Server as a media player, and that server is running on the same hardware as HA.
Maybe best to remove and re-install the LG integration? (although I'm not sure I know how to remove it!)

from core.

thecode avatar thecode commented on June 17, 2024

If I remember correctly a similar issue was due to the TV connected via WiFi and Wired LAN at the same time.
The IP for the TV is picked up automatically by what the TV advertising.
I would first do the following.

  1. Make sure the TV has only one connection to the network, highly recommended that it would be a wired one.
  2. Turn off the TV
  3. Restart Home Assistant (just core, not a full reboot)
  4. Turn on the TV

HA should pick the correct IP. If this doesn't happen you can try to remove and add the TV again.

from core.

itm1960 avatar itm1960 commented on June 17, 2024

The TV is connected via ethernet (and has never been configured for wifi).

I turned off the TV, did a "Quick Reload" restart of HA, then turned on the TV. HA still didn't pick it up. So I deleted both of the devices in the LG integration, did a full HA restart, then turned on the TV again. The LG integration had disappeared, so I reinstalled it and re-paired it with the TV. HA has now reconnected with it.

The strange thing is that the TV now seems to have a different MAC address (I had a static IP address reservation defined on my router). I'm wondering if this is what might have caused the problem, and whether a firmware update on the TV could have brought this about? (there was an update a couple of days ago).

from core.

thecode avatar thecode commented on June 17, 2024

The strange thing is that the TV now seems to have a different MAC address (I had a static IP address reservation defined on my router). I'm wondering if this is what might have caused the problem, and whether a firmware update on the TV could have brought this about? (there was an update a couple of days ago).

Yes, it can explain both why it changed the IP and why HA wouldn't pick it up again, this shouldn't happen, maybe it is a bug on the TV firmware, but for now I don't think it worth investigating this, I will note this in case it will happen to others.

from core.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.