Watson Services Authentication

[maclean-stu]

Looks like I can only use Watson Services provisioned in the Dallas location. I tried using one in Sydney but the call failed. Is it possible to update the configuration to accept a gateway url as well as the API Key so we can use the services from the closes region to our physical location?

eg the gateway for Dallas Speech to Text service is https://stream.watsonplatform.net/speech-to-text/api whereas the Sydney service it is "https://gateway-syd.watsonplatform.net/speech-to-text/api"

[mr5x5]

I am finding a similar challenge to using the IBM Watson Service - Washington D.C. URL.

It has been a few days of seeking a workaround, thinking only that I input the wrong Watson Service apikeys, username or password. The terminology is made even more difficult with the IBM Watson transition to Apikeys. I also confuse these Credentials failures with Node-Red Flow Credentials. Finally, I still have lingering issues with PiGPIO & RPI-ws281x-native modules. It did not occur to me to try Dallas.

Thank you @jeancarl for all of these incredible Labs! It's been a wild adventure getting from the standard recipes for TJBot to now tinkering in Node-Red. It has been the perfect way to get my daughter thinking about AI.

[jeancarl]

@maclean-stu Which runtime are you using? If you're using the TJBot Node.js library, you can supply a url parameter along with your apikey:

var tj = new TJBot(["microphone"], {}, {
  speech_to_text: {
    apikey: "...",
    url: "https://gateway-syd.watsonplatform.net/speech-to-text/api"
  }
});

tj.listen((text) => {
  console.log(text);
  tj.stopListening();
});

The Node-RED nodes do not currently support regions. Thank you for the feature request (https://github.com/jeancarl/node-red-contrib-tjbot/issues/11).

[jeancarl]

@mr5x5 issues with PiGPIO & RPI-ws281x-native are probably something that should be brought up on the TJBot Node.js library repo if the same experience happens using Node.js. The Node-RED nodes call the corresponding methods from the TJBot library. I haven't had time to figure out if the Node-RED environment is causing it or simply Node.js, so any feedback would be helpful. It works using Node v.8.11.

The Node-RED nodes do not currently support regions. Thank you for the feature request (jeancarl/node-red-contrib-tjbot#11).

Thank you for the kind note about the labs. There's plenty of things you can do with TJBot!

[maclean-stu]

I was using NodeRed.     RegardsStuart   Stuart Maclean, Technical Sales IBM Data & AI Mobile: +61-401715309 Explore IBM Watson AI @ https://www.ibm.com/watson/ Test drive IBM technology @ https://ibm-dte.mybluemix.net Find me on LinkedIn www.linkedin.com/in/stuart-maclean-ibm     ----- Original message -----From: JeanCarl notifications@github.comTo: jeancarl/tjbot-labs tjbot-labs@noreply.github.comCc: Stuart Maclean smaclean@au.ibm.com, Mention mention@noreply.github.comSubject: Re: [jeancarl/tjbot-labs] Watson Services Authentication (#4)Date: Wed, Feb 13, 2019 4:38 PM  @maclean-stu Which runtime are you using? If you're using the TJBot Node.js library, you can supply a url parameter along with your apikey: var tj = new TJBot(["microphone"], {}, {  speech_to_text: {    apikey: "...",    url: "https://gateway-syd.watsonplatform.net/speech-to-text/api"  }});tj.listen((text) => {  console.log(text);  tj.stopListening();}); The Node-RED nodes do not currently support regions. Thank you for the feature request (jeancarl/node-red-contrib-tjbot#11). —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.