The plugwise protocol unleashed blog series

[Mdamen]

In a weekly blog series I will publish information about the plugwise protocol (based on firmware version 2)
Part 1 (introduction): http://www.maartendamen.com/2010/01/plu ... roduction/
Part 2 (device information): http://www.maartendamen.com/2010/02/plu ... formation/
Part 3 (clock information): http://www.maartendamen.com/2010/02/plu ... formation/
http://www.maartendamen.com/2010/08/plu ... -released/

Plugwise-unleashed-0.1.pdf

(971.97 KiB) Downloaded 1595 times

Any feedback is appreciated.

[Tiz]

Wow Maarten, compared to previous version you're taking the explanation to a second level. I am programming my own HA software and I will very happily make use of your blog. It looks very nice already.

[wwolkers]

Nice!

very good work you did on the v1 plugs. If v2 is anywhere near as good.... !

keep up the good work.

[wusel]

In a weekly blog series I will publish information about the plugwise protocol (based on firmware version 2)

Cool; does that suggest that Version 2 is already beeing offered to customers not having opted out of supporting the data mining activities of Plugwise B. V. by sending their usage data? (Can't check myself, as Stick and Plugs are happily driven with Linux and FHEM now, thanks to Maarten's previous findings.)
How about a "management summary" of pros and cons of upgrading to Version 2? Are now shipped Circles already at Version 2 (and would that require an update via Plugwise software on an installed V1 network before adding new V2-Circles/Stealth' to it)?

Regards,
-kai

[Mdamen]

New series now available (part 2)

[Mdamen]

New series available again (part 3) this one is about clock information.

[roheve]

I have discovered some additional commands.
You can use portmon to capture the ASCII stream (up to 230 char per line) between the application and the emulated comport.
Then convert the logfile using a small vbscript to something more readable, and look into it to discover what happens, e.g after doing some reconfiguring, etc and relate the discovered data to what you did.

The script is on github, just get it there. It filters the protocol commands between de start and end sequences (trows away he rest), and as an after touch tries to format 'known' comands in a more readable form. The logfile location is hardcoded, but easy to change.
Suggested additions: optionally filter the 0012/0013 or 0023/0024 (both realtime scanning) and/or 0048/0049 (getting unread archived data), as that mainly clutters the more interesting datastream.

In the command-decoder function, many commands are there, but there is stil allot to discover (e.g. the flag-dword in the 0000 reply)

NB. this threath on this forum is interesting too, more discussions about the commands.

[Phoenix]

Hi Maarten,

When i plug the USB Plugwise Zigbee stick (from the Stretch 2.0) in, no matter what i send...it always responds with this string, any idea?

zigbee_putty.png (16.12 KiB) Viewed 63292 times

[RdP]

Hi,

Does anyone of you know how to get measurement info from the Sense or even the Switch/Scan devices using this method ?

THe documentation is talking about Circle devices only...

Thanks,

Rien

[SevenW]

I am not familiar with Sense/Switch/Scan. I assume that they also have a MAC. Is it printed on the backside?
If so, I reversed engineered a command that lists all connected MAC's. As a start.
If connected it should be possible to query the device with the get_info command.

Depending on your python skills we could perform a test or two.

SevenW

[RdP]

I receive this info from the Sense

0105 9FC5 000D6F0000C3CD74 939464D04FA4 (can't figure out what the last 12 bytes mean)

[SevenW]

939464D04FA4

0x9394 = 37780 Humidity
0x64D0 = 25808 Temperature
4FA4 CRC?

Rh = (37780 - 3145) / 524.30 = 66.1 %
T = (25808 - 17473) / 372.90 = 22.4 C

I can see whether I can add some of this sense/scan/switch stuff to my program.
SevenW