Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setHidWorkingStateAsync returns error code 3 #19

Open
Nederby opened this issue Dec 19, 2019 · 2 comments
Open

setHidWorkingStateAsync returns error code 3 #19

Nederby opened this issue Dec 19, 2019 · 2 comments

Comments

@Nederby
Copy link

Nederby commented Dec 19, 2019

Version: jabra-node-sdk 3.0.0-beta.1
Modal: Jabra Evolve 75 & Jabra Link 370
NodeJS: 10.13
Electron: 4.1.0

When connecting a device (Jabra Evolve 75) with Bluetooth (Jabra Link 370) device we get the following error after calling setHidWorkingStateAsync(enumHidState.GN_HID) on the Jabra Evolve 75 device.

   // after device attached.
 device.setHidWorkingStateAsync(enumHidState.GN_HID) // Enable GN hid. 
  .then( () => {
    // btn listeners
    device.on('btnPress', (btnType, btnValue) => {
      logger.log(`New input from device ${device.deviceName} is received: type ${btnType} ${enumDeviceBtnType[btnType]} value: ${btnValue}`);
    });
  })
  .catch((e) => {
    logger.log(`setHidWorkingStateAsync: ${e}`); // Exception (Error: JAsyncWorker execute failure: napi_SetHidWorkingState got Jabra_SDK error 3) when bluetooth device is attached. 
  });

Error: JAsyncWorker execute failure: napi_SetHidWorkingState got Jabra_SDK error 3

It works great when connected to the headset with a wire, but throws the exceptions when connected with Bluetooth.

Are we doing something wrong? 🤔

@jabra-slawaetz
Copy link

Thanks for posting.
There should be little or no difference on the Bluettoh connection HS. But we need to investigate and qualify the issue internally before we can return with more information.
I will raise a trouble ticket on the DevZone, so that we can track this issue on the support platform. You should get a mail notification about this.
Thanks

@pehandersen-jabra
Copy link
Contributor

Just stumbled on this old thread - and have 2 comments for the issue reported here:

  1. If you update to latest released version of NodeJS now (3.2.0 as per today), then you shouldn't need to set the HID working state as the SDK will always use GN HID when initiating a headset session.
  2. The HID working state needs to be set on the USB dongle device (Link 370) and not the headset. Likewise, the actually call control commands are to be sent to the dongle, not the headset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants