Posted: Sun Jul 13, 2025 2:59 Post subject: MX4300 IoT Devices Have High Ping
I'm currently having an issue with my MX4300 on the 07/12 build of DDWRT. I have some Tuya IoT devices that are connected to Homeassistant, and these devices in particular have extremely high ping, and often timeout (approximately 30% packet loss, with average times of 1000ms). They also seem to respond in bursts (for around 5 seconds), then stop responding for around 10-15 seconds. The devices are not dropping off of the network, and there are no entries in syslogd that would indicate something is wrong (from what I can tell). I had migrated my MX4300 to DDWRT from OpenWRT, where these same devices were working perfectly fine, without having to change any wireless settings. I saw that changing the fragmentation threshold to 1568/1538 resolves issues for ESP8266 devices for similar QCA routers, and this does work for my ESP8266 devices. This doesn't make any difference for these Tuya IoT devices. I tried connecting them to a old Belkin Share Max N300, and they work perfectly there with no packet loss and ~100ms pings. I have the wireless settings on my MX4300's matching the best QCA settings sticky thread exactly. Are there any other settings that I can try changing on these routers? I have also tried resetting the routers and setting them up again, disabling Legacy Rates (11b), WMM, and Beamforming. I apologize if this thread isn't very organized, and if there is a solution to this issue already discussed in the forum.
While I don't have any Tuya devices I always thought they used ESP devices internally. Perhaps not.
I have WMM turned on with no issues and I have my Sensitivity Range / ACK Timing set to 900. No issues with IoT devices on either of my MX4300s. Both beam forming settings off and legacy rates are disabled as well. I also have LDPC (Disable for ESP8266) disabled. I am running both 2.4ghz radios on Ch11 as I have zigbee devices in the lower 2.4ghz channels. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
Thanks for the reply. I've tried the settings that you are using, and I haven't noticed any change in these devices. Strangely enough, other IoT devices (non-Tuya) have 0 issue whatsoever. When looking at HomeAssistant, the "unavailable" periods start exactly when I migrated my MX4300s to DDWRT from OpenWRT. This would indicate, at least to my knowledge, that going from the default settings to the QCA best settings also made no difference. The integration that uses the Cloud still works without showing unavailable (seems to have a larger tolerance to missed responses), but I'd rather not have to depend on an internet connection for these devices. Would there be any benefit in downgrading firmware?
I migrated off of OpenWRT due to roaming issues (5GHZ devices would lose connection after roaming to another MX4300), and it seems DDWRT doesn't have this roaming issue. So while I'd prefer to stay on DDWRT because of this, it would be nice if this issue could be resolved as well. I'll continue to adjust some settings to see if I can get any changes.
Thanks for the suggestion, I'll try that next. I do have the Belkin, which I will use if I can't find a solution, so it isn't the end of the world. I just tried downgrading to DD-WRT v3.0-r58976 std (01/03/25), and it seems like the connection is stable. I just did an in-place upgrade without a reset (which I know isn't the best idea), and the pings are down to ~50ms consistently with no packet loss. I'll report back if it stays consistent, and if it does, I'll stay on this firmware. Are there any major issues with these earlier firmwares that I should be aware of?
Edit: It seems to be significantly better after downgrading, with only a single device giving minor issues now (that was working fine on OpenWRT). I’ll try the recommended settings given prior to see if there are any further improvements. As it stands now, this is nearly perfect, since the problematic device is merely a power meter, and isn’t sensitive to scheduled HomeAssistant actions.
Edit2: It seems that the issue happens between r60652 and r60662. 60652 is fine, 60662 isn’t (04/09/2025 -> 04/10/2025). Not sure if it’s possible to track what changed between those 2 versions.
