henrikrox
(Henrikrox)
March 14, 2021, 7:16pm
653
Heres an image when im using the other integration, works fine, heres my code, with the above from map_transformation, if i remove map_transformation it gets even smaller. so dunno whats happening, tried 2 scale, 90 scale etc
with this code
type: custom:dwains-flexbox-card
items_classes: ‘col-xs-12 col-sm-6 col-sm-6’
cards:
{% if (data | fromjson)[‘map’] %}
type: custom:dwains-flexbox-card
padding: true
cards:
type: custom:dwains-heading-card
item_classes: ‘col-xs-12 col-sm-12 col-md-12 col-lg-12’
title: Map
type: ‘custom:xiaomi-vacuum-map-card’
items_classes: ‘col-sm-12’
entity: vacuum.roborock_vacuum_s5
map_camera: camera.xiaomi_cloud_map_extractor
camera_calibration: true
3_14
(Piotr Machowski)
March 14, 2021, 7:35pm
654
Can you specify what do you want to achieve?
henrikrox
(Henrikrox)
March 14, 2021, 7:39pm
655
sorry i am not good at english
i want this card to fill out the width and height of this page.
Its worked with another solution use cloud map extractor, but when i use scale here it doesnt get bigger, or just a bit
code:
type: custom:dwains-flexbox-card
items_classes: ‘col-xs-12 col-sm-6 col-sm-6’
cards:
{% if (data | fromjson)[‘map’] %}
type: custom:dwains-flexbox-card
padding: true
cards:
type: custom:dwains-heading-card
item_classes: ‘col-xs-12 col-sm-12 col-md-12 col-lg-12’
title: Map
type: ‘custom:xiaomi-vacuum-map-card’
items_classes: ‘col-sm-12’
entity: vacuum.roborock_vacuum_s5
map_camera: camera.xiaomi_cloud_map_extractor
camera_calibration: true
camera:
- platform: xiaomi_cloud_map_extractor
host: 10.0.0.5
token: X
username: X
password: X
draw: ['all']
attributes:
- calibration_points
map_transformation:
rotate: 90
scale: 5
3_14
(Piotr Machowski)
March 14, 2021, 7:46pm
656
Scale changes only resolution of an image, to get rid of empty blue spaces around a map you have to use trim
henrikrox
(Henrikrox)
March 14, 2021, 7:47pm
657
im not worried about blue space, i want the image to get bigger, so i dont have all that “white space”. See image here for other integration
[IMG_0950]
Heres an image when im using the other integration, works fine, heres my code, with the above from map_transformation, if i remove map_transformation it gets even smaller. so dunno whats happening, tried 2 scale, 90 scale etc
with this code
type: custom:dwains-flexbox-card
items_classes: ‘col-xs-12 col-sm-6 col-sm-6’
cards:
{% if (data | fromjson)[‘map’] %}
type: custom:dwains-flexbox-card
padding: true
cards:
type: custom:dwains-heading-card
item_classes: ‘col-xs-12 col-…
3_14
(Piotr Machowski)
March 14, 2021, 7:53pm
658
Ok, so it’s something you have to do in lovelace config, not camera’s. It is probably achieved using some magic cards made by Dwaine
henrikrox
(Henrikrox)
March 14, 2021, 8:41pm
659
ok thank you, seems its not possible without doing some major work, trying to see if i can use css card mod with it.
henrikrox
(Henrikrox)
March 14, 2021, 9:41pm
660
some simple css fixed the issue sorry for bringing it up here
Followed this suggestion but this is the result, map seems to not show up:
configuration.yml
vacuum:
- platform: miio2
name: "Mi Mop P"
host: !secret xiaomi_vacuum_host
token: !secret xiaomi_vacuum_token
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
3_14
(Piotr Machowski)
March 18, 2021, 5:22pm
662
I see that you use miio2, what vacuum model do you have?
Mi Robot Vacuum Mop P (PRO) (STYTJ02YM)
token_extractor.py detects it as
MODEL: viomi.vacuum.v8
BTW, log is full of
2021-03-18 23:07:37 WARNING (MainThread) [homeassistant.components.camera] Updating xiaomi_cloud_map_extractor camera took longer than the scheduled update interval 0:00:05
2021-03-18 23:07:42 WARNING (MainThread) [homeassistant.components.camera] Updating xiaomi_cloud_map_extractor camera took longer than the scheduled update interval 0:00:05
2021-03-18 23:07:47 WARNING (MainThread) [homeassistant.components.camera] Updating xiaomi_cloud_map_extractor camera took longer than the scheduled update interval 0:00:05
2021-03-18 23:07:52 WARNING (MainThread) [homeassistant.components.camera] Updating xiaomi_cloud_map_extractor camera took longer than the scheduled update interval 0:00:05
2021-03-18 23:07:56 ERROR (SyncWorker_57) [miio.miioprotocol] Got error when receiving: timed out
So i assume that is using miio(v1?) protocol to retrive the livemap and is just incompatible with my robot… is something that i can do to help debugging/fixing?
3_14
(Piotr Machowski)
March 19, 2021, 12:18am
665
Viomi vacuums are not supported by extractor
FrancYescO
(Francesco)
March 19, 2021, 12:57am
666
Can i help you somehow to get it fixed? can you point me in the direction to get some debug information so i can try to find a way to fix? (what’s the “core” func that needs to be fixed? )
sender
March 23, 2021, 1:39pm
667
Hi all, I have in sensors:
- 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
- charger
- country
- goto
I get:
But I do not see selectable calibration points… where are they? This is see in developer tools
3_14
(Piotr Machowski)
March 23, 2021, 2:19pm
668
@FrancYescO I think that you can’t do anything at this moment, sorry
@sender I don’t really understand your problem… Calibration points are used by a card to send a vacuum to correct locations. You can see them on a map by adding debug: true
in card’s config
sender
March 23, 2021, 2:22pm
669
I meant, how can I get these:
https://github.com/PiotrMachowski/lovelace-xiaomi-vacuum-map-card/blob/ec8c4a7badc55306335ac8828d2ac68f3872384b/s3.gif
Edit: sorry I think I mixed up the word calibration pint with a map zone selection (which I believed were calibration points?)
3_14
(Piotr Machowski)
March 23, 2021, 2:26pm
670
These are “predefined zones”. You have to define them using zones
config (like here ):
zones:
- [[25500, 25500, 26500, 26500]]
- [[24215, 28125, 29465, 32175]]
- [[24245, 25190, 27495, 27940], [27492, 26789, 28942, 27889]]
- [[28972, 26715, 31072, 27915], [29457, 27903, 31107, 29203], [30198, 29215, 31498, 31215], [29461, 31228, 31511, 32478]]
You can get these coordinates using flole vac or by enabling debug: true
in card’s config and drawing them on a card in “Zoned cleanup” mode
sender
March 23, 2021, 2:41pm
671
Yes, That works for now I think. I can draw them ate least (map is now gone I believe it was due to restart by me)
Where do those coordinates “appear” to copy them back in the card?
thank you!!
3_14
(Piotr Machowski)
March 23, 2021, 2:44pm
672
They should appear in a popup after clicking “start”