DCE from commandline - Revision history

Matthew: Specify MessageSend command

2008-01-22T00:30:59Z

Specify MessageSend command

←Older revision		Revision as of 00:30, 22 January 2008
Line 1:		Line 1:
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]
	=Sending DCE events from command line=		=Sending DCE events from command line=
	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) :		There is a utility in pluto (/usr/pluto/bin/[[MessageSend]]) 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"

Matthew: Shift section degrees down to start at 1

2008-01-22T00:30:24Z

Shift section degrees down to start at 1

←Older revision		Revision as of 00:30, 22 January 2008
Line 1:		Line 1:
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]
	==Sending DCE events from command line==		=Sending DCE events from command line=
	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) :		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) :

Line 35:		Line 35:
	/usr/pluto/bin/MessageSend dcerouter 210 -1000 2 48 10 1		/usr/pluto/bin/MessageSend dcerouter 210 -1000 2 48 10 1

	==Sending DCE commands from command line==		=Sending DCE commands from command line=

	Change HouseMode command :		Change HouseMode command :
Line 78:		Line 78:


	==Other interesting DCE messages==		=Other interesting DCE messages=

	Will parse the meaning of DCE messages below in future. Just wrote it here to remember....		Will parse the meaning of DCE messages below in future. Just wrote it here to remember....

Hari at 13:58, 20 December 2007

2007-12-20T13:58:23Z

←Older revision		Revision as of 13:58, 20 December 2007
Line 1:		Line 1:
			[[Category: Programmer's Guide]]
	==Sending DCE events from command line==		==Sending DCE events from command line==
	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) :		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) :

AVJohn at 15:35, 25 September 2007

2007-09-25T15:35:31Z

←Older revision		Revision as of 15:35, 25 September 2007
Line 64:		Line 64:

	I have found out the reason. -1000 is DCERouter address, but this kind of message should be addressed directly to Security plugin - in my case this is ID of 13. I'm following this, although don't understand distinction of -1000 and 13 - if DCERouter is addressed it should relay message to security plugin anyway - so I don't understand why this is necessary - any opinion ?		I have found out the reason. -1000 is DCERouter address, but this kind of message should be addressed directly to Security plugin - in my case this is ID of 13. I'm following this, although don't understand distinction of -1000 and 13 - if DCERouter is addressed it should relay message to security plugin anyway - so I don't understand why this is necessary - any opinion ?
			<i><div style="padding-left: 30px; background: #DDDDDD;">As far as I can tell, the reason for '-1000' is to allow devices to broadcast events to the system as a whole rather than to a specific device, presumably for event-based devices that do not do a specific function. I shall look more into this... -AVJohn.</div></i>

	/usr/pluto/bin/MessageSend localhost 0 13 1 19 5 6 17 7 99 5678 100 0 101 R		/usr/pluto/bin/MessageSend localhost 0 13 1 19 5 6 17 7 99 5678 100 0 101 R

Bulek: /* Other interesting DCE messages */

2007-09-13T12:59:44Z

Other interesting DCE messages

←Older revision		Revision as of 12:59, 13 September 2007
Line 80:		Line 80:
	Will parse the meaning of DCE messages below in future. Just wrote it here to remember....		Will parse the meaning of DCE messages below in future. Just wrote it here to remember....

			It seems like "Goto Screen" command
	/usr/pluto/bin/MessageSend localhost 0 64 1 741 10 "Whatever" 159 53 9 'A message\|Ok\|Remind me later' 137 '-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer yes"\|-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer no"'		/usr/pluto/bin/MessageSend localhost 0 64 1 741 10 "Whatever" 159 53 9 'A message\|Ok\|Remind me later' 137 '-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer yes"\|-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer no"'

	To display Text Alert on Orbiter :		To display Text Alert on Orbiter :
	/usr/pluto/bin/MessageSend localhost 0 20 1 809 9 "Text to Display" 70 "alert" 182 "30" 251 "??"		/usr/pluto/bin/MessageSend localhost 0 20 1 809 9 "Text to Display" 70 "alert" 182 "30" 251 "??"

			Also interesting command is #397 "Show popup", but I have yet to discover how to use it...

	Does anyone know how to display popup with question and few answer buttons (yes/no for example) ? Can this be done without Designer to create screen - just to specify question, texts on buttons and actions on click ?		Does anyone know how to display popup with question and few answer buttons (yes/no for example) ? Can this be done without Designer to create screen - just to specify question, texts on buttons and actions on click ?

Bulek: /* Other interesting DCE messages */

2007-09-13T12:58:15Z

Other interesting DCE messages

