Skip to content

iCloud3 v3, Release Candidate 3 (8/19/2023)

Compare
Choose a tag to compare
@gcobb321 gcobb321 released this 19 Aug 14:41
· 79 commits to main since this release

I think this will probably be the final Release Candidate in the iCloud3_v3 repository. The next step will be creating a pre-release in the main iCloud3 repository that will get picked up by HACS. Both the iCloud3 and iCloud3_v3 repositories will be maintained for a while. Any issues identified and fixed will continue to be released in iCloud3_v3 before being promoted to iCloud3.

Gary

Important Links

Installing using HACS - iCloud3 is not available on HACS unless you have set it up as a custom repository. See here for instructions on how to do that and then install it. If you just go to HACS and do the installation, you will be installing v2.4.7, not v3.
Manual Download and Install - Go to the iCloud3 Releases page here. Scroll down past the notes, then select Assets, then select icloud3.zip. Download the zip file and unzip it into the /config/custom_components/icloud3 directory. Then restart HA.
Migrating from v2.4._ - See here for instructions on migrating from from an older version.
iCloud3 v3 Documentation - It is still in process, does not include the latest updates to iCloud3 and can be found here

Change Log:

  1. Reverted the 'manifest.json' file to prevent iCloud3 from hanging on an HA startup if there is a problem starting some of the HA components.
  2. Configure Settings - Added a 'Restart HA, Reload iCloud3' to the Configure Settings > Actions list. You can now restart HA or reload only the iCloud3 component if the is a problem.
  3. Migration - Fixed some v2 to v3 configuration migration issues.
  4. Area - The device will be assigned to the 'Personal Device' Area when it is added or when iCloud3 starts if it is not assigned to one.
  5. Old Location - The status of both the iOS App and FamShr location is now checked when seeing if the old location status/counter should be reset as soon as the data is available. It was being reset only when the FamShr data was updated and later in the tracking process.