Hi,
I have just bought a Pycom Pytrack and lopy4, I updated firmware on both devices, and are now trying to register it in Sigfox, but i keep getting the error, “We could not find a DevKit matching your ID/PAC”
Tom
2 Likes
Hi Tom,
Hmm, so you’ve run the sigfox.pac() method, and stuck that into the activation portal on Sigfox’s site?
That should definitely work, and while I haven’t worked with Sigfox myself, it seems fairly straightforward.
Keen to get this one back on track!
-James
1 Like
Hi Tom,
Your Sigfox ID and PAC should be displayed to you as the last step in the firmware update, the guide covers how to find them.
https://docs.pycom.io/gettingstarted/registration/sigfox/
Do you have the ID/PAC and Sigfox is not recognising them, or having trouble locating them?
1 Like
Hi James,
Yes, I have done that, and also used the Pycom Firmware update tool which also reads out the values. Both methods give the same numbers, but Sigfox doesnt like them
Tom
2 Likes
Hi Trent,
Sigfox is not recognising them.
Tom
2 Likes
Hi Tom,
Just to confirm when you updated the firmware version did you select a version marked as stable? Firmware versions in development might not be considered “Sigfox certified” devices and may need to be registered as prototype devices via a different registration method.
2 Likes
Hi Trent,
Yes i did use the stable build.
Tom
1 Like
Hi Trent, Just wondering if you had any further thoughts here?
Hi Tom,
Is there a chance your device has already been registered for the first time before? The registration process only works for the first time a device is registered, after that it instead needs to be transferred.
Does this match the error you are receiving?
Sigfox’s registration process can get quite messy as there are technically 3 different pathways to having a device registered on their network, the end-user of Sigfox devices is only ever supposed to see the method you are using.
2 Likes
Hi Trent,
No it hasn’t been registered before, I went to register it straight after opening the box when I received it from you.
The error I am seeing is:
Tom
1 Like
Hi Tom,
It would be best to get in touch with Sigfox to get their support with this. We tend to lean further into open platforms such as TTN.
If you are unfamiliar with debugging LoRaWAN connections then it might just be easier to connect to The Things Network (or another service) to split test where the issue resides.
3 Likes
