Redmi Gaming Router AX5400

[wallsilver]

Device model / 设备型号

Xiaomi Redmi Gaming Router AX5400 (xiaomi.router.rb04)

Component version / 插件版本

1.1.2

HA core version / HA版本

2026.1.2

Integrated mode / 集成方式

Automatic (自动模式)

The problem / 问题详情

Good afternoon. The Xiaomi Redmi Gaming Router AX5400 (xiaomi.router.rb04) router. All data is now in the "unavailable" status. It happened a long time ago and I can't seem to recover. Is this normal or something with the settings of the router itself?

Entity attributes / 实体属性

[custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity: <entity sensor.router_router=unavailable>

Home Assistant Logs / 系统日志

hass-assistant | 2026-01-20 09:58:25.889 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] State updater: ☁️
hass-assistant | 2026-01-20 09:58:25.890 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] Device updated: {'only_info': False}
hass-assistant | 2026-01-20 09:58:26.338 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.338 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.338 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.339 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.339 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.339 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.339 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.340 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.340 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.340 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.341 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.347 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.348 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.358 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:26.360 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] New entity:
hass-assistant | 2026-01-20 09:58:31.360 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] Update all coordinators: ['a4:39:b3:b7:2b:da-01JQ63334N4ANDADXD4NWZRHHY-miot_status']
hass-assistant | 2026-01-20 09:58:36.413 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] Device updated: {'only_info': False}
hass-assistant | 2026-01-20 09:59:36.833 INFO (MainThread) [custom_components.xiaomi_miot.core.device.xiaomi.router.rb04] Device updated: {'only_info': False}

[github-actions]

This is not normal behavior - your router entities should show actual states, not "unavailable". Based on the logs and common issues with Xiaomi Miot Auto integration, here are the likely causes and solutions:

Primary Causes

1. Network Connectivity Issues: The integration cannot properly communicate with Xiaomi's cloud servers or the router itself
2. Router-Specific Protocol Limitations: Xiaomi routers often have restricted MIoT protocol implementation
3. Subnet/Routing Conflicts: Since this is a router device, network topology issues may prevent proper discovery

Troubleshooting Steps

1. Verify Network Connectivity from HA

Execute these commands in HA's SSH/Terminal to check connectivity to Xiaomi servers:

nslookup api.io.mi.com
curl -v https://api.io.mi.com
curl -v https://account.xiaomi.com

If these fail, check your DNS settings (avoid foreign DNS like 8.8.8.8, use domestic DNS like 223.5.5.5).

2. Force Cloud-Only Mode

Your logs show "☁️" indicating cloud mode, but try re-adding the integration with "Cloud Mode Only":

• Remove the current integration
• Re-add it and select "Cloud Mode" explicitly
• This bypasses local network discovery issues that routers often have

3. Check Router Settings

Access your Redmi AX5400 admin panel and verify:

• MIoT Protocol is enabled (if available in settings)
• No firewall rules blocking HA's IP address
• Router is not in a restricted operation mode

4. Check for Detailed Error Logs

In HA, go to Settings > System > Logs and search for xiaomi_miot or xiaomi.router.rb04. Look for specific errors like:

• Unable to discover the device
• Connection reset by peer
• Read timed out

5. Network Topology Check

Since this is a router:

• Ensure HA and the router's management interface are on the same subnet
• If HA is on a different VLAN/subnet, router devices often fail to respond to local discovery even with proper routing

If Issues Persist

If none of these resolve the problem, your router model may have limited MIoT protocol support. Router devices are known to have restricted functionality compared to regular smart home devices. Consider:

• Checking the GitHub issues page for similar reports
• Submitting a new issue with your full debug logs

The "unavailable" state typically means the integration cannot retrieve any valid data from the device, either due to network issues or protocol incompatibility.

[wallsilver]

for region in cn ru us de sg in; do echo -n "$region: "; curl -s -o /dev/null -w "%{http_code} " "https://${region}.api.io.mi.com" --connect-timeout 5; echo; done
cn: 000
ru: 404
us: 000
de: 404
sg: 000
in: 000

[wallsilver]

Do I understand correctly that the cn API server is unavailable from Russia?

[nar10z]

It's as if the API isn't working. This curl was made outside of Russia.

curl -v https://api.io.mi.com
* Host api.io.mi.com:443 was resolved.
* IPv6: (none)
* IPv4: 20.47.97.231
*   Trying 20.47.97.231:443...
* Connected to api.io.mi.com (20.47.97.231) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / prime256v1 / rsaEncryption
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=*.io.mi.com
*  start date: Mar 17 00:00:00 2025 GMT
*  expire date: Mar 17 23:59:59 2026 GMT
*  subjectAltName: host "api.io.mi.com" matched cert's "*.io.mi.com"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=RapidSSL TLS RSA CA G1
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://api.io.mi.com/
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: api.io.mi.com]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.5.0]
* [HTTP/2] [1] [accept: */*]
> GET / HTTP/2
> Host: api.io.mi.com
> User-Agent: curl/8.5.0
> Accept: */*
> 
< HTTP/2 404 
< date: Tue, 20 Jan 2026 19:27:20 GMT
< content-type: text/plain; charset=utf-8
< content-length: 3
< server: MonKing/3.14
< xiaomi-security-center: if any vulnerability found, go https://sec.xiaomi.com
< 
* Connection #0 to host api.io.mi.com left intact

[nar10z]

cn: 000
ru: 404
us: 404
de: 404
sg: 204
in: 204