New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zone component error after update to 0.69 #14396
Comments
I found a solution. I didn't have the |
Great catch! Thanks! |
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. |
@theres thanks! Will look into this |
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. |
Are there any real reasons why you'd want to have multiple zones with the same name? |
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. |
Same issue with my setup. After upgrading to 0.69.x. Could someone dive into it? No error logging |
I've reverted limitations on naming for zones configured through configuration.yaml |
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
: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):The text was updated successfully, but these errors were encountered: