Announcement

Collapse
No announcement yet.

mcsMQTT Not Showing Device Action For New Zigbee Remote

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

    mcsMQTT Not Showing Device Action For New Zigbee Remote

    I recently bought a new TuYa 4 Button Zigbee Remote. Zigbee2MQTT successfully add the remote and the MQTT JSON message looks like this:

    Code:
    {
    "action": "4_single",
    "battery": 100,
    "linkquality": 60
     }
    Unfortunately mcsMQTT only sees two of those (battery and linkquality), it does not show me the whole point of the remote the "action" field.

    Sub: zigbee2mqtt/Four_Button_Blinds_Remote:battery
    Sub: zigbee2mqtt/Four_Button_Blinds_Remote:linkquality

    Click image for larger version  Name:	Screenshot_2022-09-14_20-14-29.jpg Views:	0 Size:	22.4 KB ID:	1566274

    How can I get mcsMQTT to see the "action" field of the JSON payload. My MQTT Browser does see the full payload.

    Click image for larger version  Name:	Screenshot_2022-09-14_20-15-35.jpg Views:	0 Size:	65.7 KB ID:	1566275

    Thanks for any help!
    ---------------------------------------------------
    Jean-Marie G. Vaneskahian
    jean@vaneskahian.com
    ---------------------------------------------------

    #2
    I notice your table sort is based on S column. When looking at topics it is easiest to sort by Topic.

    I see nothing unusual about the topic itself so more likely a display problem and not a recognition problem. The debug log will show more info about how it is parsing the JSON payload. In particular a line about ActOnMessageForTrigger for TuYa_Four_Button_Blinds_Remote:action

    Comment


      #3
      Should I just capture a Debug log and press the buttons on the remote to change the action?


      Jean-Marie Vaneskahian
      ---------------------------------------------------
      Jean-Marie G. Vaneskahian
      jean@vaneskahian.com
      ---------------------------------------------------

      Comment


        #4
        After doing a debug as you suggested, I still do not understand why mcsMQTT is not representing the "action" with an entry in the table that I can create an association with. I have attached the raw debug to this message but I also have the lines that reference the topic from the debug. I pressed each button once in the order of "4, 3, 2, 1" and each button press seemed to generate 3 entries in the debug log:

        Code:
        9/15/2022 11:58:24 AM 38654294 | ActOnMessageForTrigger QueueSize=0 ,Topic zigbee2mqtt/bridge/logging,Payload {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/TuYa_Four_Button_Blinds_Remote', payload '{\"action\":\"4_single\",\"battery\":100,\"linkquality\":66 }'"}
        9/15/2022 11:58:24 AM 38654294 | ProcessMessage zigbee2mqtt/TuYa_Four_Button_Blinds_Remote
        9/15/2022 11:58:24 AM 38654295 | ActOnMessageForTrigger QueueSize=1 ,Topic zigbee2mqtt/TuYa_Four_Button_Blinds_Remote,Payload {"action":"4_single","battery":100,"linkquality":66}
        
        9/15/2022 11:58:28 AM 38657863 | ActOnMessageForTrigger QueueSize=0 ,Topic zigbee2mqtt/bridge/logging,Payload {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/TuYa_Four_Button_Blinds_Remote', payload '{\"action\":\"3_single\",\"battery\":100,\"linkquality\":63 }'"}
        9/15/2022 11:58:28 AM 38657864 | ProcessMessage zigbee2mqtt/TuYa_Four_Button_Blinds_Remote
        9/15/2022 11:58:28 AM 38657865 | ActOnMessageForTrigger QueueSize=1 ,Topic zigbee2mqtt/TuYa_Four_Button_Blinds_Remote,Payload {"action":"3_single","battery":100,"linkquality":63}
        
        9/15/2022 11:58:30 AM 38660402 | ActOnMessageForTrigger QueueSize=0 ,Topic zigbee2mqtt/bridge/logging,Payload {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/TuYa_Four_Button_Blinds_Remote', payload '{\"action\":\"2_single\",\"battery\":100,\"linkquality\":63 }'"}
        9/15/2022 11:58:30 AM 38660403 | ProcessMessage zigbee2mqtt/TuYa_Four_Button_Blinds_Remote
        9/15/2022 11:58:30 AM 38660404 | ActOnMessageForTrigger QueueSize=1 ,Topic zigbee2mqtt/TuYa_Four_Button_Blinds_Remote,Payload {"action":"2_single","battery":100,"linkquality":63}
        
        9/15/2022 11:58:33 AM 38663183 | ActOnMessageForTrigger QueueSize=0 ,Topic zigbee2mqtt/bridge/logging,Payload {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/TuYa_Four_Button_Blinds_Remote', payload '{\"action\":\"1_single\",\"battery\":100,\"linkquality\":54 }'"}
        9/15/2022 11:58:33 AM 38663184 | ProcessMessage zigbee2mqtt/TuYa_Four_Button_Blinds_Remote
        9/15/2022 11:58:33 AM 38663185 | ActOnMessageForTrigger QueueSize=1 ,Topic zigbee2mqtt/TuYa_Four_Button_Blinds_Remote,Payload {"action":"1_single","battery":100,"linkquality":54}
        I do not understand why "battery" and "linkquality" each get a entry that I can create an association for in HS4 but "action" does not. What can I try next?
        Attached Files
        ---------------------------------------------------
        Jean-Marie G. Vaneskahian
        jean@vaneskahian.com
        ---------------------------------------------------

        Comment


          #5
          I found it! Apparently I had renamed it from "Four_Button_Blinds_Remote" to "TuYa_Four_Button_Blinds_Remote"!!! I am a moron! Now when I go to the new topic, I see "action"!

          Here is the raw list unfiltered:

          Click image for larger version

Name:	Screenshot_2022-09-15_12-24-45.jpg
Views:	99
Size:	30.4 KB
ID:	1566379

          It is all working as expected. My apologies!
          ---------------------------------------------------
          Jean-Marie G. Vaneskahian
          jean@vaneskahian.com
          ---------------------------------------------------

          Comment


            #6
            Here it is in action. The remote is a Zigbee 4 button and the blinds are ZWave. Thanks for creating mcsMQTT that makes this possible!

            ---------------------------------------------------
            Jean-Marie G. Vaneskahian
            jean@vaneskahian.com
            ---------------------------------------------------

            Comment


              #7
              It is great that the mixing of technologies is working well for you. Having a standard means of intercommunication such as MQTT on ethernet makes it possible.

              Comment

              Working...
              X