Aqara M100 hub networking issues

kanwhoa · July 12, 2026, 2:49am

Hi,

I’ve been experiencing networking issues with my M100 hub. Until recently, I just used to reset it every few months when it got “upset”, however, this time, I managed to get a good log of what was happening.

Below is a network trace from a router’s interface. The interface is dedicated for a 2.4G wifi and other devices on the network are working fine.

Here is the basic setup.

192.168.3.1 is the router. This has a VLAN bridge with other devices. The packet log is from here and is watching all in and out on wifi interface.
192.168.3.12 is a wired network device connected directly to the router and on the same vlan.
192.168.3.253 is the Aqara M100 hub connected via a 2.4G wifi. The router interface is on the same vlan.

Here is the raw log:

No.	Time	Source	Destination	Protocol	Length	Info
67246	11:17:30.348902	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67260	11:17:31.372623	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67299	11:17:32.395806	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67310	11:17:32.759610	f6:1e:57:6e:cd:78	Broadcast	ARP	91	Who has 192.168.3.253? Tell 192.168.3.1
67326	11:17:33.765196	f6:1e:57:6e:cd:78	Broadcast	ARP	91	Who has 192.168.3.253? Tell 192.168.3.1
67331	11:17:34.348317	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67337	11:17:34.814528	f6:1e:57:6e:cd:78	Broadcast	ARP	91	Who has 192.168.3.253? Tell 192.168.3.1
67343	11:17:35.402582	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67366	11:17:36.427018	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67374	11:17:36.763934	f6:1e:57:6e:cd:78	Broadcast	ARP	91	Who has 192.168.3.253? Tell 192.168.3.1
67409	11:17:37.842344	f6:1e:57:6e:cd:78	Broadcast	ARP	91	Who has 192.168.3.253? Tell 192.168.3.1
67415	11:17:38.347665	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67419	11:17:38.893959	f6:1e:57:6e:cd:78	Broadcast	ARP	91	Who has 192.168.3.253? Tell 192.168.3.1
67421	11:17:39.375727	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67428	11:17:39.950308	f6:1e:57:6e:cd:78	Broadcast	ARP	91	Who has 192.168.3.253? Tell 192.168.3.1
67434	11:17:40.395686	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67445	11:17:40.962392	f6:1e:57:6e:cd:78	Broadcast	ARP	91	Who has 192.168.3.253? Tell 192.168.3.1
67459	11:17:42.013845	f6:1e:57:6e:cd:78	Broadcast	ARP	91	Who has 192.168.3.253? Tell 192.168.3.1
67466	11:17:42.348175	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67492	11:17:43.391285	LumiUnitedTe_80:b1:f0	f6:1e:57:6e:cd:78	ARP	91	Who has 192.168.3.1? Tell 192.168.3.253
67493	11:17:43.391333	f6:1e:57:6e:cd:78	LumiUnitedTe_80:b1:f0	ARP	91	192.168.3.1 is at f6:1e:57:6e:cd:78
67494	11:17:43.402899	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67502	11:17:44.427217	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67536	11:17:46.349118	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67577	11:17:47.395734	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67595	11:17:48.442772	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67600	11:17:48.801870	f6:1e:57:6e:cd:78	LumiUnitedTe_80:b1:f0	ARP	91	Who has 192.168.3.253? Tell 192.168.3.1
67601	11:17:48.815689	LumiUnitedTe_80:b1:f0	f6:1e:57:6e:cd:78	ARP	91	192.168.3.253 is at 54:ef:44:80:b1:f0
67602	11:17:48.842640	LumiUnitedTe_80:b1:f0	f6:1e:57:6e:cd:78	ARP	91	192.168.3.253 is at 54:ef:44:80:b1:f0
67616	11:17:50.350321	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67638	11:17:51.406856	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67658	11:17:52.427940	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67685	11:17:54.348677	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12
67691	11:17:55.372962	02:42:c0:a8:03:0c	Broadcast	ARP	105	Who has 192.168.3.253? Tell 192.168.3.12

This is what is happening:

The ARP cache is cleared on 192.168.3.1 and 192.168.3.12. A ping is then started form both.
Until timestamp 67492 nothing happens and both devices show no response on the ping output. This means the hub is quite slow to be “found”.
At timestamp 67492, the M100 decides to back query the router to get the router’s MAC address, which is acknowledged at 67493.
On the next query from the router at timestamp 67600, the M100 responds to the router with its MAC address. There is actually two replies. At this point, the router shows the ping response.
The M100 does not respond to try to back-query the other device (192.168.3.12). The ping output on 192.168.3.12 continues to show no output.

192.168.3.12 is actually a Home Assistant server, but this test is just doing a basic ping connectivity test.

