Access Station

Access Station Micro Connectivity requirementsAccess Station Micro UtilityAccess Station Micro DatasheetAccess Station Micro Quick Start GuideAccess Station Micro Supported Countries, Safety & Certification informationAccess Station Micro Product ManualAccess Station Micro Ethernet connectivityAccess Station Micro Sealing cover ManualAccess Station Micro troubleshooting

API

API documentationAPI versioningAPI credential creationAPI credentials renewalAPI rate limitingAPI Response code referencesGlobal Coverage APITimestamps format in API

Callbacks

Principles

Getting StartedCallback and ConnectorsCallback mediumCallback integrationCustom callback creationEvent callback creationPartner Callback creation

Data callback

UplinkBidir

Service callback

StatusAcknowledgeRepeaterData advanced

Error callback

Error callback

Event callback

Event typeBreak in message sequenceOff contractOut of message sequenceOn contractReceive first test messageReceive first payable messageRenewalSuspendResumeReplaced toInvalid private keyChange device typeReplaced byIntra transferExtra transferRestartOverusageContract switch

Partner built-in callback

AWS IoT built-in callbackAWS Kinesis built-in callbackIBM Watson IoT Platform built-in callbackMicrosoft Azure Event hub built-in callbackMicrosoft Azure IoT hub built-in callbackUnaConnect built-in callback

Callback troubleshooting

Callback error logCallback troubleshooting procedure

Backend user access management

Backend user creation: invitationBackend user timezoneDeleting users from a groupBackend user rolesBackend user account creationBackend user role modificationPage forbiddenReset Backend User password

Certification

Sigfox Certifications

Sigfox Certification HandbookChecklist for device based on another Sigfox Ready device -similarity-

Sigfox Radiated Performance tests

Be prepared for Radiated Performance TestsSigfox Radiated Performance Test Specifications v2.0

Sigfox RF & Protocol tests

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

Device HW

Device Current Drain : Downlink optimizationAntenna Design for Sigfox Ready devicesSens’it antennaOscillator Technical NoteBattery Application Note

Device management

Device Type

Device type: meaningCreate a new device typeContractsPayload display parameterSet a keep alive delayCommunication status indicator

Principles

Radio ConfigurationSequence number: general knowledgeSequence number: troubleshootingLink Quality: general knowledgeDownlink informationDownlink callbacks

Device

Register a deviceRegister a batch of devices in one goDevice ID/PAC coupleDevice and Token lifecycleMove a deviceSuspend & ResumeUnsubscribe a deviceStop a Sigfox subscription and billingSubscription automatic renewalDevice not communicatingDeleting DevicesRestart a device subscriptionEnd product certificateEdit multiple devices simultaneouslyReplace a deviceDevices being transferredBulk operationsExport a list of devicesOut Of Band (OOB) messagesOff-contract deviceDevice messages delayRegister as a prototypeSet device location

Helpful

GLOSSARY

Industrialisation

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

Products & Services

UnaConnectTest messages: Contract optionBackend user helpbook

Coverage

Display the Sigfox global coverageDisplay the Sigfox Monarch global coverageSigfox coverage maps .kmz filesSigfox Service map

Atlas Service

Actual device position outside of location radiusAtlas service callback creationNetwork location: service not availableLarge location radiusNetwork Location position moving over timeProvided location far from actual locationMessage location accuracyNo location provided for a messageLocations over seaAtlas service: Micro stations geographical coordinates

UnaBiz Ready-to-Use Products

UnaMKRUnaMKR (Mini)UnaBell LTE-MUnaReaderUnaSensorsUnaShield

Other

Sigfox Partner NetworkSigfox support portal login issuesTicketing tool login

SDR Dongle

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

Sigfox Network Emulator

Sigfox Network Emulator - User GuideSigfox Ready™ modules compatibilitySigfox Network Emulator - troubleshooting

Radio Signal Analyzer

Radio Signal Analyzer - User guide

Sens'it

Sens'it v3 datasheetSens'it v2 user guidesSens'it v3 user guideHow to use Sens'it after closure of sensit.io applicationSens'it Device all you need to knowSens'it for Sigfox learnings
Device managementDevice

Subscription automatic renewal

Before considering the subscription automatic renewal option, you should check the validity of the contract(s) associated with the device type (available tokens, activation end date and communication end date).

Example of situations where the subscription automatic renewal has no effect:

  • device type associated with a single contract purchased on the Buy platform: a subscription cannot be renewed on the same Buy contract, and no other contract is available to allow renewal.
  • device with a Token validity field = N/A : this means that the associated contract has no communication end date and no subscription duration defined for the associated tokens.

If in doubt, please contact your Sigfox operator directly for more information about your contracts and the application of subscription automatic renewal.

How to be sure that the renewal will be effective

If you want a device to keep communicating after the end of its subscription duration, please perform the following checks:

  1. If automatic renewal is enabled at device level, then check step 2. Otherwise, no renewal is allowed.

  2. If automatic renewal is enabled at the device type level, then check step 3. Otherwise, no renewal is allowed.

  3. If the renewal is enabled at the level of the contract that is still valid, automatic renewal will be effective. Otherwise, no renewal is allowed, but an automatic transition to another contract on the same device type is possible.

Subscription automatic renewal management

You can configure subscription automatic renewal at device, device type and contract level. A field has been added to these sections when registering and editing, be it a single item edit or a bulk edition.

The possible statuses are:

  • Allowed
  • Not allowed: disabled at one of the aforementioned levels
  • Ended: subscription already expired
  • Renewed: renewal already occurred

If the automatic renewal of the subscription is not allowed, a warning message is displayed.

In-depth

The automatic renewal feature is based on two items of a contract:

  • Subscription duration
  • Communication end date

The subscription duration is a timespan, set in contract's parameters (e.g. one year).

The communication end date is arbitrarily set when creating a contract (e.g. January 1st, 2021).

As an example, let us consider a contract starting on January 1st, 2018 with a one-year subscription duration and an communication end date set to January 1st, 2021.

A device is activated on this contract January 1st, 2018. If the subscription automatic renewal has been activated on all levels (as described above), its information page will display a token validity of 3 years. In case automatic renewal is disabled at one level the token validity will only be 1 year.

When a device has reached its token validity date and renewal or automatic transition to another contract is not allowed or not possible, the token status will change to "Off contrat" status on the next message received.

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!

slack logo

Ask the community >