Difference between revisions of "Command:1"
From Awesome Baozam
(13 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | == | + | ==GET== |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | == | + | 1 cmd type |
− | + | 2 cmd id // set by server | |
+ | 1 {{{1|parameter}}}s count // max 256 | ||
+ | {{{1|parameter}}}* | ||
+ | 4* address | ||
+ | |||
+ | <noinclude> | ||
+ | === Notes === | ||
+ | * If count == 0 device should send in response all parameters | ||
+ | * TODO depend on user level (?) | ||
+ | |||
+ | {{cmd:2}} |
Latest revision as of 11:23, 18 November 2015
GET
1 cmd type 2 cmd id // set by server 1 parameters count // max 256
parameter*
4* address
Notes
- If count == 0 device should send in response all parameters
- TODO depend on user level (?)
response to GET
1 cmd type 2 cmd id // set by server 1 parameters count // max 256
parameter*
4 address 1 parameter type [wl] values count; if this > 1 then pt < 0 and this byte presents in the packet v* value; see details into parameter type