This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Why do I have to reboot my EAP225 before a Raspberry Pi Zero W will connect to it in a way that actually allows data to pass?
After a few hours the connection goes dead again.
Is TP-Link's implementation of 2.4GHz WiFi really brain dead?
The Raspberry Pi Zero W has a really old low power b/g/n class chipset and from experience found this doesn't like 40mhz wide channels
Try setting the width on the 2,4ghz to 20mhz with N only (if possible) and this might be more stable. From my experience with Pi devices like this, it causes the same problems regardless of vendors.. sadly too common!
@Philbert Thank you. I was already using 20MHz but I will try different combinations of bandwidth and mode to see if any work better. Weirdly I can see that the Pi Zero W usually manages to get an IP address assigned by DHCP but then nothing else will transfer over the connection.
@BrianG61UK Nothing works. :(
Helpful: 0
Views: 1027
Replies: 4
No one has voted for it yet.
We use cookies and browser activity to improve your experience, personalize content and ads, and analyze how our sites are used. For more details, please read our Privacy Policy.
