-
Notifications
You must be signed in to change notification settings - Fork 13
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
➤ Solution (Fixed in v3.1.4)-Cannot log into Apple Acct, 503 Error, 0 of 0 Devices Tracked #378
Comments
Here's a quote from an earlier post by gcobb321 related to your duplicate entities: The _2 suffix is added by HA, not iCloud3. HA does that when it finds the entity already exists and is being used when iCloud3 starts again. I found that they will be created if you do a reload iCloud3 service call while iCloud3 is also running. They might also be created by doing several integration adding-delete-add without restarting HA in between each one. From what I have seen, when HA starts, it reassigns the entity name iCloud3 uses without the _2 There has been no changes to any of that code since v3.0 was released last year. They may be created when the iCloud3 integration is deleted and then readded. Once the integration is added, deleting and readding will not solve any problems.
|
@cedricdelecole |
Hi - what exactly are the steps needed to "Reenable using the Family Sharing data source"? Thanks. |
@simondsmason |
I'm curious what your plans are in terms of the next release / code updates. I'm on 3.1.3 and I'm still logged in to iCloud and everything is still OK so I'm hesitant to roll back to a previous release - especially if a new one is on the horizon and I can just wait. |
ok, in that screen I see these screens but I don't see an option to enable iCloud/Family Sharing? Thanks. |
@simondsmason |
@tydalforce |
You are correct. I did not successfully roll back. I didn't think to check the version number and sure enough it is still reporting 3.1.3. Sorry about that. However, seeing your last note I will wait for updates that you are looking at that try both methods so this isn't necessary. Thanks. |
@cedricdelecole did you notice that the MobileApp in your Event Log shows 'NotUsed" ? This mirrors what I'm seeing also.. note that it never gets updated. What's more when I leave my home, the status of my location is not being tracked and automations are not being triggered. Is this something you are also seeing? |
I have no clue why ... I assume @gcobb321 knows more ;-) |
@bastero Have you verified the iCloud device tracker entity name generated by the companion app on your apple device matches the entity name being used by iCloud3? Is the companion app tracker configured as a data source? Are redundant, differently named (-2) device tracker entities present in your HA states listing? |
Thanks.. Q#1: Can you elaborate, where exactly do I find the device tracker entity name generated by the companion app to compare to the name being used by iCloud3 ? Perhaps the following from the event log may help. Q#2: Yes, the companion app tracker is configured as the source. Q#3: Yes, there are some entities with _2 device trackers |
Q#1: Look in your HA UI in the Developer Tools tab. Select States at the top of the page to view a listing of entities known to HA. Your looking for "device_tracker.iphoneexpress" You should have one configured by iCloud3 showing device configuration info spanning several sections, and a second, showing GPS coordinates and data. Q#2: After viewing device_tracker entities in HA, does the device_tracker entity name assigned as the companion app data source match the entity populated with GPS data? You'll want to rename the companion app device_tracker entity to distinguish it from the IC3 (iCloud3) tracking entity. Q#3: _2 entities indicates you've let HA create duplicate entities. This doesn't prevent IC3 or the companion app from tracking, it just makes assigning entities in your tracking card more confusing. I re-posted Gary's instructions for cleaning these from your installation earlier in this thread. Perhaps when you get things running correctly you can backup HA then clean up the duplicates. I see you are currently running _2 device trackers as your IC3 data sources. These should be fully populated with several sections of device configuration data. You can keep these as-is for now. |
Here's what the data source screen looks like on 3.0.5.9: Does the screen you're seeing match the one above? If not, we're on different versions. If the screens match, verify the Family Sharing List and Mobile App are checked, then return to the main menu and select iCloud3 Devices and click submit to open the Devices menu: As shown above, you should see the FamShr and MobApp device tracker entities listed nest to each data source. In my case the mobile app device tracer entity is gary_ma. IC3 prepends "device_tracker" to the iCloud device name which is why you have device_tracker.device_tracker.iphoneexpress1. If the device tracker entities don't match, you'll have to reconfigure so they do. |
Hey! Easy fix :-) We all miss the little things from time to time. |
@cedricdelecole I've run into the "Unknown error occurred" message also. I haven't discovered the cause, but I work around the issue by directly editing the IC3 configuration file. A quick check would be to view-only the configuration file located at /config/.storage/icould3. Check the data_source line in the "data": section:
If "mobapp" isn't listed, IC3 is configured to not use data from the Companion App. |
Downgraded to the 3.0.5.9 but even with a clean install I cannot login with iCloud. the prompt ask me for email and password, I did receive the 2 factor code screen but the interface on home assistant stay stuck with the spinning circle and never complete, asking me for the code. |
@crospa91 |
Same thing was happening to me. Eventually got a code. My charge percentage and charge state is still not updating though. Is this expected with the roll-back? |
Apple broke iCloud3 Again
At the end of October, Apple changed the method of validating passwords to use the Secure Remote Password method where a hash token is calculated using the password on the iCloud3 and the Apple side. Icy sends this hash token to Apple instead of the password and if they are the same value, the password is valid and the login process. This broke iCloud3 and a lot of other programs. iCloud3 v3.1 fixed this and could log into the Apple account again.
Apple has reverted to the old method of verifying passwords and broke iCloud3 again so it could no longer log into the account. Messages like the following are in the Event Log:
Revert iCloud3 Back to v3.0.5.9
Downgrading to v3.0.5.9 goes back to the old way of verifying the password and getters iCloud3 working again.
Do this:
1. Go to HACS.
2. Find iCloud3 or the iCloud3 Developer Edition if you are using that version
3. Choose redownload from menu
4. Choose the v3.0.5.9
5. Install like you normally do.
6. Restart HA
Then do this:
1. Reenable using the Family Sharing data source and Mobile App data source if you are using the Mobile App on the Configure > Data Sources-Apple Accts & MobApp screen
Then restart HA again
The text was updated successfully, but these errors were encountered: