Asked
— Edited
The IBM Watson Services plugin created by @PTP currently allows you to perform Speech to Text and Text to Speech as well as visual recognition using Watson Services.
You can download and install the plugin here https://www.ez-robot.com/EZ-Builder/Plugins/view/251
Before you can use the plugin, you will need to apply for a free 30 day trial of IBM Speech to Text Account here https://www.ibm.com/watson/services/speech-to-text and a free 30 day trial of IBM Text to Speech https://www.ibm.com/watson/services/text-to-speech/
I will create some examples as it moves forward and try to answer any how to questions.
Thanks for creating this PTP, as with all your plugins this is an excellent piece of work and showcase of your talents.
Hi @ptp ,
Thank you for your work on the IBM Watson Plugin. I tried to play with it a little bit and it seems that IBM Watson is now only providing an API Key and URL for the new accounts. So no more credentials with username/password.
https://console.bluemix.net/docs/services/watson/getting-started-tokens.html#tokens-for-authentication :
This link is also mentionning the migration : https://www.ibm.com/watson/developercloud/text-to-speech/api/v1/curl.html?curl#introduction
I could only try with the visual recognition and I have the following error : IBM.WatsonDeveloperCloud.Http.Exceptions.ServiceResponseException : The API query failed with status code Unauthorized :....
Not sure if it's my bad, or some big change were made on the Watson .NET SDK :
Hi @Aryus96 I will send you some credentials off line to my old account. Seems to still work.
@Nink,
I'm investigating... my services are working.
Do you know how to convert an existing service (user/password) to the new authentication method ?
I can't find an upgrade option.
I also cannot find a way to generate a basic authentification (username/password) with my new account.
@ptp I'm also working on a personal plugin that include the Watson .NET SDK, using the 2.11.0 and I'm having some difficulties with the dependencies of system.net.http... Did you encountered some similar problems ?
I deleted the existent service and created a new service. Although London location is not available, the new service is located in Washington DC.
I created a new service on my personal account and I was issued a token. I didn't want to touch my old services as they still work.
I'll update the plugin to support both user/password and the api key/token method. Tokens seems more secure in advanced scenarios where a proxy service creates and delivers time limit tokens, if an attacker gets the token is not a major issue: has a time limit and is not the service's API key.
@ptp No it doesn’t work for me. It’s not because of the Token but versions of the SDK & Dependencies for .Net 4.6.1, as you succeed to make it run, you might be the only one who could help me. What version of the SDK and dependencies are you using ? I opened an issue here with more details : https://github.com/watson-developer-cloud/dotnet-standard-sdk/issues/307