Announcement

Collapse
No announcement yet.

Plugin not seeing that door has opened or closed.

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

  • Plugin not seeing that door has opened or closed.

    Hi,

    Recently, I've noticed that sometimes the plugin does not see that the garage door has opened or closed. Most of the time it works normally, but this morning (Jan. 23) it happened again. I opened the garage door around 6:25 AM when I left for work, but the garage door "Last Change" status is yesterday at 5:05:37 PM. I didn't see anything unusual in the HS log file. Everything else in HomeSeer seems to be working normally. I'm running plugin version 1.1.17344.311 on Windows 10. Is there anything I can check or modify to resolve this problem?



    Current Date/Time: 1/23/2018 7:17:43 AM
    HomeSeer Version: HS3 Standard Edition 3.0.0.368
    Operating System: Microsoft Windows 10 Pro - Work Station
    System Uptime: 4 Days 11 Hours 13 Minutes 42 Seconds
    IP Address: 192.168.1.100
    Number of Devices: 217
    Number of Events: 176
    Available Threads: 400

    Enabled Plug-Ins
    2.0.93.0: BLRF
    1.1.17344.311: MyQ
    0.0.0.35: Pushover 3P
    3.0.5.6: SDJ-Health
    3.0.1.130: Z-Wave

  • #2
    Originally posted by regm View Post
    Hi,

    Recently, I've noticed that sometimes the plugin does not see that the garage door has opened or closed. Most of the time it works normally, but this morning (Jan. 23) it happened again. I opened the garage door around 6:25 AM when I left for work, but the garage door "Last Change" status is yesterday at 5:05:37 PM. I didn't see anything unusual in the HS log file. Everything else in HomeSeer seems to be working normally. I'm running plugin version 1.1.17344.311 on Windows 10. Is there anything I can check or modify to resolve this problem?



    Current Date/Time: 1/23/2018 7:17:43 AM
    HomeSeer Version: HS3 Standard Edition 3.0.0.368
    Operating System: Microsoft Windows 10 Pro - Work Station
    System Uptime: 4 Days 11 Hours 13 Minutes 42 Seconds
    IP Address: 192.168.1.100
    Number of Devices: 217
    Number of Events: 176
    Available Threads: 400

    Enabled Plug-Ins
    2.0.93.0: BLRF
    1.1.17344.311: MyQ
    0.0.0.35: Pushover 3P
    3.0.5.6: SDJ-Health
    3.0.1.130: Z-Wave

    You could change the logging level to see if we can catch what is happening there. Most of the time when trying to find intermittent issues like this it ends up being that the MyQ web service was not responding during that time interval. Unfortunately they've got it locked down so much that we cannot communicate directly with the garage door opener, but have to go via their web service. The web service has been proven to be very finicky when it comes to availability.

    If it happens frequently, I'd say try changing the logging level. If it's very infrequent, I fear changing the log level may just fill up your log files with nonsense.

    Comment


    • #3
      OK, if it happens more often I will change the logging level. But I guess there is not much that can be done with their unreliable web service.

      FYI, I did check the LiftMaster web site and it does show that the door was opened and closed this morning.

      TODAY

      6:24 AM - Double Garage Door just closed

      6:24 AM - Double Garage Door just opened

      Comment


      • #4
        Originally posted by regm View Post
        OK, if it happens more often I will change the logging level. But I guess there is not much that can be done with their unreliable web service.

        FYI, I did check the LiftMaster web site and it does show that the door was opened and closed this morning.

        TODAY

        6:24 AM - Double Garage Door just closed

        6:24 AM - Double Garage Door just opened
        That is perhaps a change I will make to the plugin in the future. Currently my plugin only updates the last change date/time when the plugin sees it change. However the web service does report a last change that it's receiving from the door openers. Perhaps I'll change the plugin to show what the web service is reporting as the last change.

        Comment


        • #5
          Originally posted by kingfetty View Post
          That is perhaps a change I will make to the plugin in the future. Currently my plugin only updates the last change date/time when the plugin sees it change. However the web service does report a last change that it's receiving from the door openers. Perhaps I'll change the plugin to show what the web service is reporting as the last change.
          For me, it was useful that the plugin only updates the last change date/time when the plugin sees a change. Today, I noticed that the garage light did not turn off when the garage door was closing. The light turns off when the plugin sees that the door "changes and becomes Closing". It was easy to identify the problem when I saw that the garage door last change date/time had not updated.

          Are there any pros/cons to using "Closing" vs "Closed" that would affect the reliability of the plugin/web service?

          Comment


          • #6
            Originally posted by regm View Post
            For me, it was useful that the plugin only updates the last change date/time when the plugin sees a change. Today, I noticed that the garage light did not turn off when the garage door was closing. The light turns off when the plugin sees that the door "changes and becomes Closing". It was easy to identify the problem when I saw that the garage door last change date/time had not updated.

            Are there any pros/cons to using "Closing" vs "Closed" that would affect the reliability of the plugin/web service?
            Well, the web service reports a value of last change that indicates the last change in any state. If I change the plugin to use that value then any change in state will change the device's last change timestamp.

            If you see value in leaving it the way it is, then I will be happy to oblige. Ultimately the plugin is for you all, I'll try the best I can to make it work with whatever scenarios you can dream up.

            Comment


            • #7
              The garage door was opened a few minutes ago but the Homeseer garage door status was not updated. I tried to access the MyQ plugin from Plugins > Manage, but it would not respond. I tried several times and this message was displayed each time: "Initializng... Retry in 10 seconds". In Task Manager I could see that HSPI_MyQ was running and every few seconds there was network activity. The plugin memory usage was unusually low at 6MB. I stopped and started Homeseer and can now access the MyQ plugin configuration page. The plugin memory usage is a normal 25MB. I'll continue to monitor the garage door status.

              Comment


              • #8
                I'm seeing a lot of MyQ errors in the HS log file. After seeing these errors the garage door status is not updated in HS and the plugin configuration page returns "Initializng... Retry in 10 seconds". I must restart HS or disable/enable the plugin to restore the plugin to an operational state.

                Can I provide any other information?


                Jan-24 12:55:30 PM MyQ Error Exception in httpGET|ErrorCount:0|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-24 12:53:41 PM MyQ Error Exception in httpGET|ErrorCount:5|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-24 12:52:23 PM MyQ Error Exception in httpGET|ErrorCount:4|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-24 12:50:34 PM MyQ Error Exception in httpGET|ErrorCount:3|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-24 12:47:42 PM MyQ Error Exception in httpGET|ErrorCount:2|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-24 12:46:56 PM MyQ Error Exception in httpGET|ErrorCount:1|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-23 6:56:14 PM MyQ Error Exception in httpGET|ErrorCount:0|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-23 6:54:46 PM MyQ Error Exception in httpGET|ErrorCount:5|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-23 6:53:08 PM MyQ Error Exception in httpGET|ErrorCount:4|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-23 6:51:31 PM MyQ Error Exception in httpGET|ErrorCount:3|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-23 6:51:16 PM MyQ Error Exception in httpGET|ErrorCount:2|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-23 6:50:07 PM MyQ Error Exception in httpGET|ErrorCount:1|https://myqexternal.myqdevice.com/ap...iceDetails/Get
                Jan-23 2:42:19 PM MyQ Error Exception in httpGET|ErrorCount:0|https://myqexternal.myqdevice.com/ap...iceDetails/Get

                Comment


                • #9
                  Seeing the same thing here...

                  Comment


                  • #10
                    Ok,

                    I wonder if they changed something again in the API to attempt to block us again. Time to roll up my sleeves and dig back at it. Give me a bit to see if I can find any changes.

                    Also, have you tried a reboot recently? Had someone the other day just needed a reboot.

                    Comment


                    • #11
                      Yep, seeing the same thing on my side also. Looks like they changed something. Stay tuned for updates.

                      Comment


                      • #12
                        It appears to have started working again on my side now. I have started looking into the newest MyQ android app and they have modified tons of code. I'm worried this may have been a dry run to switch things over again. Either that or the service was simply down on their side as part of an outage.


                        Let me know if your plugin is working again after a plugin stop/start. I have a bunch logs I've gathered on my side and I'm digging through their new code on the Android app to see if this is an indication of them attempting to take us down again.

                        Comment


                        • #13
                          Update, still crawling through code and still seeing instability in the communications to their server

                          Comment


                          • #14
                            Still no update after plugin stop start, but at the moment, no error messages in the log either.

                            Well spoke too soon! Got my first error message again. Same as the ones above. My IOS app shows correct status for the doors.

                            Comment


                            • #15
                              yeah, I'm watching it pretty closely on my end right now and I'm seeing intermittent connectivity issue to the server. Running full debugs right now to see if we can get to the bottom of it.

                              It seems right now every so often we get a string of the server spitting back:

                              The remote server returned an error: (500) Internal Server Error.

                              Looks like their server is responding, just with errors. Still looking through all the code changes they made on the app to see if maybe their expecting something different from us. But the intermittent nature of it suggests that they're having infrastructure issues on their end.

                              Comment

                              Working...
                              X