MQTT Broker/Bridge on the ESP8266

The esp_uMQTT_broker is an MQTT broker, client, and bridge, as well as an automation controller. This video describes the ideas of the project as well as its features.
Find the code and more info on github: github.com/martin-ger/esp_mqtt
The pure library code for the ESP8266 Arduino environment is available here: github.com/martin-ger/uMQTTBr...

[@MANNAS3]

I watched your video a year ago and thanks to you I had a very good starting point implement what I desire, so there is no words that can express my gratitude for your efforts with such a great explanation!

[@seledwin]

Thank you So much! I couldn't simply go without thanking you after watching this video.. Thanks for sharing your knowledge!

[@asiw]

Wow, this looks fantastic. Can't wait to try it out. Many thanks for sharing and providing a very detailed and clear review of options that are available for Iot systems. Best wishes, Arthur

[@casholsen5848]

Martin, very well done! I've been looking toward MQTT broker in router (openwrt), but I think I favor this solution. By the comments and your responses this project is (will be) solving a dilemma many of us have faced. Bravo.

[@alaskawoodman]

Very well done overview and video presentation. One of the best I have seen. I will be checking out the esp_uMQTT_broker, it looks impressive. Thank you for taking the time to put together such a well thought-out and detailed introduction.

[@juergenfoterek6743]

Ja genau was ich gesucht habe. Suche noch das folge Video um mehr zur der einfachen Programmsprache zu erfahren. Gute Arbeit für schmale Projekte ideal.Danke Martin für deine tolle Arbeit.

[@giorgioboiero]

Hi Martin A very clear video about your project Your idea is great

[@tasterpipko4141]

Really nice work. Broker works fine, and scripting language too! Thanks for sharing and keep on good work.

[@sorin.n]

Excellent work! Thank you for sharing!

[@adaw9]

Wow... Thank you so much, almost use my very old laptop as broker. Excellent work! Thank you for sharing!

[@sanjeevtarigopula2620]

Excellent video..eagerly waiting for your next video

[@divyanshuanand8017]

Great !! I was searching this months ago. Great work man

[@maximussamir2332]

I know I'm kinda randomly asking but do anyone know a good website to watch new tv shows online ?

[@johnnymayson9150]

@Maximus Samir I watch on FlixZone. Just search on google for it :)

[@guatagel2454]

It works! Thank you very much. I tested it with 2 clients, an ESP8266 client and an Android phone with MyMQTT. I will migrate all my machine-to-machine apps to MQTT.

[@guatagel2454]

Both ESP8266 client and broker are Amica NodeMCU.

[@GoranKalic]

Great work! Thanks

[@hatemelborai]

Thank you very much, very nice presentation

[@luizmendesalmeida]

Hi Martin. First of all it's a great idea. Due to security concerns, I don't think it is good idea to expose uMQTT to internet. However, it should be really cool working in the internal network, acting in a mesh network. Best regards, Luiz Almeida.

[@shafieimohammad4925]

Hi Thank you so much for sharing your knowledge

[@gaetanrey8734]

Wonderful!!! good work

[@jonathanpeace3167]

Thanks so much for this Martin, it's a really nice architecture. Have you ported it to ESP32 yet or know of anyone who has?

[@CrazyGuyOfficial]

Good Job man

[@michaelbishton9439]

I think that this is very clever, Martin Ger. I'm just starting to get into this stuff, but can imagine that if multiple ESP devices were set up to be client/brokers, it could create a mesh data network. Am I correct? Have you tried this with the ESP32s that have more memory and speed?

[@iotguy2423]

Very nice project but it would had been great if you could had shown us step by step in installing broker and client in video

[@ZulfiqarAadil]

I am waiting for the next from you to load uMQTT inside of ESP

[@MrBobWareham]

I think we are going to have a long wait??

[@chris5461]

Hi Martin, are there any plans for ESP32 or ESP32-S2 as well?

[@lindnerlars81]

Hi Martin, thank you very much for this great project. Could you please create another video, how to implement and use your esp_uMQTT_broker library in an ESP32 please? Thanks a lot and with best wishes, Lars

