Xiaomi Miio and Smartmi Fan 2 (zhimi.fan.za3) not responding intermittently #67926
Comments
|
xiaomi_miio documentation |
|
Hey there @rytilahti, @syssi, @starkillerOG, @bieniu, mind taking a look at this issue as it has been labeled with an integration ( |
|
Could you check what's the error message in the logs? Is it unable to discover the device or is it something else? |
|
Hi. Does that help? |
|
I don't see anything here using either |
|
Having same kind of issues. My fan often goes "Unavailable". Can these logs help?
|
|
the same here. Problem with fans and purifiers. Log full of this lines
|
|
Guys did you figure out a workaround? Would really like to get my fan working again... Unofficial integration does the job for now but isn't as sleek. |
|
Exact same issue here with zhimi.fan.za3. I used to have a custom integration for many years that worked flawlessly (ancient miio integration). Today I have installed the fan again as days are getting warmer in my area. As I changed the SSID during winter, I had to reinitialize the Wifi connection. I registered the device again on the Xiaomi app (using sg country). This worked flawlessly. I was then offered to update the fan to 2.0.3.0013 (was in 2.0.3.0010 before). The update went fine. I then removed the custom integration from HA (from my config.yaml) and proceeded to add the fan via the "official" Miio integration. The integration did its job fine until the end, meaning it connected to sg server and identified all my registered devices. I did the same with my home purifier few weeks ago. The Fan gets then added as a new device without issue, and is responsive for about 20 seconds. But It then disconnects from HA and is no longer available as a device. It is nonetheless perfectly seen by the Xiaomi application and does not lose its IP connection. My firewall does not block any traffic neither. Wish you can find a solution to this. |
|
I should add that I also have an Air Purifier (zhimi.airpurifier.mb3) using the exact same SSID and Integration in HA and it does NOT suffer from the same behavior. I have tried to manually add the Fan using the proper API token (extracted using the token extractor python script). The Token is accepted when manually adding the device. But the resulting behavior is identical, with alternating connections/disconnections. Because I doubt the issue is LAN related, this leaves us with 2 options : |
|
The detection problem for zhimi.fan.za3 is ongoing. Has someone found a solution to this ? It is very annoying. |
Unfortunately not :( |
|
@Lefuneste83 How many Xiaomi (miio) devices do you own? Does the situation improve if you remove the Airpurifier so just one miio device is integrated? |
|
@syssi I'm having issues with zhimi.fan.za4 and no other miio devices on the network. Nothing about my setup has changed since the issues began. If anyone needs testing, logs etc. please message. I'd gladly provide in order to fix this issue. |
|
@ollioddi Could you provide the running firmware version of your device? |
|
img disconnects/unavialable example:
HA info: devices with problems: devices fw: I have: And problem is on all devices |
|
@KitHubek Could you tell me the model names / devices without issues and the used integration per device? |
|
@syssi I am running firmware 2.0.3.0011 |
|
devices with no problems: 2x lumi.gateway.mieu01 |
|
@KitHubek How did you integrate the lights and plugs? Do you use the official |
|
using custom comp |
|
In summary: Only devices interfaced via the official |
|
yes true. I have more devices from Xiaomi but branded Yeelight and working with Yeelight integration, but all this devices i see in my XIaomi Home app. Filament bulbs, desk lamp, lightbar and led strips. This all yeelight devices working with no problems |
|
Is somebody here with the same issue + having access to a local linux machine (!= the Home Assistant host). I would like to spin up a second Home Assistant core (virtualenv) instance. I guess virtualenv installs aren't affected and the issue is somehow docker/container related. |
|
I'm asking for support because I'm unable to reproduce the issue locally.
|
|
problem exsist, and now after update HA core errors appears more more times. last 24h error appears over 11k times...
|
|
I'm looking for somebody who is able to setup a Home Assistant Core (python virtualenv) instance to compare the behavior of the pure HA core setup with a Home Assistant OS (docker) setup. |
I'd be happy to help but I'm not sure what this means or entails. What do I need to do? |
|
@spacecakes You've new mail. |
|
Reopened by request of author |
|
last 7 days. Xiaomi purifer PRO not affected
|
@KitHubek are you running HA in Docker? |
|
no |
spacecakes
changed the title
|
I mentioned it in the description, but it was somewhat obscured by all the information, so for anyone finding this issue in search of a fix : The custom integration by @syssi still works absolutely fine. Uninstall or disable the official one and install this instead to get your fan working with HA. |
|
I'm also experiencing this issue with my Home Assistant setup as per the below and am happy to configure any additional environments to help debug the issue further. @syssi Just let me know how I can help, I am familiar with Home Assistant, Docker and Linux systems so can get you what you need quickly to progress this issue.
Configuration
Log Data
Let me know how I can help, this Fan has been flakey for quite some time, would love to get it stable ! Additional Log Data I've then generated the attached log data for your reference. From what I can see, there are long delays in the current status of the fan occurring, resulting in timeouts. You'll see in the logs the other fan I have working correctly, and you can ignore the vacuum messages, this all works fine, it's just offline at the moment. |
|
Connected with #59215 |
|
I encountered exactly the same problem with a Xiaomi Philips Bulb ( I discussed this with another user of the same bulb in the HA Community, but they didn't have the problem. They confirmed that they were using the HA OS directly on a Raspberry Pi, which made me suspect that this problem had something to do with my containerised HA. However, I can control my Google Nest Hub from my containerised HA. Really confused as a noob to HA, Docker, and Linux. Any help will be very much appreciated! |
|
Feel free to give the dev branch a try to see if the #82601 fixes (or at least alleviates) the issue, and please report back, thanks! |
The problem
Xiaomi Smartmi Fan 2 sets up properly using the GUI, then swiftly becomes unavailable and unable to be controlled.
It pops back up intermittently for brief periods and can be controlled, then goes offline again. Other apps can control it just fine, so there is something going on with this integration and this fan.
Edit: I should mention I am running HA in Docker. @syssi suspected this might have something to do with it, although other users below are not and still have problems.
What version of Home Assistant Core has the issue?
2022.3.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Xiami Miio
Link to integration documentation on our website
https://www.home-assistant.io/integrations/xiaomi_miio/
Diagnostics information
Does not seem to provide any, unfortunately
Example YAML snippet
N/AAnything in the logs that might be useful for us?
Not more than this unfortunately
Additional information
Some notes that may be of use:
python-miioCLI is able to read the fanAccording to
python-miio:The text was updated successfully, but these errors were encountered: