Announcement

Collapse
No announcement yet.

Issues with event action controls - manual PI device controls working correctly

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

  • Issues with event action controls - manual PI device controls working correctly

    • HS Version: HS3 Standard Edition 3.0.0.478 (Windows)
    • Plugin version: 1.4.0.1: Honeywell WiFi Thermostat
    • Description of the problem: Cool Setpoint and Hold Type not behaving as expected when controlled by event - details below. Shortly after completing this testing/logging, mytotalconnectcomfort.com appears to have gone offline, possibly in connection with the announced planned maintenance. My issues have occurred since initial install of the plugin several days ago.
    • HS3 Server OS: Microsoft Windows 10 Pro - Work Station
    • Thermostat model: Honeywell RTH6580WF Wi-Fi Thermostat
    • Log file: Attached, changed extension from .log to .txt to avoid .log upload prohibition. Link: [ATTACH]n1278051[/ATTACH]
    • Data dump (if your thermostat has updated at least once): Failed to do this. If data isn't in log Iet me know and I'll redo the testing/logging and grab the dumps.

    I created these 2 test events to demonstrate the issue.
    Click image for larger version

Name:	00Events.PNG
Views:	11
Size:	55.8 KB
ID:	1278052

    Here are the devices created by the plugin for my 2 thermostats. I verified the values by comparing with mytotalconnectcomfort.com.
    Click image for larger version

Name:	01DevicesBeforeEvent1.PNG
Views:	28
Size:	195.4 KB
ID:	1278048

    After running the 1st event, heating setpoints are corrected changed, but cooling setpoints are not changed and Hold Type is incorrectly set to Temporary rather than Permanent.

    Log after 1st event:

    Click image for larger version

Name:	02LogAfterEvent1.PNG
Views:	11
Size:	25.3 KB
ID:	1278053

    Devices after 1st event. Heat setpoints unchanged and hold type set incorrectly. I gave it a couple minutes to be sure the plugin had time to update mytotalconnectcomfort.com
    Click image for larger version

Name:	03DevicesAfterEvent1.PNG
Views:	10
Size:	194.4 KB
ID:	1278049

    I then manually made the adjustments to Cool Setpoint and Hold Type using plugin device controls and verified that both were correctly set by checking mytotalconnectcomfort.com:
    Click image for larger version

Name:	04LogAfterManualAdjustmentsBetweenEvents.PNG
Views:	9
Size:	34.4 KB
ID:	1278050

    [Continued in next post]

    -Wade

  • #2
    [Continued from prior post]

    Devices just before running event 2 (after manually adjusting Heat Setpoints and Hold Types):

    Click image for larger version

Name:	05DevicesBeforeEvent2AfterManualAdjustments.PNG
Views:	14
Size:	194.0 KB
ID:	1278058

    Log immediately after 2nd event:
    Click image for larger version

Name:	06LogAfterEvent2.PNG
Views:	10
Size:	25.7 KB
ID:	1278059

    Devices after 2nd event. Heat setpoints and hold types did not change. I gave it a couple minutes to be sure the plugin had time to update the mytotalconnect.com server.
    Click image for larger version

Name:	07DevicesAfterEvent2.PNG
Views:	9
Size:	193.8 KB
ID:	1278060

    I ran event 2 a second time for the heck of it. No change of result.
    Click image for larger version

Name:	08LogAfterEvent2SecondRun.PNG
Views:	9
Size:	52.9 KB
ID:	1278061

    Devices after 2nd run:
    Click image for larger version

Name:	09DevicesAfterEvent2SecondRun.PNG
Views:	8
Size:	180.3 KB
ID:	1278062


    Please advise what I should do to further troubleshoot. Thank you.



    As an aside, I received this error in the log when trying to download the log via the plugin configuration. I manually grabbed the log from C:\Program Files (x86)\HomeSeer HS3\Logs.

    Click image for larger version

