# DevKit contract

Every Sigfox Pycom device comes with free Sigfox connectivity - Sigfox DevKit contract. It provides one year of Sigfox connectivity. This is great for prototyping.

But every device you want to add to Pybytes you need register on Sigfox backend. You need to repeat [Sigfox activation procedure](/getting-started/registration/sigfox.md).

After you add your Sigfox credentials to Pybytes you can see DevKit contract type is selected as default (on page Settings → Sigfox API).

![](/files/-LKN86_qlgaBVLxrqnLk)

## Add your device to Pybytes

1. Create Sigfox device (Lopy4, SiPy, FiPy) in Pybytes and copy its device token to clipboard.
2. Connect your device to your computer and update it with Pycom firmware updater.
   1. Select Pybytes firmware
   2. Paste your device token to firmware updater

{% hint style="info" %}
Detailed steps which are same for all devices are [**described here**](/pybytes/connect/quick.md).
{% endhint %}

## Check sigfox status

Go to: Devices → \<your\_device\_name> → configuration

Now you should see sigfox status component.

Click on *Check Sigfox status* button

![](/files/-LKN86_uY2VVWye2M2Hv)

You should see two green lights.

First green light means that your device was found in Sigfox group which uses Sigfox API credentials you saved to Pybytes.

Second green light means that HTTP POST callback was created on Sigfox backend for your *Dev Kit* device type. Because Dev Kit device type is associated with Dev Kit contract (which can hold only one device), you need to create Sigfox callback for every device you add to Pybytes.

Note that Sigfox callback are associated to Sigfox device types.

This is not an issue with Custom contract, where *device type* on Sigfox backend can contain many devices, therefore you just need to one Sigfox HTTP POST callback (It is created automatically by Pybytes).

## Troubleshooting

[Disengage Sigfox sequence number](/tutorials-and-examples/sigfox.md#disengage-sequence-number)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://development-test.pycom.io/pybytes/connect/sigfox/devkit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.