Xiaomi Cloud Vacuum Map Extractor

3_14 · July 7, 2021, 8:01am

You have to add trimming to your config

Takaszi · July 7, 2021, 8:10am

Sorry, I’m new to these bricks and found nothing like that in the developer tools

For me it looks like this:

access_token: xxxxx
calibration_points:

vacuum:
x: 0
‘y’: 0
map:
x: 400
‘y’: 399
vacuum:
x: 1
‘y’: 0
map:
x: 420
‘y’: 399
vacuum:
x: 0
‘y’: 1
map:
x: 400
‘y’: 379
model: viomi.vacuum.v8
used_api: viomi
friendly_name: Xiaomi Cloud Map Extractor
entity_picture:> -
/api/camera_proxy/camera.xiaomi_cloud_map_extractor?
token = xxxx
supported_features: 1

There are no such entries as below

trim map false 0
Configure the map triming.
Each crop direction is a percentage: a value of 25 means that a quarter of the image size is cropped within that dimension. Available buttons: [left, right, up, down]

3_14 · July 7, 2021, 8:13am

It’s not in dev tools, but in camera’s configuration in yaml. Here you have an example usage of trimming

Takaszi · July 7, 2021, 8:54am

Well, I have a request, another one for a freshman. What the notation / syntax should look like. I’m plugging it and it’s still wrong.

3_14 · July 7, 2021, 9:01am

These values should be correct for your map:

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
    draw: ['all']
    attributes:
      - calibration_points  
    map_transformation:
      scale: 2
      trim:
        top: 45
        bottom: 30
        left: 35
        right: 35

Takaszi · July 7, 2021, 9:13am

Oh yes, it’s perfect now. I will analyze your entry and see if I can handle further modifications. Thank you very much.

3_14 · July 8, 2021, 10:50am

@gersilex Can you try running version from this branch with debug logs?

Btw, I forgot to mention that @andreasc has solved the problem by providing a correct token.

gersilex · July 8, 2021, 11:55am

With pleasure. It yields the “empy (zero-bytes) image” from my previous reply.

With this configuration

camera:
  - name: Simple Camera
    platform: xiaomi_cloud_map_extractor
    host: scruffy.nest.de
    token: !secret xiaomi_vacuum_token
    username: !secret xiaomi_cloud_username
    password: !secret xiaomi_cloud_password
    country: de

it prints these logs after a restart and those continue in the same interval:

2021-07-08 12:28:54 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration google_home which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-08 12:28:54 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration garbage_collection which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-08 12:28:54 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration presence_simulation which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-08 12:28:54 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration spotcast which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-08 12:28:54 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration browser_mod which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-08 12:28:54 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meteoalarmeu which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-08 12:28:54 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration xiaomi_cloud_map_extractor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-08 12:28:54 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration trakt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-08 12:28:54 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-08 12:28:54 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-08 12:28:58 DEBUG (SyncWorker_3) [custom_components.xiaomi_cloud_map_extractor.camera] Logging in...
2021-07-08 12:28:58 DEBUG (SyncWorker_5) [custom_components.xiaomi_cloud_map_extractor.camera] Logging in...
2021-07-08 12:28:59 DEBUG (SyncWorker_3) [custom_components.xiaomi_cloud_map_extractor.camera] Logged in
2021-07-08 12:28:59 DEBUG (SyncWorker_3) [custom_components.xiaomi_cloud_map_extractor.camera] Retrieving device info, country: de
2021-07-08 12:28:59 DEBUG (SyncWorker_5) [custom_components.xiaomi_cloud_map_extractor.camera] Logged in
2021-07-08 12:28:59 DEBUG (SyncWorker_5) [custom_components.xiaomi_cloud_map_extractor.camera] Retrieving device info, country: de
2021-07-08 12:28:59 DEBUG (SyncWorker_3) [custom_components.xiaomi_cloud_map_extractor.camera] Retrieving map name from device
2021-07-08 12:28:59 DEBUG (SyncWorker_5) [custom_components.xiaomi_cloud_map_extractor.camera] Retrieving map name from device
2021-07-08 12:28:59 ERROR (SyncWorker_1) [spotipy.client] HTTP Error for GET to https://api.spotify.com/v1/me/ returned 401 due to The access token expired
2021-07-08 12:29:05 DEBUG (SyncWorker_3) [custom_components.xiaomi_cloud_map_extractor.camera] Map name rubyslite%2F322176735%2F16
2021-07-08 12:29:05 DEBUG (SyncWorker_3) [custom_components.xiaomi_cloud_map_extractor.camera] Unable to retrieve map, reasons: Logged in - True, map name - rubyslite%2F322176735%2F16, device retrieved - False
2021-07-08 12:29:08 DEBUG (SyncWorker_7) [custom_components.xiaomi_cloud_map_extractor.camera] Retrieving device info, country: None
2021-07-08 12:29:10 DEBUG (SyncWorker_5) [custom_components.xiaomi_cloud_map_extractor.camera] Map name rubyslite%2F322176735%2F17
2021-07-08 12:29:10 DEBUG (SyncWorker_5) [custom_components.xiaomi_cloud_map_extractor.camera] Unable to retrieve map, reasons: Logged in - True, map name - rubyslite%2F322176735%2F17, device retrieved - False
2021-07-08 12:29:21 DEBUG (SyncWorker_7) [custom_components.xiaomi_cloud_map_extractor.camera] Retrieving map name from device
2021-07-08 12:29:21 DEBUG (SyncWorker_7) [custom_components.xiaomi_cloud_map_extractor.camera] Map name rubyslite%2F322176735%2F0
2021-07-08 12:29:21 DEBUG (SyncWorker_7) [custom_components.xiaomi_cloud_map_extractor.camera] Unable to retrieve map, reasons: Logged in - True, map name - rubyslite%2F322176735%2F0, device retrieved - False
2021-07-08 12:29:21 ERROR (SyncWorker_3) [spotipy.client] HTTP Error for GET to https://api.spotify.com/v1/me/ returned 401 due to The access token expired
2021-07-08 12:29:23 DEBUG (SyncWorker_1) [custom_components.xiaomi_cloud_map_extractor.camera] Retrieving device info, country: None

