Tasshack

@PiotrMachowski i found out that these devices are using encrypted map data and aes key can be acquired from `map_request` action `object_name` response property. Request: `[{'piid': 2, 'value': '{"req_type":1,"frame_type":"I","force_type":1}'}]` Response:...

@michal-tadeusiak-by VSLAM robots are not supported yet but will be on the next release. You can follow the related issue about this https://github.com/Tasshack/dreame-vacuum/issues/12. I can give you the private key...

> I removed the Dreame integration via HACS, then added it again via HACS (latest version), then restarted Home Assistant. It's working correctly, and my vacuum's cards and entities all...

@vulbas navigate to this url; `(YOUR HOME ASSISTANT URL)/hacs/repository/544426802` Press the button on the top right corner and select remove; 

@jove01 problem is not with the current version but it was caused by an older version so it would be impossible to update to any version from if you have...

Which version are you using? Also I need the full model number.

I cannot access the miot right now to check it but that device probably not manufactured by Dreame therefore cannot be used with this integration. I will notify you when...

I can add it to the supported devices list if I can confirm that this is actually the same device with the L10s Ultra as you claimed.

> > here is it: `xiaomi.vacuum.c102gl` > > i've tried to add to `config_flow.py` , but when it send token there is no response from the device :( You need...

You can at least try to add the device using the Beta version of the integration by adding it to the config flow but just to confirm that this is...