9. Troubleshooting
For testing I always use Lolin controllers as there is detailed documentation available for these devices.
- ESP8266 - Lolin/Wemos D1 mini, 4MB
- ESP8266 - Lolin/Wemos D1 mini Pro, 16MB
- ESP32 - Lolin D32
- ESP32 - Lolin D32 PRO
Tested with Mosquitto https://mosquitto.org/
on Raspberry Pi with Mosquitto 1.5.7 and on Windows 10 x64 with Mosquitto 2.0.18a
Should work with any MQTT broker and on any operating system.
-
The MQTT broker should run in the same network segment as your Roc-MQTT-Display controller and your Rocrail or Node-RED.
The IP-Adress of the MQTT broker is typically the IP-Adress of the device it's running on, e.g. a Raspberry Pi. Do not use "localhost" or 127.0.0.1 as these are local adresses that cannot be reached over the network. -
Leave the port in all configurations at 1883.
-
To communicate with the MQTT broker from other devices you need some additional settings after the setup of Mosquitto. In the installation folder (e.g. C:\Program Files\mosquitto) the file mosquitto.conf must contain these two lines without # at the beginning:
listener 1883
allow_anonymous true -
Restart the PC/Raspberry Pi after these steps.
-
Check if the Broker Service (Dienst) is set to starttype automatic.
-
Make sure your desktop firewall or anti virus program allows network traffic on TCP/UDP port 1883 inbound and outbound.
-
If your WLAN router is a AVM Fritzbox please enable this option in the WLAN / Security configuration.
Allowing wireless devices to communicate
Click "Wi-Fi" ("Wireless") in the FRITZ!Box user interface.
Click "Security" in the "Wi-Fi" ("Wireless") menu.
Enable the option "Active wireless devices may communicate with each other" in the section "Additional Security Settings".
Click "Apply" to save the settings.
Routers from other vendors may have a similar option, please check your manual in case your ESP device cannot connect with the MQTT broker.