<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Doorbell update</title>
	<atom:link href="http://rooreynolds.com/2008/05/18/doorbell-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://rooreynolds.com/2008/05/18/doorbell-update/</link>
	<description>What's Next?</description>
	<pubDate>Thu, 04 Dec 2008 19:23:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Roo</title>
		<link>http://rooreynolds.com/2008/05/18/doorbell-update/#comment-47865</link>
		<dc:creator>Roo</dc:creator>
		<pubDate>Mon, 26 May 2008 23:14:27 +0000</pubDate>
		<guid isPermaLink="false">http://rooreynolds.com/?p=595#comment-47865</guid>
		<description>Update: it's been offline for a while; I broke the antenna. I now have a new soldering iron, so I shall fix it soon. I might use a longer piece of wire to see if I can improve the range and reliability too.</description>
		<content:encoded><![CDATA[<p>Update: it&#8217;s been offline for a while; I broke the antenna. I now have a new soldering iron, so I shall fix it soon. I might use a longer piece of wire to see if I can improve the range and reliability too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rooreynolds.com: Hacking the doorbell</title>
		<link>http://rooreynolds.com/2008/05/18/doorbell-update/#comment-47245</link>
		<dc:creator>rooreynolds.com: Hacking the doorbell</dc:creator>
		<pubDate>Tue, 20 May 2008 21:24:33 +0000</pubDate>
		<guid isPermaLink="false">http://rooreynolds.com/?p=595#comment-47245</guid>
		<description>[...] Doorbell update  [...]</description>
		<content:encoded><![CDATA[<p>[...] Doorbell update  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roo</title>
		<link>http://rooreynolds.com/2008/05/18/doorbell-update/#comment-47205</link>
		<dc:creator>Roo</dc:creator>
		<pubDate>Tue, 20 May 2008 12:28:08 +0000</pubDate>
		<guid isPermaLink="false">http://rooreynolds.com/?p=595#comment-47205</guid>
		<description>&lt;em&gt;"internal telemetry is cheap and not for direct human consumption - regular updates from sensors and stuff like that would be welcome there, but the -&#62;Jabber gateway would do 'smart' analysis of the data and convert it into more interesting streams of pertinent messages when things change or exceed limits"&lt;/em&gt;. 

Exactly. Well put. 

I'll take a look at Clickatell too. Sounds handy.</description>
		<content:encoded><![CDATA[<p><em>&#8220;internal telemetry is cheap and not for direct human consumption - regular updates from sensors and stuff like that would be welcome there, but the -&gt;Jabber gateway would do &#8217;smart&#8217; analysis of the data and convert it into more interesting streams of pertinent messages when things change or exceed limits&#8221;</em>. </p>
<p>Exactly. Well put. </p>
<p>I&#8217;ll take a look at Clickatell too. Sounds handy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alaric Snell-Pym</title>
		<link>http://rooreynolds.com/2008/05/18/doorbell-update/#comment-47188</link>
		<dc:creator>Alaric Snell-Pym</dc:creator>
		<pubDate>Tue, 20 May 2008 09:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://rooreynolds.com/?p=595#comment-47188</guid>
		<description>Yeah, similarly, I'm taking the approach that internal telemetry is cheap and not for direct human consumption - regular updates from sensors and stuff like that would be welcome there, but the -&#62;Jabber gateway would do 'smart' analysis of the data and convert it into more interesting streams of pertinent messages when things change or exceed limits.

But yeah, Jabber can do the IM stuff, and SMS is easy too (see http://www.clickatell.com/; sign up, buy some credit, then invoke their SMTP or HTTP APIs); those are what I'm currently using for event notification in my external systems. Finally wiring the house properly will take a bit longer, though - we've only just got the floor back in! :-)</description>
		<content:encoded><![CDATA[<p>Yeah, similarly, I&#8217;m taking the approach that internal telemetry is cheap and not for direct human consumption - regular updates from sensors and stuff like that would be welcome there, but the -&gt;Jabber gateway would do &#8217;smart&#8217; analysis of the data and convert it into more interesting streams of pertinent messages when things change or exceed limits.</p>
<p>But yeah, Jabber can do the IM stuff, and SMS is easy too (see <a href="http://www.clickatell.com/" rel="nofollow">http://www.clickatell.com/</a>; sign up, buy some credit, then invoke their SMTP or HTTP APIs); those are what I&#8217;m currently using for event notification in my external systems. Finally wiring the house properly will take a bit longer, though - we&#8217;ve only just got the floor back in! :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roo</title>
		<link>http://rooreynolds.com/2008/05/18/doorbell-update/#comment-47131</link>
		<dc:creator>Roo</dc:creator>
		<pubDate>Mon, 19 May 2008 10:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://rooreynolds.com/?p=595#comment-47131</guid>
		<description>I use Twitter to expose this (so far, more outputs coming soon) partly because Twitter already fits nicely into my life. It very easy to get things sent to IM and/or SMS. I'd only expose the just-for-fun stuff of course, and I'm not planning to publish any ultra sensitive stuff in a channel which is both public and (let's be honest) prone to random failure. :-)

There is a pub/sub messaging system inside my house already (using the &lt;a href="http://mqtt.org/" rel="nofollow"&gt;MQTT&lt;/a&gt; protocol, but I'm also thinking about Jabber/XMPP too). This external exposure of certain bits of it is a subset of that of course.</description>
		<content:encoded><![CDATA[<p>I use Twitter to expose this (so far, more outputs coming soon) partly because Twitter already fits nicely into my life. It very easy to get things sent to IM and/or SMS. I&#8217;d only expose the just-for-fun stuff of course, and I&#8217;m not planning to publish any ultra sensitive stuff in a channel which is both public and (let&#8217;s be honest) prone to random failure. :-)</p>
<p>There is a pub/sub messaging system inside my house already (using the <a href="http://mqtt.org/" rel="nofollow">MQTT</a> protocol, but I&#8217;m also thinking about Jabber/XMPP too). This external exposure of certain bits of it is a subset of that of course.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alaric Snell-Pym</title>
		<link>http://rooreynolds.com/2008/05/18/doorbell-update/#comment-47130</link>
		<dc:creator>Alaric Snell-Pym</dc:creator>
		<pubDate>Mon, 19 May 2008 09:32:51 +0000</pubDate>
		<guid isPermaLink="false">http://rooreynolds.com/?p=595#comment-47130</guid>
		<description>Why use Twitter for this, out of interest? I was thinking of using a combination of Spread and Jabber for those kinds of things myself - a Spread group running over my private network for events to be notified to and things to subscribe to, one of which would be a Jabber bot that notifies a select list of people (Wife and I) of interesting events.

Mainly, this is because I feel nervous about (a) making stuff about my house's workings public, for security reasons (you should see the security system I'm designing... but, then I'd have to kill you) and (b) relying on a third-party online free thing like Twitter for anything important rather than just fun!</description>
		<content:encoded><![CDATA[<p>Why use Twitter for this, out of interest? I was thinking of using a combination of Spread and Jabber for those kinds of things myself - a Spread group running over my private network for events to be notified to and things to subscribe to, one of which would be a Jabber bot that notifies a select list of people (Wife and I) of interesting events.</p>
<p>Mainly, this is because I feel nervous about (a) making stuff about my house&#8217;s workings public, for security reasons (you should see the security system I&#8217;m designing&#8230; but, then I&#8217;d have to kill you) and (b) relying on a third-party online free thing like Twitter for anything important rather than just fun!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
