Yes. I forgot to change the internal version number.
No problem.
Iām really liking iCloud3 so far - thank you for all of your hard work! One question: I also have Life360 configured and I am more times than not seeing Life360 react much quicker than iCloud3 to zone changes - I especially notice the home zone exits and enters seem to be as much as a minute or two quicker with Life360. Is that to be expected?
My goal is to stop using Life360 and just use iCloud3ā¦
Thank you again for all of your hard work and your responsiveness - I donāt know how you can keep up with all the requests for help - you are incredibly patient!
@eBoon
iCloud3 relies on the iOS App for zone enter/exit triggers and monitors any iOS App state changes/triggers on a 5-second cycle. I have to assume that the delays in reacting to zone changes are due to the iOS App.
The iCloud3 has an update service call that lets you change the zone using an automation or script. Maybe you could create an automation that fires when Life360 detects a zone change. This is explained in the iCloud3 docs here and might do what you want.
1 Like
This is a fantastic idea - Iāll give it a go!
Thank you again for all of your efforts!
I authenticate through the regular iCloud integration to get icloud3 to work.
Is there anyway to use an Apple Watch as a device_tracker without constantly polling it? Looking at the logs it seems that the HA app on the Watch doesnāt send zone changes? Any idea what this does to battery life on the Watch?
@avd706
ICloud3 v2.2.0 that has not been released supports 2fa and can be installed by downloading the Release Candidate zip file from the iCloud3 GitHub repository. Scroll up a few pages to the Release Candidate 11f post for installation instructions and more information.
Thatās what Iām trying to say.
With a clean install of d and upgrading to f it didnāt negotiate the 2fa but did piggyback if I authenticated on the built in iCloud integration.
@avd706
The entry of the verification code is not related to updating iCloud3 to a new version or doing a clean install. It is controlled by the cookie file in the .storage/icloud directory. The file name is the icloud account email address without any punctuation. The cookie has an entry in one of the lines with the authentication expiration date. Apple will ask for the verification code when that date is reached. If you delete the cookie file, the code is requested immediately by iCloud3 or by the iCloud integration.
iCloud3 will not ask for the code when the iCloud integration is installed since they both use the same cookie file with the same authentication information.
First: I need to go on record to state that this whole integration is awesome and works greatā¦
What I tried to explain above is if I install icloud3 beta on a fresh HA instal, it wonāt negotiate the 2fa. The kluge I use is to authenticate my iPhone with iCloud integration.
If I donāt do that, icloud3 seems to work but I wonāt get location.
Iāve tried to find a resolution to the constant (every half-hour) 2FA iCloud prompts to my device. But Iām unable to find one. If I specify fmshr for my configuration, I get my devices tracked but keep getting the 2FA āthingā. If I specify fmf for my configuration, I continue to get āno devices to trackā. Iāve tried to follow the part of the instructions that address that error, back in 2019 I think, but canāt get it to work.
Are you on 2.2.0 beta RC11f? or 2.1?
Because 2.1 has issues with 2fa and will pop up every half hour. 2.2.0 beta fixes that.
Iām at 2.1. Iāll install 2.2 and check it out. I believe itās as simple as copying over the changed files into the config folder, right?
Yep, just scroll up a couple of post. Gary has posted version rc11f earlier this week. All links for repo, and update instructions are in his post.
Thanks, Alex.
Iām still getting hammered with 2FA approvals every 30 min.
@WiFiNetGuy
You probably have not gone through the account verification process. Do you have an orange dot next to the Notifications area on the HA Sidebar? If yes, open the Notifications and start the verify process by selecting the trusted device that will get the 6 digit code. If no, you want to rename the iCloud cookie file in the /config/.storage/icloud directory. And restart HA. iCloud3 will start the verification process after it starts. The cookie fileās name is the iCloud account email without the punctuation.
Go to The v2.2.0 docs here for more information.
Release Candidate 11g is available
Download the installation zip file here
Full Change Log is here
v2.2.0 Documentation is here
Installation instructions are here
Changes:
- The Event Log will display the first 10 letters of the iOS State and iC3 Zone names to prevent formating errors.
- The Stationary Zone is now set to a passive state when it is at itās base location to try to prevent the iOS App from moving a phone into it. Itās icon will no longer show on the map when it is at itās base location 1km north of the Home zone.
- Reverted the Stationary Zoneās friendly name to using the complete zone name rather than an abbreviation using the first 3 letters of the devcename (gary_iphone_stationary instead of gar:stationary). This was creating a problem when the first three letters of multiple devices being tracked are the same.
2 Likes
Thanks, Gary. Iāve renamed the cookie file as you suggested. I then restarted HA. Upon restart, I got the 2FA challenge, which I selected Allow and OK. However, I am never presented with a configuration in the Notification area.