Climate Plugin - Revision history

Wierdbeard65 at 08:31, 2 May 2010

2010-05-02T08:31:59Z

←Older revision		Revision as of 08:31, 2 May 2010
Line 1:		Line 1:
	[[Category:Climate]]		[[Category:Climate]]
	[[Category:LinuxMCE_Plugins]]		[[Category:LinuxMCE_Plugins]]
			{{versioninfo}}
	== Description ==		== Description ==

Bulek: /* Description of enhanced 710 plugin and ability to control displayed info on floorplans */

2008-12-15T15:48:54Z

Description of enhanced 710 plugin and ability to control displayed info on floorplans

Bulek at 15:46, 15 December 2008

2008-12-15T15:46:19Z

←Older revision		Revision as of 15:46, 15 December 2008
Line 246:		Line 246:
	*''More complicated to do opinion: I think that Thermostat is too complex including Heating,Cooling and Fan control. Maybe we also need some simpler devices like only heating thermostat and separate fan (ventilation control)...		*''More complicated to do opinion: I think that Thermostat is too complex including Heating,Cooling and Fan control. Maybe we also need some simpler devices like only heating thermostat and separate fan (ventilation control)...

			== Description of enhanced 710 plugin and ability to control displayed info on floorplans ==
			Currently, I've done this to enhance Climate Plugin under 710 (with the goal that changes will be in 810 too, when stable and finished)...I've come up with quite flexible idea of controlling what is displayed on floorplans for Climate devices (this could be easily extended to all rendering plugins)...I'll be happy to hear your opinions (please post to coresponding thread in Developers forum).


			I've done this:
			- by default behaviour stays the same as before
			- if you add Extra parameters data to certain device, then you can control info displayed on floorplan by its content:

			Explanation:

			State for Climate devices consists of following parts ($x x=1..5, represents each part of current state information):
			OSD display format for Orbiter floorplan ($1=ON/OFF,$2=HEAT\|COOL\|FAN_ONLY\|AUTO,$3=HIGH\|AUTO,$4=SET TEMP ($5=CURRENT TEMP))

			for instance: default string value for displaying exactly the same info as it is know is :
			'$1/$2/$3/$4 ($5)' - omit quotes when entering into Extra parameters!

			Climate device has a state consisting of five components: Active($1), Mode($2), FanMode($3),Setpoint($4),ActualTemp($5) and by default everything is displayed on floorplan... Now by changing this string you can easily control/select and add text info to floorplan - few examples :
			'Outside ($5)' will display text Outside and then ActualTemp
			'$2 ($4)' this is probably the thing for actual thermostat without fan....

			OSD string is changed from default - computed :
			- only if Extra parameters string exists
			- if they exist, $1..$5 are replaced by actual values one by one
			- everything else is intact...

			I've tried to do this on my 710 system and must admit that now my floorplan is getting more user friendly and informative....

			What do you think about solution ?

			I also have an idea for further possible replacement of hardcoded states that are displayed on floorplans:
			- for instance what if you don't like HEAT/COOL/AUTO, then you could set an replacement for them -something like
			'$1/$2/$3/$4 ($5) ?$3\|HEAT\|High?$3\|COOL\|Low' - omit quotes!

			String consists of parts, determined by '?' character. First part (obligatory) determines how will be values displayed on floorplan, remaining parts determine potential substitutions of predefined states to text that will be displayed on floorplan. In mentioned case, when evaluating $3, state of 'HEAT' is replaced by custom 'High' and 'COOL' is replaced by custom 'Low'...

			I'll try to code this in next few days, although will be happy if someone more c++ experienced will give a hand...



	[[User:Bulek\|Bulek]] 15:10, 2 December 2008 (CET)		[[User:Bulek\|Bulek]] 15:10, 2 December 2008 (CET)

Bulek: /* Potential problems with current content of Climate Plugin */

2008-12-02T14:10:26Z

Potential problems with current content of Climate Plugin

←Older revision		Revision as of 14:10, 2 December 2008
Line 245:		Line 245:

	*''More complicated to do opinion: I think that Thermostat is too complex including Heating,Cooling and Fan control. Maybe we also need some simpler devices like only heating thermostat and separate fan (ventilation control)...		*''More complicated to do opinion: I think that Thermostat is too complex including Heating,Cooling and Fan control. Maybe we also need some simpler devices like only heating thermostat and separate fan (ventilation control)...




			[[User:Bulek\|Bulek]] 15:10, 2 December 2008 (CET)

Bulek: /* Potential problems with current content of Climate Plugin */

2008-12-02T13:45:37Z

Potential problems with current content of Climate Plugin

