-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
Cloud Extractor unable to retrieve data #583
Comments
I don't think uploading has finished successfully |
Try now |
Version of HA or version of integration? |
Integration. Which was 2.2.1 for me. But even if I rollback further it's not working now. Like something changed in API. I tried to rollback 3 months back and it's not working anyway. |
|
I did back do 9.x edit: sorry I meant 2024.9.3 |
Checklist
The problem
Recently I've noticed that cloud extractor can't fetch map data from xiaomi cloud. I know it was working before updating to newest version but now it's not even if I rollback to previous version. Pretty much just wanted to check if anyone has the same problem or problem is only on my end.
What version of an integration has described problem?
2.2.3
What was the last working version of an integration?
No response
What vacuum model do you have problems with?
Viomi.vacuum.v8
What version of Home Assistant do you use?
2025.1.0
What type of installation are you running?
Home Assistant OS
Camera's configuration
Errors shown in the HA logs (if applicable)
2025-01-07 09:08:50.330 DEBUG (SyncWorker_13) [custom_components.xiaomi_cloud_map_extractor.camera] Logging in... 2025-01-07 09:08:50.761 DEBUG (SyncWorker_13) [custom_components.xiaomi_cloud_map_extractor.camera] Logged in 2025-01-07 09:08:50.761 DEBUG (SyncWorker_13) [custom_components.xiaomi_cloud_map_extractor.camera] Retrieving map from Xiaomi cloud 2025-01-07 09:08:51.024 WARNING (SyncWorker_13) [custom_components.xiaomi_cloud_map_extractor.camera] Unable to retrieve map data
Additional information
No response
The text was updated successfully, but these errors were encountered: