There were some errors in the protocol, but we found and corrected them.
For example header needs to be Stick_3A (in hex) and example given was:
53 54 69 63 6b 5f 33 41 while correct header is below. Also Zone 1 (global is actually (00) not (01) etc.
Now is working no problem. We are actually triggering scenes directly via IP from Lutron HomeWorks system.
Area A (0), Scene 1 Run:
53 74 69 63 6b 5f 33 41 6d 00 (02) 00 (00) (01) 00 00 00 00 00 00 00 00
first parenthesis - scene # (1 do 8)
second parenthesis - zone - 00=A, 01=B etc.
Third parenthesis - o1=play, 00=stop
and the best thing, there is no 40 command limit (like RS232) you can recall any of 8 scenes in any of 10 areas.
Been trying and trying for several evenings and hours in a row to figure it out.
I am trying to control the stick by ip.
What i do not understand is how to get the right values to control the page/scene that i want to turn on.
I mean, i have used a hex/text conversion tool.
when i converted the 1 field it said STICK_A3
using the example string from the manual
For triggering scene 5 on page A (page 0)
(0x53 0x74 0x69 0x63 0x6b 0x5f 0x33 0x41) < this string is able to convert.
(0x6D 0x00) < then i understand the second field always has to be 109 ( but these codes do not correspond with 109 ? .. ok well just copy this then and use like the manual says)
(0x05 0x00) < this should be the field to call scenes on pages, but how do i for example get the code for page B scene 2 ? this is not hex is it ?
The same goes for the following fields.
What am i not getting here ?
Hope someone can give me some info what and how to do since its getting pretty frustrating
Thanks in advance
To trigger a scene: Scene Number = Page Number * 50 + SceneNumber(0x05 0x00) < this should be the field to call scenes on pages, but how do i for example get the code for page B scene 2 ?
Example: Trigger scene 1 on page B:
We can work out the scene number is 51 using the above equation ...
51 = 1 * 50 + 1
But it's actually very simple:
Page A is scene 1-50, Page B 51-100 etc.
Next, convert 51 (decimal) into hexadecimal, which is 33. Then add it to the string in the correct location ...
53 74 69 63 6b 5f 33 41 6D 00 33 00 00 01 00 00 00 00 00 00 00 00 00 00
You should find that this triggers Scene 1, Page B.
it makes sence now.
I was converting it into hex and not hexadecimal.
This is why i got these strange results.
Also the reply from pilasz makes sence now.
Haven't fired up an scene yet but this is probably because of the homeseer plugin.
I do get messages back from the stick when i send a raw text string with the 53 74 69 63 6b 5f 33 41 6d 00 01 00 00 01 00 00 00 00 00 00 00 00 00 00 for example so i am a step further in the process.
Code: Select all
10-3-2018 8:17:24:[drhsIpPlugIn]->PostBackControlArray(0)=oTabCommands 10-3-2018 8:17:35:[drhsIpPlugIn]->Wait 500ms... 10-3-2018 8:17:36:[drhsIpPlugIn]->Got 110 response bytes from stickde3: Stick_3A# spots Keuken d Stick_3A# spots Keuken d
Also, the remote protocol document says that it sends a status packet every 5 seconds but it sends it like every second which is way too chatty. Is there any way to control the frequency of the status packet. Also, is there a more comprehensive document that expains that data in the status packet more thoroughly?
Asking cause I can't get status message from my stick-de3 after update.
As I remember with the previous version of the firmware there was enough do connect to TCP port 2431 to start receiving status packets.
Unfortunately with the Stick-DE3 firmware 2.1, the remote protocol no longer supports TCP packets. You must use UDP packets on port 2430 instead.
We need to update the documentation to reflect this. The last firmware that supported TCP remote protocol was 1.13.