Changes between Version 11 and Version 12 of WikiStart
- Timestamp:
- 2012-03-21 17:52:02 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v11 v12 23 23 3. Vera will display the message "Please wait while the plugin is downloaded". 24 24 25 4. Click "close" on the "Please wait..." dialog in the Vera portal.25 4. Once the plugin has been downloaded and installed, Vera will show the device configuration dialog 26 26 27 5. On the Advanced Tab of the device configuration dialog, enter the IP Address of your thermostat in the "IP" field.27 5. Click on the "Advanced" tab of the device configuration dialog, enter the IP Address of your thermostat in the "ip" field. 28 28 29 29 6. Close the configuration dialog, and click "Save" to save your configuration. … … 37 37 Vera does not attempt to take exclusive control of the thermostat. Unless the thermostat is placed in "Hold" or "Simple Screen" mode, the schedule programmed into the thermostat will still be in effect. If you're feeling adventurous and want to completely control the thermostat from Vera, I would suggest placing the thermostat in Simple Screen mode. (this is effectively hold mode, but without displaying "Hold" on the thermostat display) See the "How to change from standard screen to simple screen" link on [http://www.radiothermostat.com/filtrete/help/ this page] for information on how to change to simple screen mode. 38 38 39 = Advanced Configuration = 40 41 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. 42 43 === !InitialPollDelay === 44 45 '''Default Value:''' 3 46 47 '''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. 48 49 === !PollInterval === 50 51 '''Default Value:''' 60 52 53 '''Description:''' The time period (in seconds) to wait between each poll of the thermostat. 54 55 === !LogLevel === 56 57 '''Default Value:''' 20 58 59 '''Description:''' Set the logging level / verbosity. Three levels are supported: 60 61 10 - Error (least verbose) 62 20 - Info (medium verbosity) 63 30 - Debug (most verbose) 64 65 === !ForceHold === 66 67 '''Default Value:''' 0 68 69 '''Description:''' When this variable is set to "1", the thermostat plugin will set the thermostat into "hold" mode 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. 70 39 71 = Known Issues / Limitations = 40 72 41 * Vera only has access to the current heating and/or cooling setpoint values when the thermostat is actually set in that mode. That is, if you startup the plugin with the thermostat in heating mode, the cooling setpoint will not be updated. (and vise-verse) 42 * Changing the setpoint for heating will place the thermostat in heating mode, regardless of it's current mode. (i.e. it would switch from cooling to heating). The reverse is also true: setting the cooling setpoint will place the thermostat in cooling mode. 73 * Changing the temperature set point for heating will place the thermostat in heating mode, regardless of it's current mode. (i.e. the thermostat will switch from cooling to heating mode). The reverse is also true: setting the cooling set point will place the thermostat in cooling mode. 43 74 44 75 = Future Enhancements = … … 46 77 This is a list of things that should be possible to implement in the future. If you're interested in any of these, let me know: 47 78 48 * Adjustable polling interval (currently fixed at 60 seconds)49 79 * Display current status information (fan running, actively cooling, etc.), not just settings, in the Vera UI 50 80 * View and set thermostat's built-in schedule from Vera UI 51 81 * Provide more detailed status information for multi-stage systems. For example, instead of just "heating", provide a status that differentiates between which stage is active (heat-pump vs aux/electric). This would be useful for detailed energy tracking. 52 82 83 = Version History = 84 85 == 0.7 == 86 * Added adjustable polling interval 87 * Added Celsius support 88 * Re-based UI on current UI5 Z-Wave thermostat UI 89 * Added support for maintaining hold setting across mode changes 90 * Added support for "Force Hold" to always keep thermostat in hold mode 91 * Reworked logging code to support run-time adjustable log levels 92 93 == 0.4 == 94 * Improved reliability of communications, minor bug fixes 95 96 == 0.1 == 97 * Initial release 98