Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to find mapping for zhimi.airp.mb3a, falling back to zhimi.airpurifier.ma4 #69458

Closed
caohuongls opened this issue Apr 6, 2022 · 14 comments · Fixed by #75415
Closed

Unable to find mapping for zhimi.airp.mb3a, falling back to zhimi.airpurifier.ma4 #69458

caohuongls opened this issue Apr 6, 2022 · 14 comments · Fixed by #75415
Assignees
Labels

Comments

@caohuongls
Copy link

The problem

The issue show in logger as below when using component for Mi Air Purifier 3H. The device and control device is still working but the log display many times. I'm using server Singapore for this device

Logger: miio.miot_device
Source: /usr/local/lib/python3.9/site-packages/miio/miot_device.py:172
First occurred: 12:03:45 AM (196 occurrences)
Last logged: 12:51:00 AM

Unable to find mapping for zhimi.airp.mb3a, falling back to zhimi.airpurifier.ma4

What version of Home Assistant Core has the issue?

2022.4.0

What was the last working version of Home Assistant Core?

2022.4.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Xiaomi Miio

Link to integration documentation on our website

https://www.home-assistant.io/integrations/xiaomi_miio/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2022-04-07 00:03:45 WARNING (SyncWorker_2) [miio.device] Found an unsupported model 'zhimi.airp.mb3a' for class 'AirPurifierMiot'. If this is working for you, please open an issue at https://github.com/rytilahti/python-miio/

Additional information

No response

@probot-home-assistant
Copy link

Hey there @rytilahti, @syssi, @starkillerOG, @bieniu, 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!
(message by CodeOwnersMention)


xiaomi_miio documentation
xiaomi_miio source
(message by IssueLinks)

@reinhardsiegel79
Copy link

same here, same device, same errormessage :(

@github-actions
Copy link

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.

@rytilahti
Copy link
Member

Created rytilahti/python-miio#1468 to mark that model as supported, thanks for reporting!

@mainLink0435
Copy link

Maybe I'm doing something wrong - I updated to 0.5.12 but I'm still getting the error. HA docker 2022.8.5

@caohuongls
Copy link
Author

@rytilahti when it update to home assistant OS. I check and update the lastest version HA OS, it's stll not working

@rytilahti
Copy link
Member

Uhh, looks like it was named zhimi.airpurifier.mb3a in the commit, sorry for that... I created a new one to add the model you reported @caohuongls.

@rytilahti rytilahti reopened this Aug 16, 2022
@mainLink0435
Copy link

Apologies I'm not exactly sure how this works.. do we get a new version of python-miio now? 0.5.13?

@joes63t
Copy link

joes63t commented Aug 27, 2022

Uhh, looks like it was named zhimi.airpurifier.mb3a in the commit, sorry for that... I created a new one to add the model you reported @caohuongls.

Hi, can you help me with my model zhimi.airp.mb3a ?
i have issue WARNING (SyncWorker_8) [miio.miot_device] Unable to find mapping for zhimi.airp.mb3a, falling back to zhimi.airpurifier.ma4

@mainLink0435
Copy link

Uhh, looks like it was named zhimi.airpurifier.mb3a in the commit, sorry for that... I created a new one to add the model you reported @caohuongls.

@rytilahti Any chance we can get this committed into the code?

@rytilahti
Copy link
Member

It will require a new python-miio release, I hope we can make that happen for homeassistant 2022.11.

@issue-triage-workflows
Copy link

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.

@caohuongls
Copy link
Author

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.

It's still issues on version HAOS 2023.1.0

Logger: miio.miot_device
Source: /usr/local/lib/python3.10/site-packages/miio/miot_device.py:172
First occurred: 6:00:35 PM (467 occurrences)
Last logged: 8:09:32 PM

Unable to find mapping for zhimi.airp.mb3a, falling back to zhimi.airpurifier.ma4

@issue-triage-workflows
Copy link

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.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 15, 2023
@github-actions github-actions bot locked and limited conversation to collaborators May 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants