You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to inherit the Thread certification, companies need to proof that the OpenThread library version they use matches the certified version of Espressif. For example, during the Thread 1.3 certification process, we had to manually check out a specific commit of the OpenThread library. As this specific commit was not referenced in any esp-idf commit, we had to checkout the submodule manually.
In the future, it would be very helpful if Espressif could:
Create tags for certified OpenThread versions. The next certified release will be Thread 1.4, probably with esp-idf 5.3 or 5.4.
Provide Docker containers for ESP-Matter and ESP-IDF that include the exact certified version of the OpenThread library.
This would require minimal effort on your end but would simplify the certification process for many companies. For example, when a company uses the espressif/esp-matter docker container that uses the certified Thread version.
Thank you for considering this request.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Tags and Docker Containers for Certified OpenThread Versions
Tags and Docker Containers for Certified OpenThread Versions (CON-1456)
Dec 5, 2024
@jzwyssig We have an official process to support our Thread customers in inheriting the platform's Thread certification. Please reach out to our team via Espressif Technical Inquiries, and we will provide the Thread certification ID along with the corresponding IDF release versions.
In order to inherit the Thread certification, companies need to proof that the OpenThread library version they use matches the certified version of Espressif. For example, during the Thread 1.3 certification process, we had to manually check out a specific commit of the OpenThread library. As this specific commit was not referenced in any esp-idf commit, we had to checkout the submodule manually.
In the future, it would be very helpful if Espressif could:
This would require minimal effort on your end but would simplify the certification process for many companies. For example, when a company uses the espressif/esp-matter docker container that uses the certified Thread version.
Thank you for considering this request.
The text was updated successfully, but these errors were encountered: