Announcement

Collapse
No announcement yet.

HomeSeer MQTT plugin.

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

    #76

    Comment


      #77
      I don't quite understand you. Are reading that temperature from HomeSeer side or the Node-RED side? Because MQTT (MQ Telemetry Transport or Message Queuing Telemetry Transport) apart from relaying messages to and from HomeSeer does not process anything within HomeSeer. That is done by the HS3 server because it creates the device references. Or else where do you get the device string ( $$DTARef) from? Because I believe that's what HS3 should have created! For more on that check out this post here : https://forums.homeseer.com/showpost...46&postcount=7 You may also dig deeper in here : https://homeseer.com/support/homeseer/HS3/HS3Help.pdf

      Let say if you have HomeSeee (mqtt plugin) subscribe to your topic from Node-RED a virtual device will be created and thus the ref. then HomeSeer /Sonos can speak the contents of that device.

      Can you please explain it a bit better? If it's complicated the plugin author will help you here : https://www.domoticaforum.eu/viewforum.php?f=74


      Eman.
      TinkerLand : Life's Choices,"No One Size Fits All"

      Comment


        #78
        Last edited by Fischi; December 12, 2017, 01:38 PM. Reason: failure

        Comment


          #79
          https://www.homeseer.com/support/hom..._variables.htm =====> Mark the Colon (punctuation) at the end of 1569 ====> ":"

          Eman.
          Last edited by Eman; December 12, 2017, 05:59 PM.
          TinkerLand : Life's Choices,"No One Size Fits All"

          Comment


            #80
            The format for the reference variable is $$DVR:(ref):

            Note the colon at the end of the variable - which you did not have

            Comment


              #81

              Comment


                #82
                There is no way HomeSeer is going to speak a message round trip to Node-RED and back just the way are you doing it. That's why you are having problems. Yes HS3 will speak your device value but there's no reason to send the message from Node-RED.
                If say the set point of your sensor was reached then you would create an event of that device with in HS3.
                If it was Node-RED sending the value then MQTT in HomeSeer would subscribe to that value and thus a device created and HS3 would speak that value.. If you send an Mqtt message and subscribe to a new device ID is created in HomeSeer.

                NOTE: To create devices that you subscribed to you have to click the add button on left.

                Eman.
                Last edited by Eman; April 24, 2018, 08:11 PM.
                TinkerLand : Life's Choices,"No One Size Fits All"

                Comment


                  #83
                  MQTT in the ESP8266 WemosD1Mini

                  Hello, I've learned a lot here but am missing the final piece in my puzzle.
                  I set up a RPI3 with Mosquitto and verified it sends and receives.

                  My HS is a HS2 and I have loaded the MQTT plugin.

                  I want to send a payload from HS to a Wemos D1 Mini to make a single GPIO pin close a relay for 2 seconds to open or close my garage door, then report the open/closed status based on either a tilt sensor (already in HS) or magnetic sensors.

                  What do I put on the Wemos to make it listen for MQTT packets and respond?

                  Thank you in advance for any advice/help.

                  Comment


                    #84
                    To start you should flash the ESPEasy firmware on the Wemos D1. ESPEasy has an MQTT stack - the protocol to use would be "openHAB MQTT"
                    http://www.twoenter.nl/blog/en/ardui...wemos-d1-mini/

                    Read up on the required ESPEasy configuration for GPIO pins etc:
                    https://www.letscontrolit.com/wiki/i..._web_interface

                    Then use Step 3 in my guide here to configure HS3 for control via MQTT:
                    https://forums.homeseer.com/showpost...2&postcount=60

                    Comment


                      #85
                      Originally posted by rxmas View Post
                      Hello, I've learned a lot here but am missing the final piece in my puzzle.
                      I set up a RPI3 with Mosquitto and verified it sends and receives.

                      My HS is a HS2 and I have loaded the MQTT plugin.

                      I want to send a payload from HS to a Wemos D1 Mini to make a single GPIO pin close a relay for 2 seconds to open or close my garage door, then report the open/closed status based on either a tilt sensor (already in HS) or magnetic sensors.

                      What do I put on the Wemos to make it listen for MQTT packets and respond?

                      Thank you in advance for any advice/help.


                      First off this plugin is for HS3.
                      The second point is if your Wemos device doesn't have a plugin in HomeSeer then it can't be controlled. But only if your device was mqtt ( which I think can be) based like the ESP2866 then you could load mqtt on it then add it the group of devices you want to control with the mqtt plugin. All you would do is to publish custom topics of what you want.

                      Here: http://jpmens.net/2016/03/22/mqtt-on-an-esp8266-thing/ There is a good topic about the Wemos thingie!

                      But if still inquisitive the go here : https://www.domoticaforum.eu/viewfor...297beabb71713a and ask the author of the plugin.



                      Eman.
                      TinkerLand : Life's Choices,"No One Size Fits All"

                      Comment


                        #86


                        Hello Fischi,

                        I had another hard look at your explanation above and it looks like you are sending topics from HomeSeer to Node-RED. And it seems you are using the Sonos control of Node-RED ==>https://flows.nodered.org/node/node-red-contrib-sonos.

                        What I can tell is Node-RED can't speak HomeSeer language thus ===> $$DVR:1569: So in order to do what you on about, the sensor has to be connected to Node-RED with some node .

                        So to sum it all up your question if am not wrong would be "how would you publish the value of your sensor from HomeSeer to Node-RED?"

                        To publish your devices you add them using the PUBLISH button. See this image here : https://forums.homeseer.com/showpost...4&postcount=67 then have Node-RED subscribe to the those topics.

                        It would be much more easier for either Node-RED or HS3 to handle the sensor and do the Speaking. Both have the Sonos plugins. But if you deside Node-RED then you can also add an mqtt topic to HS3 to create a device and do something with that as well.




                        Eman.
                        TinkerLand : Life's Choices,"No One Size Fits All"

                        Comment


                          #87
                          Originally posted by taylormia View Post
                          To start you should flash the ESPEasy firmware on the Wemos D1. ESPEasy has an MQTT stack - the protocol to use would be "openHAB MQTT"
                          http://www.twoenter.nl/blog/en/ardui...wemos-d1-mini/

                          Read up on the required ESPEasy configuration for GPIO pins etc:
                          https://www.letscontrolit.com/wiki/i..._web_interface

                          Then use Step 3 in my guide here to configure HS3 for control via MQTT:
                          https://forums.homeseer.com/showpost...2&postcount=60


                          Nice one man @taylormia

                          you got there first.


                          Eman.
                          TinkerLand : Life's Choices,"No One Size Fits All"

                          Comment


                            #88
                            Good call

                            Originally posted by Eman View Post
                            First off this plugin is for HS3.
                            The second point is if your Wemos device doesn't have a plugin in HomeSeer then it can't be controlled. But only if your device was mqtt ( which I think can be) based like the ESP2866 then you could load mqtt on it then add it the group of devices you want to control with the mqtt plugin. All you would do is to publish custom topics of what you want.

                            Here: http://jpmens.net/2016/03/22/mqtt-on-an-esp8266-thing/ There is a good topic about the Wemos thingie!

                            But if still inquisitive the go here : https://www.domoticaforum.eu/viewfor...297beabb71713a and ask the author of the plugin.



                            Eman.

                            Thanks for the links. I'm getting closer

                            Comment


                              #89
                              I use mqtt now with nodered and a raspberry pi to allow my car to access control straight to the dash.

                              Needs a little work but the trial works really well.

                              Comment


                                #90
                                Originally posted by gd1210 View Post
                                I use mqtt now with nodered and a raspberry pi to allow my car to access control straight to the dash.

                                Needs a little work but the trial works really well.


                                I really like what you have done here. If only I would ask you a big favour ===> Link up with this guy here : https://play.google.com/store/apps/d...tdash&hl=en_GB and ask him to join the Homeseer club so we can have an app like his for HomeSeer for the not the so technical people like I'm but love HomeSeer dearly. Even if it was a paid for version, it would bring great joy to folks me.



                                Eman.
                                TinkerLand : Life's Choices,"No One Size Fits All"

                                Comment

                                Working...
                                X