[@veereshy5444]

Thank you very much. It was quite helpful to decide on my requirements. One quick question.. Can I use the same architecture (using only ESPs ) to implement mqtt mesh for farm automation as wifi range of devices is concern to me. If so please can you suggest me a best mqtt mesh libraries for ESPs..

[@martinger327]

You can use my esp_wifi_repeater (in automesh mode) for a tree-style mesh. I am not aware of another mesh-lib on the ESP8266 that allows for TCP/IP traffic (as MQTT requires).

[@sanjeev44]

will u please upload the video how to setup mqtt broker on nodemcu as soon as possible...thank you

[@larkbox8427]

Hi Im late to the party as usual, this looks like a great lil project, ideal for my BAN (eBike Area Network) initially a rgbled control system for lighting and indicator warning lighting..

[@RaadYacu]

Martin - awesome work based on the video. I am eager to replace rpi with esp broker. Perhaps moving this to ESP32 would be better since more resources exist? So one question popped out based on the video, when you say max 8 connections, are these concurrent connections? Is there a config to determine the how long before connection becomes stale? Thanks again

[@martinger327]

Yes, the limitation is on the number of concurrent connections. MQTT connections have an MQTT-level keep-alive. Thus, connection typically never become stale. A client must explicitly (or implicitly by walking away) disconnect. There are several reasons for the limitations on the numbver of clients: max. 8 WiFi-clients for the ESP (can't change that, it is given by the Espressif-driver and a hard limit in AP mode), max. number of TCP-connections in the lwip-lib (working on that), and RAM memory consumption for the MQTT-state (working on this, too). So I hope, to increase the number beyonde 8 at least when in STA mode. An ESP32 port is surely interesting and probably not too hard (and it would lift the limitations due to RAM), however the price of the ESP32 is still in the range of a RasPiZeroW, which is probably the better broker with Mosquitto running on it.

[@gustavoenriquejimenez8098]

@@martinger327 It is true that the price of the ESP32 is in the range of a RasPiZero W. But, with a ESP32 (or ESP8266) you don't have to worry about SD card corruption after bad shutdowns. The ESP32 just run once powered up.

[@ezequielbella4624]

Hi Martín! Great work, i really appreciate your generosity on sharing this with us. I've been using the broker on my nodemcu chip for a while, very stable by the way. I was wondering how could i use it as a library in lua. Is there any out there?

[@martinger327]

Thanks and sorry, I am not aware of such a port.

[@iotguy2423]

mqtt broker works fine but hard to connect with esp mqtt client to broker esp i get issue failed, rc=-2 try again in 5 seconds Attempting MQTT connection...failed, rc=-2 try again in 5 seconds

[@gbenna1]

This is a great idea but when I try to use the mqtt_sub.IMO example I get an error MQTT does not name a type on MQTT myMqtt(CLEINT_ID,192.168.0.1.1883); What am I doing wrong?

[@aradivil]

Спасибо. Получилось запустить брокера на ESP8266.

[@abhiabhityas9409]

Hi Martine sir I need your answers for following questions. 1. Can we use esp8255 for industrial applications? If yes, then where we have to buy good quality esp8266 ?

[@martinger327]

I am not sure, whether I am the right one to answer these questions. Surely the ESP8266's functionality is well suited to be used in industrial applications. But up to now, I am mainly aware of (chinese) products that use the ESP8266 for home automation puposes. To decide, whether it fits into your special environment (e.g. temperature range), you best visit Espressif's website an look for the data sheet. I am buying my ESPs in small quantities from various vendors using the usual usual end-user channels, but I guess, Espressif can also name official distributors.

[@konradzaremba5478]

Works perfectly. I use umqqt broker in my project. Super great work. Thanks for the dirty hack for adding the library to esp repo.

[@abhijeetec]

Hi @Konrad, Can you please tell how did you do it?

[@nunomcp]

Hi, great work! It's possible to do it with a Sonoff Zigbee Bridge? Thanks!

[@martinger327]

Might be possible, havn't tested that so far.

[@RaphaelNunes67]

Hello, I am having difficulty getting the data through an ESP01 client. I was able to make an ESP01 by generating an AP through it, being a publisher, and owning an internal broker. From the app "MyMQTT" present in the playstore I manage to make my smartphone a client. But I can't make an ESP01 connect as a client. Can you help me? Thanks.

[@AlecTraubBigAL]

Hi Martin thanks for the upload. I read through your github uploads and fiddled with the uMQTTBroker example in the arduino IDE. Although I am not always certain which info to change in the code for my specific purpose for eg/: if it says topic in the arduino code is that a variable or shall I change that to my topic name. If you perhaps had time could you please go over dowloading the uMQTT broker on to an ESP module. thank you.

[@martinger327]

"Topic" in the Arduino code means an MQTT-topic as given in the protocol spec, i.e. a string name for a publication. The Arduino code is a library that is dropped into the library directory and then the code download to the ESP works as with any other sketch.

[@Dialbist]

Good way it's create broker on router Xiaomi, 2 in one, router+mqtt broker (with modificate firmware)

[@user-co8un6lx3t]

Hi! looked at your code in the example for arduino, is delay (1000) required in the loop () function?

[@martinger327]

No, it is not - just to do anything... ;-)

[@user-co8un6lx3t]

@@martinger327 🥃

[@RobinGerritsen1995]

Hi, How do I compile all the files? I am currently using Arduino IDE, but I really need the MQTT broker on the esp8266, because it can handle the mqtt pub/subs and can work either offline as online, right? I want to make a wall-controller with buttons, build with esp8266 and I want to use multiple esp8266 for the lights, I don;t want to be depending on a mqtt server.

[@martinger327]

Ritght: it can work online (with connection to an uplink AP and the internet) as well as offline (without internet connection offering it's own AP). It compiles with the esp-open-sdk: github.com/pfalcon/esp-open-sdk and the included Makefile. (Not with the Arduino IDE). You might want to test the included binaries (flashing instructions for windows are the same as here: github.com/martin-ger/esp_wifi_repeater#building-and-flashing )

[@martinger327]

Added some instructions on how to add the broker functionality to any ESP Arduino project. You can find it at the bottom of the README.md.

[@byxlettera1452]

Dear Martin I would like to use your work, but I don't know how to do. Is it possible to have some intructions on how to add broker funcionality to an ESP project? A little tutorial would be great. Anyway there is a good readme in your second Github. Thanks

[@gbenna1]

How would I set up an iphone app as a client with this to display sensor data. Can this go outside local network?

[@martinger327]

For access from the Internet you will need a cloud service or a dynDNS for your home router and an MQTT port forward to access the broker from outside.

[@cad3175]

Hi Martin, I don't know if you will see this message but I'll post anyway. I'm planning a Lora application where I'll have 20 Lora esp32 nodes geographically distributed within 1.5km. All nodes will communicate with a central hub device only. The hub device will also send response messages to the nodes so it's two-way communication. Each node will have a keypad whereby users will transmit approximately two bytes of data back to a central hub (maybe a raspberry pi with Lora shield). The central hub will then respond to an incoming message by communicating a "message received" response to the node that originally sent the data. My first question is what would be the best choice of device for the central hub, I'm thinking of raspberry pi4 with a Lora shield maybe My second question is what software do you recommend? Some of the problems I see are - how will the central hub handle two or more messages coming in at the same time - should I dedicate a second hub device to handle responding to nodes to make sure the receiving hub is not too busy - can the available open source mqtt software handle all this or am I hoping for too much Also just to say this is not a commercial project, I'm developing this to help out a sporting organisation which is struggling so there's no gain in this for myself Thanks for your video, very clear :)

[@martinger327]

A (any) RasPi with Mosquitto will certainly be enough for the hub. LoRa has duty cycles (percentage of allowed airtime) and it will be impossible with 20 nodes to reach a bandwidth that cannot be handeled by a RasPi. Before you further go into details of the application, please considere this bandwidth limitation of LoRa. I seems to me, you are expecting a high load. LoRa is definitely not designed for high loads. Typical application is perhaps several messages per hour/day. Also think about power: LoRa is a low power RF technology, the ESP32 however consumes several 10mA when active. An ESP32 runs on battery only for some hours (if you don't use excessive deep sleep periods). If power is an issue, I would consider other MPUs than the ESP32 (especially when you dont use its WiFi). If power is not an issue (but bandwidth) I would perhaps consider mesh WiFi networking on the ESPs. Another issue: LoRa is not build for bidirectional traffic: typically you use it in the uplink of sensor nodes. Nodes send their status from time to time, if one message is lost - doesn't matter, it will be send again after some time (minutes).

[@KP-KP]

Hi, Thanks for the video, But I have no clue how to setup your code. If this video is for experts then I am sorry for asking the question. If not, then can U please explain how to set it up, where to set it up and how to run it?

[@martinger327]

github.com/martin-ger/esp_mqtt#building-and-flashing

[@vergSecurity]

Thank you very much Martin for this valuable work , As you know the most important part of IOT is its security , My question is about MQTT username and password and SSL connection to esp-broker , I'm using Arduino source code and I didn't get how to add a username and password in the ESP broker and connect to it using MQTT-Client , I will appreciate if you add an example about adding username and password in the sketch and use it on mqtt-client , Regards , M

[@martinger327]

Find an example for username/password here: github.com/martin-ger/esp_mqtt/issues/10#issuecomment-339541258 This works now. Up to now, the ESP cannot work reasonable (for more than one client) as TLS server due to memory constraints.

[@vergSecurity]

How many messages per second can I send to the esp? Actually ,I used Mqtt buddy as mqtt client on my mobile and If I send messages slowly(1 per sec) its OK, but If I send several messages in a second It will show sent messages with delay, Any Idea pls?

[@martinger327]

walt22 did some tests here: www.esp8266.com/viewtopic.php?p=70155#p70155 saying, that "that the broker can handle at least 100 pubs/subs per second." Of course this heavily depends on the size of the massages. You might even set the CPU-Freq to 160 MHz to speed it up a little bit.

[@vergSecurity]

It seems mqtt buddy doesn’t work correctly, I tried with a script using mqtt.fx and sent many messages per 10msec,it works perfect, Thanx Martin,

[@mxynidis]

Hello, Martin. I am very glad you shared your work. I set up an 8266 as a standalone MQTT server using the Arduino IDE according to the "fast-and-dirty hack" instructions in the README.md file from your esp_mqtt fork. It works! I loaded MQTT.fx on my Windows computer, and MQTT Snooper on my Android phone, and can publish and subscribe messages to topics between the two. Perfect. However, upon enabling Telnet on the PC, I cannot connect to the broker. The response was: "Connecting To 192.168.4.1...Could not open connection to the host, on port 7777: Connect failed" from Telnet. I tried the PuTTY clone, SmarTTY, getting similar results: "Connection test failed: No connection could be made because the target machine actively refused it 192.168.4.1:7777". Am I missing something? ...or is something not working right? Again, thanks for the very-nice broker implementation.

[@martinger327]

Hi Michael, the telnet server functionality is not included in the libmqtt.a but it is part of the additional control layer (user_main.c etc. in the "user" directory), i.e. this only works with my complete SDK project (and the included firmware). The "fast-and-dirty hack" only brings the pure MQTT-broker to Arduino. If you use it in an Arduino project, you will have to add your own WiFi configuration code.

[@abdulrehmanrao555]

Hi, thanks for awesome video. Please guide me how can I use ESP as uMQTT broker and mobile app and another ESP as clients? It will be actually a stand alone network. Is that possible?

[@martinger327]

Install this software github.com/martin-ger/esp_mqtt on one central ESP as broker. Configure it as AP. Let the other ESPs connect to this broker. Use any MQTT enabled software there e.g. Tasmota or your own sw, e.g. Arduino programs using the pubsub-library. There are many Android apps out there to contol via MQTT. I use "IoT MQTT Dashboard".

[@abdulrehmanrao555]

Thanks Martin, Can I connect uMQTT broker with AWS IOT via router and some other ESP8266 in station mode so that connection remain established and doesn't interrupt with AWS, when I get some data from ESPs

[@leef_me8112]

Could this be used on an ESP32? I wanted this for 15-20 total ESP32. One 'master' and many 'slaves'.

[@martinger327]

No, it doen't work on an ESP32 yet. Mainly because of the missing espconn interfaces. Has to be ported. Also 15-20 clients is too much for the AP interface. And as far as I know, there is also a mem limitation on the number of concurrent TCP connections.

[@leef_me8112]

Thank you for your reply. Best wishes.

[@maxbombel877]

Das klingt sehr interessant, aber wie bekomme ich das auf einen D1 mini drauf? Ich probier da jetzt schon stundenlang rum, aber im WLAN taucht MyAP einfach nicht auf. Mit Tasmota funktioniert es einwandfrei... Ich hab zuerst versucht, die .bin aus dem firmware Ordner mit ESPEasy Flasher einzeln aufzuspielen, dann hab ichs über Linux Mint und ESPtool erfolglos versucht, jetzt hab ich noch mit dem Download Tool von Espressif beide .bins versucht an jeweils 0x0... und 0x1... zu flashen. Auf drei Arten versucht den Flash zu erasen, mit GPIO0 auf low geflasht, zig mal resetted, aber ich bekomm einfach nie den "MyAP" angezeigt. Kann mir da jemand weiterhelfen?

[@carcelayani7430]

Hi, good project. How can I add other commands like 'on','off', 'toggle', and 'blink', Thanks.

[@martinger327]

In the scripting language you can define actions on the reception of am MQTT topic message. If you look into "script.sonoff", there it understands the command topic and depending on the contents ('on','off', 'toggle', and 'blink') it does the local action with the switch. If you mean this, just connect to the ESP with an MQTT client (e.g. mqtt-spy (Java) or MQTT Lens (Chrome plugin)) and publish a command on the command topic. On do you mean a direct command on the command line? This can only be done in the code (in console_handle_command() in user_main.c). Can be done, but this is not the main purpose.

[@carcelayani7430]

Thank you Martin. I have an other question, how can I use use your software over Websockets?. Thanks.

[@martinger327]

No, Websockets are currently not supportet.

[@RTmadnesstoo]

@@martinger327 Have you looked at the Shelly1 units? They can be installed in existing switch or receptacle boxes.

[@MrBobWareham]

A shame this has not gone further I see no other reference to running MQTT on an esp everybody wants to use a Raspberry I wish someone would do more on the subject 11-06-2021

[@dhavalpatel4208]

how can we connect this to cloud

[@martinger327]

You can additionally speak MQTT as a client to a cloud broker.

[@muhammedserter3214]

Hi. I need to run ESP8266 as a Broker. There are a few places in uMQTTBroker.h library that I hang out with. 1) How to connect a broker with ESP8266 2) How do we assign a username and password to this broker when we run as ESP8266 Broker?

