OK, at this point go to the digi web site and look under support.  There is also a forum there where the real experts on these little devices support various people.  I've gotten several answers to problems here and you could too.  It's also possible to call them and actually talk to a human, but time zones are always a problem doing that.

It sounds like the little module died, but there may be some help at digi.

Try reading the XBee, then program it with what you just read.  If that doesn't work, you may have a bad XBee.

What I've seen a lot of is that you have XCTU set up for something, reprogram the XBee, then get an error because XCTU is not set up properly after the programming.

For example, you have an XBee set at 9600 baud and you want to change it to 57600.  So, you set the baud rate in XCTU to 9600, and you can talk to the XBee just fine.  Then you change the settings on the page you show to 57600 and program the XBee for that.  Suddenly, you can't talk to the XBee anymore.  So, you have to reset XCTU to 57600 before you can move on.  This also happens when you go from API mode to AT mode or vice versa.  See, you're changing the XBee and not XCTU; they have to match.

go to openenergymonitor.org, the code is open source and supports pulses or CTs.

Another mix I have yet to try is glass strands in concrete.

I did this a couple of months ago.  A contractor I had working on my house years back didn't put enough foundation under one part and the room started to drop.  I had a crew (shovel...that much...not me) dig it out under the existing foundation and then out three feet to form a walkway.   I filled it with fiberglass reinforced 3000 lb concrete and rebar.  Really can't speak to the survivability, but the stuff has totally stopped movement on that part of the house.

But I have got to experiment with that building idea.  I'll start small, maybe a flower pot, planter, dog house, something on that scale.  It's just too cool

I had to give up on hot glue.  Darn stuff gives way in the AZ heat.  Now, that epoxy putty that come in a clear cylinder; that stuff is the bomb.

And, you keep looking, I've jumped in on some of your finds and look forward to doing it again.

Check in the forum on networking.  There are a lot of internet related posts there that you can get information from.

Then the code you have is a reasonable place to start, hook it up and give it a try.  However, change the delays in the code from 10 to a 1000 or more.  The unit for delay is millisecond and 10 isn't enough for the transmitter and 10 on the receiver won't be enough to sound a bell or alarm or whatever.  Use a second on the transmitter and around 500 on the bell to start off with.

Which series of XBees are you using 1 or 2?  To do what you want to do using strictly transparent mode, they have to be set up as coordinator and router (or end device).  There's a number of things you need to do to get this to work.  What have you set up so far?

But basically, the code you have should get you started if the XBees are already set up and ready to go.  One of the folk on this forum has a blog post for getting started the first time with a series 2 XBee it's here <link> Take a look and then give it a try.

Terry King (one of the folks on this forum) has a nice example of posting multiple values.  Take a look and see if it helps.
http://arduino-info.wikispaces.com/Cosm-Arduino

What you're seeing is the entire API packet.  Check out the XBee user's guide and you'll see all the stuff like the start sentinel, length, frame type, etc.  The extraneous stuff is actually necessary to get the packet to where it's actually going.  There a lot of things you need to know that would probably bore the other readers of this thread, and I think I summed them up on my blog.  So, go there, prowl around a bit, and then ask any left over questions you have.  Sound fair?  Start here <link>

You'll be most interested in the stuff I have on using the XBee library.

This looks like you're using the wrong XBee library.  You have to get the latest that has been updated to use software serial.  I can't remember where I picked it up, but I think it was here: https://code.google.com/p/xbee-arduino/  on the downloads page.  They also recommend using altsoftserial, but I don't for my stuff because it limits which pins can be used and 9600 is plenty fast for my stuff.

You can send the data from a lot of sensors to cosm.  I send several to them.  The provide an easy way to get graphs, one data set at a time.  If you want to graph temperature and humidity, it's easy to send them the data and get graphs for each of them.  If you want both of them on the same graph, it gets harder.  The graph I have is temperature and power usage; that took some javascript code to do.  I just used the google graph api and some javascript code to do mine.

Take an actual look at cosm, they have a ton of articles on how to send the data and get it back to do something with.

I collect and store data on cosm for my house; have been doing this for a few years now.  I have an arduino 2560 that acts as a collector for the various sensors and controls around the house and I send some of the data up to cosm, emoncms, and thingspeak.  The reason I send it to all three of these is that I wanted to try out as many of the cloud storage services for this kind of thing as I could.  The arduino collector also serves as a web server for control and monitoring of the house.  I can load its web page and it will tell me what's going on and I can change things if I want to.  

I put together some json code and it runs in the user's browser to present a graph of temperature and power usage for a 24 hour period.  I did it this way because I wanted it to be as close to real time as possible and I wanted to be able to expand the graph enough to see what appliances were running (you get to know them intimately over time).  The cool thing about using the user's browser is that the arduino doesn't have to do any work, it just sends code to the browser.  The json code is held on a cloud server as well so that it doesn't take up space on the arduino.

You can see the screen I put up to monitor the house, but remember, it's an arduino with 4 simultaneous connections, so you may have to try a couple of times to actually get in.  Once you get in and the page starts to load, the data for the last 24 hours is gathered and presented on your browser, so it may take 10 seconds or so to collect, and sometimes cosm will time out first.  The timeout doesn't happen very often so it doesn't bother me.  If you hit it with a cell phone, the little browsers on them sometimes don't like the iframe that holds the graphs and gauges, just use a different browser or use a pc.

This is very much a work in progress and probably will be for a long time.  I change it pretty often, mostly because I can, but sometimes I add or change something based on experience. The little arduino is at <link>, but be kind to it, it's only a little arduino, not a bank of servers like google or bing.

Oh, I also write about this setup on my blog, see the signature line for the link.

Good point.  You may be stuck without an answer until something kicks it into failing again and you have the time to chase the problem.