Announcement

Collapse
No announcement yet.

No Devices detected

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

    No Devices detected

    Loaded plugin, went through authorizations steps and copy pasted URL and hit authorize. No devices found. Went online to my LG account and can verify the washer and dryer are part of the account. Can't figure this out. Help!

    #2
    Hi! Sorry it doesn't work for you. Anything in the HS4 log that could help?

    If not, can you enable all logging (including logging to file) and restart the plugin? Let it run for a minute and stop the plugin agian. That hopefully quickly reveals what is going wrong.

    Feel free to send the log to me using a PM (it might contain personal information). You can find the logfile in the "Logs" directory of your HomeSeer root.
    stefxx

    Comment


      #3
      Great, easy fix. You will need to open the LG ThinQ app, login and agree to the terms. After that it should work.
      stefxx

      Comment


        #4
        I've tried everything. I've updated my password, added my device registration at mylg.com, logged in to the mobile app where I can see my washer. And I connected the skill successfully to Alexa. But your log shows this everytime I try to refresh devices, which are still showing none:
        2/16/2022 8:35:50 PM Send: https://route.lgthinq.com:46030/v1/s...on/gateway-uri
        2/16/2022 8:35:50 PM API error during error catch: Object reference not set to an instance of an object.
        2/16/2022 8:35:52 PM Send: https://route.lgthinq.com:46030/v1/s...on/gateway-uri
        2/16/2022 8:35:52 PM API error during error catch: Object reference not set to an instance of an object.

        I'll try again tomorrow.

        Tim

        if I put https://route.lgthinq.com:46030/v1/s...on/gateway-uri into my browser, I get:
        {"resultCode":"0003","result":""}

        Comment


          #5
          HI timlacey , I don't think this is related to the issue in this thread. But still a problem off course. I'll reach out to you to see if we can quickly fix this!
          stefxx

          Comment


            #6
            The issue of timlacey has been resolved in the latest beta. Turns out that Windows 7 uses another SSL version by default compared to newer Windows versions.

            The correct SSL version is now being set (forced) by the plugin.

            Thanks for your help Tim!
            stefxx

            Comment

            Working...
            X