Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any plan to add PnP support by updating azure iot c sdk to LTS_07_2020_Ref01? (CA-105) #107

Open
xiongyu0523 opened this issue Dec 7, 2020 · 5 comments

Comments

@xiongyu0523
Copy link

We have some partners want to certify their ESP based device to Azure PnP. They start from here so I'm checking whether we can update SDK to the latest LTS. Thanks.

@github-actions github-actions bot changed the title Any plan to add PnP support by updating azure iot c sdk to LTS_07_2020_Ref01? Any plan to add PnP support by updating azure iot c sdk to LTS_07_2020_Ref01? (CA-105) Dec 7, 2020
@shahpiyushv
Copy link
Collaborator

@xiongyu0523 , as of now, we have PNP support being maintained on a separate branch preview/pnp_example. Have you checked that out?

@xiongyu0523
Copy link
Author

that's great. I will check it.

@xiongyu0523
Copy link
Author

It works perfectly on my ESP32 board. Thanks.

In PnP certification requirement document, it explicitly ask for IDscope transfer capability. Can ESP32 platform support this?

Device must implement easy transfer of DPS ID Scope ownership without needing to recompile the embedded code

@lhespress
Copy link
Collaborator

@xiongyu0523 ESP32 platform has support DPS ID Scope, but it need to recompile the embedded code. we haven't provide without recompile the embedded code.

@xiongyu0523
Copy link
Author

xiongyu0523 commented Dec 10, 2020

I understand your IDscope is in Kconfig. That might be treated as a 'no code' solution. let me check with people who take care of certification. THanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants