Metadata API to see the device info for the KMC.BAC-121036CE device
It's ID right now in Metadata is: 598cb184e4b0c393ed53d9b4 (you would have a different ID when you start yours)
http://192.168.99.100:48081/api/v1/device/598cb184e4b0c393ed53d9b4

Note the Profile and it's commands in the response - especially the command for GET CurrentTemperature
 "path": "/api/v1/device/{deviceId}/CurrentTemperature",
 
 
This is the path on the device service (the Virtual Device micro service) for that command

So we can invoke it
http://192.168.99.100:49990/api/v1/device/598cb184e4b0c393ed53d9b4/CurrentTemperature with a GET request (again your device and command IDs will be different)
and we get back the current temperature from that device

    {
        "AnalogInput_3000290": "-16.25"
    }

Now let's call on the Command micro service to see the commands for the same device
http://192.168.99.100:48082/api/v1/device/598cb184e4b0c393ed53d9b4

Note the commands now in this list - especially the command for GET CurrentTemperature
 "url": "http://192.168.99.100:48082/api/v1/device/598cb184e4b0c393ed53d9b4/command/598cb17fe4b0c393ed53d9a3",
 
This is the path for the command through Command micro service

So we can invoke it and we get back the response from Command
{"AnalogInput_3000290":"-16.25"}


What we saw was Command talked to the Device Service that then talked to the device that responded back up