Closed tannisroot closed 9 months 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!
(message by CodeOwnersMention)
xiaomi_miio documentation xiaomi_miio source (message by IssueLinks)
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.
The problem
When trying to add my Xiaomi Air Purifier Pro H (zhimi.airpurifier.vb2), I get the following error:
The device model is not known, not able to set up the device using config flow.
I am then prompted to choose the model manually. From what I've tried both zhimi.airpurifier.va1 and zhimi.airpurifier.mb3 configs work fine (I am testing mb3 rn but it exposes more functionality functionality), although with both configs the device suffers from intermittent connection (device has a stable, strong connection to Wi-Fi yet entities constantly go "unavailable"). However this issue also occurs with an integration from HACS calledMiot Auto
, not just with built-inMiio
from HASS.What version of Home Assistant Core has the issue?
core-2023.10.3
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 Miio
Link to integration documentation on our website
https://www.home-assistant.io/integrations/xiaomi_miio/
Diagnostics information
config_entry-xiaomi_miio-eb79bce829845d0eb895a472e12c6d83.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
There was another issue that described lack of support for this device (https://github.com/home-assistant/core/issues/68823) but the user wrongly closed the issue thinking the hack they found resolves it.