Access Station

Access Station Micro Connectivity requirements Access Station Micro Utility Access Station Micro Datasheet Access Station Micro Quick Start Guide Access Station Micro Supported Countries, Safety & Certification information Access Station Micro Product Manual Access Station Micro Ethernet connectivity Access Station Micro Sealing cover Manual Access Station Micro troubleshooting

API

API documentation API versioning API credential creation API credentials renewal API rate limiting API Response code references Global Coverage API Timestamps format in API

Callbacks

Principles

Getting Started Callback and Connectors Callback medium Callback integration Custom callback creation Event callback creation Partner Callback creation

Data callback

Service callback

Status Acknowledge Repeater Data advanced

Error callback

Event callback

Event type Break in message sequence Off contract Out of message sequence On contract Receive first test message Receive first payable message Renewal Suspend Resume Replaced to Invalid private key Change device type Replaced by Intra transfer Extra transfer Restart Overusage Contract switch

Partner built-in callback

AWS IoT built-in callback AWS Kinesis built-in callback IBM Watson IoT Platform built-in callback Microsoft Azure Event hub built-in callback Microsoft Azure IoT hub built-in callback UnaConnect built-in callback

Callback troubleshooting

Callback error log Callback troubleshooting procedure

Backend user access management

Backend user creation: invitation Backend user timezone Deleting users from a group Backend user roles Backend user account creation Backend user role modification Page forbidden Reset Backend User password

Certification

Sigfox Certifications

Sigfox Certification Handbook Checklist for device based on another Sigfox Ready device -similarity-

Sigfox Radiated Performance tests

Be prepared for Radiated Performance Tests Sigfox Radiated Performance Test Specifications v2.0

Sigfox RF & Protocol tests

Be prepared for Sigfox RF & Protocol Tests v5.0.2 Sigfox RF & Protocol Test Specification v5.0.3 Sigfox RF & Protocol Test Procedure

Device HW

Device Current Drain : Downlink optimization Antenna Design for Sigfox Ready devices Sens’it antenna Oscillator Technical Note Battery Application Note

Device management

Device Type

Device type: meaning Create a new device type Contracts Payload display parameter Set a keep alive delay Communication status indicator

Principles

Radio Configuration Sequence number: general knowledge Sequence number: troubleshooting Link Quality: general knowledge Downlink information Downlink callbacks

Helpful

Industrialisation

How to test in production ?How to get Sigfox Credential from CRA ?Sigfox Credential provisioning for Open Software Architecture modules and SDK

SDR Dongle

Sigfox SDR dongle datasheet What is the public key and how to activate it?

Sigfox Network Emulator

Sigfox Network Emulator - User Guide Sigfox Ready™ modules compatibility Sigfox Network Emulator - troubleshooting

Radio Signal Analyzer

Radio Signal Analyzer - User guide

Sens'it

Sens'it v3 datasheet Sens'it v2 user guides Sens'it v3 user guide How to use Sens'it after closure of sensit.io application Sens'it Device all you need to know Sens'it for Sigfox learnings

Device managementDevice

Unsubscribe a device

This feature will allow you to terminate a valid token. Please be advised it will be permanently lost.

With group administrator privileges, this feature is available through the backend GUI and through API. If you do not have access to this feature, please reach out to your local Sigfox Operator.

Multiple contracts rule

Please be advised that a device unsubscribed from a multiple contract device type will be able to renew its subscription using a different valid contract from the list, unless its subscription automatic renewal is set to false at device-level or device-type-level.

GUI usage

If multiple valid contracts are associated with a device type the device will reactivate automatically, please refer to the previous section for details.

From the device information page, a SET button is displayed next to the Unsubscription date field.

If the current date is set the device will automatically go off-contract upon confirmation.

If a future date is set, the token will be terminated (the device will switch off-contract) when the date is reached. For yearly prepaid contracts (except for contracts purchased on buy.sigfox.com), the unsubscription date shall be set the day before the anniversary date (activation date + x Year(s) – 1day) to avoid a renewal of the subscription and associated fees.

Once a device is off-contract its subscription can be restarted using the Restart feature.

API usage

If multiple valid contracts are associated with a device type the device will reactivate automatically, please refer to the previous section for details.

The dedicated single and bulk endpoints are publicly documented in the API documentation.

If a past date is set the device will automatically go off-contract upon API request.

If a future date is set, the token will be terminated (the device will switch off-contract) when the date is reached. For yearly prepaid contracts (except for contracts purchased on buy.sigfox.com), the unsubscription date shall be set the day before the anniversary date (activation date + x Year(s) – 1day) to avoid a renewal of the subscription and associated fees.

Once a device is off-contract its subscription can be restarted using the Restart feature.

Force unsubscription

If you already used the Unsubscribe feature with a future date, please be advised that you can still force unsubscription by setting a past date with the dedicated API endpoint.

Can't find what you're looking for ?

Have questions? Our worldwide Community of expert fans can answer them.
Have answers? Join the Community and help!

Ask the community >