Sidewalk – iotconnect

Amazon Sidewalk

/IOTCONNECT™ integrates with Amazon Sidewalk — a shared, low-bandwidth network that connects IoT devices beyond the range of home WiFi. Sidewalk uses existing compatible Devices as Bridges, creating a neighborhood-level mesh network that typically does not require users to purchase or manage their own gateway.

What is Amazon Sidewalk

Amazon Sidewalk is a shared, low-bandwidth wireless network that helps IoT devices work better at home and beyond the front door. It uses Bluetooth Low Energy (BLE), 900 MHz (FSK), and LoRa radio protocols to provide connectivity to low-power endpoint devices.

Key difference from other wireless protocols: With Sidewalk, you do NOT need to purchase, configure, or manage a gateway. Compatible smart home devices already deployed in neighborhoods act as Sidewalk Bridges (gateways), creating a community-operated shared network.

How it works:

Sidewalk endpoint (your Device): A battery-powered sensor or tracker that communicates via BLE or sub-GHz radio.

Sidewalk Bridge: Existing compatible smart home devices (echo, ring, etc.) that relay Sidewalk signals to the cloud using a small portion of the owner’s bandwidth.

Amazon Sidewalk cloud: Routes the data to the appropriate AWS account and destination.

/IOTCONNECT™ Platform: Receives, decodes, stores Telemetry, and enables Commands and Device management.

Network characteristics:

Feature	Specification
Coverage	Neighborhood-level (extends beyond WiFi range)
Bandwidth	Low (designed for small, infrequent messages)
Power	Ultra-low power (Potential for multi-year battery life, depending on usage and hardware)
Cost	No recurring network fees — uses community Bridges
Region	United States only (currently)
Protocols	BLE, 900 MHz FSK, LoRa (sub-GHz)
Gateway Required	No — uses existing Sidewalk Bridges automatically

When to Use Sidewalk

Sidewalk is ideal when:

No gateway infrastructure: You need connectivity without purchasing or managing gateways.

Extended range beyond WiFi: Devices are in yards, garages, sheds, or nearby outdoor areas beyond WiFi reach.

Low data rate is acceptable: Your devices send small packets infrequently (temperature, door status, location pings).

Currently supported in the United States: Your target market is the United States (current Sidewalk availability).

Battery-powered Devices: Ultra-low power consumption is critical for multi-year battery life.

Typical use cases:

Asset tracking: Track pets, packages, tools, or equipment beyond WiFi range.

Smart home extended: Mailbox sensors, garden moisture, driveway motion — Devices too far for WiFi.

Environmental monitoring: Outdoor temperature, humidity, air quality in neighborhoods.

Leak Detection: Water leak sensors in detached garages, basements, or crawl spaces.

Smart Lighting: Outdoor lights and motion sensors beyond WiFi infrastructure.

Architecture

The Sidewalk data path in /IOTCONNECT™:

Layer	Component	Role
1. Endpoint	Your Sidewalk Device	Reads sensors, encodes data, transmits via BLE/sub-GHz radio
2. Bridge	Sidewalk Bridge (community devices)	Receives radio signals, forwards to cloud via home internet
3. Cloud Network	Amazon Sidewalk Cloud	Routes data to your AWS account, manages device identity
4. Processing	/IOTCONNECT™ Lambda	Decodes payload, maps to template attributes
5. Application	/IOTCONNECT™ Platform	Stores telemetry, triggers rules, delivers to dashboards

Key architectural difference from LoRaWAN: Sidewalk Bridges are NOT managed by you. They are existing consumer devices in the neighborhood that participate in the Sidewalk network automatically. Your Sidewalk endpoint device roams freely — connecting to any available nearby Bridge without explicit pairing or configuration.

Onboarding Modes

/IOTCONNECT™ supports two Sidewalk onboarding modes:

Mode	Purpose	Certificate Source	Scale	Status
Prototype Mode	Development and testing	Generated by /IOTCONNECT™	Single Device	Available
Production Mode	Mass manufacturing	Provisioned in factory via AWS pipeline	Thousands+	Planned

Prototype mode is designed for developers building and testing Sidewalk applications. It provides quick single-Device provisioning with certificates generated directly from /IOTCONNECT™.

Production mode (coming soon) will integrate with the AWS Sidewalk manufacturing pipeline, enabling bulk Device onboarding where certificates are provisioned during factory manufacturing — not from the portal.

Device Onboarding (Prototype Mode)

Prerequisites:

/IOTCONNECT™ account with Wireless Device module access

Sidewalk-compatible hardware development kit

Firmware development environment for your hardware platform

Sidewalk Bridge coverage in your area (US only)

Step 1: Create a Template

Navigate to Wireless Device → Templates and create a template with Sidewalk transmission type. Define attributes matching your Device’s sensor outputs and commands for downlink control.

Step 2: Create a Sidewalk Device

Navigate to Wireless Device → Create Device and fill in:

Field	Description	Notes
Transmission Type	Select “Sidewalk”	—
Unique ID	Permanent Device identifier	Cannot be changed after creation
Device Type	Select your hardware platform	Matches your development kit
Display Name	Human-readable label	Editable later
Entity	Organizational unit	For multi-tenant management
Template	Sidewalk template from Step 1	Defines data schema
Notes	Optional description	Location, purpose, etc.

3. Click Save (or Save & View).

Step 3: Download Device credentials

After saving, /IOTCONNECT™ auto-provisions the Sidewalk endpoint and generates credentials:

