Kodi: inconsistency in configuration requirements

[Molodax]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
36.1, 37.0

Python release (python3 --version):
any

Component/platform:
Kodi

Description of problem:
Kodi media player does not require httpfor host name anymore (introduced in #5098), however, Kodi notification component still requires it. This is confusing that the same platform requires different format of the same host.

Expected:
Consistency in the requirements within, at least, the same platform.

Problem-relevant configuration.yaml entries and steps to reproduce:

# Example configuration.yaml entry
notify:
  - platform: kodi
    name: NOTIFIER_NAME
    host: http://192.168.0.123

media_player:
  - platform: kodi
    host: 192.168.0.123

Traceback (if applicable):

Additional info:

[tbrasser]

Maybe it's a good effort to make the host key consistent across all components? Are there any guidelines in the developer documentation that favour one over the other? Thanks for the issue, this threw me of as well, I had issues connecting to Kodi and was looking for inconsistencies in my configuration, thought I fixed it but made it worse instead.

Edit:
Lol, https://home-assistant.io/developers/component_initialization/ does actually give an example without http://, but it's not really a guideline. :P

[emlove]

Thanks for bringing this up! When I did the Kodi conversion I didn't realize there was an extra Kodi platform floating out there.

We don't have any actual guideline for host, but Kodi was one of the few if maybe the only platform to use the format. I believe it was an artifact of being one of the very early Home Assistant platforms. The problems with the format came to light when we wanted to add websocket support.