Xiaomi Gateway (Aqara) integration fails to discover Gateway

[manosioa]

The problem

Hi there, trying to use the Xiaomi Gateway (Aqara) integration that supports all my sensors and my Gateway. The integration " Xiaomi Gateway (Aqara)" cannot be setup due to the fact that it doesn't discover the Gateway. When I select the integration, the prompt asks: > "Xiaomi Aqara Gateway > Connect to your Xiaomi Aqara Gateway > The network interface to use > "any" Tried to use "any" and get the error: "Failed to discover a Xiaomi Aqara Gateway, try using the IP of the device running HomeAssistant as interface" or my HA IP address and get the error: "Unknown error occurred" and "Failed to discover a Xiaomi Aqara Gateway, try using the IP of the device running HomeAssistant as interface" or the Gateway's IP address and get the error: "Unknown error occurred" and "Failed to discover a Xiaomi Aqara Gateway, try using the IP of the device running HomeAssistant as interface" Can you please provide help with the issue? If I can help, I would be happy to contribute to the solution of the issue. Many people have the same issue and trying to find out a way to solve it. Some have mentioned that the HA 0.111 was the last version that the integration worked as it should. I cannot verify that as I'm fairly new to HA. @danielhiversen @syssi Sensors: Mi motion sensor (Model: lumi.sensor_motion.v2) Mi Door/Window Sensor (Model: lumi.sensor_magnet.v2) Mi Wireless button (Model: lumi.sensor_switch.v2) Gateway: lumi.gateway.v3-MW300 by Xiaomi Firmware: 1.4.1_176 (Latest) ## Environment

• Home Assistant Core release with the issue: Home Assistant 0.113.3
• Last working Home Assistant Core release (if known): -
• Operating environment (OS/Container/Supervised/Core): VM (fresh install) with official QCOW2 image
• Integration causing this issue: Xiaomi Gateway (Aqara)
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/xiaomi_aqara/

Problem-relevant configuration.yaml

No custom .yaml, all in UI ```yaml ``` ## Traceback/Error logs

Additional information

[starkillerOG]

If people still have issues: 1) update to the latest HomeAssistant version 2) allow your gateway to connect to the xiaomi servers (in case you have blocked it in your router, if MiHome app works it is connected to the xiaomi servers and you are fine, acces can be blocked again after you have setup everything succesfully) 3) update your gateway to the latest firmware version

If it then still does not work, follow the instructions here: https://www.home-assistant.io/integrations/xiaomi_aqara/#connection-problem, specifically:

Make sure you have enabled LAN access.

If your gateway’s MAC address starts with 04:CF:8C or 7C:49:EB, there is a good chance that the required port 9898 is closed on your gateway (you can check it with the Nmap utility, using the command sudo nmap -sU {gateway_ip} -p 9898). To fix that issue, you need to do these steps:

If you then still have problems after doing all of the above, please post error logs of HomeAssistant that show the problem.

I am kind of lost which people still have problems and what the actual errors are.

[starkillerOG]

@guyye have you updated your gateway to the latest firmware version (using the MiHome app)?

[accelle17]

Yeah, found this thread and I've had this issue for the past few versions. I just upgraded to 0.114.0 and problems remain, with the same dialogues and messages as described above. My variation on this is I have 3 hubs - two have been discovered and configured perfectly for Aqara and Miio, and the sensors discovered for both these hubs. However the third has configured correctly for Miio only, and the balance of sensors on that 3rd hub remain undiscovered. I also have a simple unifi network, and multicasting is enabled. In fact, these hubs worked perfectly with manual settings in earlier versions. Now dead :( I commented in another thread, that the only difference with the non-discovered hub is that it's on a wireless uplink to an AP, not wired, but I wouldn't think that would make a difference, but who knows. They are otherwise on the same network.

same here even on 0.114.1. I have unifi with multicast and igmp proxy enabled and I'm able to configure the gateway before 0.112 on the config. I only use the gateway for the sounds though, not as zigbee gateway. The workaround for me right now is to use the xiaomi_aqara 0.111.3 package as custom component.

Here's the error when trying to add xiaomi aqara using the integration:

