I’ve just released a new version of MyNextTstat (v1.0g) which contains the required logic for settings an ETA and cancelling an ETA through the setETA and cancelETA commands.
Examples of calls in a smartapp or in CoRE/webCoRE (rule engine):
YourNestTstat.setETA("",“sample-trip-id”,“2018-01-30 23:00:00”,“2018-01-31 23:59:59”)
N.B. The ETA start time must be within few hours/minutes of the current time, otherwise Nest will not accept it.
The new commands above allow additional capabilities for your HA scenarios with your Nest thermostat.
How ETA works
In some cases, users have a 3rd-party app that uses GPS to provide estimated time of arrival (ETA) data to the Nest API. In other cases, the user might use an app to manually enter their ETA. Or maybe the ETA is calcluated based on the user’s regular schedule.
ETA apps that are integrated with the Nest Thermostat cause the thermostat to begin warming or cooling the home before the user arrives.
Please refer to the Nest documentation about this topic:
Also, please note of the following Nest’s ETA behavior:
When you send ETA data to the API, the thermostat uses it as one of many inputs to decide whether or not to activate the hvac equipment. Over time, it will try to determine whether the ETA data from your application is accurate. If it thinks it is accurate, it will use it to activate the heating/cooling system.
To use it successfully, you need to put ETA objects like you did above (multiple over time works better). If your ETA estimates are accurate, nest will use them.
The new code is available at my store.
P.S. My contributors can use their existing selffy download link to get the latest versions.