This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Not able to read IKEA Trådfri bulb with nRF ZigBee

Hi

I read some threads about how to pair/read IKEA Trådfri.

I'm using nRF5840 dongle with the HEX code cli from SDK 17.0.0.

Using the terminal and send

bdb role zc

bdb start

bdb legacy enable

putting the bulb in "flickering mode, factory reset"

zdo match_desc 0xfff 0xffff 0xc05e 1 0 0

No result, the bulb is very very close to the dongle.

I feel stupid, because nothing happens.

What's wrong?

Parents
  • Hi,
    If you want to get a better context on what's going on in the network, but do not have a Zigbee sniffer around/other DK, you may enable logging in the CLI example through the following command:

    log enable info

    Now you should be able to see the log message, indicating that the bulb has joined the CLI's network.

    Afterwards, there is a set of commands to query/discover the device's capabilities:

    • zdo match_desc
    • zdo simple_desc_req
    • zdo active_ep

    If you do not see the successful association inside logs, there is no other way around - you will need a sniffer and paste the traffic dump here.

    If everything works, but the device does not respond to the match descriptor request (both profile IDs), try using a different broadcast address (0xFFFD). I've seen devices, that did not respond to the 0xFFFF (all devices), but replied to the 0xFFFD (routers-only).

    Side note: in the default configuration every reset of the CLI example erases the network data. As a result, you have to modify the example by changing the ERASE_PERSISTENT_CONFIG setting or factory reset all devices with every CLI reboot.

    Best regards,
    Tomchy

Reply
  • Hi,
    If you want to get a better context on what's going on in the network, but do not have a Zigbee sniffer around/other DK, you may enable logging in the CLI example through the following command:

    log enable info

    Now you should be able to see the log message, indicating that the bulb has joined the CLI's network.

    Afterwards, there is a set of commands to query/discover the device's capabilities:

    • zdo match_desc
    • zdo simple_desc_req
    • zdo active_ep

    If you do not see the successful association inside logs, there is no other way around - you will need a sniffer and paste the traffic dump here.

    If everything works, but the device does not respond to the match descriptor request (both profile IDs), try using a different broadcast address (0xFFFD). I've seen devices, that did not respond to the 0xFFFF (all devices), but replied to the 0xFFFD (routers-only).

    Side note: in the default configuration every reset of the CLI example erases the network data. As a result, you have to modify the example by changing the ERASE_PERSISTENT_CONFIG setting or factory reset all devices with every CLI reboot.

    Best regards,
    Tomchy

Children
No Data
Related