core: Android TV - HA 2022.2.1 is not migrated androidtv yaml settings after upgrade

The problem

Hi!

In HA 2022.2.1 update, in breaking changes section, about androidtv integration, it was said that the settings are transferred automatically from the yaml file after upgrade, but in my case it dind’t happened, what’s wrong and who can confirm this?

In descovery section I see three discovered devices, but, when I clicking to one of it and opens the add window - the integration is not detected the ip address of the discovered device (I mean, I know all my ips, but it’s just interesting, 'coz it’s look like correct detection of my yaml file androidtv settings, 'coz one of my three devices is offline right now, and discivering mode can’t detect it right now)… It’s a correct behaviour?

What version of Home Assistant Core has the issue?

core-2022.2.1

What was the last working version of Home Assistant Core?

core-2021.12.10

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Android TV

Link to integration documentation on our website

https://www.home-assistant.io/integrations/androidtv/

Example YAML snippet

- platform: androidtv
    name: bedroom_xiaomi_mi_tv
    host: 192.168.1.13
    apps:
      com.megogo.application: "Megogo"
      com.mitv.tvhome.atv: "Android TV Launcher"
  - platform: androidtv
    name: kitchen_xiaomi_mi_stick
    host: 192.168.1.14
    apps:
      com.megogo.application: "Megogo"
  - platform: androidtv
    name: hall_xiaomi_mi_box
    host: 192.168.1.15
    apps:
      com.megogo.application: "Megogo"
      com.mitv.tvhome.atv: "Android TV Launcher"

Anything in the logs that might be useful for us?

Nothing in logs about my yaml setting of it.

Additional information

No response

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 18 (1 by maintainers)

Most upvoted comments

@hillbicks

https://community.home-assistant.io/t/2022-2-lets-start-streamlining/387648/484?u=calisro

add sensor

 - platform: uptime

alias: AndroidTv Scans
description: ''
trigger:
  - platform: time_pattern
    seconds: /2
condition:
  - condition: state
    entity_id: automation.androidtv_scans
    state: 0
    attribute: current
  - condition: template
    value_template: '{{ ( now() - states(''sensor.uptime'')|as_datetime ).seconds > 90 }}'
action:
  - service: homeassistant.update_entity
    data: {}
    target:
      entity_id:
        - media_player.xxxxxx

calisro on Feb 4, 2022

I can report this as well, but with a slightly different scenario, maybe even a completely different bug altogether. The previous version allowed for a scan_interval setting in the yaml. This option is now completely missing from the gui setup and can’t be added manually neither. The documentation still mentions this option as well.

Or did I miss something? Neither the breaking change section in the announcement, nor the pull request mention scan_interval though.

hillbicks on Feb 4, 2022

Needed to reconfigure it as well (popped up as “new discovered device”), that’s not what to expect when reading

Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

bcutter on Feb 13, 2022

Well I turned off ADB Debugging and Apps from unknown sources, restarted Fire TV, reenabled debugging and Apps and it worked first time on both of sticks. Maybe just restarting Fire TV would have worked? I never got a pop up message to accept the connection on either one.

jwelvaert on Feb 5, 2022

Huh, well, that should do it. Thanks for pointing that out. I’ll just do it with two nodes in node red.

hillbicks on Feb 4, 2022

Which was offline? The Spacing on your

- platform: androidtv
    name: bedroom_xiaomi_mi_tv
    host: 192.168.1.13
    apps:
      com.megogo.application: "Megogo"
      com.mitv.tvhome.atv: "Android TV Launcher"

Was off. Just an observation.

calisro on Feb 4, 2022

Btw, I manually added this devices through the gui, and they pulled themselves into place, but again the question is - this how it should have happened when migrating from yaml to gui? Thanks.

SAOPP on Feb 4, 2022