Announcement

Collapse
No announcement yet.

Newtonsoft.json error for Plug-in Version 5.23.10.0

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

    Newtonsoft.json error for Plug-in Version 5.23.10.0

    Hi, Michael

    I have update to the latest version 5.23.10.0 and i have this error in log:

    ProcessMessage New TEMPO2={"JourJ1":{"Tempo":0},"JourJ":{"Tempo":0}} à MCSMQTT_2020.ProcessMessage.GetJSONKeyList(String sValue, Boolean bRetry) à MCSMQTT_2020.ProcessMessage..ctor(MqttMsgPublishEventArgs eventArg, Int32 iPubBroker) dans C:\Users\Public\Documents\TFVC\HS\MQTT\MCSMQTT_2020\ProcessM essage.vb:ligne 291 Line 577 Impossible de charger le fichier ou l'assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' ou une de ses dépendances. La définition trouvée du manifeste de l'assembly ne correspond pas à la référence de l'assembly. (Exception de HRESULT : 0x80131040)
    This works with version 5.23.5.0

    Can you help me?

    Thanks
    Jean-Francois

    My System:
    Current Date/Time: 25/03/2022 18:43:25
    HomeSeer Version: HS3 Pro Edition 3.0.0.548
    Operating System: Microsoft Windows 10 Famille - Work Station
    System Uptime: 1 Day 14 Hours 41 Minutes 51 Seconds
    IP Address: 192.168.1.219
    Number of Devices: 625
    Number of Events: 290
    Available Threads: 800
    HSTouch Enabled: True
    Event Threads: 0
    Event Trigger Eval Queue: 0
    Event Trigger Priority Eval Queue: 0
    Device Exec Queue: 0
    HSTouch Event Queue: 0
    Email Send Queue: 0
    Anti Virus Installed: Windows Defender
    In Virtual Machine: No MFG: acer
    Enabled Plug-Ins
    2.0.45.0: BLLAN
    1.0.4.0: BLShutdown
    0.0.0.31: drhsIpPlugIn
    3.28.1222.5: HSBuddy
    5.23.5.0: mcsMQTT
    3.0.0.69: mcsXap
    3.0.0.14: NetCAM
    3.0.0.63: PHLocation2
    30.0.0.41: RFXCOM
    3.0.0.60: X10
    0.0.0.11: Yeelight 3P
    3.0.9.0: Z-Wave

    #2
    Looks like the Newtonsoft version you have installed is not the one that mcsMQTT is using. The attached goes in the HS subfolder bin\mcsMQTT
    Attached Files

    Comment


      #3
      Thanks, Michael

      I installed the Dll in bin/mqtt Now I have this new error message in the Homeseer log

      JSON Payload not in proper format: {"HS3":9,4,"BLBackup":-1,"BLLAN":0,2,"BLPlex":-1,"BLShutdown":0,"BLUSBUIRT":-1,"CpsTuya":-1,"drhsIpPlugIn":0,"HSBuddy":0,4,"HSTOUCH":-1,"MCSMQTT":0,2,"MCSXAP":0,1,"MediaController":-1,"NETCAM":0,"PHLocation2":0,"RFXCOM":0,1,"SCREPOSITORY":-1,"SDJHealth":-1,"SDJ_VStat":-1,"WEATHERXML":-1,"X10":0,"YEELIGHT3P":0,"ZWave":0,3,"BLBackup":0,"BLLAN":0, "BLPlex":0,"BLShutdown":0,"BLUSBUIRT":0,"CpsTuya":0,"drhsIpP lugIn":0,"HSBuddy":0,"mcsMQTT":0,"mcsXap":0,"MediaController ":0,"NetCAM":0,"PHLocation2":0,"RFXCOM":0,"SCREPOSITORY":0," SDJHealth":0,"SDJ-VStat":0,"weatherXML":0,"X10":0,"Yeelight3P":0,"ZWave":0}
      I no longer have the Newtonsoft.json error message
      No device is updated
      If I go back to version 5.23.5.0, everything works fine

      Jean-Francois

      Comment


        #4
        I suspect the issue is {"HS3":9,4, where the comma is the decimal delimiter. Looks like I will need to produce this internal message using the period even though regional settings use the comma so that a proper JSON format is produced. The internal JSON parser was able to handle either.

        Comment


          #5
          Update in 5.23.10.1 which is posted at the bottom of first post at mcsMQTT Change Log (HS4 & HS3) - HomeSeer Message Board

          Comment


            #6
            HI, Michael

            I have updated the Dll with 5.23.10.2

            No error message in log BUT NO device are updated in web page MQTT

            The change are received in debug log mcsMQTT Debug.txt

            27/03/2022 17:56:44 74051 | ActOnMessageForTrigger Topic HS,Payload={"HS3":9.9,"BLBackup":-1,"BLLAN":0.3,"BLPlex":-1,"BLShutdown":0,"BLUSBUIRT":-1,"drhsIpPlugIn":0,"HSBuddy":0.3,"HSTOUCH":-1,"MCSMQTT":0.2,"MCSXAP":0.1,"MediaController":-1,"NETCAM":0,"PHLocation2":0,"RFXCOM":0.1,"SCREPOSITORY":-1,"SDJHealth":-1,"SDJ_VStat":-1,"WEATHERXML":-1,"X10":0,"YEELIGHT3P":0,"ZWave":0.3,"BLBackup":0,"BLLAN": 0, "BLPlex":0,"BLShutdown":0,"BLUSBUIRT":0,"drhsIpPlugIn":0 ,"HS Buddy":0,"mcsMQTT":0,"mcsXap":0,"MediaController":0,"NetCAM" :0,"PHLocation2":0,"RFXCOM":0,"SCREPOSITORY":0,"SDJHealth": 0 ,"SDJ-VStat":0,"weatherXML":0,"X10":0,"Yeelight3P":0,"ZWave":0}, Triggers=0
            27/03/2022 17:56:55 85279 | ActOnMessageForTrigger Topic Ecodevice,Payload={"product":"Eco-devices","T1_PTEC":"HPJB","T1_PAPP":660,"T1_BBRHCJB":1095594 8,"T1_BBRHPJB":11742315,"T1_BBRHCJW":2487600,"T1_BBRHPJW": 20 73050,"T1_BBRHCJR":348278,"T1_BBRHPJR":701975,"T1_DEMAIN":"----","T2_PTEC":"HPJB","T2_PAPP":190,"T2_BBRHCJB":20920530," T2_B BRHPJB":16366252,"T2_BBRHCJW":9397337,"T2_BBRHPJW":8330122," T2_BBRHCJR":380610,"T2_BBRHPJR":763405,"T2_DEMAIN":"----","INDEX_C1":0,"INDEX_C2":0}, Triggers=0
            27/03/2022 17:56:58 88337 | HSEvent VALUE_CHANGE| 1024| 3863| 23| 23| 3863
            Click image for larger version  Name:	Screen Shot 03-27-22 at 06.04 PM.JPG Views:	0 Size:	107.1 KB ID:	1533940Click image for larger version  Name:	Screen Shot 03-27-22 at 06.05 PM.JPG Views:	0 Size:	108.0 KB ID:	1533941
            If i reload V5.23.5.0, it's OK

            [ATTACH]n1533952[/ATTACH]

            jean-francois.

            Comment


              #7
              Thanks for the good data. I see the issue is transcription from HS4 to HS3 plugin. I am making another update for thermostat support and will post the update that contains this and the JSON fix in a few hours.

              Comment


                #8
                I decided to just post the HS3 update as 5.23.10.3 without the thermostat update. It is at the same location as prior updates.

                Comment


                  #9
                  Hi, Michael

                  Work with 5.23.10.3 but Url is not updated,

                  The link is etablished and closed

                  In version 5.23.10.3 mcsMQTT Debug V 5.23.10.3.txt
                  28/03/2022 09:17:39 14084 | Http Started for http://192.168.1.20/api/xdevices.json?cmd=10
                  28/03/2022 09:17:39 14085 | Http Shutdown for http://192.168.1.20/api/xdevices.json?cmd=10
                  In version 5.23.5.0 mcsMQTT Debug V5.23.5.0.txt

                  (quote]27/03/2022 18:32:57 5643 | Http Started for http://192.168.1.20/api/xdevices.json?cmd=10
                  27/03/2022 18:32:57 5742 | ActOnMessageForTrigger Topic URL/192.168.1.20/api/xdevices.json?cmd=10.GET,Payload={"product":"Eco-devices","T1_PTEC":"HPJB","T1_PAPP":790,"T1_BBRHCJB":1095594 8,"T1_BBRHPJB":11742817,"T1_BBRHCJW":2487600,"T1_BBRHPJW":20 73050,"T1_BBRHCJR":348278,"T1_BBRHPJR":701975,"T1_DEMAIN":"----","T2_PTEC":"HPJB","T2_PAPP":180,"T2_BBRHCJB":20920530,"T2_B BRHPJB":16366364,"T2_BBRHCJW":9397337,"T2_BBRHPJW":8330122," T2_BBRHCJR":380610,"T2_BBRHPJR":763405,"T2_DEMAIN":"----","INDEX_C1":0,"INDEX_C2":0.000}, Triggers=0[/quote]

                  Thanks

                  Jean-francois

                  Comment


                    #10
                    The code that keeps the connection is
                    Code:
                    Do While Not gShutdown AndAlso bPoll AndAlso IsNumeric(HttpPoll) AndAlso HttpEndpointRaw <> ""
                    It means that
                    1. Plugin is not shutting down
                    2. HS Device for this URL IP has enabled polling
                    3. A number has been entered for the polling rate on the URL tab
                    4. An endpoint has been entered below the polling rate

                    For your URL the IP should be http://192.168.1.20/api
                    and the endpoint should be /xdevices.json?cmd=10

                    It may have been in the past that the endpoint could be included in IP. I noticed that I did not make the endpoint validity before the HTTP thread was started.

                    Does this explain your situation? If so, then be aware that when the IP is changed the pseudo-topic is also changed so any associated HS device(s) will need to be changed. You would need to copy the Ref from the old association into the Ref text box of the new topic row to create the association with the same Ref as the old one.

                    Comment


                      #11
                      Thanks, Michael

                      It's work 😀

                      Click image for larger version

Name:	Screen Shot 03-28-22 at 06.10 PM.JPG
Views:	103
Size:	84.1 KB
ID:	1534120

                      Thank you for this plugin.

                      Jean-Francois

                      Comment

                      Working...
                      X