I don’t understand. I just enable the LAN access on my 2.34 android app without any trouble
Menus are all in english.
What fails ?
It looks like there are some gateways out there where the local network protocol cannot be enabled at the moment. The app reports success but the gateway cannot be discovered by home assistant and the udp ports of the local network protocol are closed. We are digging for a solution or hint.
Okay So I’m a lucky guy ! Discovery works on y third attempt.
I’m using google wifi as router if it helps.
After problems with discovering my gateway in home assistant I searched on google and found this topic.
I have exact the same problem. I configured the gateway in de Mi Home app but the HA can’t discover the gateway.
So I will wait for more info.
Same as killabee.nl, got same issue. i am so glad I found this thread.
Setup:
HA version:0.52.1 running in virtual environment on Raspberry Pi 3
iOS MiHome version: 3.23.2
XiaoMi Gateway Firmware:1.4.1_149.0143
Meraki switch & AP + Netgear cable modem as LAN gateway.
Error:
2017-08-29 12:28:43 ERROR (Thread-12) [homeassistant.components.xiaomi] No gateway discovered
2017-08-29 12:28:43 ERROR (MainThread) [homeassistant.setup] Setup failed for xiaomi: Component failed to initialize.
Troubleshooting:
no matter enable or disbale LAN protocol, the nmap status always the same:
Host is up (0.0051s latency).
PORT STATE SERVICE
9898/udp open|filtered monkeycom
open|filtered
Nmap places ports in this state when it is unable to determine whether a port is open or filtered. This occurs for scan types in which open ports give no response. The lack of response could also mean that a packet filter dropped the probe or any response it elicited. So Nmap does not know for sure whether the port is open or being filtered. The UDP, IP protocol, FIN, NULL, and Xmas scans classify ports this way.
I think syssi is right. Seems LAN protocol is the problem.
May be you are lucky. Open is fine. The bad case is “closed”.
It’s not “open”. it’s “open|filtered” which basically means UNKNOWN 
The gateway would response with “close” (ICMP: Destination unreachble (Port unreachable)) if the port is closed. Are you familiar with tcpdump/wireshark? Could you provide or analyse a dump of your network traffic?
Hello I’m from China, this bug has been submitted to the engineer, I hope there will be a response
6 Likes
Nice! Did you also report the motion issue to the developer?
My new gateway on the older firmware has started losing connection the last 2 days…I also have a new router upstairs with the gateway
2017-08-29 13:23:44 ERROR (Thread-23) [PyXiaomiGateway] Unknown gateway ip 192.168.0.23
2017-08-29 13:23:54 ERROR (Thread-23) [PyXiaomiGateway] Unknown gateway ip 192.168.0.23
2017-08-29 13:24:04 ERROR (Thread-23) [PyXiaomiGateway] Unknown gateway ip 192.168.0.23
2017-08-29 13:24:14 ERROR (Thread-23) [PyXiaomiGateway] Unknown gateway ip 192.168.0.23
router is TP-Link Archer C7, if I connect it to my Asus RTAC68U it works fine. Is this a problem with the router or the gateway old firmware please? It does work fine for 12-18 hours via the TP-Link, then out of the blue is fails and get the error above.
Cheers
Mark
It looks like the gateway does a DHCP renewal and receives a new IP address. Please set the gateway to a fixed address.
I’m not from here (I’m using Openhab instead) and I received my Gateway last Friday. Since it I’m looking for a solution because I have the exact same problem as other users mentionned. At the same moment, another user on OH reported the same issue too.
The weird thing was that I’m talking with a german OH user which configured his gateway few days before without any trouble.
I’m glad to see that I’m not the only one and the problem have been submitted to the engineer. Thank you for your message. Do you have an URL to follow the fix activity about that issue please ?
Hmm odd, as it has had .23 since I installed it. I have added it as a fixed IP in my DHCP server, let’s see thanks.
I have the same problem with Homebridge and Domoticz. They are talking (in French) about a similar problem with integration in Jeedom at:
https://www.jeedom.com/forum/viewtopic.php?f=182&t=29093&start=140
It seems to be a problem with activation of local lan communication protocol after updating firmware to 1.4.1_149. People who has activated it before updating don’t have the problem and can see their gateways in Jeedom.
Let’s hope they update soon!
1 Like
i have the same firmware and met the same issue.
already send a email to the developer of the xiaomi gateway. and i also heard some of my friend already talked to the customer service, hope it will be fixed soon.
Tonight at home I power-cycled the gateway. After that the gateway was gone in the Mi Home app.
I did a hard reset on the gateway and searched for the gateway in the Mi Home app again.
Once the gateway was connected to my WiFi network I enabled the LAN modus again.
After a restart of HA the gateway became available in HA. So with this my problem has solved.
3 Likes
How did you do the hard reset? Just push the gateway button multiple seconds?
Yes, that is correct. THat is how the Mi Home app shows how to do it.