Open eowindel opened 12 months ago
Have you tried using force_api
with other values?
Hello, yes i have tested the fourth.
Waiting for this 🙏🏻
Would be nice to have Q Revo support
I spent a bit of time trying to get the map extractor working with my q revo (roborock.vacuum.a75), as the map extractor is what I previously used with my S5, only to find that there is support for the map in the native integration
https://www.home-assistant.io/integrations/roborock
IMAGE You can see all the maps within your Roborock account. Keep in mind that they are device-specific. The maps require the cloud API to communicate as the maps are seemingly stored on the cloud. If someone can figure out a way around this - contributions are always welcome
I looked at the code here https://github.com/home-assistant/core/blob/08ca3678daafaa60bc127c21d9a33df53ddc286d/homeassistant/components/roborock/image.py#L10
I found that the roborock native integration relies on the following repository for the map https://github.com/PiotrMachowski/Python-package-vacuum-map-parser-roborock
Here is an example of the map working fine with the native roborock integration which I can click on for a larger version.
I found that the roborock native integration relies on the following repository for the map https://github.com/PiotrMachowski/Python-package-vacuum-map-parser-roborock
Yeah, that's the reason I have created it. It is basically a coffee if Map Extractor
Checklist
piotr.machowski.dev [at] gmail.com
(Retrieving map; please provide your GitHub username in the email)What vacuum model do you want to be supported?
roborock.vacuum.a75
What is its name?
Roborock Q REVO
Available APIs
Errors shown in the HA logs (if applicable)
Other info
No response