FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Sigfox Backend Not Assigning Token to Registered Device

Taksh
Associate II

‎2024-11-22 04:39 AM - edited ‎2024-11-22 08:44 PM

Hello Everyone,

I hope you are doing well.

I am currently testing the Sigfox_AT_Slave example from the STM32WL repository. My end device is configured with an ID, PAC, and Key for the South Africa region (RC = 1), as provided by the Sigfox build team. The device is located in South Africa, and all tests are being conducted within the region.

Here’s the current status of my setup:

  • The device is successfully registered on the Sigfox backend server using the provided ID and PAC.
  • I have one available token for the device.
  • The end device is able to send uplink messages successfully multiple times using the AT commands from the Sigfox_AT_Slave example.

Issue:
Despite successful uplink transmissions, the token field on the Sigfox backend server remains as "?" and is not automatically assigned to the device.

According to the Sigfox support documentation, the token should automatically be assigned upon the device's first uplink. However, in my case, this is not happening.

I would appreciate any insights or suggestions to resolve this issue.

Thanks in advance for your support!

Best regards,
Taksh

Labels:
0 Kudos
1 REPLY 1
STTwo-32
ST Employee

‎2024-12-06 01:26 AM

Hello @Taksh 

This is likely a problem lies with the Sigfox. So, contacting Sigfox support would be the best course of action. 

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

0 Kudos
Top