Thanks for the pointers! After looking through the logs, it looks like I had a typo in the device name.
Hi, I was attempting to install this vis HACS but get the following error when I check my configuration and HA doesnt allow me to restart it to get hte Integration properly installed.
Platform error device_tracker.icloud3 - Integration ‘icloud3’ not found.
Any advise…I dont want to “pull the power” incase HA does not restart again!
THanx & Merry Xmas!
After having icloud integration basically working, but being annoyed by daily warning e-mails that my icloud account was used, I stumbled over the hints to use this add-on. So I deinstalled icloud and set up icloud3 via HACS and the online guide.
My first look was mainly at the battery levels, here is my first issues:
For my own phone, the battery_level (from iOS companion app) and battery (from icloud3) sensor report the same battery level, but the icloud3 icon is always shown empty, while the other adjusts to the battery level. Is this not supported by icloud3?
For the phone of my wife, the battery sensor jumps between 0% and the correct battery level, those ups and downs can also be seen in the history. The battery_level sensor does not have this issue. I understood that the companion app would use an approximation/best of?
For the apple watch of my wife, the battery sensor does always only show 0%. It’s name fits the one in find my iPhone, where I can also see it incl. battery level. Any idea what is missing here?
- Changes to the battery icon are not supported. Maybe in the next release.
- iCloud3 just picks up the battery level from the iOS app and what is reported by Apple iCloud. I’m not sure if the battery level is reported for the watch.
iCloud3 v2.4.7 is available on HACS
This fixes the Waze ‘result’ error caused by a Waze server side variable name change. The time/distance data returned from Waze was changed from ‘result’ to ‘results’.
3 Likes
Is it possible to fire the device_tracker.icloud3_find_iphone_alert with a button in a lovelace card? Up to now it didn’t have any luck:
type: horizontal-stack
cards:
- type: button
tap_action:
action: call-service
service: device_tracker.icloud3_find_iphone_alert
service_data: {}
target: {}
entity: device_tracker.iPhone
battery levels mysteriously appear now.
I keep getting the following error with iCloud3:
Logger: homeassistant.components.device_tracker
Source: components/device_tracker/legacy.py:521
Integration: Localizzatore di dispositivi (documentation, issues)
First occurred: 00:46:03 (228 occurrences)
Last logged: 00:46:27
The see service is not supported for this entity device_tracker.xxxx
Any pointers on this would be appreciated.
I think the device_name is required in the service call.
- type: button
tap_action:
action: call-service
service: device_tracker.icloud3_find_iphone_alert
service_data: {device_name: xxxx}
target: {}
entity: device_tracker.iPhone
1 Like
@gcobb321
I changed the device name on the app as it suggested in the documentation but the error is still there
The updates of my wifes iPhone is very buggy, sometimes also of her Apple Watch.
We both have the iOS app, and while this reliably updates as soon as we come or leave home, sometimes even 30 minutes later icloud has still not updated its status, not even the app one.
So I mean the device tracker from the app shows that I am at home, but the icloud3 log still shows
Time iOS App iC3 Zone Interval Travel Distance
19:08:25 Away Away 1 hr 42 min 50.4 km
19:08:25 iOSApp state will be updated after iOSApp starts (+152 more times)
I don’t know what that means, the app has already sent its update successfully to home assistant (after driving home for 42 minutes, which icloud3 also did not recognize), just icloud3 does not recognize that the device is already at home.
Only really triggering location updates manually makes it recognize that the location is meanwhile home.
A second issue that often happens (in this case in parallel with the Apple Watch, but sometimes also the other way around the watch works fine, but in parallel the iPhone shows the same message):
Tracking Paused > Excessive Errors Encountered
• Old Location Errors-#25
• Discarded Updates-#43
---------------------------------------------------------------------------
Event Log > Actions > Resume Polling to restart
Resume polling does not change anything, the same error appears after a short time.
The “where is” app on the iPhone shows the correct locations, home assistant is also right, just icloud3 seems to have some issues here.
While I really like a lot of the features it has, unfortunately at the moment it is too unreliable for me to really use it. Any idea what is wrong here? The log entries especially when starting the service all look fine, no error message. This is also not a generic issue, sometimes it works well, but at least as often not.
Do you have a router integrated in your home assistant installation which also provides device trackers? I once had the problem that I disabled the router in home assistant, but the disabled integration nevertheless provided device tracker entities which were blocking the name…
the name configured for iCloud3 is iPhonePiero and the name on the phone is iPhonePiero and the name IOS App device is iPhonePiero_157
@pigeldi
Excessive errors like yours are often caused by having a gps_accuracy parameter that is too low that cause locations to be discarded and requested again. The time interval between the requests is increased on a sliding scale based on the old location counter and then polling will be shut down due to excessive errors. iCloud3 is the only app that takes poor gps accuracy into account, the others accept what the icloud location servers report.
I use a gps_accuracy of 65m. Additionally, the iOS App has a 100m zone distance and will report being in the zone when it gets within 100m of the zone. iCloud3 tries to take this into account but the gps_accuracy can cause a transaction to be discarded when it is actually in the zone.
Try increasing it and see what happens.
Thanks, it works like a charm!
I only partially get this.
You talk about the parameter gps_accuracy_threshold? According to the help, that is already 125m by default.