[Claude Favreau]

Hi,

I got the same issue and I don’t knwow why. I just upgraded the firmware of the conduit to 1.3.3.`
19:5:41:882|INFO|Parsing 1 rx packets
19:5:41:883|WARNING|Recv'd frame failed CRC check
19:5:44:512|TRACE|Parse downstream message 12 bytes
19:5:44:513|TRACE|Gateway 00:80:00:00:00:00:bf:b5 seen IP address 127.0.0.1:50143
19:5:54:522|TRACE|Parse downstream message 12 bytes
`

I already tried to delete and add again the node. By the past I already received data from this node. Someone has an idea how to solve it or what is the origin of this issue?

• This reply was modified 7 years, 3 months ago by Claude Favreau.
• This reply was modified 7 years, 3 months ago by Claude Favreau.

[Claude Favreau]

In addition, if I use the username/password, it won’t be really secure my connection because the username/password will be sent in clear at the distant broker?

Regards

[Claude Favreau]

I want to secure connection from the Conduit to another MQTT server with a certificate. Do you know if the Conduit will support it soon because it’s already offering by the last version of Node-Red?

I am not the better in security but usersame and password over TLS is a good alternative to certificate based authentification?

Regards

[Claude Favreau]

Hi,

Thanks, it helps me in what I want to do.

Regards

[Claude Favreau]

Hi,

Thanks very much. I have another question linked to this post. Do you know how to create a custom Node-RED app ? Because if I overwrite or I add a custom node for MQTT, I would like to have the possibility to deploy it on severals gateway easily.

Regards

[Claude Favreau]

Hi,

Yes I am agree with you but I wouldn’t to have many charge on gateways. Therefore, to avoid this problem I need to subscribe a specific topic with the serial number for each gateway. For an input mqtt node we canot give a topic like you told me.

I think the way is to have a custom node if I want to insert the serial number from each gateway dynamically. But I would like to be sure.

Regards

[Author]

Posts