Announcement

Collapse
No announcement yet.

mcsMQTT Plugin

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    I will test again. This is posted in HS3 forum. Are you using the HS3 plugin?

    Comment


      Originally posted by Michael McSharry View Post
      I will test again. This is posted in HS3 forum. Are you using the HS3 plugin?
      sorry, I posted on the wrong forum. I am using HS4 plugin 5.9.3.2

      Comment


        I did the test with current version of the HS4 plugin. The event was:

        Click image for larger version

Name:	Capture.PNG
Views:	272
Size:	21.6 KB
ID:	1441597

        I sent the Test/VD/set topic. After 1 minute the HS Log showed the Action and the mcsMQTT debug showed the following. I had other triggers setup, but the important items I highlighted.

        Code:
        12/18/2020 3:58:59 PM 521166 | ManageNewMessage Test/VD/set
        12/18/2020 3:58:59 PM 521166 | ActoOnMessageForTrigger Topic Test/VD/set,Payload=On
        12/18/2020 3:58:59 PM 521167 | Trigger List Topic Test/MultiTopic,Match=False,Trig Payload=7
        12/18/2020 3:58:59 PM 521167 | Trigger List Topic Test/MultiTopic,Match=False,Trig Payload=6
        12/18/2020 3:58:59 PM 521168 | Trigger List Topic Test/Receive/#,Match=False,Trig Payload=
        12/18/2020 3:58:59 PM 521169 | Trigger List Topic Test,Match=False,Trig Payload=ding
        12/18/2020 3:58:59 PM 521169 | Trigger List Topic Test/#,Match=True,Trig Payload=
        12/18/2020 3:58:59 PM 521170 | Trigger List Payload Match
        12/18/2020 3:58:59 PM 521171 | Trigger Fire UID 6304, TrigListUID=8322
        12/18/2020 3:58:59 PM 521171 | Trigger Fire UID 6304, TrigListUID=3718
        12/18/2020 3:58:59 PM 521172 | Trigger Fire UID 6304, TrigListUID=8970
        12/18/2020 3:58:59 PM 521172 | Trigger Fire UID 6304, TrigListUID=9344
        12/18/2020 3:58:59 PM 521173 | Trigger Fire UID 6304, TrigListUID=6304
        12/18/2020 3:58:59 PM 521174 | Trigger Fired 
        I reviewed the change log https://forums.homeseer.com/forum/li...mcsmqtt-plugin post #1 between your version and current version and did not see anything change for event triggers. You can update using the updater override process to http://mcsSprinklers.com/HSPI_mcsMQTT_5_11_6_2.zip, but I suspect you will get the same result. What do you get in the debug log following the ManageNewMessage for your topic?

        Comment


          Michael McSharry after upgrading to 5.11.6.2 it is now working (BTW your updater_override.json does not contain the correct version number)

          Comment


            Thank you for the feedback on the updater file. I fixed it so the next person will not have a problem with it.

            Comment


              Ik have a Zigbee remote which sends different messages based on which button is pressed. I want to react to this messages so I setup the following event:

              My problem is that there is also a payload which is called "up_hold". The problem is that I cannot distinguise between the "up" and "up_hold" because both payloads contain the word "up".

              My question is if I it's possible to explicitly match the payload text? (I know that the text specifically states the word "contains", but I just want to check if it's possible or not). I've tried putting single and double quotes around the word, but that doesn't work.

              Thank you in advance for taking the time to answer my question.

              Comment


                I suggest associating the subject topic to a HS device on the Association tab and use the List Control/Status UI on the Edit tab. Each payload text will now be assigned a specific Value-Status pair and then you can trigger on HS Device Value being a specific number.

                It is also better to start a new topic rather than extending this long thread because it becomes hard to search.

                Comment


                  Thanks Michael for the answer. Took me a bit of Sherlock Holmes to figure out how to solve the problem based on your answer and the plugin. That had to do with my limited knowledge of the plugin, not your answer :-). In the end it was simple once I figured it out. I will create a new topic describing my issue and the solution to it for other people new to the plugin and strugling with the same thing and for future reference.

                  btw awesome plugin. Overwhelming, but awesome. Thanks!

                  Comment


                    Hey all, I'm at my wits end here. I noticed my mcsmqtt HS3 plugin hadn't been updated since 5.4.x so I updated to 5.9.3.2 a few days ago. Since then, I'm getting MQTT commands sending 0 (off) to a number of devices from I don't know where. For instance, I have a Z-wave power strip and I monitor my washer and dryer on it. Every minute I'm seeing a washer and dryer 0 sent via MQTT. In my small home theater, when I turn off the theater lights (zigbee lights controlled from Zigbee2MQTT but I added a virtual device for it to HomeSeer to control it from my Echo Dot) it spams the heck out of MQTT with 0 to all of the lights. I literally can't turn them on. They turn off instantly lol. If I restart mcsmqtt then all is quite until I use them one time and then things go crazy again. I'm monitoring all MQTT commands from MQTT.fx but my question is does anyone have any thoughts as to how I can tell *where* the MQTT commands are coming from? If any more information is needed, I'm happy to share. I should note that I also have these devices in Node-Red which runs based upon time and/or voice command and the like. Thank you.

                    *Update: I disabled Node-Red and the MQTT commands continued. I de-associated the devices from mcsmqtt and they stopped. I re-associated the devices and the commands continue.

                    Comment


                      My guess is that your power strip is providing periodic status to HS. HS generates an event telling mcsMQTT that the device was set. mcsMQTT sends MQTT message with the status. This can be confirmed in the debug log if debug data is being collected in the plugin using the setting on the General tab.

                      I'm not certain about 5.9.3.2 operation, but with the current version of the plugin you have the ability to control only sending changes vs. sending every time HS provides the event. For non-plugin devices it is set via HS Device Management with a setting similar to Set Does Not Change Last Time. In HS4 it was renamed to Last Change Time Updates on Status Change Only.

                      The current plugin version is 5.13.2.0. It is described at https://forums.homeseer.com/forum/hs...on-and-viewing and includes references for instructions to use the Updater Override process to install it.

                      Comment


                        Originally posted by Michael McSharry View Post
                        My guess is that your power strip is providing periodic status to HS. HS generates an event telling mcsMQTT that the device was set. mcsMQTT sends MQTT message with the status. This can be confirmed in the debug log if debug data is being collected in the plugin using the setting on the General tab.

                        I'm not certain about 5.9.3.2 operation, but with the current version of the plugin you have the ability to control only sending changes vs. sending every time HS provides the event. For non-plugin devices it is set via HS Device Management with a setting similar to Set Does Not Change Last Time. In HS4 it was renamed to Last Change Time Updates on Status Change Only.

                        The current plugin version is 5.13.2.0. It is described at https://forums.homeseer.com/forum/hs...on-and-viewing and includes references for instructions to use the Updater Override process to install it.
                        Well krike, you were right... I totally missed that the power strip mqtt data was indeed stat and not cmnd. My mistake there. Thank you, I updated to 5.13.2.0 and re-enabled my theater lights subflow in Node-Red and I no longer see infinite off commands preventing me from turning them back on. I'll keep an eye on things to make sure I didn't miss anything. Thanks for your tireless efforts in helping this community with your amazing plugin(s).

                        Comment

                        Working...
                        X