How are zones handled when "location zone" is enabled?

Mobile Apps Home Assistant Companion for Android
1

I estabilished the zone around the location of my server, then I enabled “location zone” in the Android app, which is supposed to download the zones and only update the server about zone entering/exiting.

So far it seems to work fine, although I never specified that the location of the server would also be “home”, and I still get “home” and “not_home” states. But this is just a minor annoyance.

After this, I defined a different zone on the server. My problem is that I don’t get any state updates when I enter/leave this second zone.

At this point, I’m wondering if the app simply didn’t update its list of zones (in this case, when does it update?), or I’m completely misunderstanding how this is supposed to work.

2

the first zone you create is the Home Zone so you will indeed get home and not home status immediately

The list is updated upon app startup, so if you added more zones and teh app was currently running you’ll want to restart the app so it can pick up those changes.

3

Can this be changed somehow, after the fact?

Also, how do I set the radius of the zone around the server’s location? It’s read-only on the UI, and I couldn’t find in the config files where I could modify it.

4

Add to customize.yaml

zone.home:
  radius: 50
5

I made this change, but it’s not reflected on the map.

6

You restarted HA
radius zone

7

Of course I restarted HA.

$ grep -A 1 zone ./home-assistant/configuration.yaml
zone.home:
  radius: 20

state:

latitude: XXX
longitude: YYY
radius: 100
passive: false
persons:
  - ZZZ
editable: true
8

Wrong file. Needs to be customize.yaml

9

As I wrote above: are you adding it here?
/config/customize.yaml

10

Might be a good idea to read the docs too

11

This is the first time I ever see the file customize.yaml referenced. It’s not mentioned in the above linked docs either.

12

you dont have to use customzie.yaml but it can do similar thing

I recommend starting with the docs linked above, they cover your use case.

13

Okay, doing it the way it’s mentioned in the above docs did do the trick (and no customize.yaml was involved). Thanks for all the help!