Download the .zip file from the Device list containing the Device provisioning hex file.

This hex file contains the Sidewalk endpoint credentials needed for Device authentication.

Step 4: Flash the Device

Flash the downloaded hex file to your hardware development kit using your platform’s programming tool.

Also flash your firmware application hex file that implements your sensor logic and Sidewalk SDK communication.

Both the credential hex and application hex are required for the Device to function.

Step 5: Verify connection

Power on the Device within range of a Sidewalk Bridge. The Device will automatically discover and connect to any nearby Bridge. Check the /IOTCONNECT™ portal — the Device should show activity in the Last Communication field typically, within a few minutes, depending on Bridge availability

Telemetry and Commands

Telemetry (Device → Cloud):

Your Sidewalk Device sends uplink messages containing sensor data. The /IOTCONNECT™ Lambda function decodes the payload and maps it to your Template Attributes. Data appears in the Live data section of the Device details page.

Sidewalk supports both confirmed and unconfirmed uplinks:

Unconfirmed: Fire-and-forget — Device sends without waiting for acknowledgement. Best for regular Telemetry.

Confirmed: Device waits for cloud acknowledgement. Use for critical data that must not be lost.

Commands (Cloud → Device):

Send downlink Commands from the /IOTCONNECT™ portal to control Device behavior. Each Command includes:

Command payload (encoded by the platform)

Acknowledgement flag — when true, the Device must confirm execution (success / failed)

Commands are queued in the Sidewalk cloud and delivered when the Device is next reachable through a Bridge.

Prototype vs Production Mode

Feature	Prototype Mode	Production Mode (Planned)
Certificate generation	Generated in /IOTCONNECT™ portal	Provisioned in factory
Bulk onboarding	No — one Device at a time	Yes — CSV import with SMSN
Manufacturing integration	No	Yes — AWS Sidewalk manufacturing pipeline
Manual flashing required	Yes	No — factory-provisioned
Device Profile (Key Vault)	Not required	Required — shared with contract manufacturer
Scale	Single Devices	Designed for large-scale deployments
Suitable for production	No	Yes

Production mode (planned) will add:

Device profile creation from Settings → Key Vault for sharing with manufacturers

Bulk Import via CSV file with SMSN (Sidewalk Manufacturing Serial Number) and Unique ID columns

Automatic Device creation in AWS Sidewalk from the imported CSV

Sidewalk vs LoRaWAN

Both are LPWAN protocols for IoT, but they serve different scenarios:

Feature	Sidewalk	LoRaWAN
Gateway needed	No — uses community Bridges	Yes — private or public network
Coverage	Neighborhood (depends on Bridge density)	Up to 15km with your own gateway
Region	US only	Global
Cost	No network fees	Gateway hardware cost (private) or network fees (public)
Bandwidth	Very low (~80 bytes/message)	Low (~51-242 bytes/message)
Control over network	None — community-operated	Full (private) or partial (public)
Best for	Consumer / residential IoT in US	Industrial / commercial IoT globally
Device management	No gateway management needed	Gateway provisioning required

Troubleshooting

Issue	Possible Cause	Solution
Device not communicating	No Sidewalk Bridge nearby	Verify Bridge coverage — move Device to an area with known coverage
No data in portal	Hex file not flashed correctly	Re-flash both credential hex and application hex to the Device
Device not appearing	Wrong credential file used	Download fresh credentials from /IOTCONNECT™ and re-flash
Intermittent connectivity	Bridge at edge of range	Move Device closer to known Bridge locations
Command not delivered	Device not reachable	Commands queue and deliver when Device next communicates — wait for next uplink
Telemetry attributes mismatch	Template doesn’t match payload	Verify template attribute names match decoder output exactly (case-sensitive)

FAQ

Q: Do I need to buy a gateway for Sidewalk?

No. Sidewalk uses existing community Devices (Echo, Ring, etc.) as Bridges. You do not purchase, configure, or manage any gateway infrastructure.

Q: Is Sidewalk available outside the US?

Currently no. Amazon Sidewalk is only available in the United States. For global deployments, consider LoRaWAN.

Q: What happens if the nearest bridge goes offline?

Your Device can connect to another available Bridge if one is within range. The network is resilient — multiple Bridges typically cover the same area.

Q: How much data can I send?

Sidewalk is designed for small, infrequent messages (~80 bytes). It is NOT suitable for streaming video, audio, or large file transfers. Typical use: sensor readings every 5-30 minutes.

Q: Can I use Sidewalk for real-time control?

Sidewalk has variable latency depending on Bridge availability. For real-time control (<1 second response), consider WiFi or direct MQTT. Sidewalk is better suited for monitoring than real-time actuation.

Q: What’s the battery life expectation?

Depending on hardware, message frequency, and environmental conditions for typical sensor use cases (readings every 15-30 minutes). Exact life depends on message frequency and payload size.

Q: Can I see live connected / disconnected status?

No. Due to the nature of Sidewalk (community Bridges, roaming endpoints), /IOTCONNECT™ shows last communication time rather than live connection status.

ⓘ LIMITATIONS

Region: Sidewalk is supported in the US only.
Connection status: Live connected / disconnected status is not available — only last communication time is shown.
Shadow / Twin: Device shadow updates are not supported for Sidewalk Devices.
Message rate: Limited by Sidewalk network policies — designed for infrequent small messages.
Bridge dependency: Device connectivity depends on community Sidewalk Bridge availability in your area — coverage is not guaranteed.