dmytro-landiak
commented
5 months ago @freichelka,
Thank you for your request. Unfortunately, this issue is hard to reproduce. To simulate the behavior, we used the following emulator and subscribed the WS client to receive messages with different subscriptions:
docker run --network="host" -e SPARKPLUG_SERVER_URL='tcp://localhost:1883' -e SPARKPLUG_CLIENT_MQTT_USERNAME='tbmq_websockets_username' thingsboard/tb-sparkplug-emulator:latestUsing "#" subscription:
Using "spBv1.0/Sparkplug Group 1/DDATA/Sparkplug Node 1/#" subscription:
Could you please check the logs or include them here to check for potential issues?
freichelka
Describe the bug We use TBMQ for connecting Sparkplug B devices in two different environments. The devices subscribe to retained and non-retained topics. The retained topics convey the status of the "Primary Application." The non-retained topics are used to send commands to the devices (NCMD). For example, the device subscribes to "spBv1.0/{group ID}/NCMD/{device ID}/#". All subscriptions are made with QoS 1.
The messages of the non-retained topics are not delivered to the device.
Using a test client, I tried to replicate what is happening at the MQTT level. There, I observed that when I subscribe to "#", the messages arrive at the client. When I subscribe to "spBv1.0/{group ID}/NCMD/{device ID}/#", nothing arrives. When I subscribe to "spBv1.0/{group ID}/NCMD/{device ID}", the messages arrive.
In my opinion, there is a bug here.
Your Server Environment
Your Client Environment
Your Device
To Reproduce see description