<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Plugwise protocol unleashed part 2: device information</title>
	<atom:link href="http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-2-device-information/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-2-device-information/</link>
	<description>Blogging on various IT subjects</description>
	<lastBuildDate>Mon, 26 Dec 2011 09:18:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Plugwise Protocol Analysis &#171; roheve</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-2-device-information/comment-page-1/#comment-3161</link>
		<dc:creator>Plugwise Protocol Analysis &#171; roheve</dc:creator>
		<pubDate>Sun, 24 Apr 2011 16:24:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=106#comment-3161</guid>
		<description>[...] For an explanation of the fields, see Maartens blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] For an explanation of the fields, see Maartens blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roelof</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-2-device-information/comment-page-1/#comment-3160</link>
		<dc:creator>Roelof</dc:creator>
		<pubDate>Sun, 24 Apr 2011 15:24:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=106#comment-3160</guid>
		<description>I am tying to figure out how to get data from the plugs. Do you know more about reading the buffers (archived data) in the plugs. Or better, how are the buffers structured. Looking for a way to read the data in a usefull way.</description>
		<content:encoded><![CDATA[<p>I am tying to figure out how to get data from the plugs. Do you know more about reading the buffers (archived data) in the plugs. Or better, how are the buffers structured. Looking for a way to read the data in a usefull way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maarten</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-2-device-information/comment-page-1/#comment-126</link>
		<dc:creator>Maarten</dc:creator>
		<pubDate>Fri, 26 Feb 2010 14:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=106#comment-126</guid>
		<description>Hi,

This is indeed because of a different firmware version.
Plugwise unleashed is focused on the newest firmware (v2) 
V2 completely changed the way things are handled..

Greets,
Maarten</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>This is indeed because of a different firmware version.<br />
Plugwise unleashed is focused on the newest firmware (v2)<br />
V2 completely changed the way things are handled..</p>
<p>Greets,<br />
Maarten</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jhgrc</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-2-device-information/comment-page-1/#comment-125</link>
		<dc:creator>jhgrc</dc:creator>
		<pubDate>Fri, 26 Feb 2010 11:10:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=106#comment-125</guid>
		<description>Hmm, I get different kind of answer with 0024 reply code, is it because different firmware?

IN : H:     30&#124;30&#124;32&#124;34&#124;30&#124;30&#124;30&#124;44&#124;36&#124;46&#124;30&#124;30&#124;30&#124;30&#124;22&#124;43&#124;49&#124;52&#124;34&#124;22&#124;30&#124;30&#124;30&#124;30&#124;35&#124;44&#124;44&#124;35&#124;30&#124;30&#124;30&#124;34&#124;34&#124;34&#124;01&#124;60&#124;35&#124;30&#124;30&#124;31&#124;38&#124;35&#124;30&#124;30&#124;30&#124;30&#124;30&#124;34&#124;34&#124;30&#124;30&#124;31&#124;30&#124;37&#124;34&#124;38&#124;42&#124;34&#124;32&#124;35&#124;33&#124;38&#124;30&#124;32
IN : A:     0  0  2  4  0  0  0  D  6  F  0  0  0  0  &quot;  C  I  R  4  &quot;  0  0  0  0  5  D  D  5  0  0  0  4  4  4     `  5  0  0  1  8  5  0  0  0  0  0  4  4  0  0  1  0  7  4  8  B  4  2  5  3  8  0  2

So I have 0024 but not 0025 what you suspect some checksum. Immediately after 0024 I have MAC if Circle reporting my &quot;CIRCLE4&quot;. Then if after MAC is a year, my year is 2000 according to your analyzation. 

Then I am wondering why I have &quot;01 60&quot; -hex codes time to time inside answers. Have you seen those?

Well I think it is easier to discuss at domotiga forums. I just wanted to note my findings here as I was coding my perl-software to diagnose plugwise protocol. And I could not decode 0024 well..</description>
		<content:encoded><![CDATA[<p>Hmm, I get different kind of answer with 0024 reply code, is it because different firmware?</p>
<p>IN : H:     30|30|32|34|30|30|30|44|36|46|30|30|30|30|22|43|49|52|34|22|30|30|30|30|35|44|44|35|30|30|30|34|34|34|01|60|35|30|30|31|38|35|30|30|30|30|30|34|34|30|30|31|30|37|34|38|42|34|32|35|33|38|30|32<br />
IN : A:     0  0  2  4  0  0  0  D  6  F  0  0  0  0  &#8221;  C  I  R  4  &#8221;  0  0  0  0  5  D  D  5  0  0  0  4  4  4     `  5  0  0  1  8  5  0  0  0  0  0  4  4  0  0  1  0  7  4  8  B  4  2  5  3  8  0  2</p>
<p>So I have 0024 but not 0025 what you suspect some checksum. Immediately after 0024 I have MAC if Circle reporting my &#8220;CIRCLE4&#8243;. Then if after MAC is a year, my year is 2000 according to your analyzation. </p>
<p>Then I am wondering why I have &#8220;01 60&#8243; -hex codes time to time inside answers. Have you seen those?</p>
<p>Well I think it is easier to discuss at domotiga forums. I just wanted to note my findings here as I was coding my perl-software to diagnose plugwise protocol. And I could not decode 0024 well..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Plugwise protocol unleashed part 3: internal clock information &#124; Maartendamen&#39;s blog</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-2-device-information/comment-page-1/#comment-93</link>
		<dc:creator>Plugwise protocol unleashed part 3: internal clock information &#124; Maartendamen&#39;s blog</dc:creator>
		<pubDate>Sat, 06 Feb 2010 19:42:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=106#comment-93</guid>
		<description>[...] series, the other parts can be found here: Plugwise protocol unleashed part 1:  introduction Plugwise protocol unleashed part 2: device information  Posted in Plugwise unleashed &#124; Tags: linux, Plugwise, POL   &#171; Plugwise protocol unleashed [...]</description>
		<content:encoded><![CDATA[<p>[...] series, the other parts can be found here: Plugwise protocol unleashed part 1:  introduction Plugwise protocol unleashed part 2: device information  Posted in Plugwise unleashed | Tags: linux, Plugwise, POL   &laquo; Plugwise protocol unleashed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ettore Ferranti</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-2-device-information/comment-page-1/#comment-88</link>
		<dc:creator>Ettore Ferranti</dc:creator>
		<pubDate>Wed, 03 Feb 2010 08:01:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=106#comment-88</guid>
		<description>Hi Marteen,

yes it would be possible to use that formula, it&#039;s just that the volt value is never so constant. Anyway it will have to be enough :) Thanks a lot!!!

Ettore</description>
		<content:encoded><![CDATA[<p>Hi Marteen,</p>
<p>yes it would be possible to use that formula, it&#8217;s just that the volt value is never so constant. Anyway it will have to be enough :) Thanks a lot!!!</p>
<p>Ettore</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maarten</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-2-device-information/comment-page-1/#comment-86</link>
		<dc:creator>Maarten</dc:creator>
		<pubDate>Tue, 02 Feb 2010 18:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=106#comment-86</guid>
		<description>Hi Ettore,

The plug is sending puless. So no current and voltage info.
However you could use the following formula&#039;s to calculate the current I think:
Current = Watt / Volt

You know the volts right? 230v in my case.
So you could get the current aswell..

Maarten</description>
		<content:encoded><![CDATA[<p>Hi Ettore,</p>
<p>The plug is sending puless. So no current and voltage info.<br />
However you could use the following formula&#8217;s to calculate the current I think:<br />
Current = Watt / Volt</p>
<p>You know the volts right? 230v in my case.<br />
So you could get the current aswell..</p>
<p>Maarten</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ettore Ferranti</title>
		<link>http://www.maartendamen.com/2010/02/plugwise-protocol-unleashed-part-2-device-information/comment-page-1/#comment-85</link>
		<dc:creator>Ettore Ferranti</dc:creator>
		<pubDate>Tue, 02 Feb 2010 08:53:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.maartendamen.com/?p=106#comment-85</guid>
		<description>Hi, and thanks a lot for this very useful reverse engineering :)

I was wondering if it was possible to extract more information from a plugwise than its power consumption (i.e. current, volt etc...). Do you if the plug is sending more info than a simple watts value? 

Looking forward to the next chapter ;)

Ettore</description>
		<content:encoded><![CDATA[<p>Hi, and thanks a lot for this very useful reverse engineering :)</p>
<p>I was wondering if it was possible to extract more information from a plugwise than its power consumption (i.e. current, volt etc&#8230;). Do you if the plug is sending more info than a simple watts value? </p>
<p>Looking forward to the next chapter ;)</p>
<p>Ettore</p>
]]></content:encoded>
	</item>
</channel>
</rss>

