This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Philips Hue Light and CC2530

Other Parts Discussed in Thread: CC2530

Hello,

I have to do the following task:

1. Bind Philips Hue light with CC2530 zigbee module.

2. Toggle Philips LED light sending on/off commands using zstack.

can anyone suggest me how to proceed?

Regards,

Prija Nair.

  • 1. You have to set up a Zigbee HA coordinator first and make a factory default to Philips Hue. The, Philips Hue should send beacon request to search HA network to join. If the coordinator is allow association, it should associate with coordinator.
    2. You can refer to SampleSwitch that shows you how to send toggle command to SampleLight.
  • What does "make a factory default to Philips Hue" mean?

    Please be as specific as possible if the Zigbee HA coordinator need to be configured (PAN ID, Channel, etc.) in a particular way.

    Thank you.
  • When a brand new Philips Hue starts, it would send beacon requests and try to join Zigbee HA network first. If there is no Zigbee HA network, it will turn to ZLL profile. I don't know if your Hue is under ZLL or HA profile so I think you have to do a factory reset to Hue which you can refer to . If you use standard Zigbee HA profile, there is no need to modify anything to make Philips Hue to join it.

  • I am using standard Zigbee HA profile and a brand new, never plugged in Philips Hue.

    Are you saying that it should join my network without any modifications?

    Or will it need a factory reset?

    How to do a factory reset? All I have is the one bulb. No Philips hub/bridge.

    Also, once the Hue is on the network, do I just use my coordinator to discover it's address and then send ZDO Bind requests to pair it with an on/off switch on the network? Similarly, to gain dimming or hue control, I'll send separate level control cluster and lighting color control cluster bind requests?
  • 1. If you use a brand new Philips Hue, it should join your Zigbee HA network after it is turned on.
    2. To factory reset Hue, you have to buy hue dimmer switch. Then you can press and hold the ON and OFF button simultaneously until the LED light on the dimmer switch turns green (Note: the lamp is blinking during this process. Hue Beyond and Hue Phoenix are excluded).
  • So I took my brand new Philips Hue out of the box, screwed it into a light fixture with power off.

    Next I powered up my HA coordinator and my switch that is registered to receive ZDO device announce messages.

    I then powered up another zigbee device that joined the network and I saw the ZCO announce message confirming that I could receive them.

    Lastly, I powered on the Philips Hue.  It lit up, but waiting several minutes (just to be sure) I still saw no ZDO device announce message.

    I've repeated this process several times and the Hue never announces itself, indicating to me that it is not joining my HA netowrk.

    Any thoughts or suggestions?

  • I would suggest you to use Ubiqua Packet Analyzer to check over the air messages to know if Philips Hue sends beacon requests.
  • I haven't used the packet analyzer app you suggested yet.

    Instead I recursively sent ZDO_MGMT_LQI_REQ commands to discover all devices on my network, and low and behold there was one that I didn't recognize - presumably the Hue.

    So next I tried to send ZDO_MATCH_DESC_REQ commands with profile ID 0x104 (HA Profile) to the (suspected) Hue's address to learn what endpoints match the on/off, level control and color control clusters. However, I keep getting ZDO responses back from my sending device with a status of 0x80 -- zdoInvalidRequestType.

    Thoughts?
  • Try to send active endpoint request to that device. If you get active endpoint response from it, send it a simple descriptor request and see what's the response.
  • So in this example, the address of interest is 0xcf73, and the switch device i'm sending from has address 0x5f51.

    Sending an active ep request to 0xcf73 results in zdo response:

    SrcAddr: 0x5f51
    Status: 0x80
    NwkAddr: 0xcf73
    ActiveEpCount: 0

    Sending a match desc request to 0xcf73 with: profile ID 0x104 (HA), numInClusters 3, inClusterList { ZCL_CLUSTER_ID_GEN_ON_OFF, ZCL_CLUSTER_ID_GEN_LEVEL_CONTROL, ZCL_CLUSTER_ID_LIGHTING_COLOR_CONTROL }, and 0 outClusters, results in zdo response:

    SrcAddr: 0x5f51
    Status: 0x80
    NwkAddr: 0x5f51
    MatchLength: 0

    I don't understand why I'm getting invalidRequestType status in my responses. It's as something is not enabled for my device to send out this type of request, but what?

    And, why when sending the match descriptor request is the NwkAddr (device address that this response describes) my switch device's address and not 0xcf73?

    Jeff
  • It is strange to see activeEpCount=0 which means no active endpoint on 0xcf73. I think you have to setup sniffer to check this.
  • I am having the same issues as you, did you manage to get it working? thanks
  • No.  I have not got around to installing the Ubiqua Packet Analyzer sniffer tool yet to monitor the OTA traffic.

    If I do figure it out, I'll be sure to post the solution.  Please do the same!