-
Notifications
You must be signed in to change notification settings - Fork 22
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
Unknown error occurred #22
Comments
I have the same issue. Just installed it today. |
Hi, it gave me a generic error when entering the email address, I tried with the numeric ID and it worked. I hope it helps |
Seems I have a similar issue I get the same error for the "automatic" and "manual" method. But in my case, the Airfryer is in my IOT VLAN and my Home Assistant (running in docker) is in my Internal VLAN. I have MDNS reflector running (was already in-place for Google Cast), and I have (temporarily) openend all TCP and UDP ports between the Home Assistant host and the Airfryer (bi-directional). Any suggestions/help?
|
I found a solution. Turns out Xiaomi devices ignore requests coming from other subnets. Here are some details and solution. In short, you need to setup NAT masquerading on your router like so:
After that, the device will be responding to requests coming from home assistant in another subnet. Of course, the firewall should not be preventing that and there should be functioning inter-VLAN routing in place. |
Great! That got it connected. But it looks like the Air Fryer requires Internet Access for all sensors to work. Is that correct? This integration does not show a "cloud" symbol, so I was kind of expecting it to work fully local without any Internet connectivity. Not a big deal to let it connect to the Internet, but if it's not required then I'd rather not. :-) |
I blocked access for the fryer to internet and dns in my firewall. And it still happily works and shows all sensors. So, maybe the initial configuration requires xiami cloud but after that it works locally. |
Hmmm, OK. I had it internet connected to register it with the Xiaomi cloud. Then I blocked internet traffic. Now all my sensors are "Unknown" until I grant the AirFryer Internet access... I'll investigate further and I needed, I'll open a separate issue for that. Thanks for the help! |
For those with Ubiquiti devices: it seems that is now possible to masquerade NAT with the new version of Network Application. Works like a charm with my Xiaomi Smart Air Fryer 6.5L. |
@gmcinalli, cool — thanks for sharing! I didn't notice it in the changeling. No need to be messing with CLI anymore :) Would mind sharing a screenshot of how your NAT setting for XIaomi looks like in the UI? |
@GentleHoneyLover Sure! Here it is. Source is HA, destination is the AirFryer, interface is the VLAN where the fryer is located. |
Same problem. |
Quick note: if you're using a UniFi gateway and NAT rules weren't making any difference, I figured out the issue in their iptables implementation and reported the bug to Ubiquiti. I am happy to announce that version v8.5.1 of the UniFi Network Controller fixes this. It's currently in Early Access and should become GA in a few weeks from now. |
@ruimarinho Really strange, I was with an older version of UniFi Network until yesterday and everything worked fine. |
Same here. NAT settings via web ui work fine for me on v8.4.62 |
It depends on your equipment upgrade path (for example, if coming from a USG to UXG, UDM from scratch, etc). |
This worked for me. Thanks so much! :) |
Hello,
Trying to configure the integration but it fails. Tried both methods (login + password and IP + token). The Fryer is on and connected to wi-fi. I can control it via the Mi app.
Can you please help! Thanks a ton!
NAME: Mi Smart Air Fryer 3.5L
MODEL: careli.fryer.maf07
HASS: 2024.2.2 (running in Docker)
Integration installed via HACS.
The text was updated successfully, but these errors were encountered: