-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iCloud verifies, lists devices, but then says "disabled until Verification can be completed" and defaults to iOS tracking, 501 Error in HA Log #268
Comments
Same here, but HA doesn't report it unless you go in the logs. Looks like it started with HA 2023.6 |
It’s not HA but Apple. They removed FmF location data from being retrieved using a web service call. Remove the email address from the iCloud3 configuration for all of your devices. |
I don't have any email set up in my config_ic3.yaml config file though |
The configuration.yaml + config_ic3.yaml is the configuration so remove the email from that one. |
Same for me. In Stage 2b at step Family Sharing List devices that can be tracked all devices are found and marked with a check-mark.
is displayed and no tracking happens. The only way I could get it to work again, is to remove the call to |
This doesn't make any sense. The only email I have is the username in the device_tracker part of the configuration.yml, which is obviously required if you want to connect to apple API. Here is my config : configuration.yaml
config_ic3.yaml
|
The above note about remove the call to Change it to iCloud3 v3 is in the late beta stage that solves this issue and adds a lot of new features. It is a full Integration with all configuration done using configuration screens. Go here for more info and installation instructions. It’s still in beta because I’m adding a few tweaks and the docs are not complete. |
Just a note that you need to restart HA after making the edits to the file; using the "Restart iCloud3" option from the HA dashboard won't work. Confirming this also worked for me -- thank you! |
|
See the Issue Pinned to the top. Go here. Scroll to the bottom and look for the How to Solve this Problem item. |
Are you planning to merge v3 into this repo so it’s available as an update in HACS ? Or do we have to switch to the new repo ? |
I'm releasing beta 19.2 today which should become rc1 next week in the icl;oud3_v3 repository. I hope to merge it as a Prerelease with the base icloud3 repository within 2 weeks. |
@gcobb321 Does the iCloud3 V3 support tracking friends? I can see my own devices and my family devices, but not my friend. The configuration wizard does show this field: Is this completely removed by Apple, or is there some way to track a friend's device? After all they already gave consent to be tracked with the Find My app |
Apple took away the web service that provided the friends locations last May. As far as I know, no one has found a workaround or another Apple access point that provides the information. Now that iC3 is done and about ready for a general pre-release, I'll have some time to research this. But I don't have any hope I'll find a solution. |
Thanks for the quick reply. If you need any help, I'm available. I have time and programming experience, but no experience with the Apple web services, so it would be nice if you could point me in the general direction |
I was going to start with google and apple developer docs. Would appreciate the help |
@MrAlucardDante |
Version : 2.4.7
iPhone being tracked is owned by my iCloud Account.
Essentially as described in title:
Logs show:
Stage 1 : normal
Stage 2a : Lists iPhone with checkmark next to it.
Stage 2b : says "iCloud Account Authenticated (# 1), lists all of my devices + people in my FamShr, with the checkmark next to the tracked iphone, then "iCloud Alert > FmF or FamShr Tracking Method is disabled until Verification has been completed. iOS App Trackimg Method wil be used."
The rest proceeds as normal for iOS tracking afaik.
The 501 Error in the Logs is:
Thanks in advance and looking forward to upgrading to v3! :)
The text was updated successfully, but these errors were encountered: