There is a mistake on REDIS's message that Deepstream 7 about SensorId var

Accelerated Computing Intelligent Video Analytics Metropolis Microservices for Jetson
1

On the message generated from Deepstream 7 (Yolo Container) there is a mistake, instead of SensorId, the info recorded is “Name” of the sensor.

'{ "version" : "4.0", "id" : "348945", "@timestamp" : "2024-08-13T14:10:05.137Z", "sensorId" : "**portaria_motorola_lpr**", "objects" : [ "39634|361.462|475.645|405.39|591.268|Person|0", "39625|422.592|489.527|461.835|585.446|car|0" ] }'

When i inspect the sensor’s data using API i saw that these are different informations:

image
image755×804 105 KB

The correct info on sensorId var on REDIS is “a41c96a6-8f23-4846-9444-efa51a94fb91” and not the sensor name “portaria_motorola_lpr”

Obs: If you can put StreamId on REDIS message will be easier to get the source image/frame (all 3 info will be perfect, sensor_name, sensorId and streamId)

4

I will check and feedback. Can you share more reason on why you need “sensor_name, sensorId and streamId”?

5

Sensor name is important to mantain the important info about the source of data, sensorId and streamId are important because i need these data to access API, like get frame/image, or location in sensorId.

6

Can you maintain one map between sensor name and sensor id in your application to unblock you?

7

I am doing exactly this now for running my application, the correct sensorId and streamId in hardcode, but seems an error the sensorId is missing because how can i get the sensor info and streamId using only the sensor’s name?

8

Suppose you can get sensor info (name and sendorId) from VST. So you can get the sensorId from sensor name. Do you mean the streamId which used in DeepStream? Why you need streamId?

9

To get the picture/frame using the API i need to know a streamID

image

10

Can you have a try with sensorId to get the picture?

11

On my case is the same, will works.

but will it always be like this?