I am not sure if this will help someone, but it helped in my case. What I had to do was to:
more info: https://github.com/home-assistant/core/issues/37306
Could you elaborate on what you mean by âupdating the PyXiaomiGatewayâ? How did you do that?
once 13.0 has been release to pypi
pip install PyXiaomiGateway
Hi there. I am experiencing the same issue. I did some tests and the integration works well when HA and the Xiaomi device are in the same VLAN. When on different VLANS, the autodiscovery works but the integration cannot be configured. Note that the integration was working before 112.0 from YAML so I believe fix should be around parameter setting from the Integrations UI.
Unfortunately, the fix for this doesnât seem to have been added to todayâs release:
Well if upgrading PyXiaomiGateway to 13.0 is needed, that hasnât been uploaded to pypi yet it seems. https://pypi.org/project/PyXiaomiGateway/
EDIT hopefully⌠https://github.com/Danielhiversen/PyXiaomiGateway/issues/176
I have two gateways, in both I can see:
Version no. 272
fw ver: 1.4.1_176
model: lumi.gateway.v3
Both worked untill 0.111, now one is working without any problem, the other one is discovered but canât connect.
Iâve double checked, I canât find any difference beetween them.
If I remove the connected gateway, still canât connect the other one. Itâs like if the problem is on that specific device.
In logs I can see, every 70seconds:
2020-07-16 00:03:11 ERROR (Thread-5) [xiaomi_gateway] Unknown gateway ip 192.168.21.22
Rolling back to 0.111, the device works again.
In the meanwhile Iâve setted up a new HassIO that will replace my old Home Assistant Core on Docker, and the situation is the same.
Have someone found a solution?
Thank you all very much!
Iâve solved connecting the gateway on the same accesspoint of the working gateway. For now, after configuration, connecting back the gateway on the original accesspoint, itâs still working.
No idea the reason, I have a plan network without vlan, hope it could be usefull to someone, if have have similar problem.
Can confirm that this workaround works!
Letâs see if I can clarify because Iâm afraid I donât quite understand the solution. Here is a small diagram of my network, any problem here that may affect the connection to the gateway or HASS? Thanks!
There should not be any problem, because I can see just a single broadcast domain in your LAN.
But you could try to connect the Raspberry directly on the wifi router and have a try.
Can the gateway version have something to do with this issue? I have two gateways right now, the oldest one is this:
And the new one is this:
As far as I know, the new one is not compatible with Home Asistant (according to other threads that I have read) but the old one should work.
I have two gateways like the first one of your images. Try to check in Xiaomi Home App, select you gateway, tap [âŚ], tap [About], finally tap [Hub Info].
In my gateways I see:
Version no. 272
hw ver: 0220
fw ver: 1.4.1_176
model: lumi.gateway.v3
Letâs check if you have some difference from mine.
In addition, what you see in home assistant logs?
Only difference I found is the hw_ver. It says: MW300
The rest is similar. 
Today. My HA network interface error was cleared.
First of all. You guys are needs to check the 4321 & 9898 port of your xiaomi gateway.
Please using NMAP with command ânmap -sU -p 9898,4321 your xiaomi gateway IPâ
If you cannot find âopenâ signal from that comman.
You should better take an action by last things in (bottom page of the site)
https://www.home-assistant.io/integrations/xiaomi_aqara
The port open work.
After open the port 9898 & 4321. I can connect to HA easily just with network key
My gate way look like below
My knowledge of this has come to a dead end here. The ports are closed; I may try to solve it with the article you mention but I donât know if itâs worth it.
As far as âworth itâ is concerned, zigbee2mqtt is definitely worth it
Gateway is asking for FW update but I donât want to do it just in case it closes the port again
