Closed inchlogic closed 6 years ago
I want to know this too, please. I've come to rely on this skill, because it's great and it just works. Looking forward to when its ready for Australia.
I have this submitted and in certification, I'll post back here if/when its approved
As the notice of certification submission was over the 7 business days that Amazon take to assess, I can only assume the skill failed to pass certification. Please can you update on current progress.
We did get rejected, there is an apparent issue with our demo server, I'm trying to troubleshoot it this weekend, I'm hoping to resubmit today or tomorrow.
Good luck! My experience is if you respond with the issue corrected fast then they seem to only test from the points picked up, which has the impact of a fast turnaround for resubmitted skills.
On 18 March 2018 at 04:37, Dan Cunningham notifications@github.com wrote:
We did get rejected, there is an apparent issue with our demo server, I'm trying to troubleshoot it this weekend, I'm hoping to resubmit today or tomorrow.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/openhab/openhab-alexa/issues/59#issuecomment-373929334, or mute the thread https://github.com/notifications/unsubscribe-auth/AC3ReT4K8ETQl9BxiZ3sf7V38r8AsrARks5tfS3SgaJpZM4R6iHp .
Hi @digitaldan - any update?
Hi @digitaldan, could you please update on the progress... :-)
Still no on the Australian store. Guess I will have to run it in development as a private skill.
The latest news is that Amazon will not allow our app for submission until it is ported to the V3 skills api, they no longer accept new app or even updates to v2 skills. The good news is I have a working v3 skill, see https://github.com/digitaldan/openhab-alexa/blob/v3/README.md#version-3-v3-item-mapping . While the extended tags in that readme are going to be changed significantly due to a new feature in ESH, the v2 capability layer will remain and work for everyones current setup. The v3 skill API was a big change from v2 and so our v3 app is almost all new code.
Thanks @digitaldan. For the time being I have created it as a private skill in my development console.
@digitaldan I had to add a response for Authorization else I couldn't link my account.
/**
* Handle Authorization
*/
function handleAuthorization() {
var result = {
event: {
header: {
messageId: uuid(),
name: "AcceptGrant.Response",
namespace: "Alexa.Authorization",
payloadVersion: directive.header.payloadVersion,
correlationToken: directive.header.correlationToken
},
payload: {}
}
};
log.debug('Authorization result ' + JSON.stringify(result));
context.succeed(result);
}
Hi All, any updates here? Patiently waiting.
Have you considered deploying it yourself? It's working fine for me in Australia with the Skill.
@Clifford-Foster I am completely new to this. Any pointers on how deploy the skill for private use? Thanks, Alex.
Hi all, good news, we finally were approved this morning and are now live in the following languages/regions:
English (UK) English (US) English (CA) English (AU) English (IN) French (FR) German
Great stuff @digitaldan. Works well so far. Thanks for making this available in Australia.
Thank you for all your efforts, it's greatly appreciated. Skill is also working well for me. Worth the wait...
Hi All
Im trying to set this up, under AWS Console when configuring the lamba and using 'Sydney' as my location, I cannot see the Alexa Smart Home Trigger unless I set it to oregon.
For Australian users, can anyone explain how to do this?
Thanks
When will the OpenHAB skill be In Australia?