←Older revision		Revision as of 13:45, 2 December 2008
Line 226:		Line 226:

	''I think that Climate_Plugin::GetFloorplanDeviceInfo seems a bit unfinished. IT also displays all devices with all state info in same coldblue color, cause state is probably never just "OFF" as if clause is checking.		''I think that Climate_Plugin::GetFloorplanDeviceInfo seems a bit unfinished. IT also displays all devices with all state info in same coldblue color, cause state is probably never just "OFF" as if clause is checking.
	IMHO this is not convenient,it's not necessary to show all that info for instance for temperature sensors. This would be fairly easy to ~~achieve~~.
			''IMHO this is not convenient,it's not necessary to show all that info for instance for temperature sensors. This would be fairly easy to correct.

	'''My plans:		'''My plans:

Bulek at 13:44, 2 December 2008

2008-12-02T13:44:09Z

Show changes

Bulek: /* Description */

2008-12-02T12:59:20Z

Description

←Older revision		Revision as of 12:59, 2 December 2008
Line 3:		Line 3:
	== Description ==		== Description ==

			Climate plugin takes care of climate devices. Handles commands, events and sets according device states. It also gives content to Orbiter plugin when it renders Climate devices on Orbiter's floorplans.

	== How to use Climate devices in Orbiter ==		== How to use Climate devices in Orbiter ==

Bulek: New page: Category:Climate Category:LinuxMCE_Plugins == Description == == How to use Climate devices in Orbiter ==

2008-12-02T12:11:00Z

New page: Category:Climate Category:LinuxMCE_Plugins == Description == == How to use Climate devices in Orbiter ==

New page

[[Category:Climate]]
[[Category:LinuxMCE_Plugins]]
== Description ==

== How to use Climate devices in Orbiter ==

←Older revision		Revision as of 15:48, 15 December 2008
Line 257:		Line 257:

	State for Climate devices consists of following parts ($x x=1..5, represents each part of current state information):		State for Climate devices consists of following parts ($x x=1..5, represents each part of current state information):
	OSD display format for Orbiter floorplan ($1=ON/OFF,$2=HEAT\|COOL\|FAN_ONLY\|AUTO,$3=HIGH\|AUTO,$4=SET TEMP ($5=CURRENT TEMP))		OSD display format for Orbiter floorplan ($1=ON/OFF,$2=HEAT\|COOL\|FAN_ONLY\|AUTO,$3=HIGH\|AUTO,$4=SET TEMP ($5=CURRENT TEMP))

	for instance: default string value for displaying exactly the same info as it is know is :		for instance: default string value for displaying exactly the same info as it is know is :
	'$1/$2/$3/$4 ($5)' - omit quotes when entering into Extra parameters!		'$1/$2/$3/$4 ($5)' - omit quotes when entering into Extra parameters!

	Climate device has a state consisting of five components: Active($1), Mode($2), FanMode($3),Setpoint($4),ActualTemp($5) and by default everything is displayed on floorplan... Now by changing this string you can easily control/select and add text info to floorplan - few examples :		Climate device has a state consisting of five components: Active($1), Mode($2), FanMode($3),Setpoint($4),ActualTemp($5) and by default everything is displayed on floorplan... Now by changing this string you can easily control/select and add text info to floorplan - few examples :
	'Outside ($5)' will display text Outside and then ActualTemp		'Outside ($5)' will display text Outside and then ActualTemp
	'$2 ($4)' this is probably the thing for actual thermostat without fan....		'$2 ($4)' this is probably the thing for actual thermostat without fan....

	OSD string is changed from default - computed :		OSD string is changed from default - computed :
	- only if Extra parameters string exists		- only if Extra parameters string exists
	- if they exist, $1..$5 are replaced by actual values one by one		- if they exist, $1..$5 are replaced by actual values one by one
	- everything else is intact...		- everything else is intact...

	I've tried to do this on my 710 system and must admit that now my floorplan is getting more user friendly and informative....		I've tried to do this on my 710 system and must admit that now my floorplan is getting more user friendly and informative....
Line 277:		Line 277:
	I also have an idea for further possible replacement of hardcoded states that are displayed on floorplans:		I also have an idea for further possible replacement of hardcoded states that are displayed on floorplans:
	- for instance what if you don't like HEAT/COOL/AUTO, then you could set an replacement for them -something like		- for instance what if you don't like HEAT/COOL/AUTO, then you could set an replacement for them -something like
	'$1/$2/$3/$4 ($5) ?$3\|HEAT\|High?$3\|COOL\|Low' - omit quotes!		'$1/$2/$3/$4 ($5) ?$3\|HEAT\|High?$3\|COOL\|Low' - omit quotes!

	String consists of parts, determined by '?' character. First part (obligatory) determines how will be values displayed on floorplan, remaining parts determine potential substitutions of predefined states to text that will be displayed on floorplan. In mentioned case, when evaluating $3, state of 'HEAT' is replaced by custom 'High' and 'COOL' is replaced by custom 'Low'...		String consists of parts, determined by '?' character. First part (obligatory) determines how will be values displayed on floorplan, remaining parts determine potential substitutions of predefined states to text that will be displayed on floorplan. In mentioned case, when evaluating $3, state of 'HEAT' is replaced by custom 'High' and 'COOL' is replaced by custom 'Low'...