This is quite annoying because randomly over the course of a couple of months, the M100 just needs a reset before it will talk to other network devices properly.

The only difference between the two arp requests (from 192.168.3.1 and 192.168.3.12) as far as I can see is the inclusion of a trailer on the request from 1291.68.3.12 the target is all zeros. The length shown above is 91 vs 105 bytes.

I thought about trying to replay the request without a trailer, but that’s not an easy thing to do.

Anyone else? Anyone from Aqara can look at it?

AqaraBot · July 12, 2026, 2:49am

Hi there, it looks like you’re experiencing a support-related issue. We’ve automatically created a support ticket for you and will reach out via the forum email within the next two business days.

If other members have any suggestions or insights on this topic, feel free to share!

gafich10 · July 12, 2026, 4:53am

Hello, welcome to the forum.

Have a nice weekend @expert, whoever has time, please consider this issue. Thank you.

kanwhoa · July 14, 2026, 1:23pm

Followup… I had a few rounds of back-and-forth with Aqara support. There was also a firmware update to 4.5.60_0019.0017. I had no confirmation of any changes, but the issue went away. At the moment I’m not sure if the issue will come back at a later or if a fix has been put in place. I’ll update if it comes back…

denis.w · July 20, 2026, 1:45pm

Glad the Update has fixed the issue. Or does it came back?

Sugar · July 20, 2026, 6:49pm

I had similar issues, but they fixed everything with that firmware

bcdeller · July 26, 2026, 8:03am

I’ve just updated 3 M100 hubs to the 4.5.60_0019.0017 firmware and now 17 of 21 dev ices won’t connect. I’ve spent the day power cycling annd powering off and on Apple TVs and the hubs themselves in various orders trying to get things to “relearn” routes and reconnect nothing. This is infuriating and I should know better than updating a working system.

coccolino_26 · July 26, 2026, 9:02am

Did you try pressing on each device to wake them up?as many child devices that are batterie powered they most of the time are sleeping to preserve batterie and when an hub goes off or reboot after an power failure or an updated many of those child devices won’t show as connected and you ether wait till each device send signal to the hub depending on how each need to send that signal or press once on the power button on each so the hub see them again.

bcdeller · July 26, 2026, 9:19am

Yes tried that several times with different devices. Have now also checked MDNS and IGMP settings on the IOT network, can;t find any reason for the sudden networking issues.

bcdeller · July 26, 2026, 9:20am

Now I’ve reset one of the hubs and lost all the b@#!* devices and automations.

coccolino_26 · July 26, 2026, 12:35pm

Well I am not an big expert on router setups but what I did find working great for me is that I just use smart WiFi I didn’t set the IoT for my smart devices or the guest mode ether.what I did is using smart WiFi o set each device to use the band is suppose to use meaning if most of devices use 2.4Ghz only I set that for each instead of let it automatically by default also I reserve the IP for each this way each device will stay connect on that band witch supports and with his IP address.now regarding your reset if you did an factory reset yes you need to add them all back from scratch and also make all automations back, but if you just eliminate the hub from aqara app then you can add it back and all zigbee devices connected to it will show back including automations.

gafich10 · July 26, 2026, 1:00pm

Hello, what devices are missing, please give a description.

bcdeller · July 26, 2026, 8:41pm

The M100’s were the updated hubs. Now the devices that haven’t reconnected are a mix of Door and Window Contact Sensors, Motion Sensors, Relays and water Leak Sensors. I have since begun adding them back in but am finding many have issues reconnecting. The Door sensors for example don’t do the flashing three times after pressing for five seconds. instead they flash continuously until you release the button then they stop flashing but still won’t reconnect. Seems like since the update, everything is pretty broken.

bcdeller · July 26, 2026, 8:42pm

Tried that and nothing reconnected in there own. Am now manually removing the “not connected” devices to re-add them back in but having trouble with many of those too.

coccolino_26 · July 26, 2026, 9:10pm

That is very weird.did you contact again aqara support?also I see you message regarding the blinking light that is new to me that even pressing the button till it flash 3 times you mention that is continuous blinking.now in the contact sensor you can’t remove the batterie without unglue it.my he press 10 times in a row as usually that is factory reset an Aqara device and if this doesn’t work ether you try keep pressing on that button more de 5 sec like 10/15 sec see what happens.

bcdeller · July 27, 2026, 1:45am

Ive tried a few different ways to reconnect including changing batteries to eliminate that as a potential cause. I think i may need to contact support for help.

gafich10 · July 27, 2026, 2:53am

Hello, the support service will definitely analyze the situation accurately.

coccolino_26 · July 27, 2026, 5:08am

Yes as aqara support knows better what is happening with your devices just tell them exactly the issue.