Node-Red connection issues with MQTT

[Xenicle]

Hello everyone,

I have a connection problem from the Node-RED integration to the MQTT integration.

My MQTT topics in Node-RED are not connecting:

I can connect to Gladys’ MQTT with MQTTX without any problem.

An example of a topic on Node-RED:

The MQTT broker config in Node-RED:

I may be mistaken but I noticed that in Security the password length is not the same after deployment:

Before:

After deployment:

Is that the problem?

[Xenicle]

For those who might be interested, here’s what the flow looks like:

For more info, feel free to ask!

[Terdious]

Hi @Xenicle !

@Xenicle

I may be wrong but I noticed that in Security the password length is not the same after deployment:

[quote=« Xenicle, post:1, topic:8699 »]
Is the problem there? :confused

[Xenicle]

I tried with the MQTT V3.1.1 protocol:

And, after deployment, still no connection…

[Terdious]

If in doubt about the password, can you try to re-save the password by following:

Problème AutoFill AutoComplete des navigateurs

Il arrive que les navigateurs intercepte les données entrées (mot de passe du container mqtt entre autre) et les remplace à la volée et sans prévenir par celles qu’il a en mémoire quand on essaie de sauvegarder ce qui fait que l’on croit que quelque chose ne marches pas alors que c’est les données stockées qui faussent l’authentification. Voici comment désactiver les informations de saisie automatique dans certains navigateurs pour éviter que ces informations ne soient enregistrées ou utilisées…

[Xenicle]

I tried disabling that in Brave, but also in Firefox with no saved passwords and the same login problem…

[Xenicle]

I can even see that nice try at saving the correct password.

[Xenicle]

Is it normal that in the Docker bridge there is no eclipse-mosquitto:

docker network inspect bridge
"...
Containers": {
            "07047a22b4ce0d70099c959d957516813b41c7d726431c16f7e0104af363c924": {
                "Name": "gladys-node-red",
                "EndpointID": "6f225535c88d71a8f3e81eb2d09e111e0d409b532840012ecbbf0a9e540d268d",
                "MacAddress": "02:42:ac:11:00:03",
                "IPv4Address": "172.17.0.3/16",
                "IPv6Address": ""
            },
            "d5ee1ba9aad7331016b95a42c8d9f7d7e3639bdf257d1aaed8ec20f54411bbc0": {
                "Name": "watchtower",
                "EndpointID": "e7ebe4ca4c4ac1945884afd65f0598517b0e25dc1c12678c2ca6e6383528bec2",
                "MacAddress": "02:42:ac:11:00:02",
                "IPv4Address": "172.17.0.2/16",
                "IPv6Address": ""
            }
        },
...

And that eclipse-mosquitto has no IP?

docker inspect eclipse-mosquitto
"...
Networks": {
                "host": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "c52c79bdb90384fdc2b909c0d7db9432c5ae7cd45bcaf68ecb70122e5cd783cf",
                    "EndpointID": "b16e687927eff9372ac097d230233212444024c23a3a7b04e8f40aaae3878c58",
                    "Gateway": "",
                    "IPAddress": "",
                    "IPPrefixLen": 0,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "",
                    "DriverOpts": null
                }
            }
...

[Xenicle]

With the URL on the Pi’s external IP it works!!!

[Xenicle]

What can I do to fix this mosquito that’s going bbzzzzzzzzzzzz ?

[Terdious]

Ah, in that case I can’t help you, I don’t use eclipse-mosquitto but a mosquitto installed next to Gladys on a different Pi^^. Same for node-red!!

Strange indeed…

@Xenicle

With the URL on the Pi’s external IP it works!!!

Well, that’s already something

[Xenicle]

Yes that’s already something, in the meantime thanks for your help!

[cce66]

@Xenicle
Apparently it can no longer resolve the localhost IP 127.0.0.1
This can happen after a Node-RED update
Export your flows, stop Node-RED, delete the flows.json file, restart Node-RED and re-import your flows

[Xenicle]

Thanks @cce66, I tried that solution and it didn’t change anything: still no connection on localhost…

(on the other hand the flows.json file wasn’t recreated afterwards…)

[cce66]

@cce66

and reimport your flows

did you reimport it?

[Xenicle]

Yes, I did reimport my flow via the Node-RED interface…

You’d think the file was recreated elsewhere ^^

[cce66]

Did you deploy? Did you restart the streams?

[Xenicle]

Yes, several times…

But I must have broken something with Docker a few weeks ago…

I think I’ll take advantage of Gladys Plus to reinstall the Pi!

[cce66]

Back up your flows to your email

Mini-tuto Backup par email des flows Node-red

Un mini-tuto pour envoyer par mail les flows et package (palette) de node-red chaque jour à 00h00 les node-modules ne sont pas backuper mais le json package contient la liste des nodes et la recharge Importer le node « node-red-node-email » en cliquant sur « Gérer la palette » [image] Cliquez sur l’onglet latéral « Palette » Entrez le nom du node « node-red-node-email » et cliquez sur « Installer » [image] Importer le flow ci-dessous dans node-red en cliquant sur « Importer » [image] [ …

But it’s surprising that

[Xenicle]

Thanks for the tutorial on backing up the flows!

Reinstallation is in progress…