3 ms·
I will start by saying I am not an embedded engineer. Given that I am but a consumer of about a dozen different IoT devices, I would love it if embedded wifi ch
by ipython 3y ago
I will start by saying I am not an embedded engineer. Given that I am but a consumer of about a dozen different IoT devices, I would love it if embedded wifi chipsets didn’t suck so much. I don’t care if it’s WiFi 4, just make them not suck.
Each manufacturer seems to have their own little quirks you need to work around: one device only works well on 2.4 channel 1, another will aggressively roam to other access points (even though it and the ap are stationary, and the closest ap has < -60dbm signal). Even the most relatively well behaved modules will disconnect and reconnect constantly (average connection time is ~10 minutes to an hour, mind you the device is constantly connected to mains power). God forbid you enable any 802.11 extensions on the radio servicing those devices, then you’re really in for a world of hurt.
Then when you complain to the manufacturer, you get super helpful advice like “factory reset your router” and “open the following 28 ports through your nat gateway to our device” (sooooo… and if I have two of your devices, what then?). It’s a total shitshow.
- fusslo 3y agoAs an embedded engineer, I also wish wifi chipsets didn't suck so much Back when I was working on homekit smart products, we would test our products against a huge swath of wifi routers, including apple's. There was a handful of conformity tests we'd run, including Bonjour, DHCP, arp, etc. I don't think a single router passed every test, including Apple's. So our wifi stack was pretty good, but we also had to watch out for all these corner cases of different vendors and how they don't behave to spec. Its been about 6 years since I was full time in wifi, and I hope we've progressed, but I doubt it