Forum
No internet connection
  1. Home
  2. WISE-PaaS/DB services

Node-Red, MQTT connection settings[WISE-PaaS/EnSaaS DB Service]

By @Yong
    2020-08-23 08:45:08.958Z

    Good evening, I'm using WISE-6610 as sensor gateway to receive data from WISE-4610 sensor node. After received the data from the sensor node, i'm trying to use Node-red to establish a MQTT connection by using the RabbitMQ secret provided in the namespace.

    May I know which information from the secret shall I provide in the following columns (server, username & password) ?

    Thanks in advance !

    • 4 replies
    1. S
      @sk_chen
        2020-08-24 09:17:10.368Z2020-08-24 09:25:18.146Z

        Hi
        You need to check RabbitMQ in portal-service and get MQTT connection certificate in secret.

        1. Link to portal-service
        2. Select RabbitMQ
        3. Create secret
        4. View secret and get credentials
          • host : External Hosts
          • port : mqtt.port
          • username : mqtt.username
          • password : mqtt.password
        1. Y@Yong
            2020-08-26 09:17:15.614Z

            Hi, It works on my raspberry pi, but not for the WISE-6610.. Not sure what's the error..

            1. Stanley Yeh @adv.stanley
                2020-09-23 08:01:24.996Z

                What is the Node-RED version on WISE-6610? Is it the same as RaspberryPi? Also, Do you have any screenshots or error message for us to look into this issue?

            2. C
              In reply toYong:
              Chance Tran @ChanceTran
                2021-10-20 15:53:33.812Z

                Hi......I began Node-Red a few days prior and was glad to discover "TTN uplink" ( Node-red-contrib-ttn) on my establishment on a NAS. As I moved to my Raspberry Pi 2 B Model I was looked to the note that TTN uplink is deplored. It was difficult to track down, that this was uniquely for the Raspberry Pi.

                By and by you are correct. It is considerably more adaptable to go with "MQTT in" as you approach EVERY data and not the sensor payload as it were.

                One thing I like to add is, that on the off chance that there are more than one sensor in ones application I colud address them by supplanting.