oh, wow, had no idea icloud3 could be the cause of the freezing, I’d just begun to notice a pattern with someone coming home and HA going unresponsive then restarting. Thanks, will try.
Now running v3.0.17 - if this fixes my freezes I’ll be sooooo happy
I am using version 3.0.17 - rc10.4. No previous installs. HA is asking me to upgrade to v 2.4.7 and I have been ignoring this.
Is there a new / stable version 3 now available?
one more question please. my phone with icloud3 tracker seems to be quite delayed to detect leaving the home zone. Compared to the HA app on the same phone. Can this be adjusted?
INZONE Interval is what you want - i think it defaults to two hours…so when you are in a labeled zone, there is a 2 hour delay. I dropped mine down to 15min
Thanks @demockery - I have the inzone tracking working quite well now.
My biggest problem is with using the icloud GPS data to calculate distance/speed - I need to get this working somehow. Yesterday I was driving at 2200 km/h at one point. haha.
Interestingly the HA companion app works quite well for estimating speed but it is not updating enough.
I’m still hopeful that I will get this all working. Everything else is now in place. Just need quality data that is frequent and has correct fix time data with the GPS coordinates.
@jata
Check the MobileApp device assigned to the iCloud3 device. The MobileApp will trigger zone enter/exit triggers that are picked up by iCloud3 within 5-secs of when they happen.
Unless it is a Watch that does not have the Mobile App. When another device leaves the zone, it notifies the Watch and other devices without the Mobile App to do a locate that would take it out of the zone.
Another thing you can do is create an automation with a trigger using another way of leaving Home. An example is when it disconnects from your Home network. Then run the icloud3 Update service call with a locate command for the Watch. See the Service Call chapter in the iCloud3 Docs about this.
I was actually wondering if this was possible! There is so much good stuff packed into this integration…it’s a little overwhelming at times. Lol.
Unzip into the icloud3 directory and restart HA.
icloud3_v3.0.1b4.zip
Can iCloud3 be configured to include devices being tracked in the count for zone.home or is there an equivalent entity that iCloud3 offers with the current count of devices in the home zone?
@vaniello
The “count for zone.home” done best HA by looking at the lat/long of the device and seeing it that location is in the zone when the device Location is updated.
The zone results count on the Event Log when a device is located includes the number of devices in the different zones. iCloud3 does not include that number in any device o or sensor attributes.
The re is an option on the Configure Settings > Page 2 > Format Parameters screen what lets you select how the device tracker state is set - HA by the location or iCloud3 by the zone name. Try the different options and see if another one works better for you.
Is HA using the entries in the event log from a specific sensor in iCloud3? I had disabled a bunch of sensors because there was too much noise in my HA log so I probably need to reenable a sensor if that is what HA is looking for in the event log.
@vaniello
The count in zone.home (or another zone) is strictly HA and has nothing to do with iCloud3. It is figuring out the number of devices in a zone all by itself with info in the device_tracker state fields that are set to that zone. All miscounts are from HA.
Trying icloud3 tracker for the first time. Figured out how to not create statzon# entities. Now, I just need to figure out how to remove statzon1. Anyone knows???
@duceduc
V2 - Restart HA
V3 - It should be deleted automatically in about 15-minutes or restart HA
Longtime icloud3 user. I’m so thankful Gary. In the old native iCloud integration, I could initiate find my device on any of my icloud devices by calling “icloud.play_sound” service. Is there an equivalent capability in icloud3?
That did it, thank you!
I have just updated from v2 and v3 and after the first few minutes I am really impressed how good v3 already is and how well it is treating things; like displaying a notification to clear browser cache when I had updated the dashboard resources for the event log; or sorting out after a restart that first it created _2 entities for everything, as the previous ones from v2 were also still there. After a few restarts I now only have abandoned _2 ones, which I guess I can now manually delete.
I still need to dig further into some details and see if everything still works as before, but first impression:
Very professional integration 
I’m glad everything went smoothly. I’ll be releasing v3.0.3 in a few days as the official release.
Hi, I am on V3 since first install (so I didn’t use V2 at all) and I have noticed that I have _2 and _3 of all entities now. the _3 are the currently working, rest is N/A. But I definetely had only the original ones two days ago (I have battery sensor showed on AW so it stopped working). What could be the reason? I did reinitialization of the integration because my position was stuck (happens once after some time) but I reckon that should not create new entities.
