Connecting an Xbee 24ZB to Smartthings Hub

I recently got into smart things. The hub isn't approved in New Zealand as the Zwave frequency doesn't match the stupid choice of New Zealand's spectrum. I decided I wouldn't buy any Zwave gear and stick to Zigbee that uses 2.4 Gig.

I want to make a few of my own "Things" so I decided to buy the Smartthings Maker board. WhenI went to buy some, there were none available to buy so since I had a couple of Xbees on my desk I figured I'd use them instead.

The ones I have are NOT Pro models.

I'd read a lot of conflicting "advice" as to whether this was possible. I couldn't see why it wouldn't be so I decided to go and find out.

So where to start.

The first thing is to get the Xbee setup to talk to the Hub.

There are a lot of settings that need to be set correctly so I did a bit of experimentation. In fact it didn't take long to get the Xbee connected but it was without using encryption which wasn't desirable so I needed a little help.

I found a blog of someone connecting a Propeller board via Zigbee Pro so I used his security settings for my Non-PRO Xbee

There are a few key aspects to the setup. (Using XCTU of course)

I used the Zigbee Endpoint API firmware. The endpoint firmware allows you to use power saving if that becomes desirable.

The API is the only mode to allow you to use the explicit addressing mode to send Zigbee packets AND to pass the ZDO requests through otherwise we won't see them. A0 must be set to 3.

 

We need the AO setting to allow us to receive the Zigbee explicit commands.

 

I've put my profile below to download for a look. It was an early setup but I don't think there are any deal breakers.

Download
Xbee24-ZB SmartThings Endpoint profile
profile_29A7.xml
XML Document 2.1 KB

OK so now what?

