-
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
iCloud3 v3, Release Candidate 2 - fails to load, bootstrap.py:531 #178
Comments
Are you using the iOS app and the mobile_app integration? Right now, that line looks like this. I’m running the same side version of HA. |
Yes, I am using the iOS app and the mobile_app integration. I changed the line to Still fails to start with error
Maybe this is obvious to you, but if I go into the Integrations menu and choose to Configure, I get an error too:
I will try to disable some of the other integrations and see if I can resolve it this way. The setup worked fine before upgrading to the RC2. |
I’d like to see your home_assistant.log and the icloud3_0.log files. Can’t you email them to geekstergary@gmail.com. Try reinstalling iCloud3 again. Either from HACS or unzipping the icloud3 zip file and restarting HA. |
Removing the dependency for "device_tracker" seems to have done the trick. By removing it from RC2 starts again and is working as before. I will email you the logs. |
Did you mean removing "mobile_app"? or "device_tracker"? I added "mobile_app" because HA runs the code through some type of verifier when creating a release. It kept coming up with "mobile_app" needed to be added as a dependency (which it is not) or an after_dependency (which is not needed by mee). thanks for the logs. That may tell something. |
I had to remove both mobile_app and device_tracker I hope you can figure out something from the logs. My config might just need cleaning up, it is getting old now with lots of upgrades over the years. At the same time, this will be the case for many others too, so I suppose it is good to gracefull handle such problems. |
And I'm running with both of them in the list. There must be some conflict somewhere and I hope the logs will help figure it out. Do you have a known_devices.yaml file? I'm reworking the code to remove any iCloud3 devices from it to preserve anything else that is in it. I think it's just a text file but I'm getting an HA error and want to verify the format. |
I do have a known_devices.yaml file
Each such device entry seems to be separated by one or more empty lines. |
I'm also seeing the same error. Happy to provide logs or other files if you need another set Home Assistant 2023.7.3 |
Also have problems with this version I'm reverting to the previous one |
@d-d
iCloud3 had an 'device_tracker' after_dependency in the manifest.json file which tells HA that iCloud3 has to be set up after the device_tracker. When the device_tracker failed, HA aborted iCloud3. I have removed those dependencies from the manifest.json. That HA failure to load iCloud3 caused another error later on when you opened the Devices & Services > iCloud3 Configure Settings since the configuration file had not been opened and loaded.
The real problem was #1 when HA failed to start the device_tracker and iCloud3. The manifest.json file is changed ot what it was in rc3 |
Here is a prelease of iCloud3 v3 rc3 with the fixes to your issues noted above. Download the zip file and unzip it into the iCloud3 directory. Let me know if you see anything else and I'll address it before the release. Thanks for testing it on your system. Change Log:
|
@gcobb321 sorry for the delay, I've only just been able to install the prerelease version. So far I can confirm it starts up fine with no errors but will let you know if anything else pops up |
@gcobb321 I can also confirm the prerelease starts up without issues on my system and tracking is working. I will let you know if there are issues later. |
I just posted an updated rc3. |
Upgraded to iCloud3 v3, Release Candidate 2
It fails to load
Home Assistant 2023.8.1
Supervisor 2023.08.1
Operating System 10.4
Frontend 20230802.0 - latest
The text was updated successfully, but these errors were encountered: