CODEWITHSUNDEEP
mqttnode-redthingsboardthingsboard-gateway
Caracos
Caracos

Reputation: 31

Problem Using Single Security Token for Multiple MQTT Client

Below are my setups:

  1. ThingsBoard (Community Edition)

  1. Raspberry Pi 4 running the applications below:

I'm able to publish all the sensor data from Node-Red to ThingsBoard using MQTT. The problem is that I need to use ThingsBoard "RPC Remote Shell" function. In order to achieve this I've installed TIG on my Raspberry Pi.

Both Node-Red and TIG are using the same "Security Token". When TIG is connected to ThingsBoard it will interrupt Node-Red's connection to ThingsBoard.

For now, as a workaround, I had to create two "Device" within ThingsBoard in order to get two different "Security Token". One token is for Node-Red and another is for TIG. This seems to sort out the problem temporarily but I ended up with two logical "Device" within ThingsBoard for one physical device (Raspberry Pi).

Is there a setting that to allow multiple connection from one "Security Token" on ThingsBoard? Or which part of ThingsBoard's codes do I need to edit in order to allow it? Or perhaps there's a way to enable "RPC Remote Shell" including other RPC capabilities using Node-Red instead of TIG? I have to use Node-Red as this is the easiest method to gather data instead of TIG. Let me know if you have a creative solution for this problem.

Appreciate your help. Thanks in advance.

Upvotes: 0

Views: 514

Answers (1)

Andrew
Andrew

Reputation: 732

This behaviour is controlled by ACTORS_MAX_CONCURRENT_SESSION_PER_DEVICE configuration parameter. The default value is 1. You may change this value to 2. Then both sessions will work. Although it is not recommended to change the value if you subscribe to RPC or attribute updates in both device applications (MQTT sessions).

Upvotes: 0

Related Questions