ESP32: MQTT Setup and Testing with Raspberry Pi

Поділитися
Вставка
  • Опубліковано 27 січ 2025

КОМЕНТАРІ • 16

  • @the1gofer
    @the1gofer 3 роки тому +3

    Would be nice if you provided links to the tutorials you mentioned.

  • @alin-pe4bp
    @alin-pe4bp 3 роки тому +2

    hello great video, i'm currently trying to do the same except i need to send an image. is it possible? do you have any advice, tutorial, source code or anything that could help ?

  • @svenverdonck3211
    @svenverdonck3211 Рік тому +1

    I try to let my esp32 comunicate with my pi to than on my pi run a flask website to show my esp32 topics i litarly tried everything but im not getting there

    • @roshan2017
      @roshan2017 9 місяців тому

      same here, if you found a solution please share

  • @beezeruk1
    @beezeruk1 2 роки тому

    Len Beasley. Sorry about the first one. I am trying to use the Rasberry Pi to connect to a number of ESP8622 chips and display the data on the Rasbbery Pi monitor. What software would I need on the monitor? Could it be in the form of spreadsheet with up to ten different va;ues.

  • @mr.challenge8157
    @mr.challenge8157 2 роки тому +3

    How can I find my MQTT_broker IP address on my raspberry PI?

  • @rickengman
    @rickengman 3 роки тому

    Great Video, I've got a question though...When you set up your Sub and Pub messages in mosquitto do you need to give each device (ESP32) it's own unique name? I want to use the ESP32's to deliver data like Water and Fuel Tank Levels wirelessly back to the Rpi so I can then use the data in a Dashboard. So does the ESP32 for the Fuel tank sensor need it's own Sub and Pub called Fuel Tank 1 and then 2 or Water tank 1 and 2 etc... I'm not a Software guy...but I'm trying to set up my Sailboat with Rpi's as the system backbone.

    • @BaldGuyDIY
      @BaldGuyDIY  3 роки тому +1

      You do need to set a unique device name in the ESP32 code, but that’s just for the sake of the broker allowing the device to connect. The messages and topics are not to device names, so you control what happens exclusively by the topic and message handling on the devices. Depending on how you’d like it to work, all devices could publish to the same topic with different messages, or each device could be separated to its own topic. I use both methods depending on circumstance.
      For what you’ve described, it’s probably easier to set a different topic for each devices readings, so that the message you send is only the reading and further encoding/decoding isn’t required. If all use the same topic, the message would need to be a combination of the device and the reading, which you’d have to adjust for on the receiving side to break the message into the device and readings. Hope that helps, sounds like a good project!

    • @rickengman
      @rickengman 3 роки тому

      @@BaldGuyDIY Thanks a bunch...

  • @MaksimNabiullinSeo
    @MaksimNabiullinSeo 3 роки тому +1

    what about source code for this project ?

    • @BaldGuyDIY
      @BaldGuyDIY  3 роки тому

      Thanks for watching. I did refer to two websites in the video where you can get the sample code. If you want the specific code I used in the video, send me an email to brandon@baldguydiy.com and I can send it to you.

  • @samyrebei5191
    @samyrebei5191 2 роки тому

    hello please i want the python code

  • @beezeruk1
    @beezeruk1 2 роки тому

    Len Beasley

  • @paulomalheiros4436
    @paulomalheiros4436 2 роки тому

    Thanks for eveything but for me in mosquitto_sub -h localhost -t "my_topic" show for me the message "connection refused"

    • @mariuspedersen1650
      @mariuspedersen1650 2 роки тому

      same with me! i can't connect to the rpi? found a solution yet?