[@martinger327]

I assume you are using the Arduino lib in your own program from: github.com/martin-ger/uMQTTBroker . Let me try to answer your questions: 1) You can connect from a remote node using any MQTT 3.1 or 3.1.1 client, like the pubsub lib, esp_mqtt or even a non-ESP MQTT implementation. Locally you can use the functions provided in uMQTTBroker.h like shown in the example: github.com/martin-ger/uMQTTBroker/blob/master/examples/uMQTTBrokerSample/uMQTTBrokerSample.ino. 2) For checking the user credentials you can also use a callback. Find sample code here:github.com/martin-ger/esp_mqtt/issues/10

[@muhammedserter3214]

I will start from ESP8266 How do I determine the MQTT Broker's user name and password? I have not found anything like this in the uMQTTBrokerSample and github sites. If you can actually post your email address, I can ask you better from there [e-mail]

[@madhusudhang8254]

connect to esp8266computer's USB ports, everything working fine. But, if I connect esp8266 to separate charger that has USB port, then esp 8266not running code

[@martinger327]

Most probably a power issue. Try another charger.

[@madhusudhang8254]

power supply and USB cable is working good v are giving 5v 2a power supply to esp8266

[@martinger327]

It does not rely on any USB functionality and is know to work stand-alone. If it works on USB and doesn't on a pure power supply, I am still pretty sure it is a power issue.

