52 Sigfox Assessment and Review
52.1 Introduction
This chapter provides comprehensive assessment questions to test and reinforce your understanding of Sigfox technology, deployment considerations, and comparison with alternative LPWAN solutions.
By the end of this assessment, you will be able to:
- Evaluate Sigfox technical specifications against application requirements
- Analyze real-world deployment scenarios and diagnose connectivity failures
- Justify technology selection decisions using quantitative cost and constraint analysis
- Differentiate common deployment pitfalls from best practices in LPWAN projects
Key Concepts
- Sigfox Assessment: Evaluation of Sigfox technology understanding including ultra-narrowband modulation, 12-byte payload limit, 140 uplinks/day constraint, and network model.
- Ultra-Narrowband (UNB): Sigfox’s physical layer modulation using 100 Hz channels within 200 kHz band; extremely narrow transmission enables high sensitivity but limits data rate.
- Sigfox Network: Originally operator-managed public network; Sigfox SA filed for insolvency in 2022; network was acquired by Unabiz with continued operation commitment.
- Payload Constraints: Sigfox uplinks limited to 12 bytes maximum; downlinks limited to 8 bytes and 4 per day; requires aggressive payload encoding for sensor data.
- Duty Cycle: Sigfox devices limited to 140 uplink messages per day (approximately one every 10 minutes); harder payload budget than LoRaWAN duty cycle restrictions.
- Sigfox vs. LoRaWAN: Sigfox provides managed network with no gateway investment; LoRaWAN enables private deployment and larger payloads; both target similar IoT use cases.
- Assessment Topics: Technical understanding evaluated includes modulation parameters, coverage characteristics, payload limitations, and use case suitability.
This assessment tests your understanding of Sigfox, a low-power wide-area network designed for sending very small messages from millions of devices. Sigfox takes a radically simple approach: devices can send up to 140 messages per day, each only 12 bytes. Test your knowledge of this unique IoT communication technology.
“Time to prove you know Sigfox inside and out!” said Max the Microcontroller, handing out quiz papers. “Remember the key numbers: 12 bytes per message, 140 messages per day, Ultra-Narrow Band modulation, and up to 50 kilometers range.”
Sammy the Sensor reviewed his notes. “The biggest constraint is the message limit. 140 uplinks per day means I can only report every 10 minutes. If I need more frequent updates, Sigfox is not the right choice.” Max nodded. “And downlinks are even more limited – only 4 per day. So forget about sending real-time commands to Sigfox devices.”
“Think about the real scenarios,” advised Lila the LED. “A water meter that reports once per hour? Perfect for Sigfox – 24 messages per day, well within the limit. A GPS tracker that needs updates every 30 seconds? Impossible – that would need 2,880 messages per day. Know the boundaries.”
Bella the Battery gave her final study tip. “When comparing Sigfox to alternatives, remember its sweet spot: low data, long range, low cost, zero infrastructure. A Sigfox subscription costs about 1 dollar per device per year. But you are locked into one operator’s network, and if they have coverage gaps, there is nothing you can do. Always check coverage maps before committing.”
52.2 Prerequisites
Complete all previous Sigfox chapters before this assessment:
- Sigfox Technology Overview: Core technology and architecture
- Sigfox Message Flow: Communication patterns and constraints
- Sigfox Deployment: Use case suitability and best practices
- Sigfox Hands-On Lab: Practical implementation experience
52.3 Comprehensive Quiz
52.4 Scenario-Based Questions
The Mistake: “If I have 4G coverage here, Sigfox will work too, right?”
Why This Fails:
Sigfox and cellular networks use completely different infrastructure:
| Network Type | Base Stations | Frequency | Coverage Model |
|---|---|---|---|
| Cellular (4G/5G) | ~5,000-10,000 per metro area | 700-2600 MHz | Dense urban deployment |
| Sigfox | ~100-500 per metro area | 868/902 MHz | Wide-area sparse deployment |
Real-World Scenario:
A logistics company deployed 2,000 Sigfox trackers for warehouse inventory, assuming coverage existed because they had excellent 4G cellular service.
What happened: - Indoors: 4G worked fine (high frequency penetrates via windows, microcells) - Sigfox: 73% message failure rate indoors (fewer base stations, RF shadowing) - Cost: $24,000 wasted on hardware for 1,460 non-functional devices
Why Sigfox Is Different:
- Fewer Base Stations: Cellular has 50-100× more towers than Sigfox in most cities
- Lower Frequency Helps Range BUT: Fewer stations means gaps between coverage zones
- Indoor Penetration: 868 MHz penetrates better than 2.4 GHz, but with only 1-2 nearby Sigfox towers vs. 20+ cell towers, indoor reliability suffers
- Practical RSSI Threshold: Although Sigfox’s UNB sensitivity reaches -142 dBm, reliable multi-message delivery typically requires -126 dBm or stronger. Cellular works down to -110 dBm and uses power control to compensate
Correct Pre-Deployment Process:
- Check Coverage Map: Visit
backend.sigfox.comand verify operator coverage zones - Pilot Test: Deploy 50-100 test devices at ACTUAL installation locations
- Measure Success Rate: Monitor for 30 days
- Target: >95% message delivery
- Acceptable RSSI: -110 to -126 dBm (comfortable margin above -142 dBm UNB sensitivity)
- Document Dead Zones: Map locations with <90% success rate
- Mitigation Options:
- External antenna: +3-5 dB gain (moves -125 dBm → -120 dBm)
- Relocate device: Move 5m toward window (can gain 10-20 dB)
- Alternative technology: Switch to LoRaWAN (deploy gateway on-site)
Coverage Reality Check (2024 data):
Urban Area Coverage Quality:
- Western Europe: Good (85-95% area coverage)
- US Major Cities: Moderate (60-80%, gaps in suburbs)
- Rural Areas: Sparse (20-40%, highways and towns only)
- Indoors (metal buildings): Poor (30-50% even in covered zones)
- Basements: Very Poor (5-15%)Cost of Skipping Pilot Test:
- Pilot test: $5,000 (100 devices × $50)
- Failed deployment: $50,000-$200,000 (thousands of unusable devices)
- ROI of testing: 10-40× savings
Key Takeaway: Cellular coverage is NOT a reliable predictor of Sigfox coverage. Always pilot test with real devices in the actual deployment environment before committing to mass production. The $5,000 pilot investment can save you $200,000 in deployment failures.
52.5 Summary and Key Takeaways
52.5.1 Sigfox Technology Summary
Sigfox provides a complete LPWAN solution through its proprietary network-as-a-service model:
Key Specifications:
| Parameter | Value |
|---|---|
| Uplink payload | 12 bytes maximum |
| Uplink messages | 140 per day |
| Downlink payload | 8 bytes maximum |
| Downlink messages | 4 per day |
| Data rate | 100 bps uplink, 600 bps downlink |
| Range | 3-10 km urban, 30-50 km rural |
| Sensitivity | -142 dBm |
| Battery life | 10-20 years possible |
Key Advantages:
- Lowest device cost (~$5-15 per module)
- Simplest device implementation
- No infrastructure investment required
- Global coverage through single subscription
- Built-in geolocation (Sigfox Atlas)
Key Limitations:
- 140 messages/day maximum
- 12-byte uplink payload limit
- 4 downlink messages/day maximum
- Operator dependency (cannot self-deploy)
- Proprietary protocol (vendor lock-in)
- Coverage gaps in some regions (Asia, Africa)
Best Applications:
- Smart metering (water, gas, electricity)
- Infrequent asset tracking
- Environmental sensors (agriculture, weather)
- Smart city infrastructure (waste, parking, lighting)
- Any application with < 100 messages/day and small payloads
When to Choose Sigfox:
- Small-scale deployments (< 5,000 devices)
- Maximum battery life required
- Simplest possible device design
- No technical team to manage infrastructure
- Acceptable coverage exists in deployment area
- No data privacy concerns with operator network
52.5.2 Comparison with Alternatives
| Feature | Sigfox | LoRaWAN | NB-IoT |
|---|---|---|---|
| Deployment | Operator only | Private or public | Cellular operator |
| Payload | 12 bytes | 243 bytes | 1600 bytes |
| Messages/day | 140 | Unlimited | Unlimited |
| Bidirectional | Very limited | Full | Full |
| Device cost | $5-15 | $10-25 | $8-20 |
| Coverage | Regional | Deploy anywhere | Global (cellular) |
| Best for | Simple sensors | Flexible IoT | Critical IoT |
Common Pitfalls
Sigfox is limited to 12 bytes for uplinks, significantly less than LoRaWAN’s 51–222 bytes. Assessment questions frequently test this distinction. Memorize Sigfox: 12 bytes up / 8 bytes down, and contrast with LoRaWAN’s larger payload capacity.
Sigfox’s 140 uplinks/day limit is easily confused with hourly calculations. 140/day averages to ~6/hour, but the limit is daily total, not hourly rate. Burst patterns (many messages in a short period) can exhaust the daily budget early.
Following Sigfox SA’s 2022 insolvency and Unabiz acquisition, network availability and long-term commitments changed. Assessment answers should acknowledge the operator risk dimension when evaluating Sigfox for new deployments.
Sigfox allows only 4 downlinks per day and only during the 20 seconds after an uplink. This makes Sigfox unsuitable for applications requiring device reconfiguration, firmware updates, or actuation. Always check downlink requirements when evaluating Sigfox suitability.
52.7 What’s Next
Now that you have completed the Sigfox assessment, explore related LPWAN technologies:
| Order | Chapter | Focus |
|---|---|---|
| 1 | NB-IoT & LTE-M Fundamentals | Compare Sigfox with cellular IoT standards |
| 2 | Weightless Protocol | Explore open-standard LPWAN alternatives |
| 3 | LPWAN Comparison and Review | Side-by-side comparison of all LPWAN technologies |
| 4 | MQTT Protocol | IoT application-layer messaging patterns |