core icon indicating copy to clipboard operation
core copied to clipboard

Home assistant is currently not registered with IANA in terms of 'ServiceType'

Open oliv3r opened this issue 1 year ago • 2 comments

The problem

Currently, home-assistant on avahi shows up as '_home-assistant._tcp'. This is because home-assistant is not registered on http://www.dns-sd.org/ServiceTypes.html (as per https://github.com/avahi/avahi/blob/master/service-type-database/service-types#L23).

It would be good for HASS to register itself so that it has its name properly reserved.

What version of Home Assistant Core has the issue?

core-2024.5.5

What was the last working version of Home Assistant Core?

NA

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Zeroconf

Link to integration documentation on our website

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

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

oliv3r avatar May 30 '24 10:05 oliv3r

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

Code owner commands

Code owners of zeroconf 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 zeroconf 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)


zeroconf documentation zeroconf source (message by IssueLinks)

home-assistant[bot] avatar May 30 '24 10:05 home-assistant[bot]

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 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Still needs maintainer attention?

oliv3r avatar Aug 30 '24 06:08 oliv3r

Thanks. We'll take a look

balloob avatar Aug 30 '24 21:08 balloob

I've submitted a request.

balloob avatar Sep 09 '24 13:09 balloob

Got this response 👌

We've added the following entry to the registry:

Service Name: home-assistant Transport Protocol: tcp Description: Home Assistant Registration Date: 2024-09-12

Please see https://www.iana.org/assignments/service-names-port-numbers

balloob avatar Sep 12 '24 18:09 balloob