#Hey, I am trying to place proximity
hazy hearth
No, but, you can use them in the UI for automations and such, but, they don't seem to fire off or trigger?
With that said, has the state of this changed? Maybe that is the reason, as I am using an older homeassistant Automation I created on a newer system.
Newly created
entity_id:
- zone.work
for:
hours: 0
minutes: 30
seconds: 0
id: arriving-work
below: 250```
vs
Old
- platform: numeric_state
entity_id:- proximity.work
for:
hours: 0
minutes: 30
seconds: 0
id: arriving-work
below: 250
- proximity.work
Becauase these are the errors I am fighting:
2024-02-05 21:21:38.105 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'Geofence - Roomba' trigger: In 'numeric_state' condition: entity proximity.work state 'not set' cannot be processed as a number
2024-02-05 21:21:52.122 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'Geofence - Roomba' trigger: In 'numeric_state' condition: entity proximity.work state 'not set' cannot be processed as a number
2024-02-05 21:21:52.123 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'Geofence - Roomba' trigger: In 'numeric_state' condition: entity proximity.work state 'not set' cannot be processed as a number
2024-02-05 21:22:00.107 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'websocket_api' trigger: In 'numeric_state' condition: entity proximity.work state 'not set' cannot be processed as a number
2024-02-05 21:22:00.118 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'websocket_api' trigger: In 'numeric_state' condition: entity proximity.work state 'not set' cannot be processed as a number
2024-02-05 21:22:22.129 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'Geofence - Roomba' trigger: In 'numeric_state' condition: entity proximity.work state 'not set' cannot be processed as a number
2024-02-05 21:22:22.130 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'Geofence - Roomba' trigger: In 'numeric_state' condition: entity proximity.work state 'not set' cannot be processed as a number
And then what I have in configuration.yaml:
home:
ignored_zones:
- work
- near_home
devices:
- device_tracker.phone
tolerance: 700
unit_of_measurement: m
near_home:
zone: near_home
devices:
- person.me
tolerance: 500
unit_of_measurement: m
work:
zone: work
devices:
- person.me
tolerance: 200
unit_of_measurement: m```
wet lagoonBOT
half reef
Look there at the entities, I suspect your problem is that they haven't updated yet
hazy hearth
That should update tomorrow when I leave/enter the zone, is that correct? Or do they need t be set first to be usable?\
half reef
They'll update when your device_tracker.phone or person.me updates location
hazy hearth
Hm, alright - I'll double check when I leave the house tomorrow then. Thank you. 🙂
hazy hearth
So fortunately, the proximity automations triggered, but the other automation I brought over (which I thought was at one point using proximity migrated to zones) did not.
I guess zones are less reliable? Or in that case - should I juse use the same setup with Proximity here?
half reef
Zones aren't less reliable, but it all depends on what you're using for location tracking and what your setup looks like
hazy hearth
I mean it's a pretty simple situation.
I have it pointed to the home zone, and then a "near home" zone that encompasses the home, and is also farther out.
Then the trigger is:
- platform: zone
entity_id: person.me
zone: zone.home
event: enter
- platform: zone
entity_id: person.me
zone: zone.near_home
event: enter
Which would have turned on the balcony lights
And whether the balcony lights turned on currently or not is not an issue (they were off to begin with) but the trigger didn't even fire at that point. I am guessing it should have tracked my phone since it is attached to the person entity.
half reef
Right, but the method you're using to report your location matters
There's countless options there
Which one are you using?
hazy hearth
I would have assumed my phone, but, honestly not sure. I don't recall enabling anything specific in the phone the last time.
GPS accuracy
100
Source
device_tracker.pixel_7_pro
I suppose the phone then
half reef
Well, you installed something on that unspecified phone
hazy hearth
When checking the location of the person entity
half reef
Ok, so ... probably the #android-archived app then?
hazy hearth
Yeah
Sorry - not thinking that deep into it, to me that is just a native part of Home Assistant 😅
half reef
Then you need to read the docs linked from that channel's topic for how to correctly configure the app for reporting the location when you enter/leave a zone
hazy hearth
Hm, alright... I thought that had already been done, as I see this in the person details history:
February 6, 2024
Was detected at home
18:14:42 - 3 hours ago
Was detected at Near Home
18:10:35 - 3 hours ago
Was detected at Work
14:04:46 - 7 hours ago
Was detected away
13:54:46 - 8 hours ago
Was detected at Work
13:39:20 - 8 hours ago
Was detected away
13:29:20 - 8 hours ago
Was detected at Work
09:27:51 - 12 hours ago
Was detected away
09:02:50 - 12 hours ago
Was detected at Near Home
09:00:35 - 13 hours ago
Doesn't mean you set it up with zone support
That just means it's reporting the location
hazy hearth
Ah, alright. Well... looking at #android-archived , I don't see a linked doc:
Support for Home Assistant Companion for Android (https://play.google.com/store/apps/details?id=io.homeassistant.companion.android) | iOS support in ios_and_mac | Development in devs_mobile_apps
The pinned messages? https://companion.home-assistant.io/