ERROR (MainThread) [aiohttp.server] Error handling request Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 418, in start resp = await task File "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 458, in _handle resp = await handler(request) File "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 119, in impl return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/real_ip.py", line 39, in real_ip_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 73, in ban_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 129, in handle result = await result File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 145, in post return await super().post(request, flow_id) File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 60, in wrapper result = await method(view, request, *args, *kwargs) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 106, in post result = await self._flow_mgr.async_configure(flow_id, data) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 153, in async_configure result = await self._async_handle_step(flow, cur_step["step_id"], user_input) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 201, in _async_handle_step result: Dict = await getattr(flow, method)(user_input) File "/usr/src/homeassistant/homeassistant/components/xiaomi_aqara/config_flow.py", line 90, in async_step_user self.selected_gateway = await self.hass.async_add_executor_job( File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run result = self.fn(self.args, self.kwargs) File "/usr/local/lib/python3.8/site-packages/xiaomi_gateway/init.py", line 227, in init resp = self._send_cmd(cmd) File "/usr/local/lib/python3.8/site-packages/xiaomi_gateway/init**.py", line 330, in _send_cmd _socket.sendto(cmd.encode(), (self.ip_adress, self.port)) socket.gaierror: [Errno -3] Try again

for my issue, I noticed that I was able to integrate xiaomi_aqara on a newly deployed hassos on proxmox with the same network config. When I migrated my old hassio supervised (pi 4) config to proxmox, it got the same error. I was able to integrate it by adding zeroconf: on the configuration.yaml.

[starkillerOG]

If people still have issues:

1. update to the latest HomeAssistant version

2. allow your gateway to connect to the xiaomi servers (in case you have blocked it in your router, if MiHome app works it is connected to the xiaomi servers and you are fine, acces can be blocked again after you have setup everything succesfully)

3. update your gateway to the latest firmware version

If it then still does not work, follow the instructions here: https://www.home-assistant.io/integrations/xiaomi_aqara/#connection-problem, specifically:

Make sure you have enabled LAN access.

If your gateway’s MAC address starts with 04:CF:8C or 7C:49:EB, there is a good chance that the required port 9898 is closed on your gateway (you can check it with the Nmap utility, using the command sudo nmap -sU {gateway_ip} -p 9898). To fix that issue, you need to do these steps:

If you then still have problems after doing all of the above, please post error logs of HomeAssistant that show the problem.

I am kind of lost which people still have problems and what the actual errors are.

@accelle17 have you followed all of these steps? Did you check that the port is open, have you updated to the lastest firmware?

[accelle17]

No, I'm still on hassio 0.114.2, same xiaomi gw firmware when the issue started, and same firewall policy and unifi config. Like I said before, it's working via config file using 0.113.4 xiaomi_aqara. I just turned on zeroconf and I was able to integrate it using the config flow. Im just using it to play sound, light and light sensor though.

[biglegs462]

Just chipping in here to support the bug/fix investigation. I've been using HA via docker, on the same Unifi infrastructure for going on 2 years with all the devices happily working. These last releases have broken it. I have 3 hubs, 2 are discovered successfully, 1 is not, including the devices hanging off it. All were working in the bad old days of manual entires in the config.

[biglegs462]

I have just upgraded to 0.115.2 to see if any progress has been made on this. The third hub (same network as the other two) has been discovered as previously, however it cannot be configured. The other 2 are successfully discovered and configured. The error messages have changed slightly. Starting a configuration with 'any' left as the network interface still fails, but with the message "Invalid IP Address, see https://www.home-assistant.io/integrations/xiaomi_aqara/#connection-problem" which is rubbing salt in the wound because this was previously working OK. If I the hub IP address instead of 'any' i get 'unknown error occured' and if I enter the mac address we are back to the 'Invalid IP Address' message.

[syssi]

The field you are talking about is to specify the network interface for listening. If you don't use "any" here a IP address of the Home Assistant host is required.

[biglegs462]

The field you are talking about is to specify the network interface for listening. If you don't use "any" here a IP address of the Home Assistant host is required.

