Comments for Maartendamen's blog

Comment on Plugwise unleashed document released by Olli

Olli — Wed, 08 Sep 2010 14:26:32 +0000

When I try this I just get endless 0000000000C2 back from the stick. The same happens with any command I pass in. Anyone else experiencing problems like this? The kit works ok if I connect it to Windows/Plugwise Source.

Comment on Plugwise on Linux downloads back online by Olli

Olli — Wed, 08 Sep 2010 13:15:33 +0000

When I try this I just get endless 0000000000C2 back from the stick. The same happens with any command I feed in. Anyone else experiencing problems like this? The kit works ok if I connect it to Windows/Plugwise Source.

Comment on Monitor an Oracle database with a SCOM OleDB watcher by snajgel

snajgel — Mon, 06 Sep 2010 07:50:46 +0000

Great blogpost! Thank you!

Comment on Monitor an Oracle database with a SCOM OleDB watcher by Tweets that mention Monitor an Oracle database with a SCOM OleDB watcher" -- Topsy.com

Sun, 05 Sep 2010 16:18:27 +0000

[...] This post was mentioned on Twitter by Scott Moss, Maarten Goet. Maarten Goet said: RT @maartendamen: "Monitor an Oracle database with a SCOM OleDB watcher" http://bit.ly/9OQrjB [...]

Comment on Plugwise unleashed document released by Smert

Smert — Thu, 02 Sep 2010 08:48:20 +0000

I don’t know, for me it works that way.
As I said,

“01″ results in a shorter (wrong) crc for one of my circles so it doesn’t work. Then i noticed that no power on/off code (“01″, “00″) or whatever in it’s place (e.g. “001″, “101″) turns it on!

I will post the exact messages and firmware info sometime.

Comment on Plugwise unleashed document released by Maarten

Maarten — Wed, 01 Sep 2010 15:03:28 +0000

@Smert: you need “01″ to switch something on…

Comment on Plugwise unleashed document released by Smert

Smert — Wed, 01 Sep 2010 07:48:22 +0000

Hi, thanks for your efforts and this doc.

Implementing your script in Java, crc for the switch on package for one of my circles returns a 3-digit hex number.

So then by playing a bit with it, I noticed that switch onoff packages containing powerstate code “00″ indeed turn off a device, but any other power code “011″ “1″ or even “”-nothing turn the device on.

Keep up the good work!

Comment on Plugwise unleashed document released by Kronos

Kronos — Wed, 18 Aug 2010 07:04:29 +0000

Thank you very much for your work and your Documentation. Is it possible to get a little bit more detailed explanation how the Checksum has to be calculated? I try to implement Plugwise in my Windows based Home Automation System without using the original Plugwise Software.

Greetings.

Comment on Plugwise protocol unleashed part 3: internal clock information by JMcL

JMcL — Tue, 10 Aug 2010 11:25:01 +0000

Further to Deep’s analysis of the send command/ack/response sequence, there’s an additional useful response regarding the packet sequence number

When a command packet is sent to the stick, the first reponse from the stick is a line in the form:

PutFifoUnicast 33 : Handle 129 : 000D6F0000xxxxB3

The ‘129′ in the line above is specific to the command sent. From what I’ve implemented it’s as follows:

PowerChange (code=0017) : 33
PowerInfo (code=0012) : 23
Calibration (code=0026) : 60

I presume other commands will also follow this pattern.

The handle returned is the value (in decimal) of the packet sequence Deep refers to and will be used on the subsequent ACK and data packets, so the conversation is now along the lines of (leaving out frame start/ends and inserting spaces for clarity – CCCC represents CRC):

SEND: 0017 000D6F0000xxxxB3 CCCC
RECV: PutFifoUnicast 33 : Handle 129 : 000D6F0000xxxxB3
RECV: 0000 0081 00C1 CCCC (note ‘0081′ = 129)
RECV: 0000 0081 00D8 00D8000D6F0000xxxxB3 CCCC

I guess this could be useful to optimise access to plugs. Fire a command, get the handle, and then keep track of responses received, leaving you free to send other commands in the meantime (Note: I haven’t tried this yet, it’s purely speculation!!!)

Comment on Jeenode infrared project part 1: getting started by ben

ben — Thu, 05 Aug 2010 20:17:33 +0000

thanks maarten, just got this working perfectly with my samsung tv (LE23R71B). You are a star!
Only to help others: (1) the ‘define variables’ need to be dropped into the IRremoteInt.h file (at the top). (2) Within the IRremote.h file the line “long decodeSamsung(decode_results *results);” needs to be added after the same NEC, Sony, RC5 and RC6 lines. (3) the following section needs to be dropped into the IRremote.cpp file:
#ifdef DEBUG
Serial.println(“Attempting Samsung decode”);
#endif
if (decodeSamsung(results)) {
return DECODED;
}
Well done, Ben