Is there a reason for two ways to do this and have the data stored in two different places? Is this a migration to sunset zones in the configuration.yaml? Is there a calendar of events?
Inquiring minds want to know.
O.o
??
Do you have a link?
If you go to Configuration, Integrations, Zone configure, you will be presented with a screen prompting for name, lat, long, radius, passive/not. It is stored in /config/.storage/core.config_entries.
You can create the same zone in configuration.yaml i.e.
zone:
- name: Seascape
latitude: 29.242990
longitude: -94.870588
radius: 200
icon: mdi:map-marker
passive: false
in your configuration directory.
I have done both just to see what happens… they are both active.
So you can break up your configuration for organization. FYI next time, place your whole question in your post. Not half in the title half in the post.
No clue what you are talking about.
There is a workday component that contains holidays if that’s what you’re after:
1 Like
The second one will overwrite the first one in your configuration. Again, it’s just preference.
and horrible software protocol.
It’s open source. Feel free to contribute to it. We are currently in a transition period where the developers are focusing on making configuration changes in the UI which is something people have been bitching about wanting forever. Here you have a choice and are still bitching about it?
1 Like
What does that have to do with your question? Are you just trying to get a rise out of people? Seems like this software is too hard for you, and you’re coming here to vent but don’t know how to convey yourself.
If my pointing out that having two separate undocumented methods to store the same data in two separate places, can lead to confusion and potential issues has offended you… my apologies.
2 Likes
2 undocumented methods?
You sure about that?
The configuration page is still under heavy development. I can see there not being documentation on it yet…
Not at all. This out of place comment here is why you got the hate:
If you are referring to the documents, that has nothing to do with the software protocol. Software protocol refers to the communication between home assistant and it’s devices.
In summary:
Why are there two different files to store zones? - because
Is the moving to zones into /config/.storage/core.config_entries a migration path to follow? - no comment
Is there any documentation on this? - only the existing docs that don’t mention this new feature
If so is there a schedule on when we should migrate? - no
1 Like
Because the developers JUST recently started working on pushing toward the GUI configuration of editing your configuration and those configs are currently being stored in a new file path for the ‘entities registry’
there has been no statement on this yet, please read the release announcements to keep up.
not yet, because it isn’t complete.
again, there has been nothing on this because it is not finished.
1 Like
Thank you for your answers.
Wow, a proper question. Much better than
Still have no idea what a sunset zone is.
Sunsetting is a term used in the software biz regarding the retiring of a subroutine.
TIL. Been in software for 10 years, never heard that term. Might want to avoid that phrase when a main function of this software is to deal with the sun setting.
Would be super helpful to mention the new way of doing Zones (from integrations in the web interface) in the documentation of zones, currently there is no way to edit the new zones from gui and its not clear where they are stored. I know its subject to change, but the feature is out there so…
1 Like
They are store in the hidden directory \config\.storage\. I’m not sure which file because I don’t use the ‘new method’, in fact, I just upgraded from 0.75 to 0.80. So this whole hidden .storage folder is new to me.
If I were anyone stumbling on this thread, I would completely ignore the new method until there are ways to configure and edit zones. Again, that whole section of the UI is new and it will continue to expand. Everyone is going to need a little patience. Or if you are impatient, you could put in a PR and update the documentation yourself.
Will the zone editor in the GUI allow multiple zones to be defined?