Sensors - Revision history

Wierdbeard65 at 07:19, 3 May 2010

2010-05-03T07:19:02Z

←Older revision		Revision as of 07:19, 3 May 2010
Line 1:		Line 1:
			{{Versioninfo}}
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]
	[[Category: Security]]		[[Category: Security]]

Perspectoff at 16:53, 21 May 2008

2008-05-21T16:53:36Z

←Older revision		Revision as of 16:53, 21 May 2008
Line 1:		Line 1:
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]
			[[Category: Security]]

	==Sending events from command line==		==Sending events from command line==

Ddamron: /* Standard Thermostat */

2008-01-01T11:44:54Z

Standard Thermostat

←Older revision		Revision as of 11:44, 1 January 2008
Line 76:		Line 76:

	Anyone has more insight into this ?		Anyone has more insight into this ?

			I was experiencing the same problem with lighting devices. It turns out that ON/OFF (cmds 192/193) are INDEPENDANT of other commands (in my case it was cmd184 - SetLevel, but it looks like your experiencing the same problem)
			This is why you can have OFF/100.. the OFF being the ON/OFF part, and the 100 being the variable state.. My suggestion is that you set BOTH variables at the same time.

			ddamron

Zaerc: added to "programmer's guide"

2007-10-23T15:29:14Z

added to "programmer's guide"

←Older revision		Revision as of 15:29, 23 October 2007
Line 1:		Line 1:
			[[Category: Programmer's Guide]]

	==Sending events from command line==		==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) :		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) :

Bulek: /* Standard Thermostat */

2007-10-22T23:21:52Z

Standard Thermostat

←Older revision		Revision as of 23:21, 22 October 2007
Line 50:		Line 50:
	Command: Set Thermostat to OFF		Command: Set Thermostat to OFF
	/usr/pluto/bin/MessageSend localhost 0 ID 1 193 97 "" 98 ""		/usr/pluto/bin/MessageSend localhost 0 ID 1 193 97 "" 98 ""



	'''Events:'''		'''Events:'''


	Event: Temperature changed to value - 14.2		Event: Temperature changed to value - 14.2

Bulek at 23:21, 22 October 2007

2007-10-22T23:21:30Z

←Older revision		Revision as of 23:21, 22 October 2007
Line 33:		Line 33:


	= Commands: =		'''Commands:'''


Line 51:		Line 51:
	/usr/pluto/bin/MessageSend localhost 0 ID 1 193 97 "" 98 ""		/usr/pluto/bin/MessageSend localhost 0 ID 1 193 97 "" 98 ""

	== Events: ==		'''Events:'''

	Event: Temperature changed to value - 14.2		Event: Temperature changed to value - 14.2

Bulek: /* Commands: */

2007-10-22T23:20:46Z

Commands:

←Older revision		Revision as of 23:20, 22 October 2007
Line 33:		Line 33:


	== Commands: ==		= Commands: =


Line 50:		Line 50:
	Command: Set Thermostat to OFF		Command: Set Thermostat to OFF
	/usr/pluto/bin/MessageSend localhost 0 ID 1 193 97 "" 98 ""		/usr/pluto/bin/MessageSend localhost 0 ID 1 193 97 "" 98 ""


	== Events: ==		== Events: ==

Bulek: /* Standard Thermostat */

2007-10-22T23:20:12Z

Standard Thermostat

←Older revision		Revision as of 23:20, 22 October 2007
Line 31:		Line 31:

	I've tested possible commands and events below. But I'm not sure of true meaning of values and if thermostat or Climate Plugin does anything with them ?		I've tested possible commands and events below. But I'm not sure of true meaning of values and if thermostat or Climate Plugin does anything with them ?


			== Commands: ==


	Command: Set Fan to "1" or "0" (not shown on floorplan!?)		Command: Set Fan to "1" or "0" (not shown on floorplan!?)
Line 47:		Line 51:
	/usr/pluto/bin/MessageSend localhost 0 ID 1 193 97 "" 98 ""		/usr/pluto/bin/MessageSend localhost 0 ID 1 193 97 "" 98 ""


			== Events: ==

	Event: Temperature changed to value - 14.2		Event: Temperature changed to value - 14.2

Bulek: /* Standard Thermostat */

2007-10-22T23:19:30Z

Standard Thermostat

←Older revision		Revision as of 23:19, 22 October 2007
Line 39:		Line 39:

	Command: Set Temperature to "value"		Command: Set Temperature to "value"
	/usr/pluto/bin/MessageSend localhost 0 ID 1 278 5 "18.3"		/usr/pluto/bin/MessageSend localhost 0 ID 1 278 5 "18.3"

	Command: Set Thermostat to ON		Command: Set Thermostat to ON

Bulek: /* Standard Thermostat */

2007-10-22T23:17:42Z

Standard Thermostat

←Older revision		Revision as of 23:17, 22 October 2007
Line 39:		Line 39:

	Command: Set Temperature to "value"		Command: Set Temperature to "value"
	/usr/pluto/bin/MessageSend localhost 0 ~~172~~ 1 278 5 "18.3"		/usr/pluto/bin/MessageSend localhost 0 ID 1 278 5 "18.3"

	Command: Set Thermostat to ON		Command: Set Thermostat to ON
	/usr/pluto/bin/MessageSend localhost 0 ~~172~~ 1 192 97 "" 98 ""		/usr/pluto/bin/MessageSend localhost 0 ID 1 192 97 "" 98 ""

	Command: Set Thermostat to OFF		Command: Set Thermostat to OFF
	/usr/pluto/bin/MessageSend localhost 0 ~~172~~ 1 193 97 "" 98 ""		/usr/pluto/bin/MessageSend localhost 0 ID 1 193 97 "" 98 ""


	Event: Temperature changed to value - 14.2		Event: Temperature changed to value - 14.2
	/usr/pluto/bin/MessageSend dcerouter ~~172~~ -1000 2 25 30 14.2		/usr/pluto/bin/MessageSend dcerouter ID -1000 2 25 30 14.2

	Event: Humidity changed to value of 40 (not shown on floorplan!?)		Event: Humidity changed to value of 40 (not shown on floorplan!?)
	/usr/pluto/bin/MessageSend dcerouter ~~172~~ -1000 2 26 30 40		/usr/pluto/bin/MessageSend dcerouter ID -1000 2 26 30 40

	Event: SetPoint changed to value of 16 (not shown on floorplan!?)		Event: SetPoint changed to value of 16 (not shown on floorplan!?)
	/usr/pluto/bin/MessageSend dcerouter ~~172~~ -1000 2 27 30 16		/usr/pluto/bin/MessageSend dcerouter ID -1000 2 27 30 16

	Event: Climate system changed to ON (not shown on floorplan!?)		Event: Climate system changed to ON (not shown on floorplan!?)
	/usr/pluto/bin/MessageSend dcerouter ~~172~~ -1000 2 28		/usr/pluto/bin/MessageSend dcerouter ID -1000 2 28

	Event: Climate system changed to OFF (not shown on floorplan!?)		Event: Climate system changed to OFF (not shown on floorplan!?)
	/usr/pluto/bin/MessageSend dcerouter ~~172~~ -1000 2 29		/usr/pluto/bin/MessageSend dcerouter ID -1000 2 29

	I'm still missing something about this device. What are true meanings of commands and events. For instance, when you send command ON/OFF, change is shown on Floorplan. But when you send event ON/OFF state is not changed... Also, why are not all parameters saved in state ? Only AUTO/HEAT/COOL/ON/OFF and temperature setpoint are shown on floorplan. I'm also not sure what does 100 means in state of thermostat - "OFF/100(19.2)". After some messages it's value changed to "OFF/1 (19.2)" - but I guess this must be some mixup in code that probably truncates state text to show on floorplan. Also value of 100 doesn't change with any above commands or events...		I'm still missing something about this device. What are true meanings of commands and events. For instance, when you send command ON/OFF, change is shown on Floorplan. But when you send event ON/OFF state is not changed... Also, why are not all parameters saved in state ? Only AUTO/HEAT/COOL/ON/OFF and temperature setpoint are shown on floorplan. I'm also not sure what does 100 means in state of thermostat - "OFF/100(19.2)". After some messages it's value changed to "OFF/1 (19.2)" - but I guess this must be some mixup in code that probably truncates state text to show on floorplan. Also value of 100 doesn't change with any above commands or events...

	Anyone has more insight into this ?		Anyone has more insight into this ?