Xbee/ZigBee troubles

[Plater]

Here at work we've been using MaxStream's Xbee product (ZigBee implementation). Now I have to re-work the code (our head software guy banded it out in like a day as a time crunch so it's seriously lacking).
The problem is, I have not been able to understand the conversation flow for the XBEE API and was wondering if anyone was familiar with it?

My scenario is this:
I have multiple probes with the XBEE products, each with their 16bit MY address set to a known unique number.
I have one "host" device that needs to send an ascii string (they talk on UARTs) to a probe and get an ascii string back.

The problem is with the overhead, there's some sort of double messaging going on. If I tell the XBEE "send 40128 the message 'Get Val\n' ".
It does some sort of "let me see if 40128 exists and can respond" and then it sends message and that whole area is a mess.

[Plater]

For what it's worth, using the XBEE API calls on the UART talking to the XBEE goes something like this:

microcontroller sends API_TX message on UART to XBEE
XBEE replies back with an API_TX_STAT message on the UART to microcontroler.
(This message lets you know if it found who you were sending it to or not)

The XBEE that receives that message sends an API_RX message down it's UART along with the data that was sent from the originator XBEE.

[RedSon]

Sorry plater, never seen anything like that before :(