Last Christmas I used HA’s Node-RED plugin to start/stop my light show on FPP via HA’s Mosquitto, and likewise received status messages from FPP.
This summer I noticed that the MQTT nodes in NR showed “Connecting…” not “Connected.” I don’t know how, but I got that working. I recently fired up the FPP, which says MQTT is disconnected. The authentication is identical to that used by NR. Using MQTT Explorer on my local computer, connecting to the broker also fails. Bottom line: Of the three clients, the only one that connects to the broker is the one hosted by the same machine.
I can only conclude that an update since last winter broke the broker, at least for external clients. I hope someone with more knowledge or experience than ChatGPT can enlighten me on what to do.
All is on the same subnet. I’m using the same credentials on all three clients I mentioned, and am definitely using the correct IP & port. No secured connection, and yes, Mosquitto is running. The MQTT log shows clients trying to connect, but then disconnected, not authorised (…which I should have mentioned in my OP.)
Now that I’ve been troubleshooting, NR now can’t connect either. I really need to have a better understanding of what’s blocking the (or missing) authorization.
I’ll add that I downloaded the latest HA OS and installed it in a fresh VM, restoring a backup of HA but not any add-ons. Then I manually installed Mosquitto, which also doesn’t respond to MQTT Explorer.
actually, i seem to have some problems suddenly after upgrading to latest HA aswell - not sure if it was HA OS or HA core that caused it. Trying to debug
Ever put something down and look for days until you finally find it and wonder why the hell you didn’t see it earlier? Apparently I tightened the mqtt password when I was asleep, so I remembered the wrong password.
Duh. That’s one step of faulty troubleshooting above forgetting to restart.