Skip to main content
FastMind— home
Current language
  • EnglishEnglish
  • DeutschGerman
  • FrançaisFrench
  • NederlandsDutch
  • ItalianoItalian
  • EspañolSpanish
  • PortuguêsPortuguese (Portugal)
  • PolskiPolish
  • ČeštinaCzech
  • SlovenčinaSlovak
  • MagyarHungarian
  • RomânăRomanian
  • БългарскиBulgarian
  • ΕλληνικάGreek
  • HrvatskiCroatian
  • SlovenščinaSlovenian
  • SvenskaSwedish
  • DanskDanish
  • Norsk bokmålNorwegian (Bokmål)
  • SuomiFinnish
  • EestiEstonian
  • LatviešuLatvian
  • LietuviųLithuanian
  • РусскийRussian
  • УкраїнськаUkrainian
  • СрпскиSerbian
  • TürkçeTurkish
  • العربيةArabic
  • עבריתHebrew
  • AfrikaansAfrikaans
  • हिन्दीHindi
  • 日本語Japanese
  • 한국어Korean
  • 简体中文Chinese (Simplified)
  • 繁體中文Chinese (Traditional)
  • ไทยThai
  • Tiếng ViệtVietnamese
  • Bahasa IndonesiaIndonesian
  • Bahasa MelayuMalay
  • Português (Brasil)Portuguese (Brazil)
Site menu

LoRa, Wi-Fi, Zigbee and Wired Control Compared

A condition-by-condition comparison of four control technologies for professional sites, where every cell names the condition its statement depends on.

LoRa, Wi-Fi, Zigbee and wired control solve different problems, and the choice depends on the site rather than on a single ranking. This comparison sets out how each behaves on range, power, network dependency and data throughput. On a real project the deciding factors are the cable that already exists, where the supplies are, and the cost of a new run.

LoRa, Wi-Fi, Zigbee and Wired Control Compared
LoRaWi-FiZigbeeWired
Typical design roleControl and status for points that are far apart or hard to cable, at low data rates.High-bandwidth access for people and devices where infrastructure and mains power already exist.Short-range mesh for many devices within one building, usually mains or battery powered.Direct, deterministic control where cable can be installed and a fixed topology is acceptable.
Range and penetrationLonger link across open and semi-open sites, subject to the band, the antenna, the enclosure, the mounting position, walls and a site survey.Depends on access point placement, walls, racking and channel congestion; designed for coverage near an access point.Reaches across a mesh, where each hop also carries other traffic; range depends on node density and building materials.Not a radio question. Distance is set by the cable type, voltage drop and the wiring rules that apply.
Power profileSuits battery-powered endpoints at a low duty cycle; battery life depends on the reporting interval, radio conditions and temperature.Higher continuous power; battery operation is limited and usually impractical for always-on endpoints.Can run on batteries at a low duty cycle, with power depending on whether the device acts as a router or an end device.Requires a permanent supply to each point; there is no battery question.
Network dependencyRuns on a private on-site gateway; the local rule set can continue while the wide area link is down.Usually tied to Wi-Fi infrastructure and often to an internet path; losing either interrupts control and reporting.Runs on a local coordinator and mesh; a cloud or internet link is separate and often optional.Depends only on the control wiring and the local controller; there is no radio link to lose.
Data throughputLow. Suited to commands, states and sensor values, not to streaming or large payloads.High. Suited to video, large files and high-rate telemetry.Low to moderate. Suited to device commands and short reports within one building.Depends on the protocol and cable; it can carry either high rates or simple contacts.
Behaviour when the uplink dropsLocal schedules and rules continue; remote dashboards and notifications pause and queue.Cloud, remote control and usually schedule or occupancy logic pause with the connection.Mesh control can continue if the coordinator and local logic stay online; cloud features pause.Control continues as long as the controller and the wiring are powered and healthy.
Commissioning and ecosystemNeeds a private gateway, an agreed channel plan and a site survey; the ecosystem is narrower and often project-specific.A wide device and tooling ecosystem, but it shares spectrum with other traffic and needs network expertise.A broad consumer ecosystem with vendor-specific profiles; interoperability depends on profiles and versions.Well understood by electricians, but any change to the layout means physical work at each point.

Where LoRa fits

  • Sites where control points are far apart and new control cable is expensive or disruptive to install.
  • Locations with no reliable Wi-Fi coverage and no wish to build one just for control.
  • Battery-powered sensing at a low reporting rate where mains is not available.
  • Installations that must keep a core rule set running while the internet or WAN link is down.
  • Retrofit projects that can reuse existing mains circuits instead of running new cable.

Where LoRa does not fit

  • High-bandwidth needs such as video, large file transfer or high-rate streaming.
  • Large payloads that must move quickly and often, beyond short commands and sensor values.
  • Dense interactive control where many users need immediate, high-frequency response.
  • Cases where a wired backbone is already installed and is cheaper and more deterministic to extend.
  • Positions where the environment or the available enclosures make a wireless link impractical, such as exposed marine or high-corrosion areas without suitable housing.