Core: webostv not working (0.109.1)

Created on 30 Apr 2020  路  9Comments  路  Source: home-assistant/core

The problem


webostv integration stopped working (entities not instantiated) after upgrading from 0.108.8 to 0.109.1. after restarting HA, i see the error messages list in the Traceback/Error logs. it appears that if the TVs (3) are off, webostv doesn't instantiate the TVs however in the previous revisions if did.

also note, if the TV happens to be on during HA restart all is well...

Environment

  • Home Assistant Core release with the issue: 0.109.1
  • Last working Home Assistant Core release (if known): 0.108.8
  • Operating environment (Home Assistant/Supervised/Docker/venv): venv
  • Integration causing this issue: webostv
  • Link to integration documentation on our website:
    https://www.home-assistant.io/integrations/webostv/

Problem-relevant configuration.yaml

webostv:
  - host: 192.168.1.20
    name: Living Room TV
    customize:
      sources:
        - Live TV
        - YouTube TV
        - Netflix
        - UI3 - Blue Iris
  - host: 192.168.1.107
    name: Master Bedroom TV
    customize:
      sources:
        - Live TV
        - YouTube TV
        - Netflix
        - UI3 - Blue Iris
  - host: 192.168.1.180
    name: Office TV
    customize:
      sources:
        - Live TV
        - YouTube TV
        - Netflix
        - UI3 - Blue Iris


Traceback/Error logs

2020-04-30 04:43:37 INFO (MainThread) [homeassistant.setup] Setting up webostv
2020-04-30 04:43:37 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=webostv, service=button>
2020-04-30 04:43:37 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=webostv, service=command>
2020-04-30 04:43:37 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=webostv, service=select_sound_output>
2020-04-30 04:43:38 DEBUG (MainThread) [aiopylgtv.webos_client] load keyfile from /home/homeassistant/.homeassistant/webostv.conf
2020-04-30 04:43:38 DEBUG (MainThread) [aiopylgtv.webos_client] getting client_key for 192.168.1.20 from /home/homeassistant/.homeassistant/webostv.conf
2020-04-30 04:43:38 DEBUG (MainThread) [aiopylgtv.webos_client] load keyfile from /home/homeassistant/.homeassistant/webostv.conf
2020-04-30 04:43:38 DEBUG (MainThread) [aiopylgtv.webos_client] getting client_key for 192.168.1.107 from /home/homeassistant/.homeassistant/webostv.conf
2020-04-30 04:43:38 DEBUG (MainThread) [aiopylgtv.webos_client] load keyfile from /home/homeassistant/.homeassistant/webostv.conf
2020-04-30 04:43:38 DEBUG (MainThread) [aiopylgtv.webos_client] getting client_key for 192.168.1.180 from /home/homeassistant/.homeassistant/webostv.conf
2020-04-30 04:43:39 DEBUG (MainThread) [homeassistant.components.webostv] No connection could be made with host 192.168.1.180, retrying in 60 seconds
2020-04-30 04:43:40 DEBUG (MainThread) [homeassistant.components.webostv] No connection could be made with host 192.168.1.20, retrying in 60 seconds
2020-04-30 04:43:40 DEBUG (MainThread) [homeassistant.components.webostv] No connection could be made with host 192.168.1.107, retrying in 60 seconds
2020-04-30 04:43:42 INFO (MainThread) [homeassistant.setup] Setup of domain webostv took 4.4 seconds.
2020-04-30 04:43:42 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=webostv>
2020-04-30 04:46:00 DEBUG (MainThread) [homeassistant.components.webostv] No connection could be made with host 192.168.1.180, retrying in 60 seconds


Additional information

webostv

Most helpful comment

That's why we have a "Breaking Changes" section for each release with instructions on how to handle them.

All 9 comments

Hey there @bendavid, mind taking a look at this issue as its been labeled with a integration (webostv) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

Screenshot 2020-04-30 17 56 41
Same problem for me!

Yes the most recent PR breaks the logic for startup when the TV is off. The solution would be to revert this and fix the previous issue in a more minimal way.

Having the same problem, the integration doesn't work in this version, the entities have disappeared from Home Assistant

Duplicate of #34877

I upgraded from 109 to 110 yesterday, and a duplicate entity was created for my webostv. Same IP address. New entity was created with a "_2" added to the end of the name. Could this be related to this issue or the fix to this issue?

@tescher that's the fix. Please check the 0.110 release notes: https://www.home-assistant.io/blog/2020/05/20/release-110/

@jjlawren that's it. Thanks. You're going to see a good flurry of questions for a while because of this I imagine.

That's why we have a "Breaking Changes" section for each release with instructions on how to handle them.

Was this page helpful?
0 / 5 - 0 ratings