Basic functionality for ijai map acquisition and image rendering

[Tarh-76]

No description provided.

[PiotrMachowski]

Hi @Tarh-76, thank you for your contribution!
There's just one problem: at this moment the latest development version of the integration is on dev_extracted_libraries branch. On this branch map parsing has been extracted to appropriate libraries. Would you like to do the same for Ijai vacuums?

[Tarh-76]

Hi @Tarh-76, thank you for your contribution! There's just one problem: at this moment the latest development version of the integration is on dev_extracted_libraries branch. On this branch map parsing has been extracted to appropriate libraries. Would you like to do the same for Ijai vacuums?

Hi Piotr,
Thanks for the advice, sounds like a plan to me. Do I get it right that to follow it I should rebase my branch to dev_extracted_libraries branch? The thing is I'm kinda new to GitHub and may ask some not-so-smart questions.

[PiotrMachowski]

You can try to rebase it, but it might be quite hard (there are a lot of conflicts), so it might be easier to create a branch from dev_extracted_libraries and move your changes there manually. Also you would have to create a pip library that will contain map parser for Ijai vacuums (similarly to approach used here).

[PiotrMachowski]

Uh, these conflicts do not look great... But once the vacuum-map-parser-ijai will be published in pip it should be easy to reimplement everything on the integration side

[SantaFox]

Any updates on this? Xiaomi Robot 5 Pro is still not compatible...

[PiotrMachowski]

@SantaFox this PR will not be merged, it was replaced by #679
Ijai support is available on the alpha version