CC1352P: OpenThread with Zigbee dotdot application layer

As I know, Alexa hub and Google Nest hub haven’t fully support OpenThread/Matter until now. After they fully support OpenThread/Matter, I suppose you can use this protocol. For now, you can use Zigbee 3.0 thermostat example for Alexa hub which supports Zigbee devices.

Hi,  I'm supporting a business unit in the company which I'm working for. From a business perspective, we need to be sure when and what support we can get from Texas Instruments during the design phase. Provided SDK is very important and during the last 6 months working with Texas Instruments, I notice that other vendors are more agile and implement much more OpenThread functions and recently start providing preliminary Matter SDK as well. From my perspective, TI still hasn't provided RCP mode for the OpenThread border router (NCP for BR is not supported for I guess 2 years). TCP protocol (LwIP) is also not provided in TI SDK.  I haven't found any example secured COAP connection (with the use DTLS)   and I cannot find any MQTT  example in SDK as well. Examples of how to build BorderRouter based on Beaglebone are not completed (mentioned scripts are not provided)  and are based on obsolete Linux distributions. When taking this into account - when the product will be ready to be released to market it will be vulnerable like Switzerland cheese.  I know this discussion should be taken with  TI  product manager, but I think something is not working ok in TI as getting the possibility to discuss these topics with TI product manager is not possible. Without the adoption of the above function, TI radio chips will be very slow and TI will be not prepared for Matter as well. I hope TI will understand that need to be more agile were working with external companies because without getting feedback from the market it will be very difficult to understand TI managers why TI is not as successful as other smaller companies.  With current TI processes having contact with the product manager with which you can share feedback is very difficult even when your development environment uses a few hundred TI dev kits.   I hope key management will take some serious actions to improve the situation as it's difficult to watch that so a great company with long traditions has such big market misunderstanding. 

Hi Michal,

We appreciate your perspective and feedback.

Let me try and address some of your concerns.

1. Thread
   6. We plan to have RCP in Q2 SDK (6.20, planned for release end of Q2).
   7. For preliminary evaluation, we have also shared RCP images:
      CC2652RB: https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1102043/lp-cc2652rb-openthread-rcp-firmware-needed
      CC2652P/CC1352P: https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1107691/cc2652p-rpc-firmware/4106011#4106011
      CC2652R: https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1082428/faq-cc2652r7-matter----getting-started-guide
2. Matter
   1. TI is actively involved with Matter. TI devices are supported on the opensource Matter GitHub with support for multiple examples (e.g. all-clusters-app, all-clusters-minimal-app, lock-app, pump-app, pump-controller-app).
   2. The process of developing on Matter is via the opensource github (https://github.com/project-chip/connectedhomeip)
   3. We also have a ti_simplelink_sdk submodule within Matter:
      https://github.com/project-chip/connectedhomeip/tree/master/third_party/ti_simplelink_sdk
   4. This may also be helpful: https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1082428/faq-cc2652r7-matter----getting-started-guide
3. Thread NCP should still be supported, although RCP configuration is encouraged.
4. Thread moving forward:
   1. There are many possible applications for Thread (since Thread does not specify an application layer). From a strategic standpoint, we believe that Matter is among the most future-proof. And since Thread is a cornerstone of matter, TI is working actively within the Connectivity Standards Alliance and Thread Group to make sure that TI solution is a compelling contender.
   2. With that said, TI would be ready day 1 of Matter official release to market.

Again, we appreciate your thoughts and hope the above points address your concerns.
If you’d like a further discussion, I have sent you an E2E Connect/Friend request, and we can work out an appropriate communication channel.

Thanks,
Toby