We need reliable, real-world ~20mbit/s for our warehouse scanners, not 382722 theoretical Gbit/s 5cm from the access point. And roaming that works instead of stupid clients clinging to somewhere or being thrown into a reconnect loop when the AP tries to get them to roam. I know this is theoretically possible today. But in the real world, I have inherited the setup, so AP locations are fixed for now, clients are some random old handhold motorola android devices and interference is high.

In comparison, DECT has been flawless in the same space. Set and forget, just works. I always wondered if we could have a kind of DECT proxy on the LAN, and have the ERP application talk to that proxy using DECT... I mean, it's a few EANs and stuff, DECT could handle this easily.

Yeah you can run stuff through DECT I'm not sure what handheld suitable gateway you'd use and strap to the holster of the associated scanner, but otherwise...

That said, in theory at the level you're asking for it'd be acceptable to run the system as a single frequency network by using the AP locations as remote radio heads and just not telling the handhelds that there are multiple APs in listening range.

I'd probably aim for using the wifi support mechanisms to dynamically fake nearby APs as "mimo antennas" from the POV of the handheld, but not doing so would also suffice, just transmitting from the one AP that's nearest to the specific handheld/client would already basically do the trick and could probably run with hacked firmware on commodity AP hardware basically turning the entire setup into a soft-MAC with that very software juggling the army of radios.

The setup btw. would not have the clients aware they're dealing with more than one radio on the other side.

You could be forced to ask/ping the client from multiple APs one after another if you've not heard from it in a while and it moved, but otherwise, you just rely on hearing it from multiple APs and tracking it so you don't have to make APs across the facility speak up and risk interrupting other clients that try to get a word in.

Oh, and ban by building ordinance usage of any other Wi-Fi on the channel your doing this on, or that's gonna eventually get you problems with congestion.

I hadn’t realised that DECT is still in use. It was pretty good in its heyday so glad it’s survived.

I was recently made aware of WiFi HaLow. Official standard, ranges into the hundreds of meters. Speed suffers at long ranges of course, but still respectable (50-100kbs).

Link: https://en.wikipedia.org/wiki/IEEE_802.11ah

I've had similar issues with clients (Blink camera sync modules) connecting to far-away APs instead of the much closer router. I could not force them to connect directly to the router no matter what.

Turns out the 2.4 GHz radio of my router had died (Fritzbox 7590, apparently a common issue), thus forcing 2.4 GHz-only clients to use those other APs.

Sounds like your old, random clients might be a problem?

Warehouses, factories, etc need private 5G, not Wi-Fi.

LoRa is quite nice for this in the lower frequency bands, and the bandwidth should suffice for this sorta thing. And the tech is super cheap to build and maintain, both hardware and software is open source.

> or being thrown into a reconnect loop when the AP tries to get them to roam

The AP does not have visibility into what the client actually sees, and no, a coordinator that has knowledge what the APs see isn't that much better.

Imagine a situation with two APs and a client being in the middle of the two in a RF-impeded situation (i.e. your typical office building). AP1 may "hear" the client better (i.e. it gets a higher RSSI and SNR), but the client may reject it in favor of AP2 because the client sees a better signal coming from AP2 due to reflections, a powerful RF signal from a floor above interfering with the channel of AP1 or God knows what else.

RF is a weird world.

DECT or DECT-NR+?

I do kind of want to play with this.

Ensure your network has no <WiFi6 devices.