1840 views|2 replies

75

Posts

2

Resources
The OP
 

[NXP Rapid IoT Review] + When connecting to a device via mobile app, the message "Unable to verify the device's hardware credentials" appears [Copy link]

The program is compiled on the web and can run normally when downloaded to the module. When the mobile phone APP connects to the device via Bluetooth, it can find the device normally, but when registering the device, it prompts "Unable to authenticate device's hardware credentials" and the mobile phone application cannot be used. Recompiling and downloading the code and restarting the APP cannot solve the problem. I finally finished writing the program, but the APP is not working again Please ask NXP's technical support to help solve this problem


This post is from RF/Wirelessly

Latest reply

These days I haven’t been able to add hardware using the mobile app, this kit is really a hassle.  Details Published on 2019-1-16 15:07
 

931

Posts

3

Resources
2
 
These days I haven’t been able to add hardware using the mobile app, this kit is really a hassle.
This post is from RF/Wirelessly
 
 

75

Posts

2

Resources
3
 
To further verify, I compiled and downloaded the Rapid IoT Kit Out Of Box Demo that I modified myself. The module can run normally, but the mobile phone APP still prompts "Unable to authenticate device's hardware credentials" when registering the device. This means that it is indeed a software problem, but the software prompts success when compiling and does not report any errors? When checking the mobile phone APP information, I saw AUTHENTICATION TOKENS (authentication token) under integrations, and the yellow text shows the general API token. This means that the mobile phone APP application has authorization management, and the currently authorized general APP. The reason why the software I edited cannot connect to the module should be due to authorization restrictions. I don’t understand. I use components on the web. How can the functions that appear in the Demo exceed the limit? After thinking about it, I compared the constant humidity control I wrote with the constant temperature control in the example. The main difference is that I did not use the IncTemp and DecTemp functions to increase or decrease the humidity control, but directly added the relevant code to the Humidistat_Pg button processing callback function. Is it because of this limitation? Is it because the component callback function cannot be modified?
This post is from RF/Wirelessly
 
 
 

Find a datasheet?

EEWorld Datasheet Technical Support

快速回复 返回顶部 Return list