@viesse
Event Log > Action > Locate this device using iCloud will send a location request to Apple and update it’s location.
See here for info in the iCloud User Guide about using an Action (service Call) to locate a device using an automation
Thank you for your help. In your opinion, what problems could an automation that send a location request to Apple and update it’s location cause?
Tank you 
a few days ago I thought I had seen the possibility of having the 2 views in a single view, was I wrong? It’s possible
@viesse I don’t understand what your are asking about when you talk about views.
If it is about the dashboard and how the screens are configured, you can do anything you want that meets your needs and makes sense to you. All I did was provide an example of what my configuration looks like.
Thanking you for your valuable advice
I wonder if it is possible to reduce the interval between position polling requests. Actually 5 min’ .Thanks
But the fixed interval cannot be set < 3
@viesse
That’s right. It will hammer the battery and Apple typically will be returning the previous location data if it is too short. When iC3 gets close to Home, the polling interval is reduced to a 15-sec interval.
Is it safe to upgrade now?
I’m on version v3.0.5.9 which is what I rolled back to after the whole Apple auth change thing that broke my install but I get update notifications and we’re up to v3.1.4.3 version now.
@Calzor_Suzay
Apple went with the Secure Remote Password which broke everything and has rolled back to the way it was in v3.0.5.9. v3.1.4.4 uses that method of authentication. There have been other features added and, as far as I know, nothing to prevent you from getting current. You should be fine.
Hold off for a minute. I just saw a spelling mistake on a field that generated an error that I am updating in a few minutes. Wait for v3.1.4.4
v3.1.4.4 is now available
Hmm stuck…
I got this error
Apple Acct is not selected as a data source, username/password are setup
and no matter what I seem to do/select I then get
famshr is not a valid option
Went back to v3.0.5.9 and it seems happy once again
@Calzor_Suzay
After you reinstall v3.1.4.4, The field name changed in v3.1.
Edit the config/.storage/icloud3/configuration file.
Changes the data_source parameter. It will be around line 41.
From:
“data_source": “mobappp,famshr”
To:
“data_source”: “iCloud,MobApp”
Hi, I am sorry if this topic has been discussed, I looked for solution but need to turn to more experienced of you. I have following automation to trigger when my wife is approaching home:
This shall trigger some other reactions (for now test version triggers just a message), but the trigger does not work, any suggestion of n error on my side would be appreciated.
Many thanks. J
@JurekCh1968
See Sample automations and Scripts in the iCloud3 Docs here for an example off an automation that does that.
You want to use the Home Distance state value, not the attribute for the distance trigger.
Thank you Gary. Would that mean I need to use „numeric value of another entity” in GUI? Do I understand that well? J
EDIT: I figured it out I guess, thanks to your instruction I have created scripts and automations, now will try them out 
Ok thanks, it looks to be working now.
I’ll keep an eye on it
@JurekCh1968
You may have figured it out but you want to use the home distance state value, not the max_distance attribute in the condition statement.
conditions:
- condition: numeric_state
entity_id: sensor.jurek_iphone_home_distance
attribute: max_distance. <—— REMOVE THIS LINE
above: 1
Yes Gary, thanks a lot, I have got it working. I am going to experiment with the tool, but seems to be quite useful. Many thanks again. J.