Using The XCTU in console mode with the Xbee plugged in (don't forget to push the connect button) press the reset button on the Xbee USB explorer card.


You should get a modem status returned that says the modem was reset.

Now you need to go into Smartthings app and click on add device/ add new device. This allows network discovery.

After a few moments you should get another Modem Status message. This time it should say Device joined Network.

Its important to note at this stage that SmartThings won't report that a device attached.

What has happened is that the Xbee has joined the network and has received PAN ID's and a local 16 bit address. 

In order for the App to see a device it needs to see an endpoint. That part is up to us so lets get on with it.

 

In order for us to send the required messages to the hub we need to find out our addresses. We do this by having a look back at the configuration page.

Find the MY setting and tap the refresh button to get the current setting.

this is now the 16 bit address. Write it down.

The SH and SL settings also need to be written down. Together they form the 64 bit address. If either of those two fields have less than four bytes of data, they need leading zeros.

In this example the 16 bit address is EF D2

and the 64 bit address is 00 13 A2 00 40 BF 94 F8

We will need these. 


Go back to the Console

Announce the Device

Now what we need to do is announce to the Hub that we are here. This will then send the hub into its discovery mode to try to find out who and what is doing the talking.


From here on we will be using the explicit addressing mode to send out Zigbee frames. Its not so user friendly but its what we've got.


So lets build new command. Click on the + in the Send Frames area.


Type in a meaningful name in the frame name box, like 'Device Announce'

and select ' Create Frame using frame generator tool'

Select Frame Type for Explicit Addressing.


Frame ID: anything for now

64 bit Dest: All zeros to address the coordinator

16 bit Addr: Several options but I like FF FC for the coordinator

Source and Dest endpoints are zero since this is a base ZDO command

Cluster ID: 00 13. This is the Device Announce command.

etc.


Now the payload.

AB: It just a frame ID. Anything is OK

D2 EF: Thats our 16 bit address in Little Endian format.

The next 8 bytes is our 64 Bit address, again little endian.

Finally 04: This is the capability.Lets not get too bogged down. This just says the receiver is on.

Save the frame and send it.

You should get a transmit status message back saying success and it should be followed by an Explicit receive indicator from the Hub.

In response to the Device announce, the SmartThings hub will begin its fingerprinting by returning an Active Endpoints request to see what endpoints are on the announcing device.

Looking at the message above we can see the cluster ID of 00 05, which is an Active endpoints request. If we look at the received data in the frame in this example, we can see 0C which is a frame ID (we need to reply with this) and our 16 bit address in little endian again. All good stuff.

Reporting the endpoints.

So now we need to reply buy sending an Active Endpoints Response message.

for this test we will only advise one endpoint but you can add plenty if you wish.


Make a new frame to send of the Explicit Addressing type.

The frame needs to be set out fairly similarly.

Note the clust ID is now 80 05.

its the reply to the 00 05 command so the most significant bit is set.


The Payload we need is as follows


0C: This is the same fame ID that the hub sent out. It matches them up so it needs to be correct.

00: Status message 00=OK

D2 EF: Our 16 bit address again

01: The number of endpoints in the device. We'll keep it simple.

08: The endpoint address. I randomly chose 08.


Save it and send it.

Again you will get a transmit status message and a new Request back from the hub.


(Please note, In the picture I had a transmit issue that I was too lazy to fix so I had to send the message a few times. Don't let it fool ya.)


Finding the 'Thing'

This time time we get back a Cluster ID of 00 04. This is a Simple Descriptor Request. This is our hub saying "OK I see that there is an endpoint 08, what does it do?"

We reply with a Simple Descriptor Response.. you guessed it.. set the most significant bit and get cluster ID of 80 04. 

And don't forget to note the new frame ID. 0D in this case.


Time for a new frame to send.

So set the cluster ID and now to the Zigbee data payload.

Note all multi byte fields are in little endian format


OD: The frame ID

00: Status OK

D2 EF: yup.. our address

0E: The number of bytes sent after this one.

08: The endpoint

04 01:  01 04 says our endpoint is Home Automation capable.

02 00: Says our device is an on/off output (keeping it simple)

30: don't worry.. version numbers.

03: The number of cluster types we can accept in.

00 00: First Cluster type - Basic

03 00: Second one is ID clusters

06 00: Last one is on/off clusters

00: The number of cluster types we send out.

Send it off.

You should get a Transmit Status back with a success notice.

Now if you look at the app you should note that you now have another 'Thing' connected to the hub.

Since we didn't have a device driver ready, it won't know what it is but it's connected.

Building the device type

Now is a good time to build a device type. In fact it would have been handy doing this first but anyway...

This device driver is VERY crude. It has some parts that need fixing even but for now it will do.

Once that is entered and published its ready for us to use.


The 'Thing' connected on the app needs to be deleted so do that.


Then start all over again.. you did save the frame list didn't you?

All that needs changing is to match the Frame ID and its a fairly simple matter to go through it all again. It should find the Xbee device driver from the fingerprint.

Making it Go

So now all we need to do is test it.


Go to the device on the app and turn it on.

You should receive another Explicit RX indicator for each time you turn it on or off.

Lets take a look.

So the pertinent bits...


Cluster ID 00 06 in Profile 01 04 is a Home Automation On/Off command


Looking at the Data.

01: This is the Control frame. Its saying from Client to Server. Remember the Server is the thing that does stuff.

00: This is a frame ID.. It will count up as usual.

01: This is the sub command.. It means Turn me On. If it was 00 it means Turn me off and 02 = Toggle me.


So there it is. It can be done and it isn't too difficult.

The rest is up to you.

Write a comment

Comments: 43
  • #1

    geko (Saturday, 24 January 2015 03:44)

    fan-freaking-tastic!

  • #2

    Marcio (Wednesday, 28 January 2015 04:46)

    Hi, great post! Can you explain more about the "Profile 01 04 is a Home Automation On/Off command", have any list to know it?

    Best regards.

  • #3

    George (Wednesday, 28 January 2015 11:41)

    Hi Marcio.
    Just read that line again.
    Perhaps I'll re-word it.
    Profile 0104 is the Home Automation profile.
    Cluster 00 06 (when used with that profile ID ) is the on/off command.
    It is listed in the Zigbee Cluster Library specification document.
    I hope that is clearer.

  • #4

    Marcio (Wednesday, 28 January 2015 20:16)

    Hi George, great! A last doubt, which information select the correct Smartthing Device Type?

    For example if I have two different scripts that control anything with a button, both will have Profile 0104 and Cluster 00 06 but my XBee need to select the correct thing when connect to the hub.

    Best regards,

  • #5

    George (Wednesday, 28 January 2015 20:53)

    Marcio,
    The device TYPE is reported in the simple descriptor when the coordinator (hub) asks for it. In my example its 0002 which is an "On/Off" device.. this is a device that RECEIVES an on/off command and turns a load on or off.
    Each device regardless of what it is uses their addresses as the means to differentiate one from the other.
    A device that acts as a switch would likely use device type 0007 etc.

  • #6

    Jaime (Wednesday, 11 February 2015 04:26)

    Hi!
    This is a great post, congratulations!
    I have been tried following your steps, but I am not able to succesfully connect the XBee module to the hub. The XBee module didnt join the network. I load your profile and I set the parameters into the module. Then I added a "new thing" into the web and I didnt see anything in the console after the reset frame.
    Could you please tell me wich parameter should I set in the Device Network Id? Do you think I am doing anything wrong?
    Thanks in advance.

  • #7

    George (Wednesday, 11 February 2015 13:18)

    Hi Jaime,
    I didn't add it via the webpage.. What I do is use the cellphone app. click the + on the home screen then tap "connect new device"
    this puts the hub into network discovery mode.
    then reset the Xbee so it will connect.
    That should then work for you.
    Cheers

  • #8

    Maurice (Thursday, 05 March 2015 15:49)

    George, Thank you so much for publishing this information. I have been able to use it to make a simple XBee S2 interface with SmartThings. I used a Maple board from DFRobot which has an XBee socket. So my code is pretty much Arduino compatible. I used the XBee library but had to extend it to support the Explicit commands. I'll publish my code once I clean it up a bit. Your message dumps were invaluable.

  • #9

    George (Thursday, 05 March 2015 18:28)

    Thanks Maurice. I'm pleased it has been of use.
    I have done much the same thing with the Xbee Ardunio library but I'm a bit too embarrassed to publish it since I've been pretty rough with it and it needs a good tidy up.
    So I'll be keen to see yours.
    Regards

  • #10

    Tim (Friday, 13 March 2015 21:04)

    George, great blog post!!!

    I just started to learn more about Xbee. The main thing I am currently wondering about is: shouldn't it be possible to program the XBee device to do all that automatically. In the end that is what all Xbee customer products do (e.g., Smarthings presence sensor). Or is that only possible with custom chips and potentially the programmable XBee Pro version?

    Thanks,

    Tim

  • #11

    George (Friday, 13 March 2015 22:46)

    Tim
    The Xbee does the basic connection for Zigbee but that's it. The Pro model doesn't do a lot more for you other than provide extra range. The programmable made (according to their website) doesn't support Zigbee at this time.
    This is all fairly simple stuff. It just needs a micro controller to drive it. That's what the programmable model would do if it supported Zigbee. This blog is simply to demonstrate how I got it talking to smart things using Zigbee. Adding a micro controller (Arduino/ Propeller etc) to send these commands isn't a difficult thing to do.

    The Xbee is simply a radio comms module sold by Digi. SOME Xbee modules support Zigbee as a protocol.
    Smartthings supports Zigbee as one of its protocols.
    The presence sensor works on Zigbee. Does it have an Xbee inside it? Beats me. Other people make Zigbee compatible radio modules also. The radio is just a small part of the device however.

  • #12

    Eric (Thursday, 09 July 2015 02:37)

    Hi Maurice. This kind of information was exactly what I was looking for (I was surprised how little there was out there on using xbee). Interestingly, my ST hub is actually able to see the Xbee when searching for devices. So i get "Modem Status...Modem Status...Explicit RX indicator" when I restart my xbee, and then the app finds it. I thought that maybe some new functionality has been added since you made this but when I tried to make them talk back and forth I couldn't get them to communicate. I tried making all the frames you describe above and can get the "transmit status" as a success, but never get a "Explicit RX indicator" in response. Any guesses to point me in the right direction?

  • #13

    George (Thursday, 09 July 2015 02:48)

    Eric,
    Are you sure you've got A0 set to 3?
    You need to have ZDO pass through set on otherwise you won't see the commands get returned.
    Cheers

  • #14

    Eric (Thursday, 09 July 2015 10:59)

    George,
    Yep, I am using the exact settings from the profile above, with the exception of the sleep mode, because it kept erroring out at SM = 0, so instead I am using SM = 4 (cyclic sleep). Could that be causing it?
    Best

  • #15

    George (Thursday, 09 July 2015 11:55)

    That will be it. It's going to sleep.

  • #16

    George (Thursday, 09 July 2015 12:05)

    You could try pin mode sleep and tie the pin to avoid it sleeping.

  • #17

    Eric (Friday, 10 July 2015 00:53)

    George,

    Thank you for the help, I put the xbee into pin hibernate mode and tied pin 9 to the ground. That fixed the problems with not receiving messages from the ST hub! Now I get all the way through to the end I am confused about setting frameID to 0104. As soon as I set the frameID to 0104 I stop getting explicit RX indicator back from the ST hub. Also when I set the thing to the custom device (it wasnt automatically set I had to set it in the web interface), I dont get explicit RX in xtcu. When I tried doing debugging on the custom device file, I see that the endpointId is null where as I thought it would be 08. Thanks for your help, I am more of an arduino/matlab person so the xbee and ST is new for me.

  • #18

    George (Friday, 10 July 2015 01:03)

    Do you mean the profile id? Frame id is always just is just a handshake number. It always must match the frame id from the sender.
    Profile 0104 is the address for the home automation profile. ST only uses HA.
    The custom device file must always be selected in the web setup first.
    I think that's what you mean?

  • #19

    Eric (Friday, 10 July 2015 01:55)

    George,

    You are correct I tried sending frames with the profileId as 0104, and then when I send the frame I don't get a Rx response back.

  • #20

    George (Friday, 10 July 2015 02:07)

    So you've. Got past the simple descriptor request/response and you see the new device appear on your phone app?
    You click the on/off on your phone app and should get the RX on the xbee?
    Just trying to get a handle on where you are at.
    Or. Have you departed on a different angle?

  • #21

    George (Friday, 10 July 2015 02:09)

    Might be easier to email me. My first name and the url of this site.

  • #22

    r chung (Monday, 26 October 2015 14:23)

    I purchased a S2 and followed the steps prescribed. I have no luck at all, tried the hibernate on pin, etc. However, after a very long while, somehow the ST hub will see an unknown things. Any suggestion on debugging this ? thank you for helping.

  • #23

    George (Monday, 26 October 2015 15:19)

    Hi r,
    There's been several guys do this and after following the instructions it works so just check you've done it as I've written.
    If an unknown device is showing up then you are some way through so it's just the final stages of reporting the endpoint's capabilities that's at fault.
    Cheers

  • #24

    Marcio (Friday, 01 April 2016 08:12)

    Hi, I'm trying to do this steps at Smartthings v2.0 but when I send the "ANNOUNCE THE DEVICE" the XCUT return an "Invalid frame".

    Do you test it at this version or only at v1.0?

    Best regards,

  • #25

    dexter (Friday, 01 April 2016 10:54)

    Hello,
    Is there any chance to connect these XBee S1 smartthings hub? http://www2.mouser.com/Search/ProductDetail.aspx?R=XKB2-AT-WWCvirtualkey58170000virtualkey888-XKB2-AT-WWC
    Thank you

  • #26

    George (Friday, 01 April 2016 15:08)

    I haven't got a smartthings v2 hub but zigbee is zigbee so it should work.


    I haven't tried an S1 xbee. They aren't compatible.

  • #27

    dexter (Wednesday, 06 April 2016 13:55)

    Hello,
    You can post a youtube tutorial with all the settings required to connect XBee s2 to Smartthings hub? You can share the code for your device on off? I got to device joined to the network and I'm stuck here - even if I follow your instructions unanswered from hub. Please help
    dexterbot80@gmail.com
    Thank you

  • #28

    dexter (Monday, 25 April 2016 02:24)

    Hello George,

    I am trying to connect an Arduino with 16 relays to the Smartthings Hub, while avoiding the Smartthings shield. Ideally, I would like to see each relay as an individual device (On/Off output) but I am not sure how to proceed. For now, I am trying to set it as a device with multiple EndPoints, but this would imply seeing it as a single device, am I right? So far I have followed your instructions (http://www.falco.co.nz/electronic-projects/xbee-to-smartthings) and @JohnR instructions from the forums, and got the device to show in the app, near my other Things (although for the last hours there seems to be a glitch even with this).

    So, to detail: I send the Device Announcement packet, I receive from the Hub:

    ZBExplicitRxResponse:
    From: 0xD052A853EE1C0001
    From: 0x0000
    Receive options: 0x01
    Src endpoint: 0x00
    Dst endpoint: 0x00
    Cluster id: 0x0005
    Profile id: 0x0000
    Payload: 2A 42 E6 --> all ok, this is a frameId + my xbee address

    Next, I report an endPoint (0xBB), and I get back:

    ZBExplicitRxResponse:
    From: 0xD052A853EE1C0001
    From: 0x0000
    Receive options: 0x01
    Src endpoint: 0x00
    Dst endpoint: 0x00
    Cluster id: 0x0004
    Profile id: 0x0000
    Payload: 2B 42 E6 BB --> frameId + my xbee address + endPoint address

    All seems fine, it asks for an Endpoint Description, I send a packet similar to George's (ClusterID 0x8004, inClusters 0x0000,0x0003,0x0006), and I get back:

    ZBExplicitRxResponse:
    From: 0xD052A853EE1C0001
    From: 0x0000
    Receive options: 0x01
    Src endpoint: 0x01
    Dst endpoint: 0xBB
    Cluster id: 0x0000
    Profile id: 0x0104
    Payload: 10 25 00 01 00 --> where 0x25 seems to be a frameId, it increases for the next 2 (repeated) packets.

    I don't know how to proceed any further. What's with the last packet? (I get the same response, even when I announce multiple EndPoints, and I was expecting it to inquire about all the endPoints). I can provide more details if needed. Thanks for all your help

  • #29

    George (Monday, 25 April 2016 02:32)

    Hi,
    I'm on the move at the moment and don't have a minute to check the return packet but you are on the right track in that each switch is its own endpoint. You simply copy my code with a different endpoint address for each relay.

  • #30

    George (Monday, 25 April 2016 03:38)

    Oh.. The cluster you got back is the Basic 0x0000.
    Without decoding it I'd put money on it that you've been sent an error report.
    It will just be a response to a typo in your descriptor you sent.

  • #31

    dexter (Monday, 25 April 2016 13:43)

    Thanks for your response. After the ST Hub sends the Simple Descriptor Request (e.g. payload: 4D 42 E6 BB), I send back: 7E 0 27 7D31 4D 0 0 0 0 0 0 0 0 0 0 0 0 80 4(clusterID) 0 0 0 0 4D(frameID) 0(status) 42 E6(MY address) E(length) BB(endPoint) 4 1(HA) 2 0(on/off output) 30(version!?) 3(inClusters length) 0 0 3 0 6 0 (3x inClusters) 0(outClusters) 9C. I believe it's the same as your example (Simple Descriptor Response) -- except for 7D31 which seems to be replacement for 11 (my xbee has API mode enabled, AP=2).

    Next, I get back ZBTxStatusResponse:
    FrameId: 0x4D
    To: 0x0000
    Delivery status: 0x00
    Discovery status: 0x00
    (Which I believe is a confirmation of my last sent message). And lastly, I get this ZBExplicitRxResponse:
    From: 0xD052A853EE1C0001
    From: 0x0000
    Receive options: 0x01
    Src endpoint: 0x01
    Dst endpoint: 0xBB
    Cluster id: 0x0000
    Profile id: 0x0104
    Payload: 10 3B 00 01 00 (message repeated with 3C and 3D, both after 1second)
    which I don't understand. Is there a mistake I'm making? I tried to follow your example closely. (FYI, my xbee in XCTU reports MY=E642). Thanks.

  • #32

    George (Monday, 25 April 2016 15:14)

    API with escaped characters makes life harder. They can slip in anywhere. Have you tried this with AP=1 ? Then as I did it?
    Otherwise you'll need to decode the response from the Basic Cluster. It will be in the zigbee cluster library.

  • #33

    dexter (Tuesday, 26 April 2016 17:19)

    Thanks for the pointers (I also changed to AP=1, no difference in response). I found in the zigbee cluster library that "Payload 10 3B 00 01 00" is a Read Attribute (0x00) command, for the 0x0001 attribute (it was followed by reads for 0x0004 and 0x0005). I responded to all with a Read Attribute Response containing a string of characters, "off". The device was then automatically added to the Hub, so I guess everything was ok.

    Next, I changed the Device Announcement to include 2 endpoints, repeated everything for the second endpoint, and got the same story for it.. but there's no secondary device in MyDevices on the Hub. And it reports (at Details) only the first endpoint, I have no clue where the second one is. Do you have any idea what I should try next, or where I did wrong? Should the second endpoint show up as an independent device? Thanks.

  • #34

    ScottM (Wednesday, 18 January 2017 21:05)

    I have a XB24CZ7WIT-004, which is a S2C, and was never able to get this to work. I kept getting stalled on the first connection step, the second modem reset message wasn't joining, but merely telling me that the coordinator was started.

    Am I totally using the wrong type of board?

    My testing has stopped, as I apparently bricked my Xbee, no bootloader is present any longer and I'm waiting on a new one.

  • #35

    George (Wednesday, 18 January 2017 21:37)

    Hi, sorry I'm not a lot of help on this right now. It's been a while since I've done it and I'm up to my eyeballs n another project at the moment so I can't help you with that sorry.

  • #36

    ScottMt (Wednesday, 18 January 2017 21:43)

    No worries, just wondering if you knew right off the module i had wouldn't work... thank you!

  • #37

    Zane (Friday, 20 January 2017 12:28)

    Hey Scott, I'm currently working with that S2C module too with no luck. If I find something out though I'll post here. If you find anything out please let me know as well!

  • #38

    Zane (Wednesday, 25 January 2017 11:01)

    Thanks a ton George! This has helped immensely.

    Alright, so I got it to the point where it shows up as a 'Thing - UNKNOWN' in the SmartThings iOS application with my Xbee S2C (Product family: XB24C, Function Set: ZIGBEE TH REG, Firmware version: 4059).

    My goal is to send analog data from a sensor that is connected to an Arduino to the smartthings application. How would I begin approaching that?

  • #39

    George (Wednesday, 25 January 2017 12:41)

    Hi Zane
    Pleased you got it going and this was some help.
    Probably the best way forward for you now is to log into smart things and find a device driver that is similar to what you need. From that point you can look at it to see what clusters they are using and copy them. No point re-inventing the wheel.
    I haven't done much with all this lately so I'm not that current with it all. I've got a project on that's taking up all my time but if I get a second I will look further into one of my units and put a bit more info up on it. I have a water level xbee that I made that is probably similar to what you need.
    Cheers

  • #40

    Zane (Friday, 27 January 2017 10:52)

    Hey George,

    Alright! I have played around with some code from ogiewon's 'ST_Anything' libraries and .ino files for Arduino alongwith the corresponding groovy code for the device handlers and realized I mis-understand the importance of the cluster IDs being used.

    For something like pulling in digital sensor data from a pin on the Arduino, I would need to use a cluster ID for 'Binary Input (Basic)' which is 000e, right? The one used when following the tutorial is what I ended up spending time trying with a project pulling sensor data from a DS18B20 until realizing that the On/off clusterID would not be able to work with such a intention.

    If I understand correctly, one must define an endpoint for each sensor attached (let's say 3 endpoints for 3 DS18B20 temp sensors), and then also the correct cluster ID for interpreting the data?

    The setup is as follows:
    Temp sensor on digital pin 8 of the Arduino, Xbee shield (with Xbee S2C programmed with the right clusterID), then the RX of the Xbee connected to the hardware serial TX of the Arduino, and vice versa.

    Temp sensor data -> Arduino TX -> Xbee RX -> SmartThings Hub

    Does that make sense? I'm still new to how this all connects in a way, so I may be confused in my logic.

    Thanks again for all of the help! If I can get this to work properly I will certainly post a follow up on the SmartThings forums to help others create their own SmartThings devices with Arduino/peripheral components.

    - Zane

  • #41

    Zane (Friday, 27 January 2017 14:16)

    Actually, here is a smaller question as well that I can't seem to figure out from reading the ZCL.pdf or forums...

    Where is the '20 00' (where you say: Says our device is an on/off output (keeping it simple)) found? I can't seem to find the equivalent for 'Binary Input (Basic)'. I'm also not sure what the 03 00: ID clusters refers to in the ZCL.pdf file.

    Any info on where to relate this in the library pdf file would be greatly appreciate! I feel like I am very close to figuring this out.

    Regards,

    Zane

  • #42

    George (Friday, 27 January 2017 23:48)

    On the run a bit here but..

    The main cluster list starts at Paragraph 2.2.2.1 so you can see cluster 00 06 on page 8.
    For a simple analog input is further down as n the same page. 'Input' refers to in to the zig bee device which is out there f the sender.
    The real work is done in the command frames. (2.1 on page 13 currently) Once you've got that understood and working you've got it licked. The reference is the most user unfriendly thing you could wish to read. The author need to be shot but I guess he wasn't interested in newbies.

  • #43

    Tim (Thursday, 09 March 2017 18:40)

    Zane/George

    I am also working on the XBee with that same stack the ZigBee Reg for the S2C. I just am not getting any response and feel like I am missing something silly. Could you share the XCTU configuration you got working on that firmware?