Did by any chance the token format change between v1 and v2?

3_14 · July 8, 2021, 12:04pm

Nooo, it shouldn’t. I see that it fails to retrieve device information. It tries to match device by comparing token and IP address. Can you check if token extractor returns the same values as in your config?

gersilex · July 8, 2021, 12:34pm

They are identical:

As you can see I use the FQDN of the vacuum and not the IP. Could it be an issue when comparing the token and IP address?

Edit: It works when using the IP address instead of the hostname!

3_14 · July 8, 2021, 12:37pm

That should be it… I think I can change approach to match only by token instead

gersilex · July 8, 2021, 12:38pm

Yes, it was the problem. Either change that or resolve the hostname upfront. But that might require unneccessary dependencies and increase complexity without bringing much benefit.

juaigl · July 21, 2021, 6:08pm

Hi,

I’m having a issue with the blueprint.

Error: Error rendering service name template: UndefinedError: ‘dict object’ has no attribute ‘to_state’

Template variable error: ‘dict object’ has no attribute ‘to_state’ when rendering ‘{% if trigger.to_state.state in [“unavailable”, “unknown”, “docked”] %} camera.turn_off {% else %} camera.turn_on {% endif %}’

I reviewed docs and blueprint seems correct. I can’t find the issue.

Just5 · August 5, 2021, 5:29pm

Hi,
I’m trying to solve a problem with rotating map in my vacuum. It causes vacuum goes in a wrong direction when zoned cleaning is used. I partly solved this problem but I think it could be done better. Actually I have two sets of coordinates, and then I choose one depending on the vacuum position.
Is it possible to make zoned cleaning resistant to map’s rotating easier by using xiaomi cloud vacuum map extractor or lovelelace xiaomi map card?

3_14 · August 5, 2021, 11:00pm

You can suggest a solution for map rotation detection and correction, I haven’t tried to do it so far

sjmotew · August 9, 2021, 12:09am

Noting that the map does not show the vacuum track as it was before. Nothing else changed.

dimiforty · August 15, 2021, 7:23pm

Hello all,
please i follow all the instructions i create an entity for camera but the error i get is “failed to retrievev map from vacuum”
I suppose that i have complete all the steps correctly as i foolowed the instructions.
Any suggestion?
thank you!

3_14 · August 15, 2021, 8:40pm

Check if there is anything suspicious in logs. You can also enable debug logging:

logger:
  default: info
  logs:
    custom_components.xiaomi_cloud_map_extractor: debug

dimiforty · August 16, 2021, 11:08am

thanks for answer me! I will go that way when i get back and i will see.
I believe i have done everything correct. i didn’t go through HACS. hope this did not affect the installation.
But i’ve seen the entity.

dimiforty · August 16, 2021, 4:17pm

~~hello again, i checked my logs and seem that the device is not responding~~

~~The vacuum entity i have to delete it or not? now i had remove it.~~
I can confirm that i received normally the map! The problem was the extraction token.
Two different tokens for EU servers.
Thank you for your kind help!