Announcement

Collapse
No announcement yet.

Has Version 4.1.2.0 changed the way events handles payloads?

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

  • Has Version 4.1.2.0 changed the way events handles payloads?

    I updated to 4.1.2.0 and now some of my events with specific payloads have stopped working.

    This is the syntax that was working before the update: cbus/write/254/56/10/ramp=100,20s

    Here's a screenshot:

    Click image for larger version

Name:	2019-08-07.png
Views:	98
Size:	66.0 KB
ID:	1319554

    Could you please have a look at this Michael?

    Worst case I'll try and roll back to a previous version.

    Marty
    iCore5 Win 10 Pro x64 SSD

    HS3 Pro Edition 3.0.0.435 Windows

    BLOccupied:,Device History:,Yamaha:,UltraMon3:,mcsXap:,Restart:,UltraNetatmo3:, UltraM1G3:,Ultra1Wire3:,BLBackup:,Harmony Hub:,DoorBird:,UltraECM3:,Nanoleaf 3P:,UltraRachio3:,Z-Wave:,SDJ-Health:,BLGarbage:,Blue-Iris:,Chromecast:,Pushover 3P:,EasyTrigger:

  • #2
    Seeing the same here, I have several events that send a pre-defined payload & topic to my MQTT broker where they get picked up by an RFXcom node. For some reason the messages never arrive at the broker.

    Because of time constraints I was not able to further troubleshoot (sorry !) and I had to revert back from 4.1.2.0 to 4.1.0.0, functionality was restored to normal.

    Running HomeSeer Version: HS3 Standard Edition 3.0.0.534 on Microsoft Windows 10 Pro - Work Station, MQTT Broker is Mosquitto

    BR Francois

    Comment


    • #3
      Originally posted by fvhemert View Post
      Seeing the same here, I have several events that send a pre-defined payload & topic to my MQTT broker where they get picked up by an RFXcom node. For some reason the messages never arrive at the broker.
      Good to know that it's not just me. I did a few upgrades today including our Unifi network controller so wasn't a 100% sure on the exact cause of the issue. Didn't have enough time try rolling back but I'll do that tomorrow and wait for a fix before updating again.

      The plugin is otherwise fantasic. Very quick and flexible. MQTT has been a great discovery for me, having previously used xAP. Michael has been instrumental in both. A real HomeSeer asset for the forums and users.

      Marty
      iCore5 Win 10 Pro x64 SSD

      HS3 Pro Edition 3.0.0.435 Windows

      BLOccupied:,Device History:,Yamaha:,UltraMon3:,mcsXap:,Restart:,UltraNetatmo3:, UltraM1G3:,Ultra1Wire3:,BLBackup:,Harmony Hub:,DoorBird:,UltraECM3:,Nanoleaf 3P:,UltraRachio3:,Z-Wave:,SDJ-Health:,BLGarbage:,Blue-Iris:,Chromecast:,Pushover 3P:,EasyTrigger:

      Comment


      • #4
        Originally posted by mminehan View Post
        The plugin is otherwise fantasic. Very quick and flexible. MQTT has been a great discovery for me, having previously used xAP. Michael has been instrumental in both. A real HomeSeer asset for the forums and users.

        Could not agree more !

        Comment


        • #5
          I replicated the first screenshot and this resulted in the expected event output when manually triggered.
          Click image for larger version

Name:	Capture.PNG
Views:	87
Size:	44.5 KB
ID:	1319633

          The following was produced as viewed by a capture utility
          Code:
          8:34:52 AM cbus/write/254/56/10/ramp       100,20s
          8:34:52 AM cbus/write/254/56/9/ramp         100,20s
          8:34:52 AM cbus/write/254/56/179/ramp     100,20s
          8:34:52 AM cbus/write/254/56/11/ramp       100,20s
          8:34:52 AM cbus/write/254/56/60/ramp       50,20s
          The most recent changes to handling actions is associated with LED Messaging sign where the HTML is stripped from payload if going to a sign. This should have no bearing on fixed payload text operation. In a recent version the new event action to send publist was added. This means that there are now two types of mcsMQTT actions and the plugin needs to check which of the two are being requested. Previously it did not need to make this check.

          To help isolate the issue I added debug sequence to the event action handler. For the test the following was produced in \Data\mcsMQTT\mcsMQTTDebug.txt when General tab debug is enabled. For others I do not expect the Handle Action Sign entries, but the others should be present. This version with debug is at http://mcsSprinklers.com/mcsMQTT_4_1_2_1.zip.


          Code:
          8/7/2019 9:11:24 AM    335515    | Handle Action Entry   
          8/7/2019 9:11:24 AM    335516    | Handle Action TANumber 1  
          8/7/2019 9:11:24 AM    335517    | Handle Action Topic cbus/write/254/56/10/ramp  
          8/7/2019 9:11:24 AM    335517    | Handle Action Sign 25=cbus/wr=LedSign  
          8/7/2019 9:11:24 AM    335518    | Handle Action Sign 25=cbus/wr=BigSign  
          8/7/2019 9:11:24 AM    335602    | Handle Action Topic=Payload cbus/write/254/56/10/ramp=100,20s  
          8/7/2019 9:11:24 AM    335610    | ActoOnMessageForTrigger Topic cbus/write/254/56/10/ramp,Payload=100,20s  
          8/7/2019 9:11:24 AM    335617    | Handle Action Entry   
          8/7/2019 9:11:24 AM    335621    | Handle Action TANumber 1  
          8/7/2019 9:11:24 AM    335624    | Handle Action Topic cbus/write/254/56/9/ramp  
          8/7/2019 9:11:24 AM    335627    | Handle Action Sign 24=cbus/wr=LedSign  
          8/7/2019 9:11:24 AM    335630    | Handle Action Sign 24=cbus/wr=BigSign  
          8/7/2019 9:11:24 AM    335632    | Handle Action Topic=Payload cbus/write/254/56/9/ramp=100,20s  
          8/7/2019 9:11:24 AM    335639    | ActoOnMessageForTrigger Topic cbus/write/254/56/9/ramp,Payload=100,20s  
          8/7/2019 9:11:24 AM    335641    | Handle Action Entry   
          8/7/2019 9:11:24 AM    335643    | Handle Action TANumber 1  
          8/7/2019 9:11:24 AM    335645    | Handle Action Topic cbus/write/254/56/179/ramp  
          8/7/2019 9:11:24 AM    335647    | Handle Action Sign 26=cbus/wr=LedSign  
          8/7/2019 9:11:24 AM    335648    | Handle Action Sign 26=cbus/wr=BigSign  
          8/7/2019 9:11:24 AM    335650    | Handle Action Topic=Payload cbus/write/254/56/179/ramp=100,20s  
          8/7/2019 9:11:24 AM    335656    | ActoOnMessageForTrigger Topic cbus/write/254/56/179/ramp,Payload=100,20s  
          8/7/2019 9:11:24 AM    335656    | Handle Action Entry   
          8/7/2019 9:11:24 AM    335680    | Handle Action TANumber 1  
          8/7/2019 9:11:24 AM    335682    | Handle Action Topic cbus/write/254/56/11/ramp  
          8/7/2019 9:11:24 AM    335684    | Handle Action Sign 25=cbus/wr=LedSign  
          8/7/2019 9:11:24 AM    335687    | Handle Action Sign 25=cbus/wr=BigSign  
          8/7/2019 9:11:24 AM    335689    | Handle Action Topic=Payload cbus/write/254/56/11/ramp=100,20s  
          8/7/2019 9:11:24 AM    335697    | ActoOnMessageForTrigger Topic cbus/write/254/56/11/ramp,Payload=100,20s  
          8/7/2019 9:11:24 AM    335697    | Handle Action Entry   
          8/7/2019 9:11:24 AM    335702    | Handle Action TANumber 1  
          8/7/2019 9:11:24 AM    335704    | Handle Action Topic cbus/write/254/56/60/ramp  
          8/7/2019 9:11:24 AM    335706    | Handle Action Sign 25=cbus/wr=LedSign  
          8/7/2019 9:11:24 AM    335708    | Handle Action Sign 25=cbus/wr=BigSign  
          8/7/2019 9:11:24 AM    335709    | Handle Action Topic=Payload cbus/write/254/56/60/ramp=50,20s  
          8/7/2019 9:11:24 AM    335716    | ActoOnMessageForTrigger Topic cbus/write/254/56/60/ramp,Payload=50,20s

          Comment


          • #6
            Interesting.....the event based MQTT formatted payload messages are working again with version v4.1.2.1.

            Were there any other changes other than the extra debug between 4.1.2.0 and 4.1.2.1?

            I did manually install the .exe, .png and .dlls from the zip file as per the install text file.

            Would be interested to see if fvhemert notices the same.

            Marty
            iCore5 Win 10 Pro x64 SSD

            HS3 Pro Edition 3.0.0.435 Windows

            BLOccupied:,Device History:,Yamaha:,UltraMon3:,mcsXap:,Restart:,UltraNetatmo3:, UltraM1G3:,Ultra1Wire3:,BLBackup:,Harmony Hub:,DoorBird:,UltraECM3:,Nanoleaf 3P:,UltraRachio3:,Z-Wave:,SDJ-Health:,BLGarbage:,Blue-Iris:,Chromecast:,Pushover 3P:,EasyTrigger:

            Comment


            • #7
              The updates that have been done recently are associated with messaging sign. I am not aware if they would have broader implications. If it is fixed in 4.1.2.1 then great. We shall see.

              Comment


              • #8
                Originally posted by fvhemert View Post
                Seeing the same here, I have several events that send a pre-defined payload & topic to my MQTT broker where they get picked up by an RFXcom node. For some reason the messages never arrive at the broker.

                Because of time constraints I was not able to further troubleshoot (sorry !) and I had to revert back from 4.1.2.0 to 4.1.0.0, functionality was restored to normal.

                Running HomeSeer Version: HS3 Standard Edition 3.0.0.534 on Microsoft Windows 10 Pro - Work Station, MQTT Broker is Mosquitto

                BR Francois
                Finally was able to update the plugin, I can confirm that version 4.1.2.2 has resolved the issue reported above.

                Thanks for addressing this, sorry I could not be of assistance in trouble shooting (this time)


                Comment

                Working...
                X