1) Give a description of the problem
I’ve recently noticed Nest isn’t updating to the Heating Set Point as set via webcore/smartthings.
2) What is the expected behaviour?
Webcore sets the setpoint to say 25deg (roasting warm, yes I know), and smartthings IDE updates to set point 25deg but the actual Nest device is not updating, nor is the heating kicking in.
3) What is happening/not happening?
As above, Nest is not updating to command.
**4)
**5)
29/05/2019, 09:50:59 +617ms
+1ms ╔Received event [Test].switch = on with a delay of 102ms
+70ms ║RunTime Analysis CS > 18ms > PS > 27ms > PE > 25ms > CE
+73ms ║Runtime (40274 bytes) successfully initialized in 27ms (v0.3.10b.20190514) (70ms)
+74ms ║╔Execution stage started
+88ms ║║Comparison (enum) on is (string) on = true (2ms)
+90ms ║║Condition #37 evaluated true (10ms)
+95ms ║║Comparison (enum) on changes_to (string) on = true (1ms)
+97ms ║║Cancelling condition #44’s schedules…
+98ms ║║Condition #44 evaluated true (7ms)
+100ms ║║Cancelling condition #32’s schedules…
+101ms ║║Condition group #32 evaluated true (state changed) (21ms)
+104ms ║║Cancelling statement #33’s schedules…
+115ms ║║Skipped execution of physical command [Nest Thermostat - Dining Room].setThermostatMode([heat]) because it would make no change to the device. (4ms)
+116ms ║║Executed [Nest Thermostat - Dining Room].setThermostatMode (6ms)
+7073ms ║║Executed physical command [Nest Thermostat - Dining Room].setHeatingSetpoint([22.0]) (6953ms)
+7075ms ║║Executed [Nest Thermostat - Dining Room].setHeatingSetpoint (6955ms)
+7079ms ║║Executed virtual command [Nest Thermostat - Dining Room].wait (1ms)
+7081ms ║║Requesting a wake up for Wed, May 29 2019 @ 10:06:06 AM BST (in 900.0s)
+7086ms ║╚Execution stage complete. (7013ms)
+7088ms ║Setting up scheduled job for Wed, May 29 2019 @ 10:06:06 AM BST (in 899.995s)
+7101ms ╚Event processed successfully (7100ms)