Gina

I have another problem.  Can't upload sketch to ESP32.  Tried cold rebooting Mint box but still the same.

Quote

Arduino: 1.8.10 (Linux), Board: "ESP32 Dev Module, Disabled, Default 4MB with spiffs (1.2MB APP/1.5MB SPIFFS), 240MHz (WiFi/BT), QIO, 80MHz, 4MB (32Mb), 115200, None"

Sketch uses 702242 bytes (53%) of program storage space. Maximum is 1310720 bytes.
Global variables use 40120 bytes (12%) of dynamic memory, leaving 287560 bytes for local variables. Maximum is 327680 bytes.
python /home/gina/.arduino15/packages/esp32/tools/esptool_py/2.6.1/esptool.py --chip esp32 --port /dev/ttyS0 --baud 115200 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0xe000 /home/gina/.arduino15/packages/esp32/hardware/esp32/1.0.4/tools/partitions/boot_app0.bin 0x1000 /home/gina/.arduino15/packages/esp32/hardware/esp32/1.0.4/tools/sdk/bin/bootloader_qio_80m.bin 0x10000 /tmp/arduino_build_240309/MQTT_test_ESP32_and_BME280.ino.bin 0x8000 /tmp/arduino_build_240309/MQTT_test_ESP32_and_BME280.ino.partitions.bin
esptool.py v2.6
Serial port /dev/ttyS0
Connecting........_____....._____....._____....._____....._____....._____.....____An error occurred while uploading the sketch
_

A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

edit - Yes, I did press the BOOT button!

Tried it with 2 ESP32s.

HELP - please.

Thanks for the warning.  I never really trust anything I haven't had experience of and found trustworthy.  I try to go for fail-safe and/or redundancy where it's important.  I also tend to over-engineer.

Nearly all my MQTT system deals with just useful information and you can see when it doesn't arrive.  The only control I'm using it for is opening and closing the obsy roof and I have status feedback to check the command I've sent has worked.  Also, I can see the obsy from my living room windows.  (With lantern at night.)  The status will return various messages depending on the state of the roof.

• Opening
• Open
• Closing
• Closed
• Stopped
• Fault

All these fit in my standard 8 character message strings.

Quote

You will need to handle mqtt disconnect messages and automatically reconnect.

Yes, I do that.

The indoor ESP32 is working properly again now.  Wonder if there was some problem being caused by the obsy unit.  Hope it doesn't mean the RPi Zero W with broker, Node-RED and Dashboard wasn't being overloaded!!  OTOH the outside unit was working fine.

Time for a cuppa...

I now have it plugged into USB on my Mint box and running the Serial Monitor.  It connects briefly every so often.  Anyone any idea of what might have gone wrong?  The test LED doesn't come on even with the Dashboard switch on.  It sends data though.

Problem - the indoor ESP32 unit has stopped connecting to MQTT.

Interesting link but how do you use it - no instructions, just a huge wadge of code.

I have the outside/obsy sensor unit working with MQTT.  Just one little problem, looks like the DHT22 has come unplugged.  ATM it's just connected with jumper wires.  Think I'll bring it indoors and connect it properly!

Gradually adding bits and bobs...  Think I'm nearly ready to set up the outside and observatory sensor ESP32 unit for use with MQTT.

I've set the Pressure to show up to 3 hours of data, the Temperature covers the last hour - might change that for a longer period.

I'm gradually getting to grips with Node-RED and the Dashboard but so far I haven't found a way of setting the order or position of widgets in the dashboard.  This is just testing ATM.

All this is rather premature in one way - I haven't finished the hardware yet!  OTOH I like to see that there's a way through to the end of a project, if possible, though there are times when I make it up as I go along!

Well I said I had a lot to learn!  Just found that the gauge widget already there has a "compass" variation.

QoS 2 should virtually guarantee that a message gets through (providing everything is working, or course) though nothing is infallible.  Where i'm relying on control to keep expensive equipment safe (such as ROR) I shall keep control local as far as possible.  eg. with the ROR control, the rain detector will connect directly to the ESP32 controlling the motor - not rely on MQTT.

I plan to go with the Node-RED Dashboard for the time being - "pretty" can come later if I feel like bothering.  One thing I would like in a dashboard is a wind rose or a 360 degree pointer to show wind direction.  I do have plans for a mechanical wall display for weather conditions though to build eventually.  Showing wind direction in compass points will do for a start - ATM I have nothing for wind display and as they say "anything is better than nothing" 😁

Conclusions so far :-

1. MQTT seems very good
2. Node-RED also seems well worthwhile
3. Node-RED Dashboard should work for control but has a crude display and too few "widgets" to display data

This is showing lots of promise 👍  Lots to learn though but making progress.

This shows ROR control.  3 buttons.

And this is a rough Dashboard.  I shall separate it into groups or tabs.  The ROR control will be on a different ESP32 with different name.  There will also be roof status indicators.

Found the problem.  "Pass through msg if payload matches new state: " was set - unset it and the switch in Dashboard now works.  This lets the switch icon show state of output.  It also lets the message through and the LED lights up!

Ah - that's a bit different!

I've noticed that Node-RED doesn't create MQTT topics, these are created in the sketch running on the client hardware.  I gather Node-RED just sets up links.

Could this be the problem - the output switch has no topic?  Or does the connection (link) do that?  I think I need to read up on Node-RED.

I'm trying to use the Node-RED web interface to set other controls and see what happens.  Previously I've just been following the tutorial bit by bit - sort of "blind".  The whole point of it is to be able to set up topics etc. and link clients so I shall need to see how it works if I'm to use it in the future to expand the network,  once learned it should be easier and quicker than writing code I would think.

Problem is I can't even operate the switch in the Dashboard!

I've been following THIS tutorial.  I haven't seen the NodeRed -> ESP MQTT 'ON / OFF' message in the MQTT Explorer.  I feel the problem has to be in the Node-RED Dashboard as the switch control output won't turn on.