The confusing part is that 2.4 GHz is only a frequency range.

It is not a protocol, not a network type, and not a guarantee that two devices can talk to each other.

Many unrelated systems use that same radio band:

  • Wi-Fi
  • Bluetooth and Bluetooth Low Energy
  • Zigbee
  • Thread
  • 2.4 GHz ExpressLRS
  • proprietary keyboards, mice, sensors, and game controllers

They share the same air, but they use different radio rules.

The Short Version

System Band What It Is Typical Use
Wi-Fi 2.4 GHz, 5 GHz, 6 GHz IEEE 802.11 networking IP networking, internet access, local LAN traffic
Bluetooth / BLE 2.4 GHz Short-range device radio Headphones, phones, wearables, local mesh apps like Bitchat
Zigbee 2.4 GHz globally, plus some sub-GHz regional bands IEEE 802.15.4-based low-power mesh Smart-home sensors, plugs, bulbs, buttons
Thread 2.4 GHz IPv6 mesh over IEEE 802.15.4 Matter smart-home networks
ExpressLRS 2.4 GHz or 868/915 MHz Open radio-control link FPV and RC transmitter-to-receiver control

The useful mental model:

2.4 GHz = road
Wi-Fi, Bluetooth, Zigbee, Thread, ExpressLRS = different vehicles and traffic rules

Why They Cannot Understand Each Other

A Wi-Fi router cannot decode Zigbee just because both can use 2.4 GHz.

The radio chip and protocol stack have to match.

Wi-Fi device       -> IEEE 802.11 radio + IP networking
Bluetooth device  -> Bluetooth radio + Bluetooth stack
Zigbee device     -> IEEE 802.15.4 radio + Zigbee stack
Thread device     -> IEEE 802.15.4 radio + Thread/IPv6 stack
ExpressLRS gear   -> compatible RF chip + ExpressLRS firmware

That is why a phone can usually talk Bluetooth but not Zigbee. The phone has Bluetooth hardware and software, but it usually does not have a Zigbee radio.

It is also why a Zigbee sensor needs a coordinator. The sensor is not a Wi-Fi client and does not run an MQTT client. A coordinator speaks Zigbee radio, and software such as Zigbee2MQTT translates the sensor state into MQTT topics.

Wi-Fi

Wi-Fi is the high-bandwidth IP networking layer most people already know.

Use Wi-Fi when you need:

  • internet access
  • LAN access
  • video, web, file transfer, and software updates
  • devices that can afford more power draw

In the 2.4 GHz band, Wi-Fi channels are wide compared with Zigbee channels. That is why a busy Wi-Fi access point can make the band noisy for nearby low-power radios.

Bluetooth and Bitchat

Bluetooth also uses 2.4 GHz, but it is designed for short-range device links rather than normal IP networking.

Bluetooth Low Energy is especially useful for phones, wearables, local discovery, and small data exchanges.

In the Bitchat post, Bluetooth is interesting because it gives nearby devices a local transport path even when internet access is unavailable.

That does not mean Bitchat is Wi-Fi or Zigbee. It is an app and protocol design that uses Bluetooth as one transport.

Zigbee

Zigbee is designed for low-power, low-data-rate mesh networks.

Use Zigbee when you want:

  • battery sensors
  • simple switches and buttons
  • smart plugs, bulbs, and blinds
  • a local smart-home mesh that does not put every device on Wi-Fi

Zigbee devices usually do not get IP addresses. They join a Zigbee network managed by a coordinator.

For self-hosting, the common bridge looks like this:

Zigbee sensor
  -> Zigbee radio
  -> USB or network coordinator
  -> Zigbee2MQTT
  -> MQTT broker
  -> Home Assistant / scripts / dashboards

Useful link:

Thread

Thread is close to Zigbee at the radio layer because it also uses IEEE 802.15.4 in the 2.4 GHz band.

The important difference is the network model.

Zigbee has its own Zigbee networking/application stack. Thread is an IPv6-based mesh protocol, which is why it matters for Matter smart-home devices.

Simplified:

Zigbee = 802.15.4 radio + Zigbee stack
Thread = 802.15.4 radio + IPv6 mesh stack

Same kind of low-power radio foundation, different upper layers.

ExpressLRS

ExpressLRS is a radio-control link for FPV and RC hardware.

It is not Wi-Fi, Bluetooth, or Zigbee. It is firmware and protocol logic for compatible transmitter modules and receivers.

ExpressLRS hardware exists for 2.4 GHz and 868/915 MHz. Its job is not general networking. Its job is to move RC control data and telemetry between pilot and aircraft with the right latency, range, and reliability trade-offs.

Useful link:

Why Coexistence Mostly Works

These protocols coexist because they do not all transmit in the same way.

They differ by:

  • channel width
  • modulation
  • transmit power
  • packet size
  • retry behavior
  • hopping or channel-selection behavior
  • how often they transmit

Bluetooth and ExpressLRS can hop or change radio behavior depending on mode. Zigbee is low-power and sends small packets. Wi-Fi tends to be louder and wider, but it is not transmitting constantly at maximum rate.

Coexistence is not magic. It is just enough coordination, retries, and unused airtime for many devices to share the same band most of the time.

Why Interference Still Happens

Interference happens because the radios are still putting energy into nearby frequencies.

Common problems:

  • a Zigbee coordinator plugged directly into a noisy USB 3 port
  • a coordinator too close to a Wi-Fi access point
  • a metal server case blocking or reflecting radio signals
  • too many 2.4 GHz Wi-Fi devices close to low-power sensors
  • poor antenna orientation
  • laptops, SSDs, hubs, and displays creating local RF noise

For Zigbee, a simple USB extension cable can make a large difference because it moves the coordinator away from the computer chassis and USB noise.

Practical Rules

For homelab and smart-home setups:

  1. Use 5 GHz or 6 GHz Wi-Fi for high-bandwidth devices when possible.
  2. Keep the 2.4 GHz Wi-Fi channel plan simple.
  3. Put Zigbee coordinators on a USB extension cable.
  4. Keep Zigbee coordinators away from routers, SSDs, USB 3 hubs, and metal cases.
  5. Do not assume a 2.4 GHz device can talk to another 2.4 GHz device.
  6. Match the protocol, not only the frequency.