zeroconf and/or androidtv_remote bug

[emandtf]

The problem

An user in "Home Assistant Italia" Facebook group let notice to have this issue after upgraded from 2023.4.1 to 2023.5.3.

This is his log (sorry because it's an image, but he is not much skilled using the PC):

He says to not have and neither use "androidtv" or "androidtv_remote".

Removing "default_config:" from "configuration.yaml" and declaring all integrations manually (EXCEPT for "zeroconf") seems working fine (but without "zeroconf" active obliviously)

I writing for him because he hasn't any account for Github to notice this issue here.

What version of Home Assistant Core has the issue?

core-2023.5.3

What was the last working version of Home Assistant Core?

2023.4.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

zeroconf, androidtv_remote

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

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

Code owner commands

Code owners of androidtv_remote 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 androidtv_remote Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

androidtv_remote documentation
androidtv_remote source
_{^{(message by IssueLinks)}}

[tronikos]

It's strange the mac address is missing from the discovery properties. Anyway in #94026 I'm removing the assert and instead abort the zeroconf step.