←Older revision		Revision as of 12:58, 13 September 2007
Line 78:		Line 78:
	==Other interesting DCE messages==		==Other interesting DCE messages==

	Will parse the meaning of DCE ~~message~~ in future. Just wrote it here to remember....		Will parse the meaning of DCE messages below in future. Just wrote it here to remember....

	/usr/pluto/bin/MessageSend localhost 0 64 1 741 10 "Whatever" 159 53 9 'A message\|Ok\|Remind me later' 137 '-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer yes"\|-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer no"'		/usr/pluto/bin/MessageSend localhost 0 64 1 741 10 "Whatever" 159 53 9 'A message\|Ok\|Remind me later' 137 '-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer yes"\|-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer no"'

			To display Text Alert on Orbiter :
			/usr/pluto/bin/MessageSend localhost 0 20 1 809 9 "Text to Display" 70 "alert" 182 "30" 251 "??"

			Does anyone know how to display popup with question and few answer buttons (yes/no for example) ? Can this be done without Designer to create screen - just to specify question, texts on buttons and actions on click ?

Bulek at 12:43, 13 September 2007

2007-09-13T12:43:55Z

←Older revision		Revision as of 12:43, 13 September 2007
Line 74:		Line 74:
	08 09/11/07 16:06:53.512 Parameter 100(PK_DeviceGroup): 0		08 09/11/07 16:06:53.512 Parameter 100(PK_DeviceGroup): 0
	08 09/11/07 16:06:53.512 Parameter 101(Handling Instructions): R		08 09/11/07 16:06:53.512 Parameter 101(Handling Instructions): R


			==Other interesting DCE messages==

			Will parse the meaning of DCE message in future. Just wrote it here to remember....

			/usr/pluto/bin/MessageSend localhost 0 64 1 741 10 "Whatever" 159 53 9 'A message\|Ok\|Remind me later' 137 '-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer yes"\|-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer no"'

Bulek: /* Sending DCE commands from command line */

2007-09-12T12:11:44Z

Sending DCE commands from command line

←Older revision		Revision as of 12:11, 12 September 2007
Line 58:		Line 58:
	/usr/pluto/bin/MessageSend localhost 0 -1000 1 19 5 2 17 7 99 5678 100 0 101 R		/usr/pluto/bin/MessageSend localhost 0 -1000 1 19 5 2 17 7 99 5678 100 0 101 R

	Also sending event House Mode Changed doesn't actually change house mode:		Also sending event House Mode Changed doesn't actually change house mode (that's ok, cause events are meant for notifying):

	/usr/pluto/bin/MessageSend localhost 0 -1000 2 43 38 0 39 2		/usr/pluto/bin/MessageSend localhost 0 -1000 2 43 38 0 39 2

Bulek: /* Sending DCE commands from command line */

2007-09-12T12:11:03Z

Sending DCE commands from command line

←Older revision		Revision as of 12:11, 12 September 2007
Line 63:		Line 63:


	I have found out the reason. -1000 is DCERouter address, but this kind of message should be addressed directly to Security plugin - in my case this is ID of 13.		I have found out the reason. -1000 is DCERouter address, but this kind of message should be addressed directly to Security plugin - in my case this is ID of 13. I'm following this, although don't understand distinction of -1000 and 13 - if DCERouter is addressed it should relay message to security plugin anyway - so I don't understand why this is necessary - any opinion ?

	/usr/pluto/bin/MessageSend localhost 0 13 1 19 5 6 17 7 99 5678 100 0 101 R		/usr/pluto/bin/MessageSend localhost 0 13 1 19 5 6 17 7 99 5678 100 0 101 R

Bulek: /* Sending DCE commands from command line */

2007-09-12T12:09:48Z

Sending DCE commands from command line

←Older revision		Revision as of 12:09, 12 September 2007
Line 58:		Line 58:
	/usr/pluto/bin/MessageSend localhost 0 -1000 1 19 5 2 17 7 99 5678 100 0 101 R		/usr/pluto/bin/MessageSend localhost 0 -1000 1 19 5 2 17 7 99 5678 100 0 101 R

	Also sending event House Mode Changed doesn't ~~do anything~~ :		Also sending event House Mode Changed doesn't actually change house mode:

	/usr/pluto/bin/MessageSend localhost 0 -1000 2 43 38 0 39 2		/usr/pluto/bin/MessageSend localhost 0 -1000 2 43 38 0 39 2


	~~Will try to find~~ out ~~what~~ is ~~proper way~~ to ~~change~~ house mode ~~from external systems~~...		I have found out the reason. -1000 is DCERouter address, but this kind of message should be addressed directly to Security plugin - in my case this is ID of 13.
			/usr/pluto/bin/MessageSend localhost 0 13 1 19 5 6 17 7 99 5678 100 0 101 R

			Now it changes security mode properly... Parameters in this command line are :
			0 from, 13 to Security plugin, 1-Type: Command, 19-Command "Set house mode", and the rest:
			08 09/11/07 16:06:53.512 Parameter 5(Value To Assign): 1
			08 09/11/07 16:06:53.512 Parameter 17(PK_Users): 7
			08 09/11/07 16:06:53.512 Parameter 99(Password): 5678
			08 09/11/07 16:06:53.512 Parameter 100(PK_DeviceGroup): 0
			08 09/11/07 16:06:53.512 Parameter 101(Handling Instructions): R