-
Notifications
You must be signed in to change notification settings - Fork 197
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
Relevant Alexa bug? Discovery problems... #53
Comments
Why not use the skill I made? This is one of the reason I made it
…On Mon, 9 Jul 2018 at 2:40 AM Ynot1 ***@***.***> wrote:
This may be root the cause of my Alexa not finding >5 switches yesterday .
After a few hours of quite intensive device discovery, my Alexa stopped
finding any new devices . I could see XML being uploaded from the multiple
switch code when the discovery was underway , but Alexa app didn’t display
any result. Put the code onto a new esp-01 with the same result.
In desperation I reset the echo speaker and tried discovery again. Alexa
then had 2 copies of each switch ! Looks like discovery was happening all
along , but that the results weren’t being saved somewhere.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#53>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHIM5pLwU4pca-Q3I6KkofqAt9sAN5nbks5uEmBKgaJpZM4VG2Gf>
.
|
Has the sinric skill been released world wide yet or is it still in beta? To be honest - the less moving parts the better is my motto , I like the simplicity of the direct integration . When it works...
Get Outlook for iOS
On Mon, Jul 9, 2018 at 2:05 PM +1200, "Aruna Tennakoon" <[email protected]> wrote:
Why not use the skill I made? This is one of the reason I made it
On Mon, 9 Jul 2018 at 2:40 AM Ynot1 ***@***.***> wrote:
This may be root the cause of my Alexa not finding >5 switches yesterday .
After a few hours of quite intensive device discovery, my Alexa stopped
finding any new devices . I could see XML being uploaded from the multiple
switch code when the discovery was underway , but Alexa app didn’t display
any result. Put the code onto a new esp-01 with the same result.
In desperation I reset the echo speaker and tried discovery again. Alexa
then had 2 copies of each switch ! Looks like discovery was happening all
along , but that the results weren’t being saved somewhere.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#53>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHIM5pLwU4pca-Q3I6KkofqAt9sAN5nbks5uEmBKgaJpZM4VG2Gf>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
well, it's available in US, German, India, UK, Canada, Australia and New Zealand |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This may be root the cause of my Alexa not finding >5 switches yesterday .
After a few hours of quite intensive device discovery, my Alexa stopped finding any new devices . I could see XML being uploaded from the multiple switch code when the discovery was underway , but Alexa app didn’t display any result. Put the code onto a new esp-01 with the same result.
In desperation I reset the echo speaker and tried discovery again. Alexa then had 2 copies of each switch ! Looks like discovery was happening all along , but that the results weren’t being saved somewhere.
The text was updated successfully, but these errors were encountered: