XBee PRO S2B communicating with Zigbee HA profile sensors

Is it possible to communicate with Zigbee HA profile sensors with XBee PRO S2B module, which, from what I understand, does not have a native support for HA profile.
I could not found anywhere that information. And where could I find HA profile specification, how the api packet are built. I bought some sensors from wulian company, for example:
Wireless IR Motion Detector

What settings should be set on my Xbee module in order to establish connection with them. Right now “node discovery” command returns me nothing …

2 Likes

hi!,

Common specifications are in ZigBee Aliance.
http://www.zigbee.org/Home.aspx

Probably HA Profile specifications and ZigBee Cluster Library are required.

That it is required of a setup of xbee moves in API mode, ZS=2, AO=1, and API frame will use Explicit Addressing ZigBee Command Frame and ZigBee Explicit Rx Indicator.

Possibly a setup about security may also be necessity.

Since I do not know not much in detail, I want those who know in more detail to come.

I wrote an email to their support regarding establishing a connection with their sensors and they wrote:

“Our product are HA profile .and use the TC LINK KEY
0x5a, 0x69, 0x67, 0x42, 0x65, 0x65, 0x41, 0x6c, 0x6c, 0x69, 0x61, 0x6e, 0x63, 0x65, 0x30, 0x39
and do you set the secure mechanism on your device ?
and do you set the HA PROFILE on your device?”

Which settings has to be set to this key? There are to field regarding encryption …

So from what I understand, packets in HA profile are completely different from those which uses XBee as native ones or what? :slight_smile:

It may be KY command if it is LINK KEY.

0x5a, 0x69, 0x67, 0x42, 0x65, 0x65, 0x41, 0x6c, 0x6c, 0x69, 0x61, 0x6e, 0x63, 0x65, 0x30, 0x39

It meas “ZigBeeAlliance09”. (w)

And the answer to that question would be?
“So from what I understand, packets in HA profile are completely different from those which uses XBee as native ones or what?”

hi!,

It could be said that the contents of Data payload of Explicit Addressing ZigBee Command Frame differ in about the difference between Digi private profile and public HA profile.

How to use general profile which uses XBee should read from 121 pages of product manual.

To which product manual are you referring to?

http://ftp1.digi.com/support/documentation/90000976_H.pdf

O I see … so every packet, which is based on ha profile is composed like the one shown in that manual? And from what I understand, because HA profile is public, that mean that every device which is based on that profile has to have the structure of a packet exactly the way like is written in that profile? So for example, every light switch based on HA profile would have the same packet structure, commands? And if that is so, where can I find description/manual of how packet/communication/commands for those devices is described?

Let me thank you for the information, you have give me until now … we have successfully established connection to the device :slight_smile:

There is one more thing … how can you do node discovery?
Are packet for those commands now completely different? I believe so …

hi,

Since I do not have ZigBee modules other than XBee, I cannot test about the interconnection between vendors.

If the ND command is executed by XBee set to transparent mode and ZS=2, what will happen?

Since ZS=2 is a setup using standard ZigBee Pro specification, it should be able to communicate with ZigBee Devices of all the ZigBee Pro specifications.

There were manual of how to use ZDO of Xbee.

http://ftp1.digi.com/support/images/APP_NOTE_XBee_ZigBee_Device_Profile.pdf

Although I think that a problem is probably solved now, how is it?

I’ve managed to connect to the sensor, but now I am struggling on how to configure/manage it … ND command does nothing :frowning:

Is the version of a ZigBee protocol stack in agreement? .

Since Node discovery is supported by ZDO, it must be common to all the ZigBee devices.

Was this procedure tried?
http://ftp1.digi.com/support/images/APP_NOTE_XBee_ZigBee_Device_Profile.pdf

Excuse my current lack of knowledge, but which command should I try for node discovery? Today I managed to connect to on/off switch … jupi :slight_smile:
Is sent me those packet:

Now it’s time to turn it on/off programatically … any help would be appreciated [:D]

hi,

Possibly I was wrong.
To ZDO, the same service as the ATND command was not able to be found.
Possibly the ATND command may be service peculiar to Digi.

By the way, why would you like to perform Node discovery in the network of HA profile? .
I think from this capture, as the state of the switch has been acquired correctly.

By the way, why would you like to perform Node discovery in the network of HA profile?

How can I then know which sensors are available to me? And in order to manage it, like on/off switch, I need to know it’s address.
Or is there something that I don’t know and is this handled differently. I Imagined that on start I would scan network, save all sensors information, so that I could then manage them or check it’s state.

The state of the switch has been acquired correctly, but I haven’t been able to change it without the help of my arm :slight_smile: I really don’t know at what to look for in that ZCL document … damn, it’s like if it
was written in chinese to me [:-&]

How can I then know which sensors are available to me? And in order to manage it, like on/off switch, I need to know it’s address.

I think that HA profile specifications should be first read if you want to manage HA device.

What is the purpose of source/destination endpoints?

What is the purpose of source/destination endpoints?

Make virtual and logical terminal between applications, like a tcp/ip port number.

So if on/off switch send me data with some source and destination end point value, should I use those values in tx packet?