This has been an arduous journey that's not quite over yet. I think there is something to still be done within the Zebra scanner that I haven't touched upon yet. Meraki MR-76s running 28.6 in all warehouses. Band steering turned off. SSID for scanners only announced on 2.4GHz. No visible interference in RF spectrum. Channel usage for 2.4GHz always in 'Acceptable' range. Minimum bitrate reduced to 6Mbit for this SSID. Transmit power for these MR-76s Radio Profile expanded to 20dBm for 2.4GHz. Warehouse 1 - All Zebra MC9300s are Android 10, not fully patched beyond patch revision 70. All Zebra MC9300s are using same TE application and version All Zebra MC9300s have WiFi profile deprecated to see only 2.4GHz All Zebra MC9300s have WiFi 'Never Sleep' applied through StageNow Warehouse 2 All Zebra MC9300s are on Android 8, never patched after purchase All Zebra MC9300s have same version of TE application All Zebra MC9300s have WiFi profile deprecated to see only 2.4GHz All Zebra MC9300s have WiFi 'Never Sleep' applied through StageNow The dropout rate has remained very painful for both warehouses' shipping staff. In most all the cases where a scanner has dropped its session with the host destination in the TE application, the device remains pingable from the AP. Around 80% of the time, the device is pingable from other locations in the networks on different segments that allow two-way conversations and don't have firewalls between. It's as though the device's application suite has one application go dormant and then stifles all the remaining tools. And, that application isn't the one that's being used to access order fulfillment via the TE. If anyone has insights about what additional factors in the Meraki's Radio Settings that could be manipulated, I would greatly appreciate it.
... View more