Datalogger Wi-Fi shortcomings

[Wifi_dude]

I have a W3 Smart WiFi stick (hw version 1.03, sw version 3.16) plugged into my H3.
After much banging of my head, I realized that it could only connect to my router if I set this in mixed g/n mode.
Now, this isn't really a big deal but as reported here and elsewhere the datalogger is based on a ESP-WROOM-02U chip.
According to its specs it should be perfectly able to support 802.11n (maybe not all the bands and data rates there is, but still). How is this not the actual case in practice? Even 10 years ago that should have been the norm.

Secondarily, all is configured fine and dandy and I'll have to grant the app-less setup is pretty nice.. But why is the W-xxxxx SSID continuing to show up even afterwards? It doesn't transmit anything ofc, but it still skews automatic WLAN channel allocation.
I understand that one would want to re-configure it at a later time, but I don't think it should be all that big of a coding deal if the ESP8266 switched from AP mode to just basic STA when associated/connected? Maybe with a further 2-3 minutes grace period after boot, if you really wanted to be sure.
EDIT: ok in retrospect I found out that the dongle frequency just follows the one of the access point it is connected to. Still, it would be cool if a firmware update came to hide it like happened with Daikin AC

[Will]

I've suggested to Fox that users should be able to turn off AP mode once installed and working.

[Wifi_dude]

To be fair, of those things supporting wi-fi 4 was the most important.
Both because it will avoid headaches with people that set up their router in N-only mode.. but also because it would be kinda sweet to be able to use that in the first place (of course the datalogger takes very little airwaves time, but it is my understanding that dropping compatibility with the 20+ years old standard allows to save some non-insignificant overhead).