Announcement

Collapse
No announcement yet.

Values not updating

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Values not updating

    HS Version: HS3 Standard Edition 3.0.0.258 (Windows)
    Plugin version: 1.0.2.0
    Description of the problem: Data such as temperature does not update automatically after startup. After running more than 12 hours the temperature has not updated since I restarted the computer at 6:22PM yesterday.
    HS3 Server OS: Microsoft Windows 10 Pro - Work Station (10.0.10240 Service Pack: 0.0)
    Thermostat model: Honeywell RTH9580 WiFi

    {
    "success": true,
    "deviceLive": true,
    "communicationLost": false,
    "latestData": {
    "uiData": {
    "DispTemperature": 75,
    "HeatSetpoint": 70,
    "CoolSetpoint": 75,
    "DisplayUnits": "F",
    "StatusHeat": 0,
    "StatusCool": 0,
    "HoldUntilCapable": true,
    "ScheduleCapable": true,
    "VacationHold": 0,
    "DualSetpointStatus": false,
    "HeatNextPeriod": 90,
    "CoolNextPeriod": 90,
    "HeatLowerSetptLimit": 40,
    "HeatUpperSetptLimit": 90,
    "CoolLowerSetptLimit": 60,
    "CoolUpperSetptLimit": 99,
    "ScheduleHeatSp": 70,
    "ScheduleCoolSp": 75,
    "SwitchAutoAllowed": true,
    "SwitchCoolAllowed": true,
    "SwitchOffAllowed": true,
    "SwitchHeatAllowed": true,
    "SwitchEmergencyHeatAllowed": false,
    "SystemSwitchPosition": 5,
    "Deadband": 3,
    "IndoorHumidity": 51,
    "DeviceID": 760279,
    "Commercial": false,
    "DispTemperatureAvailable": true,
    "IndoorHumiditySensorAvailable": true,
    "IndoorHumiditySensorNotFault": true,
    "VacationHoldUntilTime": 0,
    "TemporaryHoldUntilTime": 0,
    "IsInVacationHoldMode": false,
    "SetpointChangeAllowed": true,
    "OutdoorTemperature": 128,
    "OutdoorHumidity": 128,
    "OutdoorHumidityAvailable": false,
    "OutdoorTemperatureAvailable": false,
    "DispTemperatureStatus": 0,
    "IndoorHumidStatus": 0,
    "OutdoorTempStatus": 128,
    "OutdoorHumidStatus": 128,
    "OutdoorTemperatureSensorNotFault": true,
    "OutdoorHumiditySensorNotFault": true,
    "CurrentSetpointStatus": 0,
    "EquipmentOutputStatus": 2
    },
    "fanData": {
    "fanMode": 2,
    "fanModeAutoAllowed": true,
    "fanModeOnAllowed": true,
    "fanModeCirculateAllowed": true,
    "fanModeFollowScheduleAllowed": true,
    "fanIsRunning": true
    },
    "hasFan": true,
    "canControlHumidification": false,
    "drData": {
    "CoolSetpLimit": 0,
    "HeatSetpLimit": 0,
    "Phase": -1,
    "OptOutable": false,
    "DeltaCoolSP": -0.01,
    "DeltaHeatSP": -0.01,
    "Load": 127.5
    }
    },
    "alerts": "\r\n\r\n"
    }
    Attached Files
    Last edited by jmjones; April 27, 2016, 12:19 PM. Reason: Missed uploads

    #2
    I'm not seeing the plugin attempt to communicate at all in that log snippet. Can you post a screenshot of your configuration options page? Seems I neglected to add a dump of all the settings in TRACE mode like I should have in the logs...

    Comment


      #3
      Sure, by the way is still hasn't updated :-)
      Attached Files

      Comment


        #4
        While you have the plugin log level at Trace, can you please disable the plugin, delete the log file, then re-enable it the plugin and let it sit for 1-2 minutes without visiting the config page? I just did that on my system and want to have a side-by-side comparison of the processing path the logs record.

        Comment


          #5
          Unfortunately, I messed around with it yesterday. Fortunately for me I got it to work. I did disable the plugin and re-enable with trace on but did not clear the log first. That didn't fix it. I then deleted all the devices related to the thermostat, removed the thermostat and then added it back. That worked but at one point I ended up with the devices created 4 times. I removed three and all seems well now. All that is in the log but it is rather large. For now I'm up again though.
          Attached Files

          Comment


            #6
            I just noticed my "Hold Type"status has not updated in over 2 months.
            Last edited by prnorton; September 28, 2017, 04:49 PM.

            Comment


              #7
              same here seems to be coms issues with honeywell.
              Attached Files

              Comment

              Working...
              X