Rewritten (v3.0.0-alpha-8) #650
Replies: 10 comments 15 replies
-
|
An unexpected error occurs after entering the 2FA code. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
me too ! This my logs |
Beta Was this translation helpful? Give feedback.
-
|
This works! A couple questions:
Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Yes. Use the cogwheel inside the integration to change both:
|
Beta Was this translation helpful? Give feedback.
-
|
Hi. I have Xiaomi X20 Pro. During configuration it found robot as X20+, token was extracted correctly, protocol is recognized as unsupported |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, this happens for unsupported models. I'll try to make it at least not break, but to present a readable message |
Beta Was this translation helpful? Give feedback.
-
|
My s20 max also got discovered as unsupported :( But 2fa and captcha work!
great stuff
…On Sat, Sep 27, 2025 at 11:18 PM newmalexv ***@***.***> wrote:
Hi.
I have Xiaomi X20 Pro. During configuration it found robot as X20+, token
was extracted correctly, protocol is recognized as unsupported
After successfull add
image.png (view on web)
<https://github.com/user-attachments/assets/623989bb-851f-4277-af48-6555c3557c0d>
2025-09-27 23:16:48.275 ERROR (MainThread) [custom_components.xiaomi_cloud_map_extractor.coordinator] Unexpected error fetching xiaomi_cloud_map_extractor data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 392, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 293, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/xiaomi_cloud_map_extractor/coordinator.py", line 36, in update_data
return await self.connector.get_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/xiaomi_cloud_map_extractor/connector/__init__.py", line 77, in get_data
await self._get_map()
File "/config/custom_components/xiaomi_cloud_map_extractor/connector/__init__.py", line 140, in _get_map
await self._update()
File "/config/custom_components/xiaomi_cloud_map_extractor/connector/__init__.py", line 104, in _update
await self._initialize()
File "/config/custom_components/xiaomi_cloud_map_extractor/connector/__init__.py", line 127, in _initialize
self._vacuum_connector = self._create_device(device_details)
~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
File "/config/custom_components/xiaomi_cloud_map_extractor/connector/__init__.py", line 178, in _create_device
return vacuum_class(vacuum_config)
File "/config/custom_components/xiaomi_cloud_map_extractor/connector/vacuums/vacuum_unsupported.py", line 15, in __init__
self._unsupported_map_data_parser = MapDataParser(
~~~~~~~~~~~~~^
vacuum_config.palette,
^^^^^^^^^^^^^^^^^^^^^^
...<3 lines>...
vacuum_config.texts
^^^^^^^^^^^^^^^^^^^
)
^
TypeError: Can't instantiate abstract class MapDataParser without an implementation for abstract methods 'parse', 'unpack_map'
—
Reply to this email directly, view it on GitHub
<#650 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AP4QDOTUMRBZ2DBHRKDLW733U35LBAVCNFSM6AAAAACHUS5VJ6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINJTGEYTMNI>
.
You are receiving this because you were mentioned.Message ID:
<PiotrMachowski/Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor/repo-discussions/650/comments/14531165
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Works well for me. I have viomi.vacuum.v8 ! Thank you |
Beta Was this translation helpful? Give feedback.
-
|
With the old version (2.2.5) I was able to use the token_extractor with QR code to successfully login, otherwise the captcha method would never work. Then, once extracted and saved the token to the configuration YAML, the map correctly loads (although half of the time I'm still getting login issues...). With this new version I'm suffering from the same problem: I can't login no matter how many times I try with the captcha, which means the integration never gets installed. Is there a way to support the QR code method also with the new alpha version? Or maybe support a manual configuration step that would allow the user to enter directly the token if it's already available? I would like to test this alpha version to see if it fixes all of the issues present with the old one but I can't do that if I don't manage to finish the first setup. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I plan to add QR auth as well. |
Beta Was this translation helpful? Give feedback.
-
|
Besides having the token extractor bundled into the component, are there any major differences between the alpha and the latest stable version which would make testing useful? |
Beta Was this translation helpful? Give feedback.
-
|
The whole integration was rewritten (as you can see in the title of release), the list of changes is available in its description. Also, the token extractor is not bundled into it, the implementations are now completely separate |
Beta Was this translation helpful? Give feedback.
-
|
Hey @PiotrMachowski , sorry if it sounded like that but it was not my intent to criticize your work and yes, I've read the list of features and the title. I was just wondering if the rewrite of this new version also changes the polling mechanism and in general how the data is fetched and used locally, or if it's just reorganizing the same core functionalities that were present in the old version. The reason I was testing was to see whether I can fix all the issues I had with the map fetching (which are not limited to the credentials issues), that's why the local map caching appeared appealing to me and made me think the new version is actually completely different in its behavior 👍 keep up the good work |
Beta Was this translation helpful? Give feedback.
-
|
The map caching part is implemented mostly for Roborock vacuums, it basically incorporates the blueprint that refreshed map only when vacuum is running into the code of the integration. Additionally there is an incremental backoff for map download from a vacuum |
Beta Was this translation helpful? Give feedback.
-
|
Authorization OK, but Details
2025-10-01 16:29:21.722 DEBUG (MainThread) [custom_components.xiaomi_cloud_map_extractor.connector] Downloading new map.
2025-10-01 16:29:21.722 DEBUG (MainThread) [custom_components.xiaomi_cloud_map_extractor.connector] Restoring connector configuration...
2025-10-01 16:29:21.724 DEBUG (MainThread) [custom_components.xiaomi_cloud_map_extractor.connector] Initializing...
2025-10-01 16:29:21.724 DEBUG (MainThread) [custom_components.xiaomi_cloud_map_extractor.connector] Retrieving device info, server: ru
2025-10-01 16:29:21.865 DEBUG (MainThread) [custom_components.xiaomi_cloud_map_extractor.connector] Retrieved device model: dreame.vacuum.mc1808
2025-10-01 16:29:21.866 DEBUG (MainThread) [custom_components.xiaomi_cloud_map_extractor.connector] Created device, used api: DREAME
2025-10-01 16:29:21.866 DEBUG (MainThread) [custom_components.xiaomi_cloud_map_extractor.connector] Initialized.
2025-10-01 16:29:21.866 DEBUG (MainThread) [custom_components.xiaomi_cloud_map_extractor.connector] Downloading map...
2025-10-01 16:29:21.866 DEBUG (MainThread) [custom_components.xiaomi_cloud_map_extractor.connector.vacuums.base.vacuum_base] Getting map name...
2025-10-01 16:29:21.866 ERROR (MainThread) [custom_components.xiaomi_cloud_map_extractor.coordinator] Unexpected error fetching xiaomi_cloud_map_extractor data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 392, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 293, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/xiaomi_cloud_map_extractor/coordinator.py", line 36, in update_data
return await self.connector.get_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/xiaomi_cloud_map_extractor/connector/__init__.py", line 77, in get_data
await self._get_map()
File "/config/custom_components/xiaomi_cloud_map_extractor/connector/__init__.py", line 140, in _get_map
await self._update()
File "/config/custom_components/xiaomi_cloud_map_extractor/connector/__init__.py", line 108, in _update
map_data, map_saved, map_raw_data = await self._vacuum_connector.get_map()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/xiaomi_cloud_map_extractor/connector/vacuums/base/vacuum_base.py", line 78, in get_map
map_name = await self.get_map_name()
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/xiaomi_cloud_map_extractor/connector/vacuums/vacuum_dreame.py", line 78, in get_map_name
self._dreame_vacuum.call_action("map_view", params=[{'piid': 2, 'value': '{"frame_type":"I"}'}])
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/miio/click_common.py", line 184, in _wrap
return func(self, *args, **kwargs)
File "/usr/local/lib/python3.13/site-packages/miio/miot_device.py", line 89, in call_action
raise DeviceException(f"{name} is not an action (missing siid or aiid)")
miio.exceptions.DeviceException: map_view is not an action (missing siid or aiid)
2025-10-01 16:29:21.871 DEBUG (MainThread) [custom_components.xiaomi_cloud_map_extractor.coordinator] Finished fetching xiaomi_cloud_map_extractor data in 0.149 seconds (success: False) |
Beta Was this translation helpful? Give feedback.
-
|
Not working with JONR P20 Pro but authorisation seems to be ok. Capcha and 2FA. |
Beta Was this translation helpful? Give feedback.
-
|
I download beta version but can't understand where I can get captcha. URL using to token extractor didn't work. |
Beta Was this translation helpful? Give feedback.
-
|
Captcha should be displayed in the UI. If it is not displayed then try using QR auth |
Beta Was this translation helpful? Give feedback.
-
|
Also, there is no beta version, just alpha. And this one is over a month old. Install the latest one if you have installed this one |
Beta Was this translation helpful? Give feedback.
-
|
I've deleted all version and installed latest alpha. All works, but not support of my xiaomi s20. |
Beta Was this translation helpful? Give feedback.
-
|
Time will tell, I can't promise anything |
Beta Was this translation helpful? Give feedback.
-
|
I get this error with an L10s Pro
|
Beta Was this translation helpful? Give feedback.
-
|
Do you use the latest alpha version? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I'm using Version v3.0.0-alpha-18 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This is an early version of Map Extractor v3 release. It has been completely rewritten in order to provide better functionality and user experience. To use this version you have to remove old config from
configuration.yamlfile and use UI to add the integration again.Caution
Please keep in mind this is not a final release, so a lot of things might change or not work at all at this moment.
Does everything work correctly, or are there some missing functionalities? Please provide feedback in the comments below.
Changes
imageentitiesBreaking changes
cameraentity have been removedThis discussion was created from the release v3.0.0-alpha-8.
Beta Was this translation helpful? Give feedback.
All reactions