Difference between revisions of "Sensors"
From LinuxMCE
Jerry finn (Talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | + | ==Sending events from command line== | |
| − | There is a utility in | + | There is a utility in LinuxMCE (/usr/pluto/bin) that allows sending proper DCE message from command line. If you want for instance to trip motion sensors on/off you can achieve this in simple way (ID means ID of particular device that you send event for) : |
Event "tripped on" | Event "tripped on" | ||
Revision as of 10:45, 19 March 2007
Sending events from command line
There is a utility in LinuxMCE (/usr/pluto/bin) that allows sending proper DCE message from command line. If you want for instance to trip motion sensors on/off you can achieve this in simple way (ID means ID of particular device that you send event for) :
Event "tripped on"
ID -1000 2 9 25 1
Event "tripped off"
ID -1000 2 9 25 0
Event "temperature changed"
ID -1000 2 25 30 temperature_value
Event "output on"
ID -1000 2 28
Event "output off"
ID -1000 2 29
For instance -
A. tripping security sensor with ID of 195 to ON : /usr/pluto/bin/MessageSend dcerouter 195 -1000 2 9 25 1
B. play media (/home/public/data/tts/0.wav) on Xine player with ID of 44 : /usr/pluto/bin/MessageSend localhost 0 44 1 37 29 "" 41 "" 42 "" 59 "/home/public/data/tts/0.wav"