Yes, I tried both ANY and the IP Address. And the mac address just to see if it made a difference. But you do highlihgt the ambiguity of the dialolgue boxes and message inputs.

[syssi]

Is the IP address of your Home Assistant host rejected as "Invalid IP address", too?

[biglegs462]

Yep:

[syssi]

Please remove the protocol scheme "http://". The format of an IPv4 address is w.x.y.z f.e. 10.0.0.200.

[biglegs462]

I didn't input the http protocol - the error message simply can back with that error.

[manosioa]

Please remove the protocol scheme "http://". The format of an IPv4 address is w.x.y.z f.e. 10.0.0.200.

Hi there @syssi,

The issue has been the same, the error messages the same as they were 2 months ago when I opened the case.

You can scroll up and check all the different things we did. We have screenshots, explanations, everything.

The integration is not working for many people which you can find talking about the issues they face in the link I provided in previous posts on Home assistant forums.

I still have the same issues. Currently I'm using Miio integration just to have the gateway exposed so I can arm it easily using geolocation.

[syssi]

Thanks for the clarification. I haven't time to look deeper into it right now. I will try to build up a test setup next month.

[vesatakomo]

Maybe this helps someone like me. I've been trying to get my Agara Gateway working since 0.112. All the tricks here were tried with no luck. I have been using older agara integration as custom_component until I noticed I couldn't install HACS either. In its all simplicity, I had Firefox Adblock on when using my HA. Disabling Adblock and Agara & HACS installation went smoothly as everything earlier. "Sometimes simplest solutions are best"

[manosioa]

Hi all,

3 weeks ago I purchased a Conbee 2 from Amazon. 3 days ago I installed it with Deconz and all sensors are working flawlessly, without any issues, fast and reliably.

I'm currently setting up an alarm system that uses all the sensors to arm home when away or at night.

I do not own a Xiaomi Gateway anymore as I sold it.

Please keep up the good work and I hope that you will ultimately find a solution.

Thanks again for everything.

[sj3fk3]

I've also recently started to see: [xiaomi_gateway] Got error element in data {"error":"Invalid key"} When I reload the integration it will work for a while and then it looses it's marbles again...

Can't put my finger on why it looses connection (even if it does work for a while).

[syssi]

@sj3fk3 This is caused by a lossy/bad wireless connection and/or poor wifi repeaters. Try to improve your wifi network or the position of your gateway.

[sj3fk3]

@sj3fk3 This is caused by a lossy/bad wireless connection and/or poor wifi repeaters. Try to improve your wifi network or the position of your gateway.

I would like to challenge that assumption:

The Xiaomi Gateway is in the living room, any more wifi coverage and it would start to glow without any mains..

[syssi]

