Pitfalls you want to avoid in your LoRaWAN Asset Tracking projects
summary
Recommendations and hard lessons from many LoRaWAN asset tracking rollouts: require two gateways minimum and plan networks per site with IT and testing; expect onboarding complexity when scaling from hundreds to thousands with five or six downlinks per device and bulk configuration tooling; anticipate hardware rejects — about 2% defective units in large batches; watch BLE indoor setups where open doors cause outdoor bleed and GPS reflections off metal need algorithmic correction; reduce recurring costs by implementing local localization and device management.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:29Types of Asset Tracking Projects
- 2:18Pitfalls
- 4:34Onboarding
- 7:44Indoor tracking
- 10:26GPS
- 13:10Operation
- 19:16Pro Product
- 21:11Outro
related talks
15mHow to design LoRaWAN® products for scale
18mReality Check on Total Cost of Ownership in Asset Tracking
12mHow to optimise LoRaWAN for Agricultural deployments in rural areas and high plant density
27mDo's and don'ts: Electronics manufacturing and LoRaWAN devices
23mUnlocking economies of scale for LoRaWAN® deployments
28mWhat matters in LoRaWAN Smart building deployments?
23mLoRaWAN network planning, build overcapacity or plan?
24mMass Deployment of LoRaWAN Sensors