Announcement

Collapse
No announcement yet.

Cant get rid of error - Plugin not working...

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

    Cant get rid of error - Plugin not working...

    Hey Spud --

    Just purchased the plugin and an old version worked for me, but .8 keeps throwing :

    DEBUG System.IO.FileLoadException: Could not load file or assembly 'System.Threading.Tasks, Version=2.6.8.0, Culture=neutral,

    Any ideas?

    #2
    can you delete completely bin/Nest, then reinstall 3.0.0.8 from updater, and post the installation logs here

    also, what OS and .NET framework do you run?

    Comment


      #3
      Hey- Thanks for the reply ...

      I did that after posting, and reinstalled a.net 4.5 (on Windows 7) - That error is gone, but If I try to register my Nest, HS gets slow and I get :

      Dec-07 7:44:59 PM Warning Plugin Nest is not responding but it is still running, not restarting yet.

      Dec-07 7:44:58 PM Error Posting back to plugin web page nestconfig: Object reference not set to an instance of an object.

      Comment


        #4
        Ah, no - sorry - Log level reset, went back to Debug and that error is still there ....

        Comment


          #5
          you shouldn't have to register again if you already did it

          anyway, stop the plugin, kill any running HSPI_Nest.exe process from task manager, then restart the plugin, what does the logs show?

          Comment


            #6
            Originally posted by surovich View Post
            Ah, no - sorry - Log level reset, went back to Debug and that error is still there ....
            ok, then please post the installation logs as well as debug logs when the plugin starts.

            Comment


              #7
              Heres the plugin start error :

              Dec-07 8:00:52 PM Nest DEBUG System.IO.FileLoadException: Could not load file or assembly 'System.Threading.Tasks, Version=2.6.8.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)File name: 'System.Threading.Tasks, Version=2.6.8.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' at FirebaseSharp.Firebase.GetStreamingAsync(String path, DataUpdatedEventHandler updated) at NestSharp.NestClient.StartMonitoringData()WRN: Assembly binding logging is turned OFF.To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

              Probably a dumb question, but where is the install log for the plugin?

              Comment


                #8
                same place as other logs, i.e go to VIEW > Log

                you should see something like this after installing the plugin:

                Dec-07 8:03:34 PM Updater Install/Update of package Nest was successful.
                Dec-07 8:03:34 PM Updater Warning File exists, not overwriting: C:\Program Files (x86)\HomeSeer HS3\Config\\Nest.ini
                Dec-07 8:03:34 PM Updater Extraction Complete.
                Dec-07 8:03:34 PM Updater Extracting files from zip file: images.zip
                Dec-07 8:03:34 PM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\bin\Nest\NestSharp.dll
                Dec-07 8:03:34 PM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\bin\Nest\FirebaseSharp.dll
                Dec-07 8:03:34 PM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\bin\Nest\System.Threading.Tasks.dll
                Dec-07 8:03:34 PM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\bin\Nest\System.Runtime.dll
                Dec-07 8:03:34 PM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\bin\Nest\System.Net.Http.dll
                Dec-07 8:03:34 PM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\bin\Nest\Microsoft.Threading.Tasks.Extensions.dll
                Dec-07 8:03:34 PM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\bin\Nest\Microsoft.Threading.Tasks.Extensions.Desktop.dl l
                Dec-07 8:03:34 PM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\bin\Nest\Microsoft.Threading.Tasks.dll
                Dec-07 8:03:34 PM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\bin\Nest\Newtonsoft.Json.dll
                Dec-07 8:03:34 PM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\HSPI_Nest.exe.config
                Dec-07 8:03:34 PM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\HSPI_Nest.exe
                Dec-07 8:03:34 PM Updater Installing package Nest
                Dec-07 8:03:34 PM Updater Update HSPI_Nest.exe downloaded successfully
                Dec-07 8:03:31 PM Updater Downloading update: Nest
                Dec-07 8:03:31 PM Updater Starting download of updates

                Comment


                  #9
                  Ah cool - yeah, the log kept throwing that error so it was full and hard to find the install portion, so I uninstalled and reinstalled again :

                  Dec-07 8:37:34 PM Nest INFO Nest version 3.0.0.8

                  Dec-07 8:37:34 PM Info Plugin Nest has connected. IP:127.0.0.1:51882

                  Dec-07 8:37:21 PM Updater Install/Update of package Nest was successful.

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\Config\\Nest.ini

                  Dec-07 8:37:21 PM Updater Extraction Complete.

                  Dec-07 8:37:21 PM Updater Extracting files from zip file: images.zip

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\bin\Nest\NestSharp.dll

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\bin\Nest\FirebaseSharp.dll

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\bin\Nest\System.Threading.Tasks.dll

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\bin\Nest\System.Runtime.dll

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\bin\Nest\System.Net.Http.dll

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\bin\Nest\Microsoft.Threading.Tasks.Extensions.dll

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\bin\Nest\Microsoft.Threading.Tasks.Extensions.Desktop.dl l

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\bin\Nest\Microsoft.Threading.Tasks.dll

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\bin\Nest\Newtonsoft.Json.dll

                  Dec-07 8:37:21 PM Updater Making dir: C:\Program Files\HomeSeer HS3\bin\Nest\

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\HSPI_Nest.exe.config

                  Dec-07 8:37:21 PM Updater Copying file: C:\Program Files\HomeSeer HS3\HSPI_Nest.exe

                  Dec-07 8:37:20 PM Updater Installing package Nest

                  Dec-07 8:37:20 PM Updater Update HSPI_Nest.exe downloaded successfully

                  Dec-07 8:37:19 PM Updater Downloading update: Nest

                  Dec-07 8:37:19 PM Updater Starting download of updates

                  Comment


                    #10
                    in addition to bin/Nest directory do you have System.Threading.Tasks.dll (or any other dll installed in bin/Nest) installed in the HS3 root directory as well?

                    Comment


                      #11
                      You got it - There was a DLL in the root ... I should have caught that ... Thanks!

                      Comment


                        #12
                        Originally posted by surovich View Post
                        You got it - There was a DLL in the root ... I should have caught that ... Thanks!
                        cool!
                        which one? and do you know how it ended up there?
                        if it is installed by another plugin, I should contact the developer to let him know, so that this kind of conflicts does not happen again...

                        Comment

                        Working...
                        X