search

PiotrMachowski / Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor

This custom integration provides a way to present a live view of a map for Xiaomi (Roborock/Viomi/Roidmi/Dreame) vacuums without a need for rooting.
MIT License
1.12k stars 121 forks source link

Error displaying the map #540

Open GeorgePatsias opened 1 week ago

GeorgePatsias commented 1 week ago

Checklist

The problem

I have problem showing the map. Previously was working ok but a day after having problems. Check images attached. Also removed and cleared the intergrations and added it again. The configurations - creds are ok.

What version of an integration has described problem?

v2.2.1

What was the last working version of an integration?

No response

What vacuum model do you have problems with?

vacuum.viomi_v8_abb6_robot_cleaner

What version of Home Assistant do you use?

core-2024.6.4

What type of installation are you running?

Home Assistant OS

Camera's configuration

camera:
  - platform: xiaomi_cloud_map_extractor
    host: !secret xiaomi_vacuum_host
    token: !secret xiaomi_vacuum_token
    username: !secret xiaomi_cloud_username
    password: !secret xiaomi_cloud_password
    country: "de"
    draw: ["all"]
    attributes:
      - calibration_points

Errors shown in the HA logs (if applicable)

This error originated from a custom integration.

Logger: custom_components.xiaomi_cloud_map_extractor.camera
Source: custom_components/xiaomi_cloud_map_extractor/camera.py:356
integration: xiaomi_cloud_map_extractor (documentation, issues)
First occurred: 00:09:51 (103 occurrences)
Last logged: 00:18:20

Unable to retrieve map data

Additional information

Screenshot 2024-07-03 001424 Screenshot 2024-07-03 001449 Screenshot 2024-07-03 001516

kdober commented 12 hours ago

Hi, there are probably other 'issues' open about this. Very likely you get banned temporarely from the cloud servers due to too many requests. try changing the update frequency or use some of the blueprints that were made to query the map when actually using the vaccum and not so frequenly when it is docked. Haven't solved this on my side yet. Still testing...