Adding Chandradeep to CC, in case he didn't subscribe to the list.
On Tue, 9 May 2023 at 18:31, Nandor Soma Abonyi
wrote:
>
> Dear Chandradeep,
>
> Though I haven't seen your configuration yet, I tried to test the scenario.
> If you want to listen to different topics with a single processor, you
Dear Chandradeep,
Though I haven't seen your configuration yet, I tried to test the scenario. If
you want to listen to different topics with a single processor, you need to use
wildcards. If you have two clients that are publishing to
buildings/A/1/temperature and buildings/A/2/temperature, the
Dear Chandradeep,
Though I haven't seen your configuration yet, I tried to test the scenario. If
you want to listen to different topics with a single processor, you need to use
wildcards. If you have two clients that are publishing to
buildings/A/1/temperature and buildings/A/2/temperature, the
Dear Chandradeep,
It seems like the images didn’t go through.
Could you attach them again?
Best regards,
Nandor Soma Abonyi
> On 2023. May 6., at 13:59, Chandradeep Kumar
> wrote:
>
>
> Dear Dev,
>
> I’m trying to handle a scenario where more than one topic could be able to
> subscribe t
Dear Dev,
I'm trying to handle a scenario where more than one topic could be able to
subscribe to a MQTT Broker via ConsumeMQTT processor.
Currently I'm able to subscribe single topic and receive message which is
published on same topic.
Below configuration of ConsumeMQTT works fine:
[cid:imag
