Core: Zone component error after update to 0.69

[bieniu]

Home Assistant release with the issue:
0.69

Last working Home Assistant release (if known):
0.68.1

Operating environment (Hass.io/Docker/Windows/etc.):
RPi3, Raspbian, virtual_env/Python 3.6.3

Component/platform:
zone

Description of problem:
After upgrade HA to 0.69 I have error during setup component zone:

Error during setup of component zone
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/setup.py", line 142, in _async_setup_component
    result = await component.async_setup(hass, processed_config)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/zone/__init__.py", line 68, in async_setup
    hass.data[DOMAIN][slugify(name)] = zone
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/util/__init__.py", line 43, in slugify
    text = normalize('NFKD', text)
TypeError: normalize() argument 2 must be str, not None

The error occurs even when I completely delete the zone configuration or create a configuration via Settings / Integrations.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

homeassistant:
  latitude: !secret home_latitude
  longitude: !secret home_longitude
  elevation: 97

 zone:
   name: work
   icon: mdi:domain
   latitude: 52.1344
   longitude: 21.0586

[bieniu]

I found a solution. I didn't have the name option for the homeassistant in my configuration. After adding it the error disappears. According to the documentation on the page, the name option is optional.

[Kane610]

Great catch! Thanks!

[theres]

Not sure if it's the same problem, but if you have multiple zones with the same name, only the last one is visible on map. That used to work.

[Kane610]

@theres thanks! Will look into this

[Martinvdm]

same issue as @theres. Before 0.69 multiple zones with the same names are working just fine. Now, after 0.69, it is not working any more. Without an error it is only creating a sensor of the last Zone.

[Kane610]

Are there any real reasons why you'd want to have multiple zones with the same name?

[Martinvdm]

Yes. I have 2 work zones. Used in automations for my wife and myself. From_work etc. But secondly according to documentation the Name is optional and a supposed to be a ‘friendly name’ of the zone. And it is nicer to have the same name in the GUI for both persons.

[remco770]

Same issue with my setup. After upgrading to 0.69.x. Could someone dive into it? No error logging

[Kane610]

I've reverted limitations on naming for zones configured through configuration.yaml