Skip to content

iCloud3 v3, Beta 11, 2/5/2023

Pre-release
Pre-release
Compare
Choose a tag to compare
@gcobb321 gcobb321 released this 05 Feb 22:14
· 210 commits to main since this release

Beta 11 (2/5/2023)

This update fixes some problems, adds a few new features and makes some minor changes, The highlights are:

  • Each device can customize it's Stationary Zone name.
  • Changed the way inprocess device updates are handled to be able to break out of potential iC3 hang up it a device never indicated that it's update has been completed. Everything is now reset after a 3-minute wait.
  • The way the NextUpdateTime was going to break in the 2023.03 version of HA. Now it won't.
  • Added a screen that lets you change the order the devices are processed and listed on the Event Log.
  • Fixed a problem with the latitude/longitude and battery going to 0 momentarily during startup.
  • And other stuff.

Download from the Release page here. Select Assets, then select icloud3-beta-#.zip.
iCloud3 v3 Documentation can be found here
All of the Change Logs can be found here

Change Log: Beta 11 - 2/5/2023

  1. Added a Stationary Zone name parameter on the Update iCloud3 Devices parameter screen - Each device
    can now have it's own Stationary Zone friendly name. This overrides the generic friendly name on the
    Special Zones screen for the Stationary Zone.
    NOTE: A BROWSER REFRESH WILL/MAY BE NEEDED IF THE FIELD DOES NOT DISPLAY

    The default name is 'Stationary'. It can be customized on the Special Zones screen to [name]StatZone
    (GarStatZone, LilStatZone). It can now be set by device (GaryZone, LillianZone).

  2. Fixed a problem where 'Stationary' was always used for the device_tracker state for a Stationary Zone
    instead of the friendly name that was set up on the Special Zones/Stationary Zone screen. Also set the
    Stationary Zone state to 0 when it was created so the person counter would work (maybe).

  3. Because of the way iCloud location data is processed, Device updates are handled serially. Only one
    Device can be updated at a time, the next in line must wait until the previous one is complete. The
    method used to control this process was changed to ensure iCloud3 tracking would not hang in up waiting
    for one device update to finish when an unknown error occurred or it was taking a very long time to
    get location data from the iCloud account. Now, everything is reset if one device has been in an
    update process for more than 3-minutes.
    [LET ME KNOW IF YOU HAVE ANY PROBLEMS WHERE TRACKING STOPS FOR ALL DEVICES OR ICLOUD3 SEEMS TO BE HUNG UP]

  4. Changed the way the Next Update Time is displayed when the update will be done in 90-secs. For example,
    the time was formatted as '9:35:15a -45s' indicating the update would be done in 45-secs. This will
    break in a future HA release. Now, only the time until the next update will be displayed (45 secs)
    when the update will be done within 90-seconds.

  5. Added a new configuration screen to change the order the devices are tracked and displayed on the
    Event Log. They are processed in the order they were first added to iCloud3 and listed on the iCloud3
    Devices List screen. This new screen lets you change this order. Select Change Device Order on the
    iCloud3 Devices List or the Event Log Parameters screens.

  6. If there is an error reading the configuration file when iCloud3 starts, the backup configuration file
    is read and the configuration file with the error is overwritten. The configuration file with the
    error is now saved with a timestamp before it is overwritten.

  7. Fixed a problem where the latitude/longitude values for the Device were not being restored when iCloud3
    was starting. The latitude/longitude was set to 0/0 rather than the last known position, putting it in
    Atlantic Ocean on the equator off the coast of Africa on the HA map until the device's location was
    updated

  8. Fixed the problem where the battery would go from a valye to 0 and back to the value during startup.
    Again. Really, I think I have it this time, no battery = 0 in my debug logs.