No announcement yet.

Event cool setpoint reversed almost immediately

This topic is closed.
  • Filter
  • Time
  • Show
Clear All
new posts

    Event cool setpoint reversed almost immediately

    I've been having trouble setting cool setpoints from events.
    Testing it, I created an event that just changes the temperature of the cool setpoint to 74, then sends and email indicating that it ran.

    If I watch the TCC app on my phone, I see it flip to 74 for a few seconds (maybe 10?) then it flips right back to the previous setpoint of 72.

    The thermostat is: RTH9585WF
    Trace log file attached.

    Current Date/Time: 10/11/2019 1:03:27 AM
    HomeSeer Version: HS3 Pro Edition
    Operating System: Microsoft Windows 10 Home - Work Station
    System Uptime: 1 Day 18 Hours 41 Minutes 12 Seconds
    IP Address:
    Number of Devices: 202
    Number of Events: 80
    Available Threads: 1023
    HSTouch Enabled: True
    Event Threads: 52
    Event Trigger Eval Queue: 0
    Event Trigger Priority Eval Queue: 0
    Device Exec Queue: 0
    HSTouch Event Queue: 0
    Email Send Queue: 0
    Anti Virus Installed: Norton Security Windows Defender
    In Virtual Machine: No MFG: gateway
    Enabled Plug-Ins BLBackup BLEditor BLOccupied Honeywell WiFi Thermostat ImperiHome Z-Wave
    Attached Files

    I *might* have figured this out. For some reason there were two orphaned DEVICE COOL SETPOINT devices that were not part of the thermostat group. I tried to delete them but got a warning that they were created by the Honeywell plugin.

    I disabled the plugin
    Deleted the current thermostat (which broke a bunch of events!)
    Deleted the two remaining COOL SETPOINT devices (ignoring the warning)
    Re-enabled the plugin
    Re-added my thermostat
    Fixed all the busted events

    Tested my test event that just changes the cool setpoint. It seems to hold ok now.

    I'm guessing the two phantom cool setpoint devices were the problem. They didn't have any controls or any way to change them, but perhaps they were holding onto the old setpoint?

    Anyway, fixed now it seems.



      Closing this thread since this topic was continued here: