LAUNCHXL-CC26X2R1: Echo show 2nd gen

You can let your zed scan all Zigbee channel trying to join Echo show and use sniffer to sniff all channels to locate the channel of Echo Show 2.

We've been able to pair an out-of-box zed_light example to Amazon Echo devices in the past: https://training.ti.com/connect-zigbee-amazon-echo-demo

As YK mentioned you will need to increase your DEFAULT_CHANLIST or sniff for the channel that the Amazon Echo is using.  Channels 15, 20, 25, and 26 are commonly used as they avoid Wi-Fi interference.

Regards,
Ryan

Is #define DEFAULT_CHANLIST in ZSTACK_CONFIG_H the correct parameter to modify to change the channel?  Would the device try all channels if DEFAULT_CHANLIST is set to 0x07FFF800?  What is the purpose of SECONDARY_CHANLIST?  Also, is it necessary to  push button 1 to start commissioning?

Regards, Allen

Yes, yes, channels to try if the device fails to find a network to join from DEFAULT_CHANLIST (pointless if DEFAULT_CHANLIST is set to all channels), yes by default but you could set Zstackapi_bdbStartCommissioningReq at the end of initialization or from the UI.

Regards,
Ryan

Using the TI sniffer agent, the Amazon Show is using channel 25.  Changed that in config and still not working.  Since I have only one 26X2R1, I can't capture the application packets.  I did capture a Zigbee plug that the Amazon Show can find. if that's of any use to you.  I looked at the Zigbee demo that shows the 26X2R1's working with the Echo.  So it can be done.  Do you have any other ideas of what could be wrong?  By the way, I'm pretty sure I'm building and flashing correctly (empty example red led is blinking.).

Thanks,  Allen

Can you provide the sniffer log on channel 25 when you do pairing LAUNCHXL-CC26X2R1 zed_light to Echo Show?

I can't do that because I have only one LAUNCHXL-CC26X2R1.  I don't think a LAUNCHXL-CC26X2R1 can be a device and sniffer at the same time.  I can send you a log of Amazon Show to a Zigbee plug I have.  What is the correct format for that log?  I'll get another CC26X2R1 unless you have another thing to try.

Thanks,  Allen

Yes, I also suggest you to buy another LAUNCHXL-CC26X2R1 as sniffer and try pairing the first LAUNCHXL-CC26X2R1 to Amazon Echo to provide sniffer log.

A zed_light project should not blink the red LED.  You will have to press BTN-1 on the LaunchPad to have it join the Amazon Echo's Zigbee network while it is discovering devices.  Perhaps using the UART UI with a terminal program could give you more insight into the issue.  You should definitely get a second LAUNCHXL-CC26X2R1 to at least understand how the examples are designed to work.

Regards,
Ryan

Ryan, it was the Empty example I used to blink the LED, not the zed_light.  I will get the UART UI and also get another LAUNCHXL-CC26X2R1.  Appreciate the help (YK and Ryan).

Regards,  Allen

Hello,

Using 2 LAUNCHXL-CC26X2R1's, the zc_light was able to pair with the zed_sw (could toggle Led's from UART UI.)

Then I used the Amazon Echo to connect to the zed_sw.  The Echo was not able to discover the zed_sw.  The zed_sw was able to communicate on channel 25 and received a PAN ID of 0x33AB and NWK address of 0x a87FA. (in frame 10 of capture.)  After that, data and commands are exchanged between Echo and zed_sw.  Eventually Echo times out and indicates no devices found.

I have attached Wireshark captures.  I started the first capture after telling Echo to discover new devices the first time.  The second capture is after the PAN ID and NWK address have been established.

I had to change the files extension to bmp because the Forum does not allow pcapng to be uploaded.  The files are wireshark pcapng files.  Let me know if there is an easier way.

Regards,  Allen

Don't see any Wireshark capture log attached.

Obviously, the attachments didn't make it.  How can I send Wireshark pcapng files?

Regards,  Allen

ZIP it first and you can attach the ZIP file.

Can you see these?

echo_zed_sw.zipecho_zed_sw2.zip

Hello Allen,

You sniffer logs prove that the zed_sw was successfully able to join the Amazon Echo's Zigbee network.  However the Echo's application most likely does not "discover" the device since it is not interested in handling Switch endpoints.  We can see successful Active Endpoint and Simple Descriptor Requests from the Echo and Responses from the Switch, however the Echo is typically looking for Light devices that it can control and as such ignores the Switch device for which it has no use.  Behavior will most likely be different if you try to connect a zed_light project.

Regards,
Ryan

Hello,

Same result with zed_light ("no new devices found.")

See attached.  First capture  is initial join.  Second capture is another attempt for Echo to discover.

Regards,  Allen

echo_zed_light2.zipecho_zed_light1.zip

It's working now, mostly.  I kept on recommissioning the zed_light (with the UART UI) and eventually the Echo found it.  Now I can turn the LED on and off with Alexa.  If I power cycle or reset the device, I have  to use multiple commission cycles to get the device connected.  However if I tell Alexa to discover at the same I start the commission, the joining always happens immediately.  Is this a timeout problem with the device?    Is there some other way to handle this?.  By the way, the zed_sw works too.

Regards, Allen

Hello Allen,

I do not see anything concerning inside the sniffer logs.  You could try the ZR projects and see if this affects device discovery.  This behavior is most likely created by the Amazon Echo application and you would need to contact resource their support forums for more information.

Regards,
Ryan

I'll try the ZR project.  Where does user zstack control and configuration (like bdbStartCommissioningReq) go?

Regards,  Allen