Changes between Version 20 and Version 21 of WikiStart
- Timestamp:
- 2012-05-16 22:12:54 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v20 v21 1 1 [[Image(thermostat.jpg)]][[Image(VeraControl.png)]] 2 3 [[PageOutline(1-3,Contents,inline)]] 2 4 3 5 = Introduction = … … 45 47 The following settings on the "Advanced" tab of the device configuration dialog can be used to alter the default behavior of the thermostat plug-in. 46 48 47 == = !InitialPollDelay ===49 == !InitialPollDelay == 48 50 49 51 '''Required Plugin Version:''' 0.7+ … … 53 55 '''Description:''' The time period (in seconds) to wait between the device being initialized by Vera (i.e. at Vera startup) and the first poll of the thermostat device. If you have multiple thermostats, this setting can be used to "stagger" polling so that not all thermostats are polled at the same time. 54 56 55 == = !PollInterval ===57 == !PollInterval == 56 58 57 59 '''Required Plugin Version:''' 0.7+ … … 61 63 '''Description:''' The time period (in seconds) to wait between each poll of the thermostat. 62 64 63 == = !LogLevel ===65 == !LogLevel == 64 66 65 67 '''Required Plugin Version:''' 0.7+ … … 73 75 * 30 - Debug (most verbose) 74 76 75 == = !ForceHold ===77 == !ForceHold == 76 78 77 79 '''Required Plugin Version:''' 0.7+ … … 81 83 '''Description:''' When this variable is set to "1", the thermostat plugin will set the thermostat into "hold" mode and restore the previous setpoint anytime it discovers that the thermostat is not in "hold" mode. If you are using Vera to control your thermostat schedule, this setting is useful to prevent the thermostat being accidentally removed from hold mode and the internal thermostat program "taking over". 82 84 83 == = !ProgramSetpoints ===85 == !ProgramSetpoints == 84 86 85 87 '''Required Plugin Version:''' 0.8+ … … 91 93 Note: Due to the fact that this feature erases the internal schedule of your thermostat, I suggest using "ForceHold" by first, and then enabling this feature only if "ForceHold" doesn't provide enough control of the thermostat. 92 94 93 == = !ClockSync ===95 == !ClockSync == 94 96 95 97 '''Required Plugin Version:''' 0.8+ … … 101 103 Note: if you're using Radio Thermostat's cloud services, I wouldn't suggest enabling this feature as the plugin will "fight" with the cloud to keep your clock in sync. 102 104 103 == = PMATempDevice ===105 == PMATempDevice == 104 106 105 107 '''Required Plugin Version:''' 0.8+ … … 113 115 [[Image(DeviceNum.png)]] 114 116 115 == = !RemoteTempDevice ===117 == !RemoteTempDevice == 116 118 117 119 '''Required Plugin Version:''' 0.8+ … … 121 123 '''Description:''' This variable works the same way as !PMATempDevice, except that the Vera temperature device temperature is displayed as the main temperature on your thermostat, and the entire thermostat operation (heating, cooling, schedule activation, etc.) is then based on the temperature of the Vera supported sensor, not the thermostat's internal temperature sensor. 122 124 123 == = !LooseTempControl ===125 == !LooseTempControl == 124 126 125 127 '''Required Plugin Version:''' 1.0+