[known issue] Echo Gen 2 & Echo Plus discovery not working #47
Comments
|
I have the same issue. I got Echo 2 with this node in mind, so I hope it will be possible to fix. |
|
+1. |
|
Version 0.3.15 contains a possible fix for Echo Dot Gen 2 implemented by the folks at habridge. Please give it a try. |
|
hi, I just installed it on the latest version of node red and tested it with a second gen alexa:
unfortunately, the device is not detected. |
|
ok. thanks for testing. I'll dig further into this. |
|
@LennartHennigs L I've just tested with my Echo Dot 2nd Gen. It's working! |
|
Please try again with v0.3.18. There's something new in discovery protocol being implemented. |
|
I just installed the node with npm. What are the versions that work? |
|
I can confirm that after upgrading it did start to work with a 2nd gen Echo. Seems fixed to me, thank you very much! |
|
@oeuviz What are the node.js and node-red versions? |
|
version of nodejs and node-red does not really matter here. you need to get the latest version of my Alexa node. if you're using docker, please search for relevant issues here. |
|
I installed 0.3.18 version with npm. No input node to alexa, connected debug output shows nothing, discovery from browser finds nothing. |
|
Can't say for sure, but quite a few routers or APs do NOT forward UDP broadcast/multicast traffic between wired and wireless subnets. If you don't see Alexa node showing 'discover' status below the node, that's most likely is the problem. |
|
Strange. The discovery status is set 10 minutes (!) after initiating discovery. |
|
All this is strange indeed. I just did an apt-get update && apt-get upgrade on a different machine, resulting in below mentioned updated packages. This in return lead to Alexa finally finding my devices. Here's the strange thing: node-red-contrib-alexa-local was on version 0.3.12 and detection also worked with node-red-contrib-alexa-home. Upgrade: perl-base:armhf (5.24.1-3+deb9u1, 5.24.1-3+deb9u2), bluez:armhf (5.43-2+rpi1, 5.43-2+rpt2+deb9u2), libdns-export162:armhf (1:9.10.3.dfsg.P4-12.3+deb9u2, 1:9.10.3.dfsg.P4-12.3+deb9u4), libkrb5-3:armhf (1.15-1, 1.15-1+deb9u1), libraspberrypi-bin:armhf (1.20170811-1, 1.20171029-1), libgssapi-krb5-2:armhf (1.15-1, 1.15-1+deb9u1), firmware-realtek:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt2), libisccfg140:armhf (1:9.10.3.dfsg.P4-12.3+deb9u2, 1:9.10.3.dfsg.P4-12.3+deb9u4), libdbus-1-3:armhf (1.10.18-1, 1.10.24-0+deb9u1), libraspberrypi-dev:armhf (1.20170811-1, 1.20171029-1), libraspberrypi-doc:armhf (1.20170811-1, 1.20171029-1), linux-libc-dev:armhf (3.18.5-1 |
|
I just installed it on the latest version of node red and tested it with a alexa echo ( Node-RED version: v0.18.4 the node detects that alexa is looking for devices (discovery") but it is not found. |
|
I'm running Node-RED on Ubuntu 16.04.4 LTS. 18 Mar 17:00:50 - [info] Node-RED version: v0.18.4 My Echo Plus software level: In my flow I've created a node called "Kitchen": Node-red is listening on the port: There is no firewall enable: Alexa doesn't discover the device(s) in Node-RED. |
|
Unfortunately Echo Plus is not supported at the moment |
|
Hi Same problem Echo Dot Gen2 works. |
|
Can you take a photo of your Echo Dot Gen 2.
I think a lot of people is confusing this model.
…On Tue, Mar 27, 2018 at 5:08 PM, m0rph2k ***@***.***> wrote:
Hi
Same problem Echo Dot Gen2 works.
Echo Spot --> the node detects that alexa is looking for devices
(discovery") but it is not found.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#47 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAu1WHqMwwThDtAA5W5sgK5z4efh3PHLks5tig-igaJpZM4R6CfS>
.
|
|
here a photo but for what ? Echo Spot --> Unsupported? |
|
Hey @torinnguyen, I updated your node to 0.3.19, restarted the Dot and still no luck. |
torinnguyen
changed the title
|
Hi, I don't now if this helps, but I tried the node-red-contrib-wemo-emulator and it worked fine. Is the detection similar? |
|
Hi, yes my Echo Spot and Dot Gen2 find Devices with node-red-contrib-wemo-emulator |
|
great. I'll see what I can do. |
|
@m0rph2k @LennartHennigs unfortunately I can't be using wemo-emulator. There is a hard limit of 16 wemos supported by Alexa. Not sure if this has been lifted. Can both of you help to test on Echo Spot and Dot Gen2 with v0.3.22? |
|
Hi, I have just tested version 0.3.22 and it works for me. I have Echo 2 and Echo Dot 2 at home. But I have initiated search of new devices via application. |
|
Hi. Dot 2 discovered devices but now with 0-100% bar, old version On / Off (alexa app) |
|
Hi, Cheers |
|
It works if you have a Echo Dot 2 in the same network, but not otherwise. |
|
Echo Dot 2 on same wifi network as iMac running node red, Dot is not recognized. |
|
Hi, |
|
same here. did someone solve this? could it be a SSDP / UPnP issue? unfortunately, I can't activate UPnP on my router to test this. |
|
What do we have to do to fix this? I'd be happy to get involved, especially to make this work for Echo Plus. |
|
ive ds218+ with Habridge and alexa 2Gen ,alexa can't dinf anything.HAbridge works great (5.2.1).but no discovery |
|
I am using version 0.3.24, and my alexa echo 2nd Gen can't find anything still. I would like to help out with debugging this issue if I can? What information would be useful? |
|
Don't know if it is usefull, but my Echo Spot and my Echo Dot 3 detect devices in node-red with the wemo emulator without having the wemo skill activated.... |
|
Any update on the discovery of the EchoPlus? |
|
Any update? Does not work for me too with Echo Gen 2 |
|
hi, i have several installations of node-red, but alexa-local is not working. Either with echo dot Gen2 or echo spot nor Alexa app. Alexe didn't find any device. I tried the wemo-emulator - this works fine but not on all systems. For me it seems it is a problem of networking. |
|
Hi! Plz don't stop development, we need Echo plus support, thank you a lot! |
|
Working solution for Echo Plus: |
|
replaced Echo Plus gen 1 w/ Echo Plus gen 2- ALL Philips lighting stopped working. The gen 2 could not discover the lighting. Tried reboot, remove and replaced bulbs, entered serial number of bulb. Every time wasting troubleshooting Amazon asked me to do. (see answer below). Using a NEW unused bulb was discovered by Gen 2 by accident. I left the bulb ON for 20 or 30 minutes. Suddenly the bulb started to blink slowly and eventually paired on its own without the command. The others do not. |
|
If you use Philips bulbs and Echo, without node red, why you posting here? |
|
I am new to this site. I did a search for Echo Plus pairing issues. . .
Sorry if my post was not of help to you.
… On Apr 20, 2019, at 11:49 AM, Barabba11 ***@***.***> wrote:
If you use Philips bulbs and Echo, without node red, why you posting here?
Instead try to drive bulbs from node red and connect note red to alexa
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#47 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AL4CQUX4X6V6VA2IJ66CJYTPRNQS3ANCNFSM4EPIE7JA>.
|
|
If you prefer, Im happy to remove my post as it is not my intention to upset anyone on this board.
… On Apr 20, 2019, at 11:49 AM, Barabba11 ***@***.***> wrote:
If you use Philips bulbs and Echo, without node red, why you posting here?
Instead try to drive bulbs from node red and connect note red to alexa
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#47 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AL4CQUX4X6V6VA2IJ66CJYTPRNQS3ANCNFSM4EPIE7JA>.
|
|
Mate, it's ok, just say that u're looking for extra support here. Try what I suggested |
|
Ok thanksSent from my Samsung Galaxy smartphone.
-------- Original message --------From: Barabba11 <notifications@github.com> Date: 4/20/19 2:58 PM (GMT-08:00) To: originallyus/node-red-contrib-alexa-local <node-red-contrib-alexa-local@noreply.github.com> Cc: JNLA2 <imjnla2@gmail.com>, Comment <comment@noreply.github.com> Subject: Re: [originallyus/node-red-contrib-alexa-local] [known issue] Echo Gen 2 & Echo Plus discovery not working (#47) Mate, it's ok, just say that u're looking for extra support here. Try what I suggested
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/originallyus/node-red-contrib-alexa-local","title":"originallyus/node-red-contrib-alexa-local","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/originallyus/node-red-contrib-alexa-local"}},"updates":{"snippets":[{"icon":"PERSON","message":"@Barabba11 in #47: Mate, it's ok, just say that u're looking for extra support here. Try what I suggested"}],"action":{"name":"View Issue","url":"#47 (comment)"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "#47 (comment)",
"url": "#47 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
![https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open](https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open){kind=link}
|
Does this work with echo dot gen 3? I have this issue with my new one and suspect I'm missing something software wise. |
|
The dot is not an issue -it has no ability to communicate with lighting without a hub. So this method is only for echo plus or higher w hub. Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: jeffl78 <notifications@github.com> Date: 6/1/19 2:43 PM (GMT-08:00) To: originallyus/node-red-contrib-alexa-local <node-red-contrib-alexa-local@noreply.github.com> Cc: JNLA2 <imjnla2@gmail.com>, Comment <comment@noreply.github.com> Subject: Re: [originallyus/node-red-contrib-alexa-local] [known issue] Echo Gen 2 & Echo Plus discovery not working (#47) Does this work with echo dot gen 3? I have this issue with my new one and suspect I'm missing something software wise.
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "#47?email_source=notifications\u0026email_token=AL4CQUQICDXESFHPKAZNDVLPYLURJA5CNFSM4EPIE7JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXJC6Q#issuecomment-497979770",
"url": "#47?email_source=notifications\u0026email_token=AL4CQUQICDXESFHPKAZNDVLPYLURJA5CNFSM4EPIE7JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXJC6Q#issuecomment-497979770",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
Is it the first time you try this module? If so check carefully in other posts how to configure properly the server HTTP it uses |
and others
As a lot of people experienced the new Echoes don't work.
My question is:
Is the usage of the proper skill the only way to reach Alexa, or is the actual code base adjustable in a way that it can adapt to the new situation ?
In the case of ha-bridge it seems to be a sign of adaptation: timing.
See issue bwssytems/ha-bridge#860
Any suggestion?
The text was updated successfully, but these errors were encountered: