Heating is not working


#1

1) Give a description of the problem
I have a Honeywell Lyric thermostat and a piston to manage it, but for some reason the heat does not come on when the temp is below it’s heating point. However it does work correctly for cooling.

2) What is the expected behavior?
When the temp drops below the heating point set for the given time period, I’d like the heater to come on.

3) What is happening/not happening?
The heater fails to come on and is frequently below the heating point set.

4) Post a Green Snapshot of the pistonimage

  1. Logs

12/6/2017, 11:41:24 AM +341ms
+1ms ╔Received event [Home].time = 1512589285035 with a delay of -694ms
+415ms ║RunTime Analysis CS > 18ms > PS > 61ms > PE > 335ms > CE
+433ms ║Runtime (47928 bytes) successfully initialized in 61ms (v0.2.0fe.20171109) (430ms)
+434ms ║╔Execution stage started
+457ms ║║Comparison (string) :dcfc45e435756029effce77ba8466bd3: is_any_of (string) :dcfc45e435756029effce77ba8466bd3:,:9a4e047fa524f4d97ad857190529c82e: = true (4ms)
+460ms ║║Condition #24 evaluated true (13ms)
+478ms ║║Comparison (time) 42084802 is_between (time) 79200000 … (time) 28800000 = false (14ms)
+480ms ║║Condition #26 evaluated false (20ms)
+481ms ║║Condition group #1 evaluated false (state did not change) (35ms)
+491ms ║║Comparison (string) :dcfc45e435756029effce77ba8466bd3: is_any_of (string) :988dab64f04e733662608bfbbd87c25c:,:dcfc45e435756029effce77ba8466bd3:,:9a4e047fa524f4d97ad857190529c82e: = true (4ms)
+493ms ║║Condition #7 evaluated true (8ms)
+510ms ║║Comparison (time) 42084835 is_between (time) 28800000 … (time) 79200000 = true (12ms)
+513ms ║║Time restriction check passed
+516ms ║║Condition #27 evaluated true (21ms)
+517ms ║║Condition group #37 evaluated true (state did not change) (33ms)
+521ms ║║Cancelling statement #4’s schedules…
+2175ms ║║Executed physical command [Thermostat].setCoolingSetpoint([75.0]) (1646ms)
+2177ms ║║Executed [Thermostat].setCoolingSetpoint (1649ms)
+3378ms ║║Executed physical command [Thermostat].setHeatingSetpoint([68.0]) (1197ms)
+3380ms ║║Executed [Thermostat].setHeatingSetpoint (1199ms)
+3394ms ║║Calculating (integer) 0 | (integer) 68 >> (integer) 68
+3405ms ║║Calculating (string) Heating Point: + (string) 68 >> (string) Heating Point: 68
+3409ms ║║Calculating (string) Heating Point: 68 + (string) °F | Cooling Point: >> (string) Heating Point: 68°F | Cooling Point:
+3412ms ║║Calculating (string) Heating Point: 68°F | Cooling Point: + (string) 75 >> (string) Heating Point: 68°F | Cooling Point: 75
+3415ms ║║Calculating (string) Heating Point: 68°F | Cooling Point: 75 + (string) °F >> (string) Heating Point: 68°F | Cooling Point: 75°F
+3418ms ║║Executed virtual command [Thermostat].setState (0ms)
+3428ms ║║Comparison (string) :dcfc45e435756029effce77ba8466bd3: is_any_of (string) :c99bffdf9a8b20cba73ceddcc7201c29:,:b79e052a61d75b56b6a15167838bfa62: = false (3ms)
+3430ms ║║Condition #17 evaluated false (7ms)
+3431ms ║║Condition group #38 evaluated false (state did not change) (9ms)
+3435ms ║╚Execution stage complete. (3001ms)
+3436ms ║Setting up scheduled job for Wed, Dec 6 2017 @ 11:42:25 AM PST (in 57.258s)
+3458ms ╚Event processed successfully (3458ms)


#2

Swap the heating setpoint and cooling setpoint so the heat is second. See if that works or changes anything.

Also your logs need to be set to full to provide the juicy details we are looking for. Right now your logs are only semaphore waits and what you are outputting to the console.


#3

I’ll give that a shot. Thank you. I’ve also updated the logs with full details if you are curious to see them.


#4

Attach them after the change runs through


#5

No dice… I’ve updated the logs and here is another screenshot. (I increased the frequency for testing)


#6

Are you in a thermostat mode that will heat/cool? Maybe it’s just in cool mode?

I don’t have many ideas for this problem unfortunately


#7

Ah ha! That’s it! For some reason ‘Auto’ mode is not working properly on the Thermostat. I’ll need to investigate that or maybe set it based on current temp. Thanks!