Glad it was helpful!

Wow, thank you!

Thanks Chicken Lips! More videos are on the way.

You're most welcome!

Thanks peter3099. We are busy making more videos!

Thanks Jaime ! You're the best.

You are so welcome! Really glad we could help.

@@Opto22 p

@@Opto22 p

You're very welcome!

Glad it was helpful!

Thank you Krishna! In this case that's just how the node works; it will take "true"/"false" or 1/0 as input and change the LED accordingly. Other nodes may behave differently so you might need to use a change node or JavaScript in a function node to convert the message to whatever format your output node needs. To find that out just check the node's info tab or run some basic tests and go from there.

Thanks DIYDSP!

Glad you liked it!

Glad you found it helpful!

Thanks Marouane!

have you tried to use a secure connection?

@@ivanagustino4032 Sadly not, so I can't help you with this one.. :(

thanks so much

Glad it helped

Thanks Michael - Glad you found it helpful!

You bet!

Thanks Muhammed!

I am really grateful for all the tutorials you guys presented in youtube. Thank you so much, success guys!

Thanks so much

Thanks so much!!

The multi-level wildcard # only matches subtopics to the left, so ".../somethingelse" would be included in `something/#`. You must use the single-level wildcard + if you want to specify subtopics of the wildcard, so your example might be `something/+/somethingelse`.

@@Opto22 i appreciate your video guide and got the zeal to setup everything for fun if you could tell what i'm doing wrong... tasmota-firmware i installed to my sonoff basic....nodered and dashboard show all connected topic is "sonoff" or "room/sonoff" to keep things simple. the true and false show clearly in node-red logs on syslog server listening to client mqtt subscribe messages, this is what i'm getting 03-23-2019 06:56:32 Local7.Debug 192.168.1.4 sonoff-3065 ESP-MQT: room/tele/sonoff/STATE = {"Time":"2019-03-23T02:26:33","Uptime":"0T05:35:15","Vcc":3.432,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER":"OFF","Wifi":{"AP":1,"SSId":"Xiaomi_Antariksh","BSSId":"78:11:DC:17:D0:54","Channel":1,"RSSI":54}} what is missing. i'll appreciate any guidance

@@mandeepmails You would subscribe to room/tele/sonoff/RESULT. Your broker may also be case sensitive, so you should test that too when you get the chance. Edit: Result produces the plain text version of your last command. Status gives a json version of your device state including the power status from a power command.

I think you need a server that publishes and subscribes to the MQTT broker and basically translates between the messages and the API.

Thanks so much!!!

With Node-RED and MQTT.fx you can freely publish any custom payload you want, so if you know what the device data might look like you could manually type some made up values that match the format you expect into either client for testing.

We have FREE online training at: training.opto22.com/

Learn more about groov EPIC programming software here: www.opto22.com/products/groov-epic-system/groov-epic-software

groov EPIC creates an *outbound* TCP/IP connection to the broker, connecting to its only open port 1883 (or 8883, the secure port). There are no ports open on the EPIC since it is initializing the connection itself, nothing is connecting to the EPIC directly. Once that connection is established then Node-RED can both send and receive MQTT messages. Any sensors that are sending MQTT messages need some kind of MQTT client, in this case we have attached our LED to the EPIC and that controller handles the MQTT communication, but anything from a PC to an Arduino controller can support MQTT client software. The other key element is a connection to whatever broker you want, whether that's on-premise or over the internet, either ethernet or wifi; the client device will need to be able to route messages to the broker. Since it's an outbound connection these clients, like groov EPIC, do not need to have any ports open. Once they're connected (and any security credentials check out) you're free to publish their data to your local PC. Your PC can both run the broker software and subscribe to any data coming in. Node-RED is a great part of an MQTT ecosystem because it can not only publish and subscribe, it can also move that data into and out of other sources; anything from a database to an email to pretty much any web API you can think of. Node-RED also has the potential to be a broker itself, if you want to go that route.

As I understand it, he has an MQTT broker software instance at a public server on groove.com. MQTT is bi-directional so it acts as a publisher AND a subscriber. He has set up Node Red to link to the MQTT broker on groove.com. It listens for new messages in the workspace/switch topic. - essentially a folder. His laptop also knows about the same MQTT broker software on groove.com. And also knows about the same workspace/switch topic.The broker software is the middle man. So, either by direct keyboard input or some automated process written in software code, the laptop publishes a message to workspace/switch. The device with the switch uses Node Red to listen to the groove.com MQTT broker software. When it “sees” a message in workspace/switch, Node Red takes whatever action It was told to in the work flow model. It could even publish a confirmation status back which could be read on the laptop. Code on the laptop might do something with the incoming subscription message such as change a graphic or send an email, play an audio file etc. Short answer: both laptop and device are aware of the MQTT broker software on groove.com. They do not know about each other but ARE signed up to the same topic. Both the laptop and the device can publish. Both the laptop and the device can subscribe. At each end, there will be some sort of software which takes action on the received message. That action may be very simple or have multiple parts. The device and laptop do not know about each other. All they know is that they have to listen to workspace/switch. If the switch is physically pressed, it will publish a message. If a user physically taps an icon on the laptop, it will publish a message. The other side will “see” that message and react as it has been programmed to do. Node Red has the ability to connect to a specified MQTT broker, either internal or - as in this case - external. It also has a GUI to build workflows but the whole thing could have been done by other programming languages / products.

The essential elements are the broker (the server that moves messages) and the clients (that produce and consume data). In this setup the broker is on the web, and the two clients are the laptop (MQTT software) and groov EPIC (Node-RED software). Either client could produce data for the other client or the other way around, since MQTT is a bi-directional communication method clients can send AND receive messages over the one connection. When it comes to the "switch" topic, Node-RED is the *subscribing* client, it is listening to any changes in that topic and will drive the light based on the results.

yes

Absolutely! MQTT is a bi-directional communication model, so once the connection is established you could publish a message every time your switch is flipped, your clients are certainly not limited to subscribe-only.

Yes, of course you can!

@@Opto22 if you find a video or tutorial on how to set this up. I'd really appreciate it. I've been looking and trying on my own but I haven't been very successful.

Hi Imufur, please check out our video "What is an MQTT broker" ukposts.info/have/v-deo/j518dY2GjaSoy3k.html Also, be sure to check out our free online training classes at: training.opto22.com/ Additional resources can be found at: developer.opto22.com/ I hope that helps!

@@Opto22 thanks

There are a lot of software options for brokers, the best one for you will largely depend on both your technical requirements and your budget. With that said, for simple setups and general testing I highly recommend checking out the Eclipse Mosquitto broker software; it's free, open-source, and is widely documented online.

We're always in a hurry to spread the word about MQTT and groov EPIC! Thanks for watching!!