My initial question was just about why it works with iCloud component without 2FA bypass and not with iCloud3. I haven’t tried famshr because or the “only if no-2FA” thing, so I’m trying right now.
I’ve done the thing about renaming mobile app entity id because of conflict (iphone_s_adrien), but still “No devices to track.” after reboot. I think that’s because after all reboot I got a 2FA ask on my trusted devices but NO new notification in HA to put the 6 digits code.
Check the Trouble Shooting hints here to see why no devices were tracked.
The 6 digit code is not used by HA to authorize the device like it normally is with other apps. Instead an authorization code is entered from the notification panel on the HA sidebar and described here
I’ll reinstall the iCloud component and see if there are any changes I don’t know about that I could incorporate into iCloud3 regarding 2fa and the iCloud account access.
I already check the possible troubles with famshr and all is good (my apple credentials ofc, and the name of the device (“Adrien’s iPhone” > “adrien_s_iphone”, and that was the name of the iOS app entity id before I added a suffix).
I read the process about the authorization code too and that’s my issue here. I got an alert on my trusted devices but no notification in HA, so I can’t do this:
- Press the Notifications on your Home Assistant screen to open the Notification window. A window is displayed, listing the trusted devices associated with your account. It will list an number (0, 1, 2, etc.) next to the phone number that can receive the text message containing the 2-step authentication code number that is used to authenticate the computer running Home Assistant (your Raspberry Pi for example).
It seems like to same procedure as iCloud component (which is works fine for me), but not with iCloud3.
I don’t think it’s an authentication issue. You would get an authentication error message if it was.
I think it is a device name issue… The account is scanned when iCloud3 starts, matching the device name in the iCloud account with the one on the track_devices parameter. In no match is found, you get the error you have. Check the HA file or the iCloud3 Event Log for the device names that were found in the account.
The suffix is for the iOS app, not the iCloud account. With the device name in your message, Your track_devices parameter should be “adrien_s_iphone > otherparameters”.
Tips on naming the device is here
Event log info at startup is here
Ok, seems like “Adrien’s iPhone” (original name is iOS settings) need to be written “adrien_siphone” and not “adrien_s_iphone”.
This conduct to a different issue: I use the v2 iOS app which is named “adrien_s_iphone” and not “adrien_siphone” as iCloud3 detect, so iCloud3 will use v1 because of this difference.
Mobile app integration: 
Thanks for the help. I’ll tell you later if I have issues (notification on trusted devices) because of 2FA.
I have found, over the years and on multiple devices and computers, that the " 's " always makes device name assignment confusing and a crap shoot as to how different programs translate it. So my devices and computers just use a name and device type, e.g., gary_iphone, lillian_ipad, gary_pc.
The device name for iOS app v2 can be changed to any name you want. The suffix is added by the iOS app just to make it unique. You can change it to ‘adrien_siphone_v2’ and then it will be picked up by iCloud3 (assuming adrien_siphone is the device name).
Thanks, I was thinking that I cannot “completely” change to entity id for the app.
So after few hours with iCloud3 OK (famshr, I was at home), it sent a notification on my trusted devices every 2 hours (as written in doc). Maybe you should check if there has been significant change in iCloud component because I haven’t this with it (same account/device tracked).
I can’t get custom cards to work for the iCloud3 integration. I’ve got the following as a Manual Card:
entity: sensor.icloud3_event_log
icon: ‘mdi:information-outline’
type: ‘custom: icloud3-event-log-card’
And the following in my Raw Config:
And I’ve verified that in my www/custom_cards there is an icloud3 directory with the icloud3-event-log-card.js in it. But I still get “Custom element doesn’t exist: icloud3-event-log-card” error in the UI.
What else am I overlooking? Thank in advance for any help.
On my working installation there is no icloud3 sub-directory under www/custom_cards. Resource is:
- type: js
url: /local/custom_cards/icloud3-event-log-card.js?v=1.000
I understand. But since I have another custom card (Dark Sky Weather) then I created subdirs.
Even trying it without the subdir I get the same result. I know it appears that it isn’t in the right place, but I have really poured over the location and the file is there. But obviously something is amiss but I can’t see it.
My card config:
entity: sensor.icloud3_event_log
icon: 'mdi:information-outline'
title: iCloud Event Log
type: 'custom:icloud3-event-log-card'
No space between ‘custom:icloud3-event-log-card’
Thanks, GaryK. I noticed the space, too. But when I take the space out, as you have above, everything on that screen disappears. I have other cards on that screen (for lack of a better term), such as “outside”. So when I take out the space on the manual card, all other cards go away.
A little more info: when I take the space out of the manual card as you have, I get the following:
No visual editor available for: custom:icloud3-event-log-card
Just click on the upper portion of the edit window and you should be able to enter text. Lovelace can be a real bear to troubleshoot.
I’m sorry, I don’t understand.
By the way, I guess it should be obvious, but I’m not using a lovelace.yaml file. I’m just using the UI to make changes.
Yes. And if I save it, all other objects on that screen are gone.
Is it OK to have multiple entries under “resources” in my Raw Config? Here’s mine:
resources:
