Pi 3B as WiFi server, NodeMCU as client

[JeyDe]

Hello everyone,

im new to the Pi scene and I have a project i currently work on.

I want to messure 2 temperatures and send them to Pi 3B via WiFi. My sensoring Programm on a NodeMCU works fine so i just need to set up the connection and find a way to send the data over to the Pi. My research wasnt as fruitful as I hoped it to be as most projects I found are several years old and have to use a WiFi stick to work properly.

Project:
I measure 2 temps with sensors connected to the NodeMCU. The MCU is programmed with ArduinoIDE and I have the ESP8266WiFi.h library included.

I want to use a Raspberry Pi 3B as server and as a tool to directly show the data in realtime with display.

If you have any ideas or a link where i can find a working example that would help a lot!

Thanks and have a nice day!
JeyDe

Ps: no native english speaker so I apologise for every mistake I made

[JeyDe]

I forgot to say one thing: the system is not connected to any LAN and will not be connected to the internet.

[mattmiller]

Typical steps would be
Setup Pi as a WiFi access point so that the nodeMCUs can connect to it
Run an MQTT broker on the Pi
Send data as MQTT messages from nodeMCUs to Pi

Then you need method to display the data
One method (out of many) is to run Node-RED on the Pi to read in the MQTT data and use dashboards nodes to display the data on a webpage


quite a few steps needed - great summer holidays project

[JeyDe]

Thanks for the answer! That MQTT idea seems to be a good one! I'll Keep you updated

[V8Diego]

Hello!
I have my raspberry pi configured as an access point.
I have connected a nodeMCU to the broker without problem, however other two nodeMCU that I have connect without problems to the network generated by the raspberry pi, but they are not able to connect to the broker ever.
I have tried to connect one at a time, but there is only one that manages to connect (always the same) and the others do not.
Do you know what could be happening?

[mattmiller]

try giving them different client ids and see if that solves the problem