Page 4 of 4

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Thu Dec 30, 2010 11:43 am
by Bwired
Could have something to do with the latest firmware update (small one).
I dont think it has to do with amount of circles.....

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Thu Dec 30, 2010 11:45 am
by Floppe
richard naninck wrote:Finally got my set and got most of it working. However I don't see the 0061 at all. Do I need to trigger something first?
Right now I am testing with the Circle+ and one extra Circle. Maybe it starts working when more Circles are attached. In that case I will get there later today..

I also see the Source software send a 004A000D6F0000xxxxxx3C01 -> Anybody?
I haven't used the source since I upgraded the firmware in the plugs so don't know about 004A command. I don't see any 0061 response either.

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Fri Feb 25, 2011 11:22 pm
by zonique
richard naninck wrote:I also see the Source software send a 004A000D6F0000xxxxxx3C01 -> Anybody?
In the latests version of Source, Plugwise has implemented so-called groups. The implementation of these groups goes far beyond nice grouping in the UI. A group consist of a bunch of modules that internally even have their own mac address. To make sure that all modules know which group they belong to and what their relay-state should be, this group-information is supposed to be broadcasted throught the network once in a while. Command 004A controls the interval of this broadcast:

- 004A - Command: Set broadcast interval
- 000D6F0000xxxxxx: Mac address
- 3C: Interval time, 3C = 60 seconds
- 01: On/Off switch, 01 = On.

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Fri Feb 25, 2011 11:35 pm
by zonique
Bwired wrote:I see at random 0061 coming in without having to request for it.
It looks like a heartbeat (last Seen) for every Circle in the network
Looks like its pushed to the comport :)
So this could be very handy to check if all your circles are available without a request!
Can somebody confirm or test this also?
I believe command 0061 is a feature of the very latest firmware and can only be seen if modules haven't been assigned to a network yet. These modules will the request to join a network by sending command 0061, basically identifying themselves. With this feature it wouldn't be necessary to punch in all Mac addresses of all individual modules in the Source. Instead you could just approve the modules that request to be added to your network. However, unfortunately this functionality has not been implemented in the Source and till now the modules are sending their requests to join the network in vain.

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Sun May 15, 2011 10:08 pm
by roheve
Bwired wrote:I see at random 0061 coming in without having to request for it.
It looks like a heartbeat (last Seen) for every Circle in the network
Looks like a quirk in that older firmware. I only see 0006 advertisements for unconfigured modules, and the 0061 reply appears only a few times after this advertisement is accepted with a 0007 01 response FROM the computer TO the module..
I am documenting it here, but still ongoing. There are still many things to check.

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Sun May 15, 2011 10:28 pm
by roheve
zonique wrote:
richard naninck wrote:I also see the Source software send a 004A000D6F0000xxxxxx3C01
To make sure that all modules know which group they belong to and what their relay-state should be, this group-information is supposed to be broadcasted throught the network once in a while. Command 004A controls the interval of this broadcast:

- 004A - Command: Set broadcast interval
- 000D6F0000xxxxxx: Mac address
- 3C: Interval time, 3C = 60 seconds
- 01: On/Off switch, 01 = On.
I only see this send to my Circle+ in each periodic Initialisaton sequence. And the initialisation sequence I see is 000A, 0023-stick (2x), 0023-circle+, 0016, 0028, 004A. I don't know yet what the 0028 is used for.

I still have no groups or schedules defined, so can't see advertisements for 'group-mac's' . Source and manual are not very clear on how to configure this or it does not work as described. Maybe my netbook screen is too small, and some button is hidden somewhere, but that's the only thing running windows I have at home.

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Mon May 16, 2011 8:40 am
by Bwired
roheve wrote:I am documenting it here, but still ongoing. There are still many things to check.
link is not working?

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Mon May 16, 2011 11:47 am
by wwolkers

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Thu May 19, 2011 10:07 pm
by roheve
wwolkers wrote:link is missing the : :)

http://roheve.wordpress.com/2011/05/15/ ... is-part-3/
yes, changed....

Re: Firmware version 2 protocol and POL 2.0

Posted: Sat May 21, 2011 11:13 pm
by roheve
zonique wrote:Please find a couple of additions below:
The device information request indeed returns the fields you mentioned, the last field seems to indicate the module type. 01 indicates a regular plug-to-socket module.
Device information query [0023] with Reply 0024
the last byte of the answer is
  • 00 for a stick
  • 01 for a Circle+
  • 02 for a Circle
