7 Replies Latest reply: Sep 23, 2012 11:42 PM by hemant rajput RSS

device info result is incomplete

hemant rajput Newbie

Hi,

 

I'm using emulator and in the result REST  call for device info http://127.0.0.1:32001/Spokes/DeviceServices/8e68ef7293ed6b67d7145caad3b1642d/Info, this is the result I'm getting -

 

{"Description":"","Err":null,"Result":{"BaseFirmwareVersion":"80.0","BluetoothFirmwareVersion":"0","DevicePath":"plantronics_virtual_device.vpro_uc","InternalName":"Voyager Pro UC <emulated>","IsAttached":true,"ManufacturerName":"Plantronics, Inc.","ProductId":1045,"ProductName":"Voyager Pro UC <emulated>","RemoteFirmwareVersion":"40.00","SerialNumber":"01234567-89ab-cdef-0123-456789abcdef","USBVersionNumber":"2115","Uid":"8e68ef7293ed6b67d7145caad3b1642d","VendorId":1151},"Type":4,"Type_Name":"DeviceInfo","isError":false}

 

it doesn't include the state information but as as per documentation it should.

 

As per the documentation-

DeviceInfo contains all known state information for a given headset, including AudioState, MuteState, PID/VID, and so on. For users who want to communicate to a device, this is typically the first REST end point called.

 

I'm using emulator, is that the reason?

 

Thanks,

Hemant

  • Re: device info result is incomplete
    Wei Chu Adventurer

    Hi Hemant

     

    You are correct that you are not seeing all the device info because you are using the emulator instead of an actual device.

     

    Please be aware that the purpose of the emulator is to introduce new developers to Spokes SDK, such that they may experiment with the SDK before acquiring an actual device, much like what you are doing now.  The emulator is not intended to be a substitute or replacement of the actual device for development.  as such, the emulator will not be 100% compatible to the actual device.

     

    Anyway I hope you enjoyed experimenting with our SDK and welcome to the developers community.

     

    Wei Chu

    • Re: device info result is incomplete
      hemant rajput Newbie

      Even with the actual device I'm not getting complete info. This is what I'm getting - [{"BaseFirmwareVersion":"43.8","BluetoothFirmwareVersion":null,"DevicePath":"\\\\?\\hid#vid_047f&pid_0415&mi_03&col02#8&298863a9&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}","InternalName":"Delphi 2.0 Dongle (UC)","IsAttached":false,"ManufacturerName":"Plantronics","ProductId":1045,"ProductName":"Plantronics BT300","RemoteFirmwareVersion":null,"SerialNumber":"","USBVersionNumber":"843","Uid":"62515ce7c5a6c44c3684dc15f1852c05","VendorId":1151}],"Type":5,"Type_Name":"DeviceInfoArray","isError":false}

       

      As per the documentation-

      DeviceInfo contains all known state information for a given headset, including AudioState, MuteState, PID/VID, and so on. For users who want to communicate to a device, this is typically the first REST end point called.

       

      I don't see mutestate, audio state etc.

       

      Thanks,

      Hemant

      • Re: device info result is incomplete
        Wei Chu Adventurer

        I checked with our software team and I am very sorry to tell you that the error is in our documentation. Device Info does not include states. If you need to get the audio or mute states, there are other SDK api's to retreive the states.

         

        Wei

        • Re: device info result is incomplete
          hemant rajput Newbie

          Thanks for the response.

           

          In the rest api I don't see any api for getting the initial states like audio on/off, mute/unmute etc. Can you please tell me the api for the same.

           

          Thanks,

          Hemant

          • Re: device info result is incomplete
            Wei Chu Adventurer

            Hi Hemant,

             

            Sorry I did not get back to you sooner. I have referred your question to our software team and waiting for a response from them. I will make sure that you get an answer as soon as possible.

             

            Wei Chu

          • Re: device info result is incomplete
            Brandon Haston Wayfarer

            Hello Hemant,

             

            If you're working strictly with the REST service for our Spokes SDK then you can keep an eye out for MuteON/MuteOFF events while polling for device events and keep track of the last known mute event to know what the current status of the device is.

             

            I dug through the JavaScript SDK (communicates with Spokes via the REST service) and I don't see a method to directly ask for audio on/off, mute/unmute states. So, at the moment, I would recommend manually keeping track of the events as they happen.

             

            I apologize for the delay in the response. Hopefully this reply is useful for you.

             

            -Brandon Haston