I've been reading a lot lately since i am diving deeper and deeper into the darkness of Home Automation.
I do have some experience on the mc-programming (mainly arduino and esps).
I am currently using node-red as a translator between homematic, mqtt, knx and influxdb.
My harware config is this:
HomeMatic CCU IP .180
KNX Multicast Gateway .25
Mosquitto in a Docker Container on a QNAP .10:1883
Node-Red in a Docker Container on QNAP with direct LAN .29:1880
InfluxDB in a Docker Container on QNAP with direct LAN .28
Grafana in a Docker Container on QNAP with direct LAN .30:3000
Several MQTT Clients on ESP8266 via WiFi
This setup used to work flawlessly. Since i had to do a restart and update of the QNAP Firmware, everything is still running flawlessly EXCEPT the MQTT Connection between Node-Red and mosquitto.
What is working?
I can access the Mosquitto Broker via MQTT Explorer from my Windows Machine.
In the Mosquitto log, i can see the ESP Devices connect and disconnect and publish messages (which i also see in the MQTT Explorer)
I can access Grafana, that displays the InfluxDB values.
Node-Red apparently still stores the Homematic Values into InfluxDB.
What is not working?
All MQTT Nodes within Node-Red do not connect, they remain yellow.
What did i try?
Re-create the Mosquitto Docker with or without mounted folders for log/lib
Re-create Node-Red, ofc with mounted folders so my flows do not get lost
Delete the MQTT config node and re-configuring it and all mqtt-nodes so there is just one Mosquitto client on node-red running.
Here is some random part of the mosquitto log:
1610043134: New client connected from 192.168.178.244 as ESP8266Client-5953 (c1, k15). 1610043134: New connection from 192.168.178.241 on port 1883. 1610043134: New client connected from 192.168.178.241 as ESP8266Client-fde (c1, k15). 1610043145: New connection from 192.168.178.29 on port 1883. 1610043145: New client connected from 192.168.178.29 as mqtt_12f965e6.36d25a (c1, k15). 1610043145: Socket error on client mqtt_12f965e6.36d25a, disconnecting.
The most similar problem thread here i could find is This one, althoug it seems that the issue over there were multiple mqtt instances within node-red.
Does anyone have any idea what could be the issue here?