Skip to content
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

Invalid calibration_points for roidmi.vacuum.v60 #193

Closed
3 tasks done
wowgamr opened this issue Nov 22, 2021 · 12 comments
Closed
3 tasks done

Invalid calibration_points for roidmi.vacuum.v60 #193

wowgamr opened this issue Nov 22, 2021 · 12 comments
Assignees
Labels
bug Something isn't working

Comments

@wowgamr
Copy link

wowgamr commented Nov 22, 2021

Checklist

  • I have updated the card to the latest version available
  • I have cleared the cache of my browser
  • I have checked if the problem is already reported

The problem

Can't select zone for cleaning because selector locked in the upper left corner.
image

What version of a card has described problem?

v2.0.3

What was the last working version card?

No response

What vacuum model do you have problems with?

roidmi.vacuum.v60

Which integration do you use to control your vacuum (link)?

https://github.com/al-one/hass-xiaomi-miot

What browser (browsers/apps) does have this problem?

Chrome 95.0.4638.69

What version of Home Assistant do you use?

core-2021.11.3

What type of installation are you running?

Home Assistant Supervised

Card's configuration

- type: custom:xiaomi-vacuum-map-card
    entity: vacuum.roidmi_v60_9cd4_robot_cleaner
    map_source:
      camera: camera.xiaomi_cloud_map_extractor
    map_locked: true
    calibration_source:
      camera: true
    icons: []
    tiles: []
    map_modes:
      - template: vacuum_clean_zone

Javascript errors shown in the browser's console (if applicable)

Error: <polygon> attribute points: Expected number, "NaN, NaN NaN, Na…".
W @ xiaomi-vacuum-map-card.js:31
Error: <polygon> attribute points: Expected number, "NaN, NaN NaN, Na…".
_setup @ xiaomi-vacuum-map-card.js:197

Additional information

I tried to disable map rotation, but it didn't help me.
image

@PiotrMachowski
Copy link
Owner

@wowgamr can you provide calibration points from camera.xiaomi_cloud_map_extractor?

@wowgamr
Copy link
Author

wowgamr commented Nov 22, 2021

Sure.

calibration_points: 
- vacuum:
    x: 0
    'y': 0
  map:
    x: 28
    'y': 274
- vacuum:
    x: 1
    'y': 0
  map:
    x: 28
    'y': 274
- vacuum:
    x: 0
    'y': 1
  map:
    x: 28
    'y': 274

@PiotrMachowski
Copy link
Owner

Does this problem disappear after switching mode?

@wowgamr
Copy link
Author

wowgamr commented Nov 22, 2021

Are you talking about map_modes?

@PiotrMachowski
Copy link
Owner

I mean to change to a different mode from the drop-down (instead of "Zone cleanup") and then go back to "Zone cleanup"

@wowgamr
Copy link
Author

wowgamr commented Nov 22, 2021

No, it does not help. I have only one mode, but i tried to add vacuum_goto. Pointer in this mode works fine. If i switch back to vacuum_clean_zone, selector still unavailable.

image
image

@PiotrMachowski
Copy link
Owner

Can you check out if v2.0.4 has fixed this problem?

@wowgamr
Copy link
Author

wowgamr commented Nov 24, 2021

Updated to v2.0.5. There are no errors in console now, but selector still locked.

@PiotrMachowski
Copy link
Owner

PiotrMachowski commented Nov 24, 2021

Waaaaait a second... I think I have found the problem. All 3 calibration_points point to the same map coordinates for different vacuum coordinates, which is obviously wrong -> the issue is in Map Extractor

@PiotrMachowski
Copy link
Owner

Transferring issue to Map Extractor repo

@PiotrMachowski PiotrMachowski transferred this issue from PiotrMachowski/lovelace-xiaomi-vacuum-map-card Nov 24, 2021
@PiotrMachowski PiotrMachowski added the bug Something isn't working label Nov 24, 2021
@PiotrMachowski PiotrMachowski changed the title Can't select zone for cleaning Invalid calibration_points for roidmi.vacuum.v60 Nov 24, 2021
PiotrMachowski added a commit that referenced this issue Jan 3, 2022
@PiotrMachowski
Copy link
Owner

Problem should be solved in v2.1.2

@wowgamr
Copy link
Author

wowgamr commented Jan 3, 2022

Thank you! It works fine.
Happy New Year!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants