Announcement

Collapse
No announcement yet.

Random Unexplained HAI Thermostat Changes

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

    #16
    Rick, see attached; had to chop it down due to file size limits. Let mek know if you need me to furnish more/other info.

    The plugin-in / panel are responding properly but I have one Tsat out of 5 that never re-syncs and indicates comm err on the device temp.

    BTW, your plug-in is very solid with the exception of this issue which occurs for me when the power is interrrupted for >5 sec.

    -Ron
    Attached Files

    Comment


      #17
      Personally and to keep WAF high I like to be able to control my thermostat via itself and via the HAI consoles I utilize the plugin more to "watch" than to "do". I guess I don't like to watch my thermostat doing things which are not meant to occur. I haven't any other problems and I like that I can sync the HAI time to my NTP server.
      - Pete

      Auto mator
      Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
      Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
      HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
      6.10.0.104
      HS4 Lite -

      X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

      Comment


        #18
        Originally posted by basshook View Post
        The plugin-in / panel are responding properly but I have one Tsat out of 5 that never re-syncs and indicates comm err on the device temp.
        I'm sure Rick will jump in but let me help out and decode the what the panel(omni) is sending back to HomeSeer.

        In your log we see the thermostat request:
        5A-3-1E(THERMOSTAT STATUS)-1-5-A1-D1
        In this command we only care about 1-5 which says "Give me the Status of Thermostats 1 through to 5"

        And the Response:
        0-7A-78-80-3-0-FF-0-7A-77-82-3-0-FF-0-7A-78-82-3-0-FF-0-7B-78-81-3-1-FF-0-7C-79-81-3-1-FF-E5-41

        There are 7 Bytes of data the panel returns for each thermostat so the data for each thermostat is below. The last 2 bytes are a CRC value, so we can ignore E5-41.

        Thermostat 1
        0-7A-78-80-3-0-FF
        0 = No Comms Error/No Freeze Alarm
        7A,77 and 82 are Current Temp/Heat/Cool Setpoints based on how the Omni reports Temp values. Eg 7A = 21 Degrees C/ ~70 Degrees F
        3 = System Mode. 3 = Auto
        0 = Fan Mode. 0 = Auto
        FF = Hold Status. FF = On Hold (All your thermostats are holding.. Unusual)

        And so on...
        0-7A-77-82-3-0-FF
        0-7A-78-82-3-0-FF
        0-7B-78-81-3-1-FF
        0-7C-79-81-3-1-FF

        What you only really care about is the "Comms Error" reported for the Thermostat. Remember the first Byte is the Status. If the Omni could not communicate with a Thermostat, this Status Byte would equal 1. As you can see above, none of the first values listed are 1, they are all 0 meaning no Comms Errors or Freeze Alarms. This means the Omni is talking to all thermostats without problems (which you probably know as you can verify it via a console/touchscreen and PC Access).

        So I'm afraid it looks like a plugin issue that Rick will have to look into.

        Ross.

        Comment


          #19
          This morning noticed that both my AC and Heat settings were at 90. I have my thermostat configured to run the furnace fan 24/7. The set backs are set to 55 and changes are set to bring up temperature to 68 early morning 0500c until 0700c, PM 1700c until 1900c, PM 2200c until 0000c. This issue has now occurred twice this past week with no warnings.

          Regarding seeing the "remote" indicator on the thermostat. I see it on most of the time but occasionally I don't see it for a "few" hours. I occasionally control the thermostat via the other consoles and never via HS so it doesn't make sense that the remote indicator would be on most of the time.

          Would disabling any Thermostat variables help temporarily with this concern?
          - Pete

          Auto mator
          Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
          Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
          HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
          6.10.0.104
          HS4 Lite -

          X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

          Comment


            #20
            Pete,

            Log the HAI comms. It'll be very east to see if the plugin is sending any thermostat commands to the panel.
            Log the commands, wait for something to happen then zip up the file and email to me.

            Ross.

            Comment


              #21
              Thank you Ross, will do. "it" occurred again this morning.
              - Pete

              Auto mator
              Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
              Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
              HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
              6.10.0.104
              HS4 Lite -

              X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

              Comment


                #22
                Thank you Ross for having a look see. So what appears to be happening is that the plugin appears to be sending non HS initiated commands to my thermostat. This unexplained phenomena has and will continue to be a detriment to WAF.
                - Pete

                Auto mator
                Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
                Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
                HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
                6.10.0.104
                HS4 Lite -

                X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

                Comment


                  #23
                  Just so everyone knows what was happening to Pete and so they can check their own setups:

                  It's constantly setting the heat and cool setpoints, about 2 times a second in some cases.

                  You can search the logs yourself:

                  5A-5-F(COMMAND)-42- = Set Heat setpoint
                  5A-5-F(COMMAND)-43- = Set Cool setpoint
                  5A-5-F(COMMAND)-44- = Set thermostat mode (Auto/Off etc)
                  5A-5-F(COMMAND)-45- = Set Fan mode On/Auto
                  5A-5-F(COMMAND)-46- = Set Hold mode

                  Most of the heat and cool setpoints are always the same commands:
                  5A-5-F(COMMAND)-43-0-0-1-80-10

                  This means set the setpoint (43 = cool) to Zero (Zero in Omni speak = -40 degreesC/-40 DegreesF) on thermostat 1.
                  Setting it to zero is actually invalid for a thermostat. The values should range from 44-180 (in omni value which is about -15 DegreesC to 40 DegreesC)

                  Sometimes it seems to just randomly set values, such as this:

                  11/28/2007 5:11:13 AM:018673.10 ~Sending (Serial): 5A-5-F(COMMAND)-42-92-0-1-20-1
                  11/28/2007 5:11:18 AM:018678.34 ~Sending (Serial): 5A-5-F(COMMAND)-42-0-0-1-81-EC
                  11/28/2007 5:11:19 AM:018679.16 ~Sending (Serial): 5A-5-F(COMMAND)-42-92-0-1-20-1

                  So in 6 seconds, it set the Heat setpoint to 92 = 6 degreesC, then 0 (which is invalid) then 6 degreesC again.

                  Some very strange stuff going on there..

                  If it is setting "random" values, then that might explain why "remote" and a change only shows up on the thermostat every now and then. Since values less than 44 are invalid, setting the thermostat value to 0 as shown above may be ignored by the panel and/or the thermostat, so it won't show "remote".

                  Ross.

                  Comment


                    #24
                    In addition see these occasionally.

                    HAI System PollThings experienced error 9 on line 0, Index was outside the bounds of the array.
                    - Pete

                    Auto mator
                    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
                    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
                    HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
                    6.10.0.104
                    HS4 Lite -

                    X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

                    Comment


                      #25
                      I have been out of town this week but will do some debug log checking when I get back on Sunday.

                      Comment


                        #26
                        Changed the programming on the thermostat so that the heating limits and cooling limits are reasonable as a temporary fix. It seems to be working. I don't wake up to a setting of 90 F.
                        - Pete

                        Auto mator
                        Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
                        Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
                        HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
                        6.10.0.104
                        HS4 Lite -

                        X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

                        Comment


                          #27
                          Doesn't really help if the plugin is seemingly setting "random" heat and cool setpoints.
                          Have you logged a helpdesk ticket on this?

                          Ross.

                          Comment


                            #28
                            Hello Ross,
                            Opened a help desk ticket this morning. Think with the high end limit set to 72 on the thermostat ....whatever is sent to it never gets implemented....so while this is not fixing my problem it is keeping my furnace from going to 90. WAF was at all time low. She really doesn't know at this time if she sets the thermostat to 74 it will never go there.....

                            Pete
                            - Pete

                            Auto mator
                            Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
                            Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
                            HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
                            6.10.0.104
                            HS4 Lite -

                            X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

                            Comment


                              #29
                              Happen to see it having a "moment"
                              Attached Files
                              - Pete

                              Auto mator
                              Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
                              Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
                              HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
                              6.10.0.104
                              HS4 Lite -

                              X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

                              Comment


                                #30
                                That's VERY interesting. I say this because -40 is a "0" in Omni speak.
                                So what I think might have happened is the plugin has read the current state of the thermostat and (rightly or wrongly) though the response was filled with zero's, zeros for the setpoints and temp anyway. If the current mode was zero it would be "Off" and not Heat and Fan mode would be "Auto" not "On".

                                You didn't have comms logging going at the time did you? Not that I can fix it for you, but might help Rick track down the problem.

                                Ross.

                                Ross.

                                Comment

                                Working...
                                X