@eBoon
About the config_ic3.yaml file. iCloud3 has a problem and I’m looking into it to see what happened. Stay tuned. Trying to get the iosapp/icloud timing working first.
@tomdh76
But after those 12-sec, the iosapp device_tracker state gets updated and iCloud3 picks it up and iC3 goes from not set to Home. Is that correct or does it stay not set for a long time?
How are you all creating dummy accounts without 2FA? I just created a brand new one and 2FA was turned on automatically, and cannot seem to be removed.
Yes the iosapp device-tracker goes after those seconds from not set to home. Yesterday I saw that the icloud3 was set to home at that time already! If I now restart HA I see that the device ios tracker was already set to home and the IC3 also at home. So probably nothing to further follow-up i think?
@blhoward2
If I remember correctly, accounts created on a computer do not have 2fa on by default. In any case, iCloud3 v2.2.0 supports 2fa accounts. You will find it in the ICloud3 GitHub Release Candidate directory. Scroll back a few posts for info on the latest version.
Thanks, according to Apple’s website on two-factor it looks like they do. And the one I created in a web browser certainly does. I’ve downloaded the release candidate…am I supposed to be prompted to enter the code somewhere or will it just not re-prompt after the first time it pops up?
Thanks, but I’ve never seen a pop-up and I verified that my pop-up blocker is disabled.
Edit: After restarting like 8 times I finally got a notification and could text a code.
I keep getting an error that’s throwing
The see service is not supported for this entity device_tracker.xxxxxxxxxxx
There were 1426 occurrences that occurred in just 3 minutes and it quickly climbs up into the 10000’s fast. What does it mean?
Release Candidate 11e is available
Download the installation zip file here
Full Change Log is here
v2.2.0 Documentation is here
Installation instructions are here
What Changed:
- The iOS App state will be updated when it becomes available after the initial iCloud locate.
- Fixed a bug related to the Waze Region not being decoded correctly. Example: The valid Europe code is EU but iCloud3 was using a validation code ‘eu’ causing it to default to US.
- Added back the max_interval parameter. If the interval is greater than the max_interval and you are not in a zone, the interval is set to the max_interval. This is useful if you are a far from Home and want to refresh your location data on a shorter interval than one based on the Waze travel time. Default: ‘4 hrs’
- Changed the nature of the config_ic3.yaml file handling.
- If the file name is fully qualified and contains the directory and filename (it have to has a ‘/’), that is used:
config_ic3_file_name: /config/config_ic3_gary.yaml - If the filename is found in /config/custom_components/icloud3 directory, that file is used:
config_ic3_file_name: config_ic3_gary.yamland this file exists in the /config/custom_components /icloud3 directory - If the filename is found in the /config directory, that file is used:
config_ic3_file_name: config_ic3_gary.yamland this file does not exist in the /config//custom_components/icloud3 directory but is in the /config directory - Otherwise a file not found error is added to the Event Log.
- If the file name is fully qualified and contains the directory and filename (it have to has a ‘/’), that is used:
I believe the see service was called from an ic3 script at some point. Check your scripts.
Thanks, Gary - I can confirm that the config_ic3_file_name is working correctly and as expected in this latest release.
I don’t actually have any scripts running. Here’s the entire error:
Logger: homeassistant.components.device_tracker
Source: components/device_tracker/legacy.py:184
Integration: Device tracker (documentation,issues)
First occurred: 8:44:49 PM (36432 occurrences)
Last logged: 10:11:19 PM
The see service is not supported for this entity device_tracker.jeremy_iphone
The see service is not supported for this entity device_tracker.jamie_iphone
@jamieboy05
What version of HA, iCloud3, and the iOS app are you running?
Are you tracking devices other than Jeremy_iphone? Do they work without generating the error?
When you restart HA, iCloud3 writes an entry in the HA log file that itit’s starting. Does that line have an not that legacy mode will be used?
Have you installed the iCloud3 Release Candidates?
Running RC11e, after exiting a zone the update interval changes from 2 hours to 4 hours. It stays on 4 hours until a zone is entered again where it changes back to 2 hours.
@scotty1395
I just added a max_interval that defaults to 4 hrs when not in a zone and it sounds like a problem with that. It is suppose to check the calculated interval when not in a zone and if the new interval is greater than the max_intetval, it sets it to the max_interval.
Put max_interval: ‘’ in the config file to turn it off.
Are you a long way from Home by any chance that would create an interval > 4 hrs? Didn’t think so.
Thanks Gary. Will give that a go.
No, only about 10km from home at the time.
By the way, the below fix resolved my earlier issue. Seems to be working well catching the app updates when the update trigger doesn’t change. Thank you!
Release Candidate 11f is available
Download the installation zip file here
Full Change Log is here
v2.2.0 Documentation is here
Installation instructions are here
Changes in this Release Candidate:
- Fixed a bug introduced in rc11e resulting in a 4 hrs Interval when not in a zone. This was caused by testing if the max_interval > interval when it should been interval > max_interval. If the max_interval is used, the Interval that is displayed will be max_interval(interval), e.g., ‘4 hrs(7.5 hrs)’.
Man, those updates keep coming… I can’t keep up! lol
Thanks Gary. Your integration is an amazing piece for HA.
Is it expected that 11f thinks that it is 11e ?