Name:	10LogAfterLogDownloadAttempt.PNG
Views:	10
Size:	5.9 KB
ID:	1278063

    Thanks.
    -Wade

    Comment


    • #3
      Now going back and looking at the log file I uploaded, it's very brief so may not have had it correctly set to trace. Let me know if I need to redo it.
      -Wade

      Comment


      • #4
        shill Are you able to help me troubleshoot this? I'm down to a few days left on my trial period. Thank you.
        -Wade

        Comment


        • #5
          I noticed you are on HS3 .478... not sure if related but there are a lot of device and plugin issues introduced in 478 that I verified with HST. I would recommend downgrading or upgrading to at the least .489 to get passed the device/plugin issues. The latest is .495 which in a few days of testing has been fine. I just think with the known problems in .478 you may be chasing HS3 issues and not plugin specific.

          Comment


          • #6
            Unfortunately I'm travelling (business last week, vacation this week) so I haven't had a chance to look into this in any detail. I did look at the log file but you're right - it didn't have what I needed in it to see anything. In addition to what Simplex said, you're also testing this out during a 5 week rolling maintenance window at Honeywell, where I'm seeing all kinds of errors and connectivity problems. Probably the worst time in the world to do a trial of a Honeywell TCC-based product, I'm afraid.

            Perhaps HomeSeer can help you reset the trial and you can start it up again next month when, hopefully, their systems will be back to stable - and I'll have had enough time to adjust to any changes. And of course it's possible their changes could render this whole plugin inoperable So my recommendation is to wait and reevaluate in March.

            Comment


            • #7
              Originally posted by Simplex Technology View Post
              I noticed you are on HS3 .478... not sure if related but there are a lot of device and plugin issues introduced in 478 that I verified with HST. I would recommend downgrading or upgrading to at the least .489 to get passed the device/plugin issues. The latest is .495 which in a few days of testing has been fine. I just think with the known problems in .478 you may be chasing HS3 issues and not plugin specific.
              Thanks for the suggestion. I'll give .495 a go.

              Originally posted by shill View Post
              Unfortunately I'm travelling (business last week, vacation this week) so I haven't had a chance to look into this in any detail. I did look at the log file but you're right - it didn't have what I needed in it to see anything. In addition to what Simplex said, you're also testing this out during a 5 week rolling maintenance window at Honeywell, where I'm seeing all kinds of errors and connectivity problems. Probably the worst time in the world to do a trial of a Honeywell TCC-based product, I'm afraid.

              Perhaps HomeSeer can help you reset the trial and you can start it up again next month when, hopefully, their systems will be back to stable - and I'll have had enough time to adjust to any changes. And of course it's possible their changes could render this whole plugin inoperable So my recommendation is to wait and reevaluate in March.
              If updating to .495 doesn't have any effect I'll see if HS will reset my evaluation. I've noticed additional issues the past couple days--likely due to Honeywell tweaking their system. Bad luck on my timing. Thanks.
              -Wade

              Comment


              • #8
                cc4005

                UPDATE: I mistyped setpoint in the event below

                For your events to set the hold type and setpoints, you can use the "Honeywell WiFi Thermostat: Change Setpoint" action to change the setpoint and hold type in the same event. I've attached my events that I'm using here.

                shill


                I'm having the same problem. I just recently created events to set the hold type to permanent and adjust the temperature setpoints. The heat set point and the hold type works ok, but the cool setpoint does not work as part of the event, but I can manually change it from the device and that works ok.

                When running the event to set the cool and heat points to a temporary hold, only the heat setpoint and hold type is set correctly. The cool setpoint does not work as part of the event, but I can manually change it from the device and that works ok.

                I've attached the trace file as well as the events that I have configured.

                Click image for larger version  Name:	Honeywell-event-cancel hold.png Views:	1 Size:	301.3 KB ID:	1287122Click image for larger version  Name:	Honeywell-event-perm hold.png Views:	1 Size:	267.2 KB ID:	1287123

                Comment


                • #9
                  shill

                  Also, when trying to download the log file through the options tab, I get this message:
                  404 Bad Request: /skWare/Lyric/HSPI_SKWARE_HW_WIFI_TSTAT.log

                  Comment


                  • #10
                    I figured out the reason it's dropping some of those commands and am working on a solution. I'll tackle the download of the log file while I'm at it!

                    Comment


                    • #11
                      Thanks shill Your update fixed the issue and it's working as expected. I was worried Honeywell had broken the API during their maintenance.

                      Comment


                      • #12
                        I cringe every time they post a maintenance notice! So far, so good.

                        Comment


                        • #13
                          shill Does the latest version fix the issue from the original post above? My trial expired a few weeks ago so I'm not able to verify. If so then time to get licensed!
                          -Wade

                          Comment


                          • #14
                            It should, yes. The issue is your events are overly verbose and require multiple requests to the server. I try to prevent duplicate requests from being sent and accidentally considered them silicate in some cases when they weren't.

                            Comment


                            • #15
                              Originally posted by shill View Post
                              It should, yes. The issue is your events are overly verbose and require multiple requests to the server. I try to prevent duplicate requests from being sent and accidentally considered them silicate in some cases when they weren't.
                              Great,thanks! Purchase made.

                              I'm always for simplification. How can I achieve the same result with less verbose events?
                              -Wade

                              Comment

                              Working...
                              X