The Venstar interface uses the thermostat’s local API to send/receive data to each thermostat. The local API configuration setting in the thermostat, by default, is disabled. You will need to turn this option ON for each thermostat using the steps in the thermostat manual.
If you are using a ColorTouch model or any model that supports screen lock and/or authentication for the API, you will need to include the pincode and/or the username/password for each thermostat that requires this information. If you have a common pincode and/or passcode, you can choose between a global setting or individual credentials.
A reliable intranet connection is required between the PC where Events2HVAC is running and each thermostat. If the connection goes down, the last commands and setpoints sent to the thermostats will remain in effect until the local thermostat is changed or the connection is restored.
Events2HVAC will send alerts to email addresses subscribed to receive them if commands are not getting to the API. This will enable alert subscribers to take action can if needed.
Events2HVAC does not create schedules on the thermostat but sends the scheduled commands to the thermostat at the appropriate time based on the event schedules. Events2HVAC will automatically override local thermostat schedules during the occupied mode by turning off the scheduler to the thermostat. Optionally for unoccupied mode, you can either keep the unoccupied setpoints or return the thermostat back to the current scheduled period.
You can always override the current thermostat command at any time, but when the next event’s command is sent, Events2HVAC will take over again.
Discovery of Thermostats
Since Venstar uses Simple Service Discovery Protocol (SSDP) for thermostat discovery, you should locate the Events2HVAC server on the same network as the WIFI thermostat network. If the thermostats are on multiple different WIFI networks, the discovery will only find the ones on the same subnet. You will need to manually connect the other remote thermostats with the IP address and MAC address information. Your IT department can assist with this process.
Warning: Each thermostat needs to be assigned a static IP address on your WIFI network, not dynamic. Using a dynamic IP address can cause reliability issues and commands intended for one thermostat could potentially to be sent to a different thermostat. Your IT department will need to help you with this if it hasn’t already been done.
Override Button
When E2H sends commands, we turn off the schedules, unless you choose to return to schedules at the end of the event. The override button only works when schedules are active.
Available Modes
You have the option to program your available modes: Auto, Heat/Cool, Heat Only, Cool Only. It is recommended you program all thermostats to use the same available mode in order to be able to use a global setpoint for your thermostats. If one allows Auto and the rest are Heat Only, then an Auto command will fail on the Heat Only thermostats.
Setpoint Limits
If you have setpoint limits enabled in the thermostat and you try to send heating or cooling setpoint beyond the limits defined, the E2H command will be rejected.
Smart Recovery
Since E2H doesn’t send schedules to your thermostats, the Smart Recovery feature can’t be used. Events2HVAC will send occupancy setpoints to the thermostat at the pre-defined start time for the event minus any pre-start time in the E2H zone.
Holiday
Holidays will send the thermostat to unoccupied schedule if the schedule is running. E2H will override any holiday that is taking place in the thermostat. If at the end of the E2H occupancy the zone is set to “Return to schedule”, then the holiday will be allowed at the end of the event.