> For the complete documentation index, see [llms.txt](https://ask.simplehw.eu/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.simplehw.eu/kb/provisioning-and-device-setup/reconfiguration-of-the-devices.md).
# Reconfiguration of the devices
The devices can be configured either by downlinks or by local Over the Air (OTA) updates.
Firmware can be updated only by OTA update
For reconfiguration before deployment please use really good coverage better or at least at the level of provisioning coverage. Downlinks require better coverage than uplinks and Sigfox is pretty limited in how many downlinks each base station can process.
If you use direct downlinks in the Sigfox backend please erase them once the downlink is successful otherwise it is sent repeatedly.
Downlinks are confirmed by “DA” or “DB” messages which means that the downlink was received and successfully processed (that there was no problem eg. with syntax)
Usually, Sigfox or LoRaWan backends do not have implemented resending of downlink in case of a failed attempt. This feature has to be implemented on the IoT platform level. Please check if the IoT platform you are using supports that feature. If not you may need to put downling several times until downlink is successfully confirmed.
Note: it is OK to send the same downlink multiple times, repeated downlinks are confirmed as well but not processed.
**Sigfox**
1. Prepare the downlink in the backend or platform
2. Either wait for the heartbeat with a downlink request or do an extra-long press
3. Check the Sigfox backend - you should see the uplink messages and content of the downlink
Please be aware that Message confirmation means only that the Sigfox base station sent out the signal, this is very CONFUSING. It doesn't mean that the device received the message.
4. Check the backend to see how many base stations and how many frames got processed or at least whether coverage is good.
5. Check the successful downlink confirmation from the device. If not, go to step 1. If not succeeding repeatedly, get better coverage.
6. Record into the Project/provisioning document.
**LoRAWAN**
1. Prepare the downlink in the backend or platform
2. Either wait for the message or do an extra-long press
3. Check the LoRaWan/Helium backend - you should see the uplink messages and content of the downlink\
Please be aware that Message confirmation means only that the base station sent out the signal, this is very CONFUSING. It doesn't mean that the device received the message.
4. Check the backend and how many base stations are at which RSSI and assess whether coverage is good.
5. Check the successful downlink confirmation from the device. If not, go to step 1. If not succeeding repeatedly, get better coverage.
6. Record into the Project/provisioning document.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://ask.simplehw.eu/kb/provisioning-and-device-setup/reconfiguration-of-the-devices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.