@sj3fk3 Could you take a look at the community? There are some people around having trouble with unify networks + the xiaomi gateway. I don't want to blame your setup. Just try to build a small network without unify devices f.e. The HA component cannot handle udp packets in different order. The udp traffic of the gateway has a sequence number which isn't properly handled by the component. If udp packets arrives multiple times or in reverse order the component gets stuck. :-( If your wifi setup is simple the order of the udp packets is more predictable.

[sj3fk3]

@sj3fk3 Could you take a look at the community? There are some people around having trouble with unify networks + the xiaomi gateway. I don't want to blame your setup. Just try to build a small network without unify devices f.e. The HA component cannot handle udp packets in different order. The udp traffic of the gateway has a sequence number which isn't properly handled by the component. If udp packets arrives multiple times or in reverse order the component gets stuck. :-( If your wifi setup is simple the order of the udp packets is more predictable.

The problem is: I've had this network for years now and the gateway worked fine, until the last couple of versions..

[lencshu]

Fiiiiiinally I have got one solution: Open the app -> open gateway -> about -> taps on the version for dev options -> LAN communication protocol(局域网通信协议) -> toggle on the first option(局域网通信协议) -> remember the key

Then, back to the Home Assistant cfg, for the Xiaomi Gateway (Aqara), retry its config. It will ask for a key, enter the key above, maybe a mac addr is needed. Done!

[DaveFace]

I began having issues with the Xiaomi integration a few weeks ago after upgrading HA to the latest version, I thought a fresh install of HA might resolve it but unfortunately it's only made things worse.

I've encountered the same pairing issue as others here. The integrations tab in HA correctly identifies the Aqara gateway, but trying to pair with it fails with the "Failed to discover a Xiaomi Aqara Gateway, try using the IP of the device running HomeAssistant as interface".

I used Beduir's workaround by manually adding the integration, which worked, which proves it is only an issue with the discovery / configuration process - and not a 'genuine' issue with the ports or network.

However since then, the link to each Xiaomi devices is incredibly unreliable, mirroring the issues I was having before reinstalling HA. Some devices report as unavailable, others do not update their status correctly, etc. Nothing has changed in my setup, so there must be some issues with the integration and current HA version.

[daniellos]

Hi All, I have an issue with Aqara GW and Sensors from yesterday as following:

1. I updated Gateway from the Mi app on iOS to version: 1.4.1_176.0220 (as far as i remember previously i had 1.4.1_170.....)
2. After that i started to have issues on Homeassitant that GW and all sensors are seen as Unavailable. (HA Version version: 0.118.4) I had config for xiaomi aqara GW in configuration.yaml but i commented it as now it should be configured with Integration. Now when I remove integration, restart HA, Add integration - it works but untlii HA restart. After HA restart it goes to state Unavailable and if i want to see it back i need to remove and add integration again. I noticed also that even if i did not reboot during night it went aslo to Unavilable state.

Is there possibility to rollback Aqara GW FW? I think this is the reason. Before it was working fine for long time.

UPDATE: I downgraded Hassio to my older backup version i had: 0.112.0 and for now all is ok. WIll try later on to again update to latest and see if it works or not.

UPDATE 2: restore form backup to older version and then update Hassio to latest fixed the issue.

[nerdmovieproduction]

Guys any news about this? I'm going to become crazy. I'm working on my HA by 2weeks. I installed all and today my all my xiaomi gateway are unvailable. I reboot all. I reinstalled all with a new HA setup and still no working

[Ayo91]

Same issue here, I have spent days trying to figure out but no way. All my gateways except one shows: Got error element in data {"error":"Invalid key"}

[Ayo91]

Same issue here, I have spent days trying to figure out but no way. All my gateways except one shows: Got error element in data {"error":"Invalid key"}

UPDATE:

• I was able to connect the gateways to HA, I created several keys until not see the error.

However, two gateways are not reporting motion sensors information to HA. I dont know if its because a new Vodafone router I have or because Im using Proxmox v6 that not support multicast: https://pve.proxmox.com/wiki/Multicast_notes

[Ayo91]

Same issue here, I have spent days trying to figure out but no way. All my gateways except one shows: Got error element in data {"error":"Invalid key"}

UPDATE:

• I was able to connect the gateways to HA, I created several keys until not see the error.

However, two gateways are not reporting motion sensors information to HA. I dont know if its because a new Vodafone router I have or because Im using Proxmox v6 that not support multicast: https://pve.proxmox.com/wiki/Multicast_notes

UPDATE: I solved the problem with a basic tplink switch. I bought a gigabyte tplink switch and I conected all ethernet cables coming from smart home devices and suddenly everythink works. The problem at my side was the new router.

[techinpark]

            {
                "connection_class": "local_push",
                "data": {
                    "host": "192.168.1.22",
                    "interface": "any",
                    "key": "b22jb533kg1vgqx2",
                    "mac": "78:7c:2e:c3:cc:82",
                    "port": 9898,
                    "protocol": "1.1.2",
                    "sid": "787c2ec3cc82"
                },
                "domain": "xiaomi_aqara",
                "entry_id": "9d1bbfcef9dd4c47ab58b000fd55e711",
                "options": {},
                "source": "zeroconf",
                "system_options": {
                    "disable_new_entities": false
                },
                "title": "Xiaomi Aqara Gateway",
                "unique_id": "78:7c:2e:c3:cc:82",
                "version": 1
            }

78:7c:2e:c3:cc:82 - MAC address in lower case 787c2ec3cc82 - MAC address in lower case without ":". b22jb533kg1vgqx2 - gateway password from MiHome application (About -> Wireless communication protocol - > Password) 192.168.1.22 - IP address of the gateway 9d1bbfcef9dd4c47ab58b000fd55e711 - I don't know exactly, I think it's just a random GUID for Home Assistant to link the gateway configuration and its devices. During the test, left one value for both gateways. If you use two gateways at once, the values should be different.

After changing the "core.config_entries" file you should restart Home Assistant.

@Beduir how to find gateway password? i think mi home application was updated.

[starkillerOG]

@techinpark I looked in my app and indeed it is updated and I can't find it anymore. If you figure it out, please also let us know so we/you can update the documentation.

I think it is possible to retrieve the password through python-miio: https://github.com/rytilahti/python-miio/blob/7771f45f9b1724a5ecc632b591e83a667043f83e/miio/gateway.py#L351 (I wrote part of that code) But it is a bit of a hassel to do it that way....

[Beduir]

@techinpark Gateway -> "..." -> About -> Wireless communication protocol -> Password. If there is no such item, you have to click 2.77.1 several times until it appears.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[biglegs462]

Sorry, but this remains a problem. I keep updating HA but nothing is resolved, I will rery with the latest, but I see nothing in th release notes to suggest this have been adressed. I will confirm by updating AGAIN, but this remains an issue for me - I have quite a number of Xaiomi devices that were previously operating perfectly with HA.

[starkillerOG]

@biglegs462 So to recap: You have 3 gateways on a ubiquiti network, 2 are working fine, 1 is giving trouble. The one that is giving trouble is connected to a AP that has a wireless connection to your router, while the other 2 gateways are on AP's that have a wired connection to the router. Could you post (again) the error in the log the gateway is giving that does not want to be setup? It has someting to do with the multicast messages not properly getting through, but honestly I don't know why. I will see if I can figure something out.

[starkillerOG]

@biglegs462 to recap: You have 3 identical gateways (same model), all in the same ubiquiti network in the same VLAN. 2 gateways are connected to APs that are wired to your router and those work perfectly fine. 1 gateway is connected to an AP that is wirelessly connected to your router and that one does not work. Is this correct?

Could you post (again) the error in the log that you are currently getting? Is there any setting in the AP that is giving trouble related to multicast that is diffrent than the other two APs? For instance I know some Asus routers have a "Multicast sniffing" option, if you enable that you can see the mutlicast messages in your AP/router, but they get blocked when they are sniffed and therefore do not arrive at the device running HomeAssistant creating problems.

If you move the gateway that is giving trouble to one of your wired APs, does it then work? If you move one of the working gateways to the wireless AP, does that gateway stop working?

I am almost certain it is something about the multicast messages that is causing your issues. It could have somting to do with the binding of the socket in the code, or with the network setup (like the "Multicast sniffing" option I mentioned). I do not know much details of this multicast messaging, but I will try to help you and figure out what is going on and how to fix it.

[biglegs462]

Thank you for trying :) I have already tried relocating a hub from an AP with a wireless connection to a AP that was wried, and that didn't fix.
Please understand I can't just move components and test this stuff.
I will try and do that in the next few days and report back.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[justinlawrence]

Still an issue for me.

[starkillerOG]

Just a aditional note, I discovered that specifically for Ubiquiti routers/APs the “Enable multicast enhancement (IGMPv3)” setting in the router/AP should be disabled.

[starkillerOG]

justinlawrence, the xioami gateway and HomeAssistant need to be on the same VLAN to make it work. Additionally for some routers “IGMP snooping” on the used wireless interface needs to be disabled to let the IGMP/multicast messages through.

What kind of network setup do you have? Has the integration ever worked for you, or are you setting it up for the first time?

[miralemR]

Can't install xiaomi aqara integration

[biglegs462]

I can confirm that after well over twelve months this bug has not been fixed. I have had exactly the same problem: the MILO integration works fine and find some of the devices. However when you try and configure the Xiaomi Aqara Gateway, then you get to search on 'any' interface it just times and and returns the error documented above. I have three Gateway hubs. It always find the first one successfully, then times out on the other two. All are on the same network, nothing fancy and yes I have a Unifi AP network. IGMP snooping is disabled and multicast enhancement is also turned off. I have a dedicate wifi network just for them. All other integrations on a bunch of IOT stuff I've got are discovered fine. I have just reset my HA installation to configure afresh with the latest version 2021.10.5 and was disapointed to find this is still a bug.

It used to work fine prior the configuration automation. I have a ton of Xiaomi devices.

[biglegs462]

Update: The second hub did autoconfigure when I added Ip & mac address after it failed to find it automatically, then after this entered the hub password. The third hub refuses to be added this way, I don't get past entering the IP and mac. This is identical to the issues I had 12 months ago.

[justinlawrence]

justinlawrence, the xioami gateway and HomeAssistant need to be on the same VLAN to make it work.

Additionally for some routers “IGMP snooping” on the used wireless interface needs to be disabled to let the IGMP/multicast messages through.

I don't think it is on on or available via the Google WiFi network that I have installed.

What kind of network setup do you have?

Very standard, I believe. All my devices are on a single home network (192.168.86.*/255.255.255.0), over 3 meshed Google WiFi devices. IPv6 and UPnP are enabled and DNS is set to automatic.

Has the integration ever worked for you, or are you setting it up for the first time?

No, unfortunately not. I have elaborated below, in case that helps.

Home Assistant did not discover the gateway (a Xiaomi Aqara M2 Smart Hub). I added it manually via the integrations, but got a message saying "Failed to discover a Xiaomi Aqara Gateway, try using the IP of the device running HomeAssistant as interface". I tried entering the IP of the gateway, but that did not help.

Thanks for the help and thoughts!

[starkillerOG]

@justinlawrence I am not sure if the Xiaomi Aqara M2 gateway is supported, it might not have the API that the aqara integration relays on. Did you give the Xiaomi Miio integration a try (that is a diffrent integration that uses a diffrent API)?

[starkillerOG]

@biglegs462 is the model of all 3 gateways the same, all three are chinese version (not EU version)?

[biglegs462]

Yes, all the same chinese model, reigstered to the CN server. I did purchase that last one at a later date. Is there a firmware number or something like that I can confirm? In the ABOUT menu (in the mi home app) I can see version 272, and that is the same for all three hubs.

[starkillerOG]

In the mihome app you can click on the gateway, then the three dots on the top right, Updates of the device, there you can see the firmware version of the gateway. I am on 1.4.1_176.0220 which is the newest firmware for the chinese version hub.

[biglegs462]

I have a slightly different version of the app but under hub info I can work out 1.4.1_176 and then a bit further on mcu_fw_ver 0220.

I've pasted the full detail underneath: Version no：272 网关ID：57629351 Zigbee通道：25 网关信息： {"life":113290,"cfg_time":0,"token":"0b69185fa17c5f2fcaf682925e1eb698","mac":"34:CE:00:8D:66:F4","fw_ver":"1.4.1_176","hw_ver":"MW300","model":"lumi.gateway.v3","mcu_fw_ver":"0220","wifi_fw_ver":"SD878x-14.76.36.p84-702.1.0-WM","ap":{"rssi":-75,"ssid":"automate","bssid":"82:8A:20:54:74:38"},"netif":{"localIp":"10.0.0.105","mask":"255.255.255.0","gw":"10.0.0.1","gw_mac":"DC:39:6F:6B:BC:B3"},"mmfree":175904,"ot":"otu","otu_stat":[364,320,3100,726,2162,40],"ott_stat":[63,0,142,1003]}

On Tue, 19 Oct 2021 at 09:21, starkillerOG @.***> wrote:

In the mihome app you can click on the gateway, then the three dots on the top right, Updates of the device, there you can see the firmware version of the gateway. I am on 1.4.1_176.0220 which is the newest firmware for the chinese version hub.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/38582#issuecomment-946134866, or unsubscribe https://github.com/notifications/unsubscribe-auth/AL2ON3SAXMMXH2CETA6LE23UHR6UVANCNFSM4PWIF64Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.