Hi @joergent,

Some things to try:

1) if your radio uses the 2.4GHz radio, try a different channel.  Sometimes channel interference can cause connectivity errors

2) I have had connectivity issues with a small subset of non-PC devices (e.g. IoT, cameras, etc.) when "Air Time Fairness" is turned on.

3) I've also seen a variety of devices behave weirdly (across multiple vendor AP products) when band steering is enabled.  I always turn this off and use separate SSID's for each radio.

4) Make sure you update the EAP firmware to the latest version 2.7.0

5) If your clock/radio is an older device make sure the EAP is still set to support b/g devices

6) sometimes the transmit power of the AP can be too strong.  try turning it down to "medium"

Overall, the EAP's generally work great.  I have two EAP225V3's and an old EAP245V1 at home.  As well as the OC-200.  At any given time I have ~40 active devices on my home network which are generally moving 5-10GB per hour -- gaming, streaming, multiple VPN's for work, VOIP/Wifi calling, Nest cameras, a gagle of Alexa's, cloud backups, etc.

-Jonathan

@JSchnee21 

Thank you for your suggestions.

However, all your suggestions + more had been attempted except for lowering the transmit power, which changed the behaviour to 5 seconds sound between buffering with no sound. Changing the buffer from 2 to 8 seconds on the radio did not improve anything. Changing the location of the radio to the room with the EAP225 did not change anything.

Now the other access point is located right next to the radio and thus with very high transmit power next to the radio, and it is working, so the power is not really an issue.

The EAP225 firmware is a pre-release 2.6.2 which I am testing for TP-link. The highest version in Europe is 2.6.1.

However, as the radio previously has been working with the EAP225 I am assuming that it must be a software update, which has been breaking the connection.

It may be in the EAP225 or in the radio, which apparently is automatically updating its software. Falling back to the 2.5.0 version software of the EAP225 did not change anything, so I am assuming that the source of the problem must be located in the radio, and that the EAP225 is not as fault or deviation resistant as the Trendnet AP.

I just tried connecting the radio to my Samsung Galaxy S8 hotspot, and this is working

@R1D2 

Well, the 2.7.0 version is not available at the DK page, but I have now upgraded from the DE page and falled back again, as the guest network bug fix is not included in the 2.7.0 version and there was no difference in the connection problem.

FYI the radio has now been confirmed working fine with the Pixel 3 XL mobile hotspot as well, so more and more arrows are pointing towards a bug or partial protocol implementation in the EAP225