Announcement

Collapse
No announcement yet.

Questions about plugin handling of various modes

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

  • #16
    Yes, it does seem strange. I'll have to look into this and also compare with other thermostat types (venstar etc.) to see if they act similarly or if this is just a 2441th thing.
    HS 3.0.0.435 (PRO)
    Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
    Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
    Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
    http://www.kazteel.com/

    Comment


    • #17
      Question: does polling the thermostat retrieve the mode?

      When looking at the plugin status page, I noticed it showed Mode = Auto; in reality, the 2441TH was in Mode = Program. So I did a Config / Thermostat / Poll.

      As per the log, it retrieved Protocol, Devcat, version and the current temperature (probably also humidity for which I disabled logging).

      Nov-09 12:57:15 Insteon Thermostat TransmitInsteon: [2441TH] [0F] [0D] [00]
      Nov-09 12:57:15 Insteon Thermostat TransmitInsteon: [2441TH] [0F] [10] [00]
      Nov-09 12:57:16 Insteon Thermostat 2441TH protocol = 2
      Nov-09 12:57:17 Insteon Thermostat 2441TH devcat = 050B
      Nov-09 12:57:17 Insteon Thermostat 2441TH version = D
      Nov-09 12:57:17 Insteon Thermostat TransmitInsteon: [2441TH] [0F] [6B] [02]
      Nov-09 12:57:19 Insteon Thermostat TransmitInsteon: [2441TH] [0F] [6A] [60]
      Nov-09 12:57:21 Insteon Thermostat TransmitInsteon: [2441TH] [0F] [6B] [03]
      Nov-09 12:57:23 Insteon Thermostat TransmitInsteon: [2441TH] [0F] [6A] [20]
      Nov-09 12:57:25 Insteon Thermostat 2441TH Temp = 20


      I was expecting it to also retrieve Mode and Fan state, so HS would be in sync with the actual 2441TH.

      Strangely, device '2441TH Mode' on the device management page has a 'Last change' time stamp that coincides with the poll time, but the status still shows Auto instead of Program.

      I couldn't find any other way to retrieve Mode and Fan state. Any chance of including this added poll functionality in a future release? Unless I missed this in the actual version.

      Comment


      • #18
        The following log entries show that the 2441TH's mode suddenly turns to Auto, while it's been Program all day long.

        Nov-09 23:44:12 Insteon Thermostat 2441TH Heat SetPoint = 18
        Nov-09 23:46:39 Device Control Device: 2 [2:S. TV] A-Plafonnier escalier vers 2 to Off (0) by/from: CAPI Control Handler
        Nov-09 23:46:40 Device Control Device: 2 [2:S. TV] Plafonnier to Off (0) by/from: CAPI Control Handler
        Nov-09 23:46:40 Device Control Device: 2 [2:S. TV] A-Plafonnier escalier vers 2 to On (100) by/from: CAPI Control Handler
        Nov-09 23:46:40 Device Control Device: 2 [2:S. TV] Plafonnier to Dim (value)% (60) by/from: CAPI Control Handler
        Nov-09 23:46:47 Device Control Device: 2 [2:S. TV] A-Plafonnier escalier vers 2 to Off (0) by/from: CAPI Control Handler
        Nov-09 23:46:47 Device Control Device: 2 [2:S. TV] Plafonnier to Off (0) by/from: CAPI Control Handler
        Nov-09 23:51:14 Event Event Trigger "DemoPad TV_lights_Dim_then_Off"
        Nov-09 23:51:14 Device Control Device: 2 [2:S. TV] A-Plafonnier escalier vers 2 to On (100)
        Nov-09 23:51:14 Device Control Device: 2 [2:S. TV] Plafonnier to Dim 40% (40)
        Nov-09 23:51:44 Event Event Trigger "Delayed Actions Plafonnier (Delayed Action)"
        Nov-09 23:51:44 Device Control Device: 2 [2:S. TV] A-Plafonnier escalier vers 2 to Off (0)
        Nov-09 23:51:44 Device Control Device: 2 [2:S. TV] Plafonnier to Off (0)
        Nov-09 23:51:44 Event Deleting event after run: "Delayed Actions Plafonnier (Delayed Action)"
        Nov-09 23:51:44 Event Event Trigger "Delayed Actions V_TV_LED (Delayed Action)"
        Nov-09 23:51:44 Device Control Device: 2 [2:S. TV] V_TV_LED to Off (0)
        Nov-09 23:51:44 Event Deleting event after run: "Delayed Actions V_TV_LED (Delayed Action)"
        Nov-09 23:51:44 Event Event Trigger "Event triggers - TV LED Off"

        Nov-09 23:55:03 Insteon Thermostat 2441TH Mode = Auto
        Nov-09 23:55:12 Insteon Thermostat 2441TH Temp = 21
        Nov-09 23:55:15 Insteon Thermostat Error 2441TH - Unexpected device type requested for polling.




        At around 23:45, the 2441TH's hardware program changes to 'sleep' which introduces a new heating set point. Other log entries before and after have no incidence on the thermostat. And then there's that "... Unexpected device type requested for polling ..." message at 23:55:15.

        Nathan: can you help explain how the mode went from Program to Auto?

        Comment


        • #19
          Originally posted by claude View Post
          Nov-09 12:57:17 Insteon Thermostat TransmitInsteon: [2441TH] [0F] [6B] [02]

          Strangely, device '2441TH Mode' on the device management page has a 'Last change' time stamp that coincides with the poll time, but the status still shows Auto instead of Program.

          I couldn't find any other way to retrieve Mode and Fan state. Any chance of including this added poll functionality in a future release? Unless I missed this in the actual version.
          The [6B] [02] is the poll Mode command and I believe that returns a value that indicates both the mode and fan. So, I ran a test to see if I could get a mixed state between my 2441th and the plugin and sure enough I did. I manually set the 2441th to Mode=Program and verified in HS3 it showed that. First log below confirms it. I then issued the Config->Poll and look at the last log statment coming back, it says Mode=Auto! Looking at the 2441th it is still in Mode=Program. I can experiment with this more but it seems like a possible protocol issue? The thermostat itself reported Mode=Auto but the display still confirms it is in Mode=Program.

          Code:
          11/10/2015 3:32:18 PM ~ Insteon Thermostat ~ INFO ~ sh2441th [04] Mode=Program Fan=Auto
          11/10/2015 3:33:11 PM ~ Insteon Thermostat ~ DEBUG ~ TransmitInsteon: [sh2441th] [0F] [0D] [00]
          11/10/2015 3:33:11 PM ~ Insteon Thermostat ~ DEBUG ~ TransmitInsteon: [sh2441th] [0F] [10] [00]
          11/10/2015 3:33:12 PM ~ Insteon Thermostat ~ ALWAYS ~ sh2441th protocol = 2
          11/10/2015 3:33:12 PM ~ Insteon Thermostat ~ ALWAYS ~ sh2441th devcat = 050B
          11/10/2015 3:33:12 PM ~ Insteon Thermostat ~ ALWAYS ~ sh2441th version = D
          11/10/2015 3:33:12 PM ~ Insteon Thermostat ~ DEBUG ~ TransmitInsteon: [sh2441th] [0F] [6B] [02]
          11/10/2015 3:33:14 PM ~ Insteon Thermostat ~ DEBUG ~ TransmitInsteon: [sh2441th] [0F] [6A] [60]
          11/10/2015 3:33:16 PM ~ Insteon Thermostat ~ DEBUG ~ TransmitInsteon: [sh2441th] [0F] [6B] [03]
          11/10/2015 3:33:18 PM ~ Insteon Thermostat ~ DEBUG ~ TransmitInsteon: [sh2441th] [0F] [6A] [20]
          11/10/2015 3:33:20 PM ~ Insteon Thermostat ~ INFO ~ sh2441th Mode = Auto
          HS 3.0.0.435 (PRO)
          Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
          Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
          Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
          http://www.kazteel.com/

          Comment


          • #20
            Originally posted by claude View Post
            Nov-09 23:55:03 Insteon Thermostat 2441TH Mode = Auto
            Nov-09 23:55:12 Insteon Thermostat 2441TH Temp = 21
            Nov-09 23:55:15 Insteon Thermostat Error 2441TH - Unexpected device type requested for polling.


            At around 23:45, the 2441TH's hardware program changes to 'sleep' which introduces a new heating set point. Other log entries before and after have no incidence on the thermostat. And then there's that "... Unexpected device type requested for polling ..." message at 23:55:15.

            Nathan: can you help explain how the mode went from Program to Auto?
            That "Unexpected device type requested for polling" happens when you push the "Poll devices for status" icon on the HS3 home page. I think one of the HS3 devices for my plugin needs to be excluded from polling. Perhaps you have an event action that polls your system generally for status? If so, it must contact my plugin and poll the thermostat.

            Per my previous post above, it appears we have an issue with the 2441th when polled and in Mode=Program it reports back Mode=Auto but the thermostat itself doesn't actually change. Again, more research needed to see if this is a protocol/firmware issue or if it's something I can work around.

            Nathan
            HS 3.0.0.435 (PRO)
            Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
            Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
            Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
            http://www.kazteel.com/

            Comment


            • #21
              Originally posted by nfrobertson View Post
              That "Unexpected device type requested for polling" happens when you push the "Poll devices for status" icon on the HS3 home page. I think one of the HS3 devices for my plugin needs to be excluded from polling ...
              No big deal, but just to get to the bottom of that "Unexpected device type requested for polling" thing, I tried both an HS poll and the plugin's Thermostat tab poll action: no errors. Maybe one of those twilight glitches?

              Comment


              • #22
                I know I've seen that "Unexpected device for polling" while developing but it was more of a nit so I didn't get back to it yet. I have some testing to do for Rene next week so I'll put this on this list to research as well.

                Nathan
                HS 3.0.0.435 (PRO)
                Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
                Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
                Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
                http://www.kazteel.com/

                Comment


                • #23
                  I think I found the issue with using the home page polling button and getting the "unexpected device type" message. It was on the humidity devices. There was a bug in which field was being compared which resulted in that error.

                  I just posted 3.0.3.9 which can be pulled down using the updater override method for testing. I also added a CAPI Poll button to the root/parent (program) device for each thermostat to make it easier to poll just that one thermostat.

                  I'd like to get some feedback before posting it to the general updater.

                  http://www.kazteel.com/HomeSeer3/dev...r_override.txt
                  HS 3.0.0.435 (PRO)
                  Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
                  Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
                  Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory
                  http://www.kazteel.com/

                  Comment


                  • #24
                    Originally posted by nfrobertson View Post
                    I think I found the issue with using the home page polling button and getting the "unexpected device type" message. It was on the humidity devices. There was a bug in which field was being compared which resulted in that error.

                    I just posted 3.0.3.9 which can be pulled down using the updater override method for testing. I also added a CAPI Poll button to the root/parent (program) device for each thermostat to make it easier to poll just that one thermostat.

                    I'd like to get some feedback before posting it to the general updater.

                    http://www.kazteel.com/HomeSeer3/dev...r_override.txt
                    I installed 3.0.3.9 and 3.0.4.0 (hard to keep you with you ) and polling either from the device management page or from the plugin's thermostat tab is clean. On the other hand, my initial post on this issue indicates that the error popped in the log unexpectedly, not necessarily after me initiating a poll. I'll wait for a few (hardware) thermostat mode changes and will report back. Thanks.

                    Comment

                    Working...
                    X