@basteroiCloud3 v2.2.1a was just released to fix this issue. See the above release note for more information.
Thank you sir, I just saw it !!
Hi @gcobb321
Having finally found some time to wade though the logs I can see the raw API_FRIENDS.DATA returned. My email address is in the followers, but in the following section. There is only two entries there and then two locations.
I am not out of ideas, apart from creating a new apple id that I can use to be friends with everybody or not using fmf. Definately an Apple problem but I am not sure how to fix it
@Sibiu
The following section is what iCloud3 uses to extract the devices to be followed. Apple adds the device to that section when it accepts an invitation to be followed that it receives an invitation request is sent from the master account
I donāt see the new release in HACSā¦ Did update information still see 2.2.1
Absolutely, that is what I thought. But I cannot share with myself so cannot accept that invitation hence will never be in the following section, or am I still missing something?
I did not do a new GitHub release, I just updated the existing one.
āIf you have already updated to v2.2.1, open the HACS integration, search for iCloud3 and select reinstall. Or download the icloud3.zip file in the iCloud3 repository and unzip it to the iCloud3 directory.ā
Hi @gcobb321
Thanks for the update, Iām not sure if you are aware of this as an issue, but I am seeing a situation where the device_tracker is jumping in an out of a defined zone more often than in previous releases ( actually in previous releases this never happened).
Update: @gcobb321 fyi, Iām also seeing this on my iPhone and seems to be localized to iCloud3 location changing either from a defined zone or a stationary zone. The corresponding iOS app state is constant when this happens.
the āGā is probably the Stationary Zone icon. Can you export the Event Log from the Actions and send it to me so I can look at the triggers and what might have caused the phone to move to the stationary zone. [email protected].
Edit: could it be that the iOS app has her in the school zone when she was just outside of it and the iOS app did not pick it up and iCloud3 actually put her in a stationary zone where she really is?
Thanks Gary!, Iāve forwarded you the Event log.
Cheers
Hi @gcobb321 i have a couple of questions.
- do you think it will be posible to create a service to play sound like in HA official integration? This is very helpful for someone like me that loses phone every second
- my car is with me in the stationary zone however the description of the zone is not āStationaryā but enrico_iphone_stationary. How can i show stationary also for the car?
- That will never happen. There is already an iCloud3 service call that will send a notification to your phone that will cause an alert sound. See the ālost phoneā service call here.
- That might have been corrected in the v2.2.2 in the development area now.
@gcobb321many thanks for point 2.
For point 1, i see that the service device_tracker.icloud3_lost_iphone should be like Service icloud.lost_device.
Unfortunately this service makes the phone receive a notification via HA and play a short sound.
I was referring to Service icloud.play_sound, present in icloud integration. this service makes the phone ring until you reach the phone and press a button. phone rings even in mute mode. to me this would be very helpful!
iCloud3 v2.2.2rc1 is now available
iCloud3 now works with the Apple Verification ID Code and support 2-factor-authentication
This is significant update to iCloud3. It supports true 2fa verification using the 6-digit Apple ID Verification Code sent from Apple when you log into iCloud. Go here for more information about verifying your Apple account.
Download the zip file from the development-v2.2.2 directory here, unzip it into the icloud3 directory and restart HA.
When iCloud3 starts, you will get the standard Apple Login warning and the 6-digit Apple ID Verification Code notification. YOU WILL USE THAT 6-DIGIT CODE IN THE ID ENTRY SCREEN ON THE HA NOTIFICATIONS AREA.
Select the Verification Code entry window like you always have from the HA Notifications area and enter the 6-digit code. This will create the Trusted Device token like other apps and browsers. iCloud3 will then continue starting as it usually does.
Other changes:
Deleted parameter
display_zone_fname: True/False has been eliminated.
New Parameter:
display_zone_format: name/title/fname/zone, Default: name
This parameter indicates how the zone should be displayed in the device_tracker.[DEVICENAME] states field and on the Event Log. The zone is formatted as follows:
- name - A reformatted zone name. Examples: āthe_shoresā is displayed as āTheShoresā
- title - A reformatted zone name. Example: āthe_shoresā is displayed as āThe Shoresā
- fname - The zones Friendly Name. Example: āThe Shores Developmentā
- zone - The actual zone name is displayed. Example: āthe_shoresā is displayed as āthe_shoresā
Bug Fix (I think)
The sensor.[DEVICENAME_last_zone values should be correct.
I gonna try this one!!! Previous work goodā¦ Get sometimes the emails that I used the email to verify notificationā¦ But thatās OK.
What is the main big difference between this release and the previous one?
Itās the same. I just put the notification on the main iCloud3 forum to let others know about it. Before I only notified people that had opened issues.
Edit: I did do some code cleanup to remove debug code in pyicloud_ic3.py so go ahead and do the update if you want to.
1 Like
Running v2.2.2rc1.
Iāve successfully entered the verification code and everything is working fine. However, Iām getting a warning email from Apple every time iCloud3 connects to check location. Is that expected?
I think I prefer the v2.2.1method at the moment.
I have the same. I donāt care that to much. Now I donāt get all the time to revalidateā¦ that seems solved now 
@scotty1395
What tracking method are you using? Iām not getting any emails and I have bounced between fmf and famshr for the last 10-days.
Iām using famshr.