Difference between revisions of "Sensors"
From LinuxMCE
| Line 17: | Line 17: | ||
ID -1000 2 29 | 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 | /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" | ||
Revision as of 15:25, 26 January 2007
| This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto. |
There is a utility in pluto (/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"
