From: Jon B. <jb...@co...> - 2014-01-15 16:59:22
|
This targeted at a specific automate-able thermostat? I've never owned a one. I just use a x10 relay module to open the HeatRequest white wire when the alarm is set. (It rarely get below freezing where I am.) However I was looking into upgrading to an officially automate-able thermostat. I was trending towards Honeywell even though its not an open API based on reverse engineering done here: http://www.bradgoodman.com/thermostat/ http://www.jimandbekki.com/capture-wifi-thermostat-data-on-linuxbash/ Using Honeywell may or may not be a good idea: Pros - Big company, mass produced thermostat, no reoccurring fees for online thermostat access, lower upfront cost. Cons - No public API, interface may updated and break and I might have to rewrite my scripts. On Wed, Jan 15, 2014 at 5:42 AM, Joel Davidson <jr...@pr...> wrote: > And along with setback on/off, we'll need the setback temperatures. > > > On Wed, 15 Jan 2014, it would appear that Timothy Spaulding wrote: > > > The only additional control I can think of is: > > > > Setback on|off > > > > -----Original Message----- > > From: dbemowsk [mailto:dbe...@ph...] > > Sent: Tuesday, January 14, 2014 10:23 PM > > To: mis...@li... > > Subject: [mh] Thermostat common control functions. > > > > This topic is an offshoot of my touchscreen web interface. I am trying > to come up with a list of the most common thermostat control functions to > include on the climate page of the touchscreen interface. Below is the list > that I have so far: > > > > * Setting the heating set point > > * Setting the cooling set point > > * Setting the mode. Available options: off, heat, cool or auto > > * Setting the fan mode to on or off > > > > If anyone can think of more functions to add to this small list, let me > know and I can add them. > > > > The plan with this is to write a set of subroutines that will act as a > bridge to the different thermostat module functions giving it a single > command set. This bridge code file will be placed in the users private code > directory to allow access from the web interface. My plan for the naming > convention for the different bridge files is this: > > > > thermostat_bridge_{module base name}.pl > > > > The {module base name} is the base name of the thermostat module that it > is set up to control, so for example if you use an RCS thermostat with the > RCSsTR40.pm module, the bridge file would be named > "thermostat_bridge_RCSsTR40.pl" > > > > The command set for the file will provide a standard set of sub > functions to perform the different control operations of the thermostat. > To use the heating set point as an example, the sub for that would look > something like > > this: > > > > # This routine is used to set the heating set point of the thermostat. > > sub therm_heat_setpoint { > > my ($hsp) = @_; > > $thermostat->heat_setpoint($hsp); > > } > > > > "$thermostat" is the module object variable that you have set in your > code. > > The sub function for setting the heating set point using the RCSsTR40.pm > module is "heat_setpoint($value)". This would change based on your > thermostat module. What this does is allows me to code the touchscreen > interface to call one sub to set the heating setpoint versus trying to code > in different control commands for each different thermostat module that is > out there just for one function. > > > > This is just one example of why it is a good idea to standardize the > code structure for common devices such as this. Having standards in place > would eliminate the need for such bridge type files which are just more > lines of code that need to get processed eating up CPU cycles. > > > > As always, I welcome any input or feedback on this issue. > > > > Dan Bemowski. > > > > > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > |