• State Not Answered
  • Replies 3 replies
  • Subscribers 67 subscribers
  • Views 1361 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 233743
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

On-Off Switch zigbee problem

Raffaela 
Hi.
I have a question related to the Zigbee SDK's "On / Off Switch" example.
Studying the example, I cannot understand how to activate the "light_switch_send_on_off" function that allows me to send the change to the "OnOff" attribute: 
in the example, the function is called following the pressing of the keys of the board but the case is not considered where I send the activation or deactivation message from a coordinator, 
like Amazon Echo.
In fact, if I try to control the switch directly with Amazon Echo, the device does not work and is not able to drive it.

How can I solve the problem?
If I try to use the "zcl_device_cb" callback that is present in the example of the light_bulb, however, it never calls this callback when Amazon Echo sends the message to the switch.
I also tried using a sniffer to see what kind of message is being sent and I can see that Amazon Echo sends a message without APS Frame, as if it didn't recognize the command well.

Thank you and best regards.
Raffaela
  • 0

    Hi Raffaela,

    Could you check the output logs from the light_switch example when you connect with the Echo pluss? I am wondering if you are running into the same issue from this ticket.

    Best regards,

    Marjeris

  • 0 in reply to Marjeris Romero

    Hi Marjeris,

    Thank you for your answer. So I can use the On/Off Switch only if this is connected to a light bulb? Without Finding & Binding, I can't use this device?

    Best regards,

    Raffaela

  • 0 in reply to Raffaela

    This example does not implement finding and binding. Please read my answer in the other ticket:

    "in line 301 of the light switch example we check if the light bulb device has a short address or not (adress 0x0000). This is unfortunate as it seems the smartthings hub have a light bulb server cluster and we get will a light bulb with address 0x0000 (coordinator address). If a light bulb with address 0x0000 is found, the next response to match descriptor request is also parsed and zboss alarm is cancelled again, which ends with error because the alarm is already cancelled."

    It seems the Echo pluss also has a light bulb server cluster with address 0x0000 so the same problem arises.

    This bug will be fixed in next release of the SDK so then you will able to test the light switch and light bulb example together with Amazon Echo Plus as a coordinator. Until then you can test using our light_coordinator example as a coordinator.

    Best regards,

    Marjeris

Related