You will need to create a service account in the Pelican Site Manager for Events2HVAC to login to the remote API and send commands to thermostats.
Since the API talks to the Site Manager in the cloud, a reliable Internet connection is required between the local facility where Events2HVAC is running and the Site Manager. If the Internet 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.
Subscribers of Events2HVAC will get notified if commands are not getting to the thermostats so action can be taken locally if needed. As a precaution, it is recommended by the manufacturer to keep a failsafe schedule that will turn the thermostat to unoccupied mode at midnight each day or at some other time that should always be unoccupied.
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 disable local thermostat schedules during the occupied mode since these will conflict with commands sent by Events2HVAC.
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.