Gary, thanks for the great reply…
So in your example “Driving” just means you’re away from home by a certain distance (not necessarily driving/moving).
Could I use the zone.phone_stationary in a similar fashion? I just wasn’t sure what other states there are with that other than “zoning”, which is what I appear to get when in a Zone.
When I add my iPhone I end up with
device_tracker.my_iphone
When the iOS app adds an integration, per the instructions I add a suffix. (eg gary_iphone and gary_iphone_2) Instead of adding a number I just add ic3
device_tracker.my_iphone_ic3
Which one of these should I be using in my automations?
You can use either, or both. One is coming from the iOS application on the phone. The other is coming from Find My Friends via iCloud. You should use whichever gives you the best resolution.
For me, my wife doesn’t want the HA iOS app on her phone (go figure), so for her I’m using the FmF. For youself, you could build a Bayesian Binary Switch that would combine the two sensors together with probabilities to improve accuracy.
I’ve started playing with these, but haven’t gotten it working to a state that I’m willing to rely on.
How do you do set it up without the app? Are you talking about the iosapp and fmf methods?
@WiFiNetGuy Yes you can remove the iOS integration and the IOS in configuration.yaml
See the dir_of_travel and travel_time attributes here. dir_of_travel is iffy when traveling short distances between polls. travel_time will have min (2min) or sec (15 sec) in the text which can be filtered out with another template sensor.
Use my_phone to eliminate false zone exits by the iOS app. More info here
@FutureTense @pickerin
If you don’t have the iOS app, you will not get zone enter/exit triggers. More info here
Is that the same thing as sensor.my_iphone_travel_time ? Regarding this and other attributes, where can I find documentation that tells me, for example what travel_time means? Is that in minutes or seconds?
So I was watching the map as my wife drove to work, and the updates on the map started for a bit then stopped until she entered her work zone, which then updated her position. Is there a setting I can change so the updates are constant, showing near real time location as long as she is moving at driving speeds without causing negative battery performance? I’m using FmF for the tracking method.
See the iCloud3 documentation Referenced in you last two posts. Check out the Attributes section for a description of the Attributes. See the Service Calls section for instructions on overriding the interval and setting it to a constant value. And yes, doing this may eat your battery.
The device name is added to the beginning of all sensors to associate the device with the sensor. Cheech out the Lovelace and automation examples in the docs.
Great work with iCloud3, big improvements especially with battery drainage!
One question though, which enitity should i use as device_tracker for my persons? I find no coordinates under any of the added entities?
Best regards,
Anton
It’s been a while since I tried this. Last time I think it was before iCloud3, but I found that it chewed the battery on all the tracked devices pretty bad. How is battery performance these days?
@antsve iCloud3 really tracks the device rather than the person associated with the device. The device name (I.e., gary_iphone) is added to the various sensor names created by iCloud3 so I guess that would be the way to track a person who is the user of the device.
I get that, but wouln’t that result in an entity wich holds the current gps-data such as log/lat? I can only find that information in zone.devicename_stationary which and that entity cant be assosiated as a device-tracker for any person-objects.
On another note it seemes that my wifes zone.[devicename]_stationary gives me lat 90, long 180. Is that something i have to do to get the real position? For my devices it works great! Can add that i track via famshr method.
Solved the issues by deleteing known_devices.yaml and rebooting, everythings working great thanks!
Hopefully this hasn’t already been covered, I didn’t see it on my scan through.
I have icloud3 setup using the FMF setup with a dummy non2FA account.
I’ve got the custom event log card.
Anyway, I’m curious about the picture badges.
My badges show the picture, but they don’t show any other information such as the zone or home.
Have I missed something ?
The stationary zone location is set when you haven’t moved for a specific amount of time (default is i-min) and the stationary zone is created. This location is picked up by the iOS app to issue a zone exit when you leave the location. The 90/180 are dummy values used to initialize the zone and to reset it so the iOS app won’t issue other exit notifications for other devices on the same account. The location lat/long is a device_tracker attribute.
@BruceH5200 Regarding the badge not showing the correct info-Check to see if sensor.devicename_badge is being created using developer_tools>states and what the value of it is. Make sure Lovelace is referencing that sensor.
If I don’t list a photo in the config:
I get a badge that shows “Home” and a state of Home.
attributes are:
entity_picture: null
friendly_name: Bruce
icon: 'mdi:shield-account'
If I add a jpg photo to the config, I get…
A badge that shows just a photo, but no info.
state is still “Home”
attributes are:
entity_picture: /local/bruce.jpg
friendly_name: Bruce
icon: 'mdi:shield-account
Am i misunderstanding what it is supposed to do?
I can use the “person” indicator to show an image with a tag line “Home”
Thanks.
Another question, how do I debug the Waze bit, as my Waze distances are blank?
Thanks,
Bruce.