The stick returns only a MAC and version info (time/date, buffer or switch info is zero)

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Wed Jun 29, 2011 6:25 pm
by roheve
roheve wrote:I still have no groups or schedules defined, so can't see advertisements for 'group-mac's' . Source and manual are not very clear on how to configure this or it does not work as described. Maybe my netbook screen is too small, and some button is hidden somewhere, but that's the only thing running windows I have at home.
Confirmed, the {schemas} you are defining and those you should drag/drop on a device/group are outside the visible area's of the small netbook-screen (even when maximized). I reported it as an error that you can not see the {schemas} and also do not get some hint that you should scroll (well, there are no scrollbars anyway) but there is enough space for a drop-down box or something. With the window not-full-screen, you can move part of it a bit outside your display window, and the {schema} icons become just visible enough to use then. My netbook runs windows 7, unfortunately just the 'starter' version, so no RDP capabilities to go there from my linux box for a bigger screen.

Anyway, I captured the 'send schema' traffic and that looks sensible to me (it just send a big table with 'on/off/standbykill' values for a whole week).

No time to document it yet...
Below some captured and filtered output (filtered and formatted using vbscript)

looks like this is the start of it:

Code: Select all

SEND	0040 000D6F0000D3595D 00 01    -> opens a schema on a circle
RECV	0000 0224 00C1 
RECV	0000 0224 00E5 000D6F0000D3595D

SEND	003E 000D6F0000D3595D
RECV	0000 0225 00C1 
RECV	003F 0225 000D6F0000D3595D 161838 02 01 45 7A

SEND	003B 0000 00040005 00040005 00040005 00040005
RECV	0000 0226 00C1 
[... a lot more...]
SEND	003B 0520 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
RECV	0000 0278 00C1 
SEND	003B 0530 00040005 00040005 00040005 00040005
RECV	0000 0279 00C1 
192 bytes a day for 7 days, so 8 bytes for an hour (I think it was a half-hour schedule, but I have to check (doet me denken aan dit liedje)).
the 00040005 pattern is for the standby killer setting. On is ffffffff, Off is 00000000 (or the other way arround)

then a long sequence with this

Code: Select all

SEND	003C 000D6F0000D3595D 01
RECV	0000 027A 00C1 
RECV	003D 027A 000D6F0000D3595D 01
SEND	003C 000D6F0000D3595D 02
RECV	0000 027B 00C1 
RECV	003D 027B 000D6F0000D3595D 02
[... more...]
SEND	003C 000D6F0000D3595D 29
RECV	0000 02A2 00C1 
RECV	003D 02A2 000D6F0000D3595D 29
SEND	003C 000D6F0000D3595D2A
RECV	0000 02A3 00C1 
RECV	003D 02A3 000D6F0000D3595D2A
and concludes with a 003e/003f/0040 again

Code: Select all

SEND	003E 000D6F0000D3595D
RECV	0000 02A4 00C1 
RECV	003F 02A4 000D6F0000D3595D 161903 02 01 59 71
SEND	0040 000D6F0000D3595D 01 01   -> closed a schema on a circle
RECV	0000 02A5 00C1 
RECV	0000 02A5 00E4 000D6F0000D3595D
probably this is deleting the schema again (not sure yet)

Code: Select all

SEND	0023 000D6F0000D3595D

RECV	0000 02A6 00C1 

RECV	0024 02A6 000D6F0000D3595D 0B069D21 00047620 00 85 653907014023 4CCEC0C2 02	[Time:0B069D21, Buffer:1732]


SEND	0040 000D6F0000D3595D 00 01

-> opens a schema on a circle

Code: Select all

RECV	0000 02A7 00C1 

RECV	0000 02A7 00E5 000D6F0000D3595D

SEND	0059 000D6F0000D3595D FFFF -> probably deactivates it...
RECV	0000 02A8 00C1 
RECV	0000 02A8 00FA 000D6F0000D3595D
so documented it a tiny bit :)

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Thu Jul 28, 2011 11:54 pm
by roheve
roheve wrote:
Bwired wrote:I see at random 0061 coming in without having to request for it.
It looks like a heartbeat (last Seen) for every Circle in the network
Looks like a quirk in that older firmware. I only see 0006 advertisements for unconfigured modules, and the 0061 reply appears only a few times after this advertisement is accepted with a 0007 01 response FROM the computer TO the module..
Well, it seems a bit different. If a module is not configured in your network, it sends BOTH 0061 and 0006 broadcasts. program SOURCE only responds to the 0006 (sends an 0007 01 CircleMAC), and that seems to add the module into the network. Then the module is initialised (depending on several factors, e.g. time set and buffer set)

The 0006 broadcast is more often as the 0061 broadcast, and both only contain he CircleMAC (and a bogus sequence number).

Re: Firmware version 2 Plugwise protocol and POL 2.0

Posted: Wed Nov 16, 2011 4:02 pm
by structor
A small question since plugwise is .net has anybody tried to run it using mono? Or does it die immediately since it's using ms-access :D