You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Will scope this to adding a config option in the Broker settings to define the top-level scope that you wish to subscribe to for traffic, defaulting to # (for now)
Current Behavior
Some Brokers do not permit subscribing to
#
and therefore the Broker Hierarchy never gets populated with any topicsIn particular, EMQX (by default), Azure IoT Hub, AWS IoT Core and many others do not permit subscribing to
#
Expected Behavior
We may wish to include a topic filter on the broker configuration.
We may also want to consider
Steps To Reproduce
Try adding an emqx broker (that by default does NOT return anything on
#
) - no topics are populated.Environment
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
The text was updated successfully, but these errors were encountered: