gcobb321 / icloud3_v3

iCloud3 v3, Development Version - This Repo/Version is used for development and testing of new and updated features. It is not the official release of iCloud3 v3, .
MIT License
169 stars 13 forks source link

iCloud3 v3.1 ➤ A new release of iCloud3 v3 is available - 11/4/2024 #349

Open gcobb321 opened 2 weeks ago

gcobb321 commented 2 weeks ago

This update MUST be installed to be able to log into the Apple Account after November 1, 2024.

Change Log - v3.1

  1. APPLE ACCOUNT LOGIN (Fixed) - Apple changed the method of logging into the Apple Account to use Secure Remote Password verification where a hash-key is calculated from the password by both iCloud3 and Apple. The hash-key, instead of the password, is sent over the internet. Apple then compares the hash-key sent by iCloud3 to it's hash-key to determine the validity of the password. Note: In a few cases, the hash-key algorithm used by iCloud3 may not be the same as Apple for a valid password and you will need to change your password.
  2. MULTIPLE APPLE ACCOUNTS (New) - iCloud3 now supports tracking devices from more than one Apple Account. The accounts are setup on the 'Configuration > Data Sources' screen and devices can be tracked from any apple account and the d if the device is set up as an account owners deviceThe Primary account belongs to the person with the main Family Sharing list as it always has. Secondary accounts can also be configured and devices from those accounts can be tracked. The Apple Account for the specific iCloud3 device is selected on the Update Devices screen as it always has.
  3. FAMSHR - Everything called FamShr has been changed to iCloud.
  4. THE APPLE ACCOUNT (Improved) - Logging into the Apple Account is now started before the beginning the HA process that creates the device_tracker and sensor entities. Both processes now run concurrently, eliminating (or reducing) any delays waiting for the Apple Account device data to be returned. The result is iCloud3 starts up faster.
  5. APPLE ACCOUNT & MOBILE APP DEVICE ASSIGNMENT (Improved) - The results of matching the Apple Account iCloud devices and the Mobile App devices during startup are displayed in the Event Log. This has been simplified and is easier to read.
  6. CONFIGURATION SCREENS (Improved) -
    • Saving changes is faster.
    • The iCloud3 Devices screen indicates if there is a problem with the iCloud or Mobile App device selection.
    • Update Devices screen - Impoved selection of Apple Account and Mobile App devices.
  7. MISSING APPLE ACCOUNT DEVICES (Improved) - Sometimes, an iCloud device's information is not returned from iCloud when iCloud3 starts. The error recovery and data request retry routines have been rewritten to only retry setting up devices with the error. This greatly simplifies and reduces the steps needed to retrieve the data from iCloud.
  8. WAZE & WAZE HISTORY (Improved) - Improved the error checking, added retry on error conditions and updated the History database recalculation routines to better support concurrent operations.
  9. APPLE ACCOUNT DEVICE STARTUP ERRORS (Enhanced) - Improved the handling and reporting duplicate and missing Apple Account devices. 8 STARTING/RESTARTING ICLOUD3 -
    • Device Sensors (Fixed) - They were being reinitialized when Restarting iCloud3 when they shouldn't have been.
    • Mobile App entities (Fixed) - They are no longer being reinitialized when iCloud3 is restarted on a configuration change or Event Log restart request. This includes the device_tracker, battery, trigger and notify entities..
    • Improved messaging and fixed miscellaneous bugs
momab commented 2 weeks ago

Hi, @gcobb321,

thank you very much for the incredible work! As I had issues with the migration to the latest update, I removed it completely and tried to set it up from scratch, but the documentation seems to still show the v2 integration.

gcobb321 commented 2 weeks ago

@momab The docs linked to in the (?) on the Event Log are for v3.0. V3.1 was released early to deal with the password problem Apple created 2-weeks ago. It will catch up in the near future. Right now, the priority is not on the docs.