Announcement

Collapse

Contacting HomeSeer This Week

HomeSeer is open and operational this week. All orders are being processed and shipped as usual. However, some staff are working from home. If you need to contact HomeSeer for support or customer service, please use our Email or Chat options. https://homeseer.com/contact-us/
See more
See less

Honeywell TH8320ZW1000 Not Updating

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

  • Honeywell TH8320ZW1000 Not Updating

    I have the Honeywell TH8320ZW1000 with the C wire connected homeseer knows it is powered. I used the green blower wire for this until I can run another wire. I am using a Z-troller and every thing is most current version.

    I have been trying to get the plugin to update but have to go in and manualy update it. I have Polling set to 300 seconds and the Zwave health is excellent for the Tstat, and the rest of the Zwave devices

    I have read many threads of similar problems. But I am confused on the best approach to remedy the problem. I tried to write a recurring script to poll every ten minutes but I can not get it to work.

    this is the script I used - &hs.pollDevice("q13") - I have checked wait for script and run 1 instance.

    Can anyone tell me where I am going wrong with this.

    Thanks

  • #2
    Did you purchase the hardware from HomeSeer? If so how long ago did you purchase this stat. There are some older stats floating around that have older firmware that had issues reporting certain parameters so you may need a firmware update. Also check to see if the root device of this stat is associated with HomeSeer. Lastly ensure you are running HomeSeer build 2.5.0.74 and HSTouch Server 1.0.0.69. These are test builds that are slated for release very soon. Please update to these and see if the problems are still there, they should not be.
    Last edited by Rupp; December 28th, 2012, 02:32 PM.
    -Rupp
    sigpic

    Comment


    • #3
      This looks like a new thermostat. First make sure you set association on root thermostat device with home-seer. This will ensure *temperature* changes are communicated back automatically. *NO* other local changes on thermostat will be communicated back - this is how they work.

      If you want to keep things up to date you will have to do polling. You can set that up on the root thermostat device as well.

      The script you wrote is alternative to using polling. Make sure you are using root thermostat device code and not temperature device code.

      Comment


      • #4
        More details

        Originally posted by Rupp View Post
        Did you purchase the hardware from HomeSeer? "I purchased it off amazon becuase you were out of stock"

        If so how long ago did you purchase this stat. "About 2o Days"

        There are some older stats floating around that have older firmware that had issues reporting certain parameters so you may need a firmware update.

        Also check to see if the root device of this stat is associated with HomeSeer. "There was no association i have done this now--Associate Z-Wave Interface Z-Wave Thermostat 26 with HomeSeer at group 1", result: Association set successfully"


        Lastly ensure you are running HomeSeer build 2.5.0.74 and HSTouch Server 1.0.0.69. " I ran updater and these versions were installed 2.5.0.49 and 1.0.0.60 , I checked Homeseer.com for the betas you listed but cannot find them.

        These are test builds that are slated for release very soon. Please update to these and see if the problems are still there, they should not be.
        Thanks Rupp

        Comment


        • #5
          The latest version of HS is available here:
          http://board.homeseer.com/showthread.php?t=157463
          The HSTouch server is available here:
          http://board.homeseer.com/showthread.php?t=156700
          -Rupp
          sigpic

          Comment


          • #6
            Person

            I just did the association now. When you and Rupp refer to root. Do you mean the device status screen and configure device?

            Not sure what you mean by this. "Make sure you are using root thermostat device code and not temperature device code." I configured Z-Wave Thermostat 26 and did nothing with "Z-Wave Thermostat 26 Temperature Q14 Z-Wave Sensor Multilevel Temperature "

            Thank you

            Comment


            • #7
              Originally posted by kpaxson View Post
              Person

              I just did the association now. When you and Rupp refer to root. Do you mean the device status screen and configure device?

              Not sure what you mean by this. "Make sure you are using root thermostat device code and not temperature device code." I configured Z-Wave Thermostat 26 and did nothing with "Z-Wave Thermostat 26 Temperature Q14 Z-Wave Sensor Multilevel Temperature "

              Thank you

              Now that you have association (which you had to do on the thermostat root device which seems to be Z-Wave Thermostat 26 in your case) you should see temperature changes from thermostat being automatically pushed to homeseer (instant status) with no polling needed. See example below.

              2/18/2012 10:18:24 PM - HSTouch Server Deb - 10:18:24:4540 ~ String change event for Q3 to string:
              2/18/2012 10:18:24 PM - HSTouch Server Deb - 10:18:24:4550 ~ String change event, value is: 6900
              2/18/2012 10:18:24 PM - Device Update - Device: 1st floor Living Room Temperature value set to 70 (7000/F)
              2/18/2012 10:18:24 PM - HSTouch Server Deb - 10:18:24:4570 ~ String change event for Q3 to string:<img align="absmiddle" src="/images/HomeSeer/Thermometer-70.png" width="24" height="24"> 70 F
              2/18/2012 10:18:24 PM - HSTouch Server Deb - 10:18:24:4570 ~ String change event, value is: 6900
              2/18/2012 10:18:24 PM - HSTouch Server Deb - 10:18:24:4580 ~ Status change Q3 Command: 2Level: 7000 Status: 70 F
              2/18/2012 10:18:24 PM - HSTouch Server Deb - 10:18:24:4580 ~ Sending DEVICECHANGE notification to clients REF:3728 Cmd: 2 CAPI Stat: 70 F
              2/18/2012 10:18:24 PM - HSTouch Server Deb - 10:18:24:4590 ~ Value change Q3 NewVal: 7000OldVal: 6900
              2/18/2012 10:18:24 PM - Event - Event Trigger "Check thermostat"

              This will update Z-Wave Thermostat 26 Temperature Q14 Z-Wave Sensor Multilevel Temperature device to correct temperature. This will not update Z-Wave Thermostat 26 temperature or any other status (fan/mode). That is why I poll my T-stat (event "Check thermostat" in green above) on any temp changes. I poll it twice, within 5sec and then in 4 min.



              Reason for 4 min is cool off time - t-stat will run fan after final temp was reached to reduce furnace wearout. So to see fan OFF you need to query after cool off time. But, fan status is not working correctly in current HS version. I will be testing 75 soon to see if this is fixed.


              For example, root device is Q2, temperature device is Q3 in my pic below ...

              Attached Files

              Comment

              Working...
              X