[solved] Mosquitto_pub Node Red


i have a Raspberry Pi with Node Red, nothing else till now.

i have a second Raspberry Pi with a 433 Dongel and installed like this

to collect and view it on the Monitor works!

then installed mosquitto-clients
sudo apt install -y mosquitto-clients

and done this command
rtl_433 -F json -M utc | mosquitto_pub -t home/rtl_433 -l
i found out the Port 1883 is closed on the this device. but found no config file

and yes sorry basicly it is not a Node Red Proble :wink:
but the next step will be the connection

have a nice day

Have you installed mosquitto? That is the package that provides the mosquitto broker, mosquitto-clients gives you the command line client for sub and pub.

@Colin thanks for your feedback.
on the Raspi where Node Red is or on the place where the data are?
on the 433 Raspi i have only installed a mosquitto client

On whichever device you want to run the broker. Often that will be the device running node red but it is up to you where you run it.
I suspect you don't know a lot about mqtt, if so I suggest you read this set of tutorials.

@Colin it is true i have to read more, it also a bit confusing with all the systems working together or sometimes not :wink:

So now it is a Node Red Question

from a Raspberr Pi wiht a 433 Dongel i got message like this:
iot12-rpi3b-gw-433 : msg.payload : Object


time: "2020-12-16 21:31:37"
brand: "OS"
model: "Oregon-THGR122N"
id: 126
channel: 2
battery_ok: 1
temperature_C: 6.2
humidity: 77

the fist question how offen will a ID change?
The Model i have two time but on different Chanel, should a Switch be used to splitt the data?

have a nice day

Since this now appears to be a question about the oregon device and the data it provides then it would probably be better to start a new thread with a title describing the problem, then possibly someone who knows that device will be able to help.

In the meantime though, as to whether to split the messages down two paths using a switch node that depends on what you want to do. If possible it is better to make one flow that will cope with both channels and use the id to determine what to do, but that depends on what you want to do with the data.

@Colin thanks
changed the Forum

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.