I would start by installing MQTTExplorer on my PC and connecting the broker, and checking what that sees. If it sees the same as node-red then the messages are not getting to the broker.
Which MQTT broker are you using? Is it running on the pi?
Mosquitto is good, the problem will not be with mosquitto.
Try MQTTExplorer. It is a useful tool to have anyway, often one wants to know what topics things are publishing on.
I would guess your sending loop on the ESP is the problem - you have probably not completed filling the messages before you exit the loop and send out the messages
Also there is a limited buffer on the ESP (i assume you are using Ardunio IDE for this ?) are you sure you are not overfilling it ?
Lastly have you looked at the excellent Tasmota code ? even if you do not use their precompiled code you can use the source code as the basis for this - check out their sensors stream
void readLight() {
int sensorLight = analogRead(sensorLight_PIN);
client.publish("vikend/weather_station/sensors/light", String(sensorLight), true);
delay(DELAY_AFTER_PUBLISH); // ADDED a delay hoping that would help but it doesnt
}
void readLux() {
sensorLightLux.begin();
int sensorLux = sensorLightLux.GetLightIntensity();
client.publish("vikend/weather_station/sensors/lux", String(sensorLux), true);
delay(DELAY_AFTER_PUBLISH);
}
etc
At the end there is deepsleep call:
void deepSleep() {
...some other code
delay(500); // ADDED a delay hoping that would help but it doesnt
esp_deep_sleep_start();
}
MQTTExplorer:
Each square represents random cycles(5min) of data that i get. Most of the time i get all data. But sometimes i get only red, blue or green.
After disabling deepsleep and after around 30 x 1min cycles i did get everytime my all 9 sensor data without skipping.
(example for last client-publish data voltage-raw; 1min cycles)
So question is why with deepsleep enabled skips randomly?
Should i put some code before it goes to deepsleep? Some sort of cleaning, disabling connection.. not good at this, any suggestion?
My procedure to go to deep sleep in something like this ...
With DeepSleep enabled after 30 x 1min cycles i got 9 skips on voltage-raw sensor which is the last in the series that i publish. 30% loss which is bad.
Other sensors have different skip numbers.
You have to remember that after a deep sleep, you need time to wake, reconnect to WiFi and then reconnect to MQTT. My guess is that you are not getting enough time to do all of that before you try your next sleep.
Honestly, if you don't have much experience in programming microprocessors, it is likely that you would be better off using a pre-built firmware rather than rolling your own.
My personal choice is ESPHome which gives a nice balance between robustness, being able to simply configure all of your sensors, outputs, timings and being able to drop into C++ code should you need something that the project hasn't already covered (though they have virtually all of the common sensors and controls already pre-configured). It also has the advantage that you can break your config up into reusable parts which is great if, like me, you have a lot of different ESP devices of different types.
If you do want to roll your own, I would advise you to get the basics right without dealing with deep sleep (which is a whole subject area in itself) and then go do some research on the best way to use deep sleep with MQTT.
I have created 1 object with multiple sensors readings and only 1 client.publish instead of having 9 seperated sensors readings / 9 client.publish events.
Results are the same. Skipping if using deepsleep. Without deepsleep it works normally
