Beta 9
This update fixes some problems, adds a new feature dealing with sensors and makes some minor changes, The highlights are:
- Fixed a problem with the zone's HA name was not being used for zone sensors, leading to problems with the HA person entity,
- Fixed some problems with the battery level and status not being reported correctly or updated in a timely manner.
- Fixed a problem where nearby devices could loop back to themselves, causing iCloud3 to hang and stop tracking devices.
- Fixed several problems calling the iCloud3 update service.
- Alert messages are not summarized at the end of the startup process to make them less likely to be missed.
- Cleaned up some code and simplified messages in the Event Log (Requires a browser refresh on all devices).
- Added a screen on the Sensor configuration (Exclude Sensor) to select specific sensor entities that should not be created. This lets you override the normal sensor entity creation process. For example, you normally create a battery level/status sensor for all devices. You can now not create the battery sensor for a device that only uses FmF for tracking that does not report battery information.
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:
- Fixed a problem selecting several of the Actions from the Configurator.
- Fixed a problem where the zone was not being displayed in the _badge sensor and the zone's
friendly name was not being displayed on the Event Log (and other places) correctly. - Added the Battery Level to the Info sensor for the device. Also fixed a problem getting the
battery level from the iOS App when the iOS App was reporting a 'not_set' value and reworked the
reporting of changes to the battery status (charging, not charging, etc). - Fixed a problem with the v2 --> v3 configuration migration with a message ha_country_code not
found. - Fixed another problem determing if a near by device's tracking results can be used that was causing
iCloud3 to hang and stop tracking all devices. The problem was caused by a circular loop where
A > B > C > D > B > C > D etc. The A, B, C and D are devices that are scanned in sequence to see
if they are near by and could be used. A check is made, following the path of devices that are
already being used, trying to find the end. In this case, the end did not exist and iCloud3 died.
An additional timer check was added to stop liiking after 5-secs. - Added a code to the Near By devices that are not eligible to explain the reason it is not eligible.
(a-GPS Accuracy, lb-Would Loop Back to itself, sz-Stationary Zone) - Fixed a problem calling the iCloud3 update service with the 'device_name' parameter,
- Added the ability to exclude a specific device sensor from being created when iCloud3 started.
Select Exclude Sensors from the Configurator > Sensors screen, then select the actual sensor to
be excluded. A Filter can be used to limit the sensors displayed and the Excluded Devices are
displayed on the Sensors and Exclude Sensors screen. An HA restart is required to complete
the process. - Fixed a couple of problems with the iCloud Account interface (pyicloud_ic3).
- The Alert messages generated when iCloud3 is starting are redisplayed in the Event Log when
the startup process has completed. This summarizes all alerts in one place to help prevent
then from being missed. - Event Log:
1. Changed the Event Log to better indicate when Debug & Rawdata logging are on. The Debug
level is now displayed in the tracking results header area in the time field. This also
shows when it was turned on and off.
2. Reordered some of the Action items.
3. Changed some Event Log messages for clarity.
4. Cleaned up some code.
REQUIRES A BROWSER REFRESH ON ALL DEVICES