MQTT Subscription Failed

[Luke-Guangzhong]

Hello！

Here is my text which used to build the factory reset database:

I used Device.MQTT.Client.1.Subscription three times. But when I login in the MQTT Broker, I can only see the topic defined in the Device.LocalAgent.MTP.1.MQTT.ResponseTopicConfigured

How to subscribe more topics for the MQTT Client？
Can you help me point out where I have written wrong?

Thanks ！

[holme-r]

MQTT Subscriptions should work. Are the subscriptions present in the output of 'obuspa -c show database' ?

[RamonRomeroQro]

Hello!

Same problem here, the subscriptions are defined on the obuspa factory file and on the output for the data base, but no subscribe message is sent to the broker

Device.MQTT.Client.1.Subscription.3.Alias => cpe-3
Device.MQTT.Client.1.Subscription.3.Topic => status/usp/newtopic
Device.MQTT.Client.1.Subscription.3.QoS => 1
Device.MQTT.Client.1.Subscription.3.Enable => true

Notes:

• Running using the dockerfile
• My mosquitto acl were also tested to publish and subscribe without problems.
• Also Device.LocalAgent.MTP.1.MQTT.ResponseTopicConfigured subscribes but not receiving message from broker
• messages sent to Device.LocalAgent.Controller.1.MTP.1.MQTT.Topic received.

Maybe our configuration files for subscriptions are wrong, could you please share a tested configuration file for one or multiple subcriptions?

Thanks !

[Luke-Guangzhong]

MQTT Subscriptions should work. Are the subscriptions present in the output of 'obuspa -c show database' ?

Hi ！
Thank you for reply.
Here is my output of obuspa -c show database:

By the way, I'm using Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-62-generic x86_64). Do I need to do something else because of my OS?

Thanks ！

[holme-r]

I can reproduce the issue and am working on a fix.

[Luke-Guangzhong]

Thank you very much ! 😁

[RamonRomeroQro]

@Luke-Guangzhong hello, have you already tested your mqtt factory file with the new code?

[Luke-Guangzhong]

@RamonRomeroQro Hi!
I'm sorry, my team leader postponed the task.
Now I am preparing for the internal exam.
If I test it, I'll let you know as soon as possible.

[RamonRomeroQro]

@Luke-Guangzhong already tested with an example similar to the one which you posted, it seems to be working

[Luke-Guangzhong]

@RamonRomeroQro
I'm sorry, it took a long time to prepare for the internal exam.:sweat_smile:
Thank you very much. 👍

[holme-r]

@RamonRomeroQro For more info on how USP uses MQTT see: https://github.com/BroadbandForum/usp/blob/master/specification/mtp/mqtt/index.md Answers to your questions: 1. The topic for the response is specified by a "reply to" Topic in the message received by the USP Agent. 2. Sorry, but I don't understand what you mean by a 'periodic subscription'. It implies you want the subscription to only be active at certain times (periodically), and I can't understand why you'd want to do that.

…

On Thu, 2 Sept 2021 at 21:32, Ramón Romero ***@***.***> wrote: @holme-r <https://github.com/holme-r> Thanks for your answers, 2 more doubts, - once I have created the subscription, how can I define the topic for the response? - How can I define a periodic subscription to a specific topic? Sorry for so many questions, I do not have found a lot of docs — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#23 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADF65VTQE57PRINRURUDPK3T77NPJANCNFSM5CLL3ACA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[RamonRomeroQro]

@holme-r Thank you so much for your work and replies, I have already solve those issues 😁

[holme-r]

Closing as the fix is committed.