To use Events2HVAC with Venstar devices, all of the following must be provided:
• One or more of the supported thermostats with the local API setting enabled on each thermostat. (See the Venstar thermostat manual on how to enable the api)
• Venstar device discovery uses SSDP to discover thermostats on your local network. Devices need to be on the same network as the Events2HVAC server for discovery to work. Also, if you have devices on different subnets or between routers and firewalls, discovery most likely will only see the local subnet. Undiscoverable thermostats will need to be manually configured with IP address and MAC address.
• It is highly recommended to set up each thermostat with a static IP address since this address is used to access the device. A DHCP change in IP address on a thermostat will cause unreliability and possibly a re-assignment to a different thermostat.
• Any thermostats that have a screen lock PIN or is using authentication for the local API must enter the credentials/pincode during the configuration of Events2HVAC. Please contact support if you have authentication or PIN codes enabled. We will need to do further testing to complete this part of the interface.
• Each device must be reachable from the Events2HVAC server IP address via the thermostat’s default api port (typically port 80 http).
• Reliable wireless connections to your thermostats.
• Events2HVAC software installed on premises (See system requirements in the Events2HVAC installation section.)
Note: Residential models of Venstar and any OEM thermostats that are non-Venstar branded have not been tested to date, so there may be some initial testing for sites that deploy these thermostats. Contact Streamside Solutions support for details on initial testing requirements.