I upgraded my router os do version 7.20.4 after that my older devices stop working. They cannot obtain IP adress from DHCP and on Wireless page on WinBox shows, show TxRate:
As a test, can you set the 2.4 GHz WiFi to ‘b/g’ only mode?
For ESPEasy I always advice users to test in b/g only mode, as these do not know about newer features like band steering and WiFi mesh features (and other features introduced in ‘n’ mode)
What I often see happening with ‘modern’ access points is that they quickly force a disconnect to let the node try to reconnect either on 5 GHz band, or some other WiFi mesh access point. And other disconnect reasons like 4-way handshake error, etc.
If you force the node to connect using 802.11g mode, then all those newer WiFi features are not trying to mess up your connection.
If you can’t set it on your node, then maybe set the access point to only advertise ‘b/g’ mode.
I don’t know if this also disables other features of the access point, but at least it will help you diagnose the issue a bit more.
When you decide to try upgrading again, I’m interested what went wrong as I also have AX^3, still on 7.19.4 though.
I upgraded my router os do version 7.20.4 after that my older devices stop working. They cannot obtain IP adress from DHCP
Configuration and logs are essential to begin troubleshooting. It would be worth sharing full configuration and logs as very first step. As first sight wireless configuration is ok while DHCP server configuration needs an attention.
They cannot obtain IP adress from DHCP and on Wireless page on WinBox shows, show TxRate:
does this device have action:accept on the “Access list” tab? How many devices are connected to that wireless interface at a time?
Up to upgrade router os printer and sonoff device works fine without any problems with connect & obtain IP address.
Are those devices successfully connected to 5GHz while older devices on 2.4GHz only end up on Registration List but can’t get DHCP address lease? Do these interfaces share the same subnet? How large is this subnet? How long is lease time? How many addresses are available to give?
On 2.4GHz radio I'd definitely go with channel width only 20MHz ... 2.4GHz band tends to be crowded and with only 20MHz channels things will be slightly better (better chance of finding channel with only mild interference, 3dB higher Tx power also helps) and it's more standard (up to 802.11N it was only option in 2.4GHz, legacy devices might freak out if they see features they don't understand). The "freak out" stance also applies to any other modern features, such as WPA3, GCMP, FT or anything newer than device's own 802.11 generation.
Also beware that some clients associate more than only SSID to the WiFi PSK stored. When settings change (such as encryption type, e.g. WPA -> WPA2 or even WPA3), then it might be necessary to "make them forget" the WiFi network and re-enter WiFi password.
Some people get around these problems by adding a slave interface with different SSID and different (legacy) security parameters ... tailored for those legacy (IoT et.al.) devices. Unfortunately that's not a solution for radio features (channel width, radio standard) because they are shared by all wifi interfaces running off the same radio (master and all slaves).
