I subscribed to:
application/00000000-0000-0000-0000-000000000001/device/+/command/down
But it looks like I’m only seeing the downlinks that other applications send to CS but I do not see the downlinks that are sent via CS itself (i.e. the downlink queue). This used to work before CS4.
I also took a look at us915_1/gateway/+/command/down
but the downlink is already encrypted.
I don’t know if this is a bug or not an option or I’m missing something.
My application is supposed to monitor the main application and CS itself to some extend, this includes that I can see all downlinks that are sent if possible.
Unfortunately, I think the us915_1/gateway/+/command/down is the only way via MQTT to view downlinks triggered from the UI or gRPC. The topic application/+/device/+/command/down is just for integrations that trigger downlinks via MQTT. If you need to see what is in the downlink queue I believe that is stored in redis, likely this is encrypted as well though.
Likely the reason you could see them in V3 was the application server had to send the downlink to the network server for encryption, but now that they are merged Chirpstack only needs to post it to the gateways topics.
Ok, thanks, and gee that was the fastest reply ever
Since this is for production environments I’d rather not start messing with redis.
This wouldn’t be the only data my program is missing out on since CS4 but it’s OK, I will take what I can get and not a big deal.
