We haven’t seen the result of the nmap test yet. Please provide.
nmap not installed on this ssh console
Well then run it on another machine.
1 Like
C:\Users\>nmap -PN -sV -p 9898 192.168.1.65
Starting Nmap 7.70 ( https://nmap.org ) at 2019-02-03 22:11 ???? ???? ???????
Nmap scan report for 192.168.1.65
Host is up (0.018s latency).
PORT STATE SERVICE VERSION
9898/tcp closed monkeycom
MAC Address: 7C:49:EB:88:CB:1B (Unknown)
Service detection performed. Please report any incorrect results at https://nmap
.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 24.94 seconds
Starting Nmap 7.70 ( https://nmap.org ) at 2019-02-03 22:21 ?
Nmap scan report for 192.168.1.65
Host is up (0.0081s latency).
PORT STATE SERVICE
9898/udp closed monkeycom
MAC Address: 7C:49:EB:88:CB:1B (Unknown)
Nmap done: 1 IP address (1 host up) scanned in 22.05 seconds
how can I open this port on my router ?
Thank you again 
The nmap is showing the TCP not the UDP port . Sorry my predictive text reversed the syntax
nmap -sU -v -p 9898 x.x.x.x
For HA to connect to the gateway you need this port open
9898/udp open monkeycom
If this port is closed and and the wireless communication protocol is on in the MI app. You will need to connect a serial port to the gateway and open it.
Im running https://github.com/hassio-addons/addon-ssh in Hass.io which include nmap
edit sorry its late I can see UDP port is closed from your output. Confirm the above . This was my problem and connecting serail cable to the gateway fixed it for me.
It could be router issue but I don’t think so. I did find this
1 Like
Hey 
the second log related to the udp test and it’s also close .
just to make sure i made this test through my laptop instead Hassio because it haven’t nmap
sorry see above. Your test is fine. Just confirm the ip address is your Gateway
yes it is 
With UDP port 9898 and 4321 closed . HA will never connect 
So currently soldering is the only option?
Look like a bug or feature in the the firmware is not opening the ports. The Serial connection will allow to issue the command to open the ports . The MI App should do this for you with the wireless communication protocol turned on . It maybe a bug and Xiaoami may issue a firmware fix ? It could be a firewall ? Serial connection is the next logical step
1 Like
ROTFLMFAO!
That’s a bit harsh
OK well then point me to the Xiaomi issues tracker, or forum, or any other system that will actually get them to fix any damn thing, or provide any proof whatsoever that Xiaomi react to problems like this, or are even interested in having systems outside their own infrastructure interact with their hardware. Or that they have any commitment to the open source community what so ever.
Not defending any company, especially as we are using the devices outside mainland china, but here is the official english speaking Xioami Forum
There is some good info on Xiaomi gateways
They do appear ? to contributing to some open source
There have been at least 6 firmware updates since I purchased my hub a couple of years ago and they fixed some issues . The MI home app also has not yet removed the option for opening port 9898
as I said a little harsh but maybe true
To get back on topic ( sort of)
I have a large number of Xiaomi products and the Xiaomi hub has been extremely reliable and cheap. I have been investigating other alternatives if Xioami are trying to turn off 3rd party support to the hub.
The Mi home app uses ports 5353 and 54321 which supports a huge range of devices known as the miio protocol . There is a python library will has some support the Xioami gateway without using ports 9898
Protocol information
So there is hope in the future .
4 Likes
I will try it later and I will update
Did it work?
up to now it doesn’t work…