[@madhusudhang8254]

I think it's taking program support From the Computer v tested power supply in multimeter it is working good v are getting out put 5v it can supply max 2Amp same power supply it's working with Raspberry Pi zero

[@madhusudhang8254]

I will send program if its possible plz check and tell weather any mistake in program

[@NDR008]

Would it work and would it work any better on ESP32?

[@martinger327]

More memory would help a lot. However, for the ESP32 it would require a port to FreeRTOS and the socket interface.

[@NDR008]

@@martinger327 ok. Hmmm. I used all my esp8266... And bought 2 ESP32. I was really hoping to cut out the raspberry as a broker. I want a more robust system like yours. I already started changing over to mqtt to 433mhz by esp8266. How to compile your code? I am not sure what tool / IDE I have to use.

[@NDR008]

@@martinger327 wait. I can put this on sonoff???? I have one not used yet.

[@NDR008]

@@martinger327 icircuit.net/esp32-introduction-freertos/1297 Isn't freertos already available? :)

[@martinger327]

On the ESP8266 I used the esp-open-sdk. On the ESP32 I would definitly start with the esp-idf.

[@dhavalpatel4208]

how to interconnect esp8266 with each each sir ???

[@martinger327]

How to connect the ESPs? Either via an external AP/WiFi network or via the SoftAP on the broker.

[@dhavalpatel4208]

I m a beginner in this and I m confuse that how to flash it which software is to use ??? Arduino ?? Atom ?? Which one

[@martinger327]

github.com/martin-ger/esp_wifi_repeater#building-and-flashing On Windows you can flash it using the "ESP8266 Download Tool" available at espressif.com/en/support/download/other-tools. Download the two files 0x00000.bin and 0x10000.bin from the firmware directory.

[@seledwin]

I would suggest you to use Arduino since you are a beginner it will be very easy . no need of flashing thins :)

[@dhavalpatel4208]

can i use google iot with this ?

[@olafk8232]

Has anyone used this successfully on a Shelly 1?

[@martinger327]

I am not aware of that.

[@mikerussell3640]

Martin, Great work! Some would say an ESP8266 MQTT broker is not practical and yet here is a broker plus more! This is true full utilization of an ESP8266 when a limited number of MQTT clients are planned. I am thinking about placing your broker code plus my existing client/control code into this ESP8266 RGB LED controller - tinkerman.cat/closer-look-h801-led-wifi-controller/#lightbox-gallery-kUiZ/4/. Actually I likely will switch also to your scripting/control - looks nice. Is flash usage with control and scripting such that OTA update support could be added? The H801 LED controller has an 8Mbit flash so code plus file system

[@martinger327]

Thank you! OTA provisioning of the complete firmware is currently not supported. The fw uses about 280KB of code and 12KB of flash mem for saving the status. Do you know any good sample for OTA support with the SDK? Script code, however, can be loaded OTA. This is sufficient in most cases, as this covers the complete appication logic and local configuration.

[@mikerussell3640]

There are many examples for Arduino environment OTA but I didn't find any complete ones for the SDK. With IoT evolving I could see OTA being very useful, especially ~years after installation when some majority standard may emerge to migrate to (assuming 802.11n and the driven hardware are still used / of value). Of course security in OTA is a concern. I will look more at adding optional OTA (leverage ArduinoOTA.cpp?) and post an issue/recommended enhancement on your project's github if/when I make progress. SDK environment is new for me and many unknowns. For control I would use scripting but was hoping to "standardize" via mqtt json and parsing that via scripting doesn't look practical. There are some RGB implementations with gamma correction (array indexed) and that looks tough/not possible? with current scripting. Still, mqtt broker and client on ESP8266 - awesome!

[@martinger327]

If you just need the broker with Arduino app code and OTA you migth consider the "quick-and-dirty" Arduino integration at: github.com/martin-ger/esp_mqtt#using-the-esp_umqtt_broker-in-an-arduino-project Actually, i am currently working on a simple JSON-parsing feature for the scripting language, but, of course, there are limits concerning the complexity of the task. When the scripting language gets as complicated as a real language, you better use that, as it is faster and better designed than my ad-hoc approach (that initially was only intended to define MQTT bridging rules). Also I will use this SW in a course at my university. Perhaps we get an OTA feature as a result of the project work...

[@gsge]

Little more from my serial log data: MQTT_ClientCon_recv_cb(): 2 bytes of data received MQTT: TCP: data received 2 bytes (State: 17) MQTT: total_len: 2 MQTT: message_type: 12 MQTT: receive MQTT_MSG_TYPE_PINGREQ MQTT: Server task activated - state 17 MQTT: Sending, type: 13, id: 0000 MQTT_ClientCon_sent_cb(): Data sent MQTT_ClientCon_recv_cb(): 26 bytes of data received MQTT: TCP: data received 26 bytes (State: 17) MQTT: total_len: 26 MQTT: message_type: 3 MQTT: Publish received, message_len: 26 MQTT: Published topic "\GREENHOUSE\" MQTT: Matches to: MQTT: Client: Office Topic: "#" QoS: 0 MQTT: Next message to client: Office MQTT: Server task activated - state 17 MQTT: Sending, type: 3, id: 0000 MQTT_ClientCon_sent_cb(): Data sent WD : Uptime 21 ConnectFailures 20 FreeMem 17912 UDP : Send Sysinfo message EVENT: Rules#Timer=1 ACT : Publish GREENHOUSE/IP,192.168.0.70 ACT : timerSet,1,30 EVENT: Processing time:266 milliSeconds EVENT: Clock#Time=Mon,22:22 EVENT: Processing time:260 milliSeconds WD : Uptime 21 ConnectFailures 20 FreeMem 17912 UDP : Send Sysinfo message EVENT: Rules#Timer=1 ACT : Publish GREENHOUSE/IP,192.168.0.70 ACT : timerSet,1,30 EVENT: Processing time:266 milliSeconds MQTT_ClientCon_recv_cb(): 2 bytes of data received MQTT: TCP: data received 2 bytes (State: 17) MQTT: total_len: 2 MQTT: message_type: 12 MQTT: receive MQTT_MSG_TYPE_PINGREQ MQTT: Server task activated - state 17 MQTT: Sending, type: 13, id: 0000

[@thedudemru]

Well I'm a noob at this can someone help me ?

[@namilo8863]

how to change port 1883 and (change username + password) ? Thanh you !

[@martinger327]

The console is available either via the serial port at 115200 baud or via tcp port 7777 (e.g. "telnet 192.168.4.1 7777" from a connected STA). Then: set broker_user unsername: sets the username for authentication of MQTT clients ("none" if no auth, default) set broker_password password: sets the password for authentication of MQTT clients ("none" if empty, default) set broker_port portno: sets the port number where the broker listens (default: 1883)

[@namilo8863]

@@martinger327 And how can i turn off AP ? Thanh you.

[@martinger327]

@@namilo8863 set ap_on [0|1]: selects, whether the soft-AP is disabled (ap_on=0) or enabled (ap_on=1, default)

[@namilo8863]

@@martinger327 Thanh you ^ ^

[@namilo8863]

@@martinger327 mDNS: STA interface but I can't find mdns when I use ping mqtt.local. How to find ip by using ping name mdns ?

[@AhmetTasdemirDJLuds]

Static ip with Mqtt server... Local network is not real internet...

[@martinger327]

Can use static Ip or MDNS, also DNS if clients are in the ESPs AP network.