Announcement

Collapse
No announcement yet.

plugin error

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

    plugin error

    Hi Michael, After I update the plugin, I don't see the mqtt plugin appear on the manage menu. the HS4 log show error below. Can you help me out please. Thanks.
    5/19/2022 4:47:33 PM
    HomeSeer
    Error
    Examining properties on plugin (2) HSPI_MCSMQTT.exe: Object reference not set to an instance of an object

    #2
    I have this same problem. I've lost control of everything.

    A restore from a system backup doesnt resolve the issue.

    Rasp pi HS4

    Comment


      #3
      What files does your system backup cover? Does a restore replace all files? I don't understand what a backup restore would not remove everything that was added by the Updater.

      Something to look at is the reference path that is contained in HS folder file HSPI_MCSMQTT.exe.config with line
      Code:
            probing privatePath="bin/mcsMQTT;bin/homeseer"
      This was changed becasuse mcsMQTT uses the most current Newtonsoft version 13 while HS user the prior version 12. The path was changed to look first in mcsMQTT subfolder before looking in HS subfolder.

      Before submitting I did an updater override install of the plugin on both Rpi and Windows to confirm the install.

      There is a developer mode that can be enabled from the HS Setup menu. It creates console window on Windows and I think it does into a system log file on Linux. Dont know if the window will even be created if HS cannot find the HSPI_MCSMQTT.exe object.

      Another thing to look at is the mcsMQTT Debug.txt file when enabled to see if any additional information in it. Not likely as it seems the problem is with HS not able to find some file.

      Maybe with some more clues we can run down the problemm.

      Comment


        #4
        I'm running debian 10. I had HSPI_MCSMQTT.exe file. Inside had a folder and two files. Inside the folder has version.txt file. Below is inside the version.txt file. I had the code above just extra / > after homeseer". Since the plugin not even start I don't have any debug file. Is possible roll back to last version?

        FILEVERSION 5,24,3,5
        PRODUCTVERSION 5,24,3,5
        FILEFLAGSMASK 0x3F
        FILEFLAGS 0x0
        FILEOS VOS_UNKNOWN | VOS__WINDOWS32
        FILETYPE VFT_APP
        FILESUBTYPE 0x0
        {
        BLOCK "VarFileInfo"
        {
        VALUE "Translation", 0x0, 1200
        }
        BLOCK "StringFileInfo"
        {
        BLOCK "000004b0"
        {
        VALUE "Comments", ""
        VALUE "CompanyName", "mcsSolutions"
        VALUE "FileDescription", "HSPI_MCSMQTT"
        VALUE "FileVersion", "5.24.3.5"
        VALUE "InternalName", "HSPI_MCSMQTT.exe"
        VALUE "LegalCopyright", "Copyright © 2020-2022"
        VALUE "LegalTrademarks", ""
        VALUE "OriginalFilename", "HSPI_MCSMQTT.exe"
        VALUE "ProductName", "HSPI_MCSMQTT"
        VALUE "ProductVersion", "5.24.3.5"
        VALUE "Assembly Version", "5.24.3.5"
        }
        }
        }

        Comment


          #5
          I was referring to the file "HSPI_MCSMQTT.exe.config" and not the .exe file.

          I am able to reproduce the problem so should be able to find a resolution.

          Comment


            #6
            That is show in the hs4 log after reinstall the plugin and I restart the system.

            HomeSeer
            Warning
            Plug-in mcsMQTT is set to load but was not found, removing from settings.

            Comment


              #7
              The problem was in HSPI_MCSMQTT.exe.config . The probing path needs to have forward and not reverse slash. Tihis file is in HS folder. The updated one is attached. Restart HS after unzipping this file into HS folder.
              Attached Files

              Comment


                #8
                Thank you Michael. It fix the issue.

                Comment


                  #9
                  I just edited the HSPI_MCSMQTT.exe.config file. It was easier and it seems to have fixed the issue for me too. Tnx!

                  Comment

                  Working...
                  X