raiseHeatingSetpoint Not Working on Honeywell TCC 8000/9000 Thermostat [SOLVED]


#1

1) Give a description of the problem
Trying to have my thermostat raise the heating set point by 1 degree, if the thermostat is in Heat mode.

2) What is the expected behavior?
As above.

3) What is happening/not happening?
Setpoint not raising. According to logs the command is being sent to the thermostat, but the set point does not change.

4) Post a Green Snapshot of the pistonimage

5) Attach any logs (From ST IDE and by turning logging level to Full)
10/26/2018, 2:02:21 PM +135ms
+3ms ╔Received event [187 Montgomery Avenue].routineExecuted = 2382ff84-4562-4223-bbc1-e39d92e50b69 with a delay of 67ms
+272ms ║RunTime Analysis CS > 16ms > PS > 50ms > PE > 205ms > CE
+275ms ║Runtime (48513 bytes) successfully initialized in 50ms (v0.3.108.20180906) (271ms)
+276ms ║╔Execution stage started
+311ms ║║Condition #4 evaluated false (25ms)
+312ms ║║Condition group #19 evaluated false (state did not change) (28ms)
+314ms ║║Condition group #31 evaluated false (state did not change) (30ms)
+322ms ║║Comparison (string) :2b36f191d805dca7164ca533b3b56fd7: executes (string) :2b36f191d805dca7164ca533b3b56fd7: = true (5ms)
+324ms ║║Cancelling condition #35’s schedules…
+326ms ║║Condition #35 evaluated true (10ms)
+327ms ║║Cancelling condition #1’s schedules…
+328ms ║║Condition group #1 evaluated true (state changed) (46ms)
+331ms ║║Cancelling statement #2’s schedules…
+428ms ║║Executed virtual command setLocationMode (94ms)
+458ms ║║Executed virtual command sendPushNotification (21ms)
+475ms ║║Comparison (decimal) 71.0 is_greater_than (integer) 70 = true (3ms)
+478ms ║║Condition #64 evaluated true (15ms)
+480ms ║║Condition group #59 evaluated true (state did not change) (16ms)
+487ms ║║Cancelling statement #60’s schedules…
+885ms ║║Executed physical command [DOWNSTAIRS].cool() (393ms)
+886ms ║║Executed [DOWNSTAIRS].cool (396ms)
+935ms ║║Executed physical command [DOWNSTAIRS].setCoolingSetpoint([74.0]) (44ms)
+937ms ║║Executed [DOWNSTAIRS].setCoolingSetpoint (46ms)
+958ms ║║Executed virtual command [DOWNSTAIRS].sendPushNotification (16ms)
+962ms ║║Cancelling statement #7’s schedules…
+980ms ║║Skipped execution of physical command [Cabinet Lights].setLevel([100]) because it would make no change to the device. (12ms)
+981ms ║║Executed [Cabinet Lights].setLevel (13ms)
+991ms ║║Skipped execution of physical command [Xmas Tree].setLevel([100]) because it would make no change to the device. (6ms)
+992ms ║║Executed [Xmas Tree].setLevel (9ms)
+1005ms ║║Comparison (integer) 18 is_less_than_or_equal_to (integer) 20 = true (2ms)
+1007ms ║║Condition #77 evaluated true (11ms)
+1008ms ║║Condition group #75 evaluated true (state did not change) (13ms)
+1010ms ║║Cancelling statement #75’s schedules…
+1025ms ║║Skipped execution of physical command [Chandelier].setLevel([100]) because it would make no change to the device. (10ms)
+1026ms ║║Executed [Chandelier].setLevel (12ms)
+1039ms ║║Comparison (enum) heat is (string) heat = true (2ms)
+1041ms ║║Condition #88 evaluated true (11ms)
+1043ms ║║Condition group #87 evaluated true (state did not change) (13ms)
+1046ms ║║Cancelling statement #89’s schedules…
+1075ms ║║Executed physical command [UPSTAIRS].raiseHeatingSetpoint([1]) (23ms)
+1078ms ║║Executed [UPSTAIRS].raiseHeatingSetpoint (28ms)
+1083ms ║║Cancelling statement #91’s schedules…
+1088ms ║║Executed virtual command wait (1ms)
+1089ms ║║Requesting a wake up for Fri, Oct 26 2018 @ 2:27:22 PM EDT (in 1500.0s)
+1095ms ║╚Execution stage complete. (819ms)
+1097ms ║Setting up scheduled job for Fri, Oct 26 2018 @ 2:27:22 PM EDT (in 1499.994s)
+1106ms ╚Event processed successfully (1106ms)


#2

Can anyone help please?


#3

I was able to solve this by using an expression to set the heating point instead [UPSTAIRS : heatingSetpoint]+1.