Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor icon indicating copy to clipboard operation
Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor copied to clipboard

Xiaomi Cloud Map extractor blocking integration Home Connect Local

Open proasnet opened this issue 8 months ago • 1 comments

Checklist

  • [x] I have updated the integration to the latest version available
  • [x] I have checked if the problem is already reported

The problem

Dear @PiotrMachowski , Your integration works fine for me, but now I have found one major problem that your integration for importing Home Connect Local from HACS causes. When your integration is active in HA, it is not possible to integrate Home Connect Local. I have already informed the integration developer. https://github.com/chris-mc1/homeconnect_local_hass Now to be able to control the dishwasher, I had to disable the Xiaomi Cloud Map Extractor integration.

What version of an integration has described problem?

v2.2.3

What was the last working version of an integration?

v2.2.3

What vacuum model do you have problems with?

Mi Robot Vacuum 1S

What version of Home Assistant do you use?

2025.4.1

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
    draw: ['all']
    attributes:
      - calibration_points
    colors:
      color_path: [0xFF,0xFF,0xFF]

Errors shown in the HA logs (if applicable)

homeassistant.requirements.RequirementsNotFound: Requirements for homeconnect_ws not found: ['homeconnect-websocket==1.2.6'].

Additional information

After comment integration in configuration.yaml, Home Connect Local working.

proasnet avatar Apr 09 '25 04:04 proasnet

It seems like a problem with downloading dependencies. My integration doesn't enforce any specific version of used dependencies and lets HA decide which ones to use. I suspect the problematic one is pycryptodome. You can try to specify the verison in manifest.json of map extractor to this one: pycryptodome>=3.21.0 and check if it helps.

PiotrMachowski avatar Apr 09 '25 10:04 PiotrMachowski