You will need to create a service account or use an existing user account in the Honeywell Home app for Events2HVAC to login to the remote API and send commands to thermostats. Events2HVAC will exchange an OAUTH2 token with the logged in user and use that token for communications with the API.
Since the E2H talks to the Honeywell Home API in the cloud, a reliable Internet connection is required between the local facility where Events2HVAC is running and the Honeywell Home API servers. 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.
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.
Note: Events2HVAC won’t be able to notify users if the command doesn’t make it to the thermostat. E2H will send the command to the API server, but the API server is responsible for making sure the command is delivered to the thermostat.
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 sending a HOLD command to the thermostat. Optionally for unoccupied mode, you can either HOLD 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.