I have a Honeywell TStat Pro connected (using AC power) and i am unable to get it to change temperature using code in an app. I do not use the builtin scheduler; instead i want trigger a 1 degree drop when the he is changed to night mode (sleep), and then a 1 degree rise when the Day mode is triggered.
The tstat has been connected to the he for some months. I have a tile on a dashboard and that allows me to set the temperature, and the it works instantly.
However when i use the below code it does not change the temperature setting on the tstat (see log entries). The app does successfully change the LED status.
Log of the last triggered event app:2952022-07-09 09:00:03.079 infoAction: END-IF app:2952022-07-09 09:00:03.075 infoAction: setLED(4, 'blue', 100) on TV Room Scene (skipped)
[)2022-07-09 09:00:03.064 infoAction: setLED(3, 'blue', 100) on TV Room Scene (skipped) app:2952022-07-09 09:00:03.056 infoAction: ELSE-IF (Mode is Movie(F) [FALSE]) THEN (skipping) app:2952022-07-09 09:00:02.956 infoAction: Thermostats: T-Stat --> Adjust Heat: 1.0 --> Adjust Cool: 1.0 app:2952022-07-09 09:00:02.876 infoAction: setLED(4, 'white', 100) on TV Room Scene app:2952022-07-09 09:00:02.866 infoAction: ELSE-IF (Mode is Day(T) [TRUE]) THEN app:2952022-07-09 09:00:02.856 infoAction: setLED(4, 'green', 100) on TV Room Scene (skipped) app:2952022-07-09 09:00:02.849 infoAction: ELSE-IF (Mode is Morning(F) [FALSE]) THEN (skipping) app:2952022-07-09 09:00:02.840 infoAction: setLED(4, 'red', 100) on TV Room Scene (skipped) app:2952022-07-09 09:00:02.833 infoAction: ELSE-IF (Mode is Evening(F) [FALSE]) THEN (skipping) app:2952022-07-09 09:00:02.822 infoAction: Thermostats: T-Stat --> Adjust Heat: -1.0 --> Adjust Cool: -1.0 (skipped) app:2952022-07-09 09:00:02.816 infoAction: setLED(4, 'blue', 100) on TV Room Scene (skipped) app:2952022-07-09 09:00:02.792 infoAction: IF (Mode is Night(F) [FALSE]) THEN (skipping) app:2952022-07-09 09:00:01.463 infoAction: Scenes per mode: Day: Day
Evening: Evening
Morning: Morning
Movie: Movie
Night: Night app:2952022-07-09 09:00:01.257 infoTriggered app:2952022-07-09 09:00:01.183 infoEvent: mode Day
Help me understand why this isn't working as you believe it should?
When I read your Rule, it says that if "Mode is Day", then to adjust the heat and cool settings by "1.0" (not "-1.0"), and the log indicates that is exactly what happens.
Thank your help and sorry if I was not clear in the first paragraph above. Let me restate.
Objective:
I use an App named "Change, Mode" that is triggered when the HE systems mode is changed. This can be manual change or by schedule. When the mode is changed to 'Night' (for example, manually when i go to sleep), the app is triggered and i want it to reduce the Cool / Heat setting by 1 degree (-1). WHen the mode is changed to 'Day' (automatically by schedule at 0900hrs), i want the Cool / Heat to increase by 1 degree (+1).
The attached image above shows that when the App logic "If Mode is Night then...Adjust -1"
Similarly, the above shows that when App Logic "ELSE-IF Mode is Day... Adjust 1"
Summary
The App logic works fine on the LED settings lines and the log shows that code for the tstat is executed, however the tstat temperature does not change.
The tstat temp can be changed using the Devices page as well as from a tile in a dashboard i have created. But fails when sent the code from the app.
I did not have device logging turned on. This has been enabled and i will post once the next event fires.
Thanks
I set the mode to "night" and here is the log entry. This time it changed the set point of the tstat as per the code. It did not do this last night nor did it change +1 today on the mode change to "day".
I did update the system to the latest version after i posted the original.
There are two variables since the previous two failures; 1) I update dthe HE to the latest version, and 2) I set the tstat driver to debug logging on.
I will monitor going forward and see if there is another failure to change the setpoint.
Thanks
The tstat has been updating correctly as designed / expected for the past 5 mode changes. It failed on the first two and then started working as expected.
I do not know if the application of the pending update or the restart after the update is what corrected the issue.
Should i receive further issues i will update this post.
The process above failed to change the tstat temperature setting during last mode change to "Night" mode.
The log shows that the command was sent, but the tstat never adjusted. The app command line to change the LED settings that is immediately before the command line to set the tstat temp processed correctly as indicated by the switch led color change.
I did notice that after the night mode change was sent, the garage door would not close from zwave connected button controller. Log shows the close command was received from the button controller, but the zwave garage door did not close. I closed manually using the garage door opener hard wired switch,
I mention teh garage door issue as perhaps it is related to the tstat as a network issue? Congestion?
This. @aaiyar don't these thermostats act like bad repeaters like the light bulbs do in Zigbee?
@kenny could you post a screenshot of your Z-wave Details page (Settings tab, Z-wave Details). There may be something we can see there that would help diagnose this.
I do not believe it is the tstat, as i can change the temperature settings using the the device page or using the dashboard and the tstat effects the change immediately.
I have the tstat powered from the AC source, not battery, so the tstat is in repeater mode (no sleep).
You have at least one incomplete pairing. Likely caused by your remotec controller. remove power from that device then remove the ghost above it. Might have to power cycle it to remove it (shut down, unplug power at the wall not the hub for 5 mins and power back up)
Device 15? I have tried to remove it for some time, even using the PC controller method.
SO remove power from the Remotec device (016), then Refresh the ghost and then remove?
I would give that a whirl. You will have problems as long as it's present. The reason it won't remove is that the device that made it is still powered on and pingable
