Xiaomi Mi Robot Vacuum-Mop 2 Pro (ijai.vacuum.v3) not listed

dsimop commented 1 year ago

The problem

The official Xiaomi integration (xiaomi_miio) does not include in the respective list the Xiaomi vacuum mop 2 pro (ijai.vacuum.v3). Although, the https://github.com/rytilahti/python-miio/pull/1497/ for that particular vacuum is already merged to master.

What version of Home Assistant Core has the issue?

core-2022.12.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Xiaomi Mizo

Link to integration documentation on our website

https://www.home-assistant.io/integrations/xiaomi_miio/#xiaomi-mi-robot-vacuum

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 year ago

Hey there @rytilahti, @syssi, @starkillerog, mind taking a look at this issue as it has been labeled with an integration (xiaomi_miio) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `xiaomi_miio` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign xiaomi_miio` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

xiaomi_miio documentation xiaomi_miio source _{^{(message by IssueLinks)}}

DrLEEi commented 1 year ago

Unfortunately, it does not work with my device either in automatic or manual installation

Xiaomi Mi Robot Vacuum Mop 2 Pro

"The device model is not known, you cannot configure the device using the configuration process.

Device model chuangmi.plug.v1"

VaultVulp commented 1 year ago

I guess we wait for a new release of the python-miio package, that should bring support for this device.

There is an issue in that package that is focused on its release schedule.

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

VaultVulp commented 1 year ago

I think that this issue is relevant still.

PaulvanEeden commented 1 year ago

Good day All I'm brand new to HA and to Home Automations. I've recently bought this Mi Robot Vac and other Smart devices to setup a smart home, with help of the community I've setup most of my devices but the robot Vac is a big issue. As this forum discussed the same issue as i currently have in 2023 i would like to find out if someone found a fix yet ?

VaultVulp commented 1 year ago

@PaulvanEeden , there is no fix yet. We are all waiting till the maintainer of the python-miio publishes a new version of his package.

antoweb commented 1 year ago

But in readme i see vaccum mop 2 pro https://github.com/rytilahti/python-miio#supported-devices

ashkanj commented 1 year ago

@VaultVulp looks like it is supported since https://github.com/rytilahti/python-miio/commit/aa2718853455c40b5b8c2a1883019d8cb7a683b4

VaultVulp commented 1 year ago

@antoweb and @ashkanj, you are correct, and yet we cannot use this integration for now.

Home Assistant is built in Python. Python projects can rely on another package to solve some problems (ex: when they need to work with some specific devices). These helper packages are called "dependencies." In our case, home-assistant depends on python-miio.

Each time the dependency is updated, there is a small risk that the compatibility between the main project and the dependency will be broken, and the main project will become unusable. To mitigate this issue, project maintainers depend on the specific version of the particular package.

As per https://github.com/home-assistant/core/blob/dev/requirements_all.txt#L2111 home-assistant depends on the latest available version of the python-miio - 0.5.12.

Right now, we have to wait until the maintainers of python-miio publish a new version of their package. When they do this and if this new version is compatible with the internal implementation of the home-assistant, we will be able to connect our lovely little Xiaomi Mop Twos.

I hope I made the current situation more apparent.

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

VaultVulp commented 1 year ago

Nope, Mr. issue-triage-workflows. We are still humbly waiting for this issue to be resolved.

issue-triage-workflows[bot] commented 10 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

slecram commented 10 months ago

Still open

VaultVulp commented 10 months ago

I've already sold my Mop 2, yet we're still waiting for the release of a new version of python-miio.

issue-triage-workflows[bot] commented 7 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

slecram commented 7 months ago

Issue is still there

issue-triage-workflows[bot] commented 4 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

antoweb commented 4 months ago

Hello new versione of python miio including this model Is available?

antoweb commented 3 months ago

Hello the new python._miio (python-miio-0.5.12) now support ijai.vacuum.v3 root@raspberrytv:/home/pi# python3 /usr/local/bin/miiocli cloud

== Aspirapolvere (Dispositivo online ) == Model: ijai.vacuum.v3 Token: >omissis> IP: 192.168.1.100 (mac: 50:ec:50:4d:b0:ec) DID: Locale: de

But official integration says not found device. An upgrade of the integration is possible

dsimop commented 3 months ago

Unfortunately, the v0.5.12 does not support this model. It supports the Xiaomi Vaccum Mop 2 Ultra and Pro+ (dreame versions). The Xiaomi Vaccum Mop 2 Pro (jai.vacuum.v3) is expected to be supported with the next official release, according to the python-miio repo.

issue-triage-workflows[bot] commented 1 week ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

antoweb commented 1 week ago

Is now compatibile?

home-assistant / core