search

originallyus / node-red-contrib-alexa-local

An easy-to-use NodeRED node for adding Alexa capability to NodeRED. NO Alexa Skills required.
107 stars 25 forks source link

[known issue] Echo Gen 2 & Echo Plus discovery not working #47

Open fenyvesi opened 6 years ago

fenyvesi commented 6 years ago

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?

ArnieX commented 6 years ago

I have the same issue. I got Echo 2 with this node in mind, so I hope it will be possible to fix.

LennartHennigs commented 6 years ago

+1. I got it working (without a problem) on a friends 1st gen Echo Dot. But on my new one it wasn't detected.

torinnguyen commented 6 years ago

Version 0.3.15 contains a possible fix for Echo Dot Gen 2 implemented by the folks at habridge. Please give it a try.

LennartHennigs commented 6 years ago

hi, I just installed it on the latest version of node red and tested it with a second gen alexa:

12 Mar 19:43:09 - [info] Node-RED version: v0.18.4 12 Mar 19:43:09 - [info] Node.js version: v8.6.0 12 Mar 19:43:09 - [info] Darwin 17.4.0 x64 LE

unfortunately, the device is not detected. the node detects that alexa is looking for devices (discovery") but it is not found. nor is the discovery state exited. sorry.

torinnguyen commented 6 years ago

ok. thanks for testing. I'll dig further into this.

torinnguyen commented 6 years ago

@LennartHennigs L I've just tested with my Echo Dot 2nd Gen. It's working! You may want to try again after restart your Echo. Some folks reported that you need to restart Echo to clear up 'bad' discovery cache.

torinnguyen commented 6 years ago

Please try again with v0.3.18. There's something new in discovery protocol being implemented.

fenyvesi commented 6 years ago

I just installed the node with npm. It seems not to work when I initiate discovery from Amazon client in a browser. I use node.js: v8.9.4, node-red: v0.18.0

What are the versions that work?

oeuviz commented 6 years ago

I can confirm that after upgrading it did start to work with a 2nd gen Echo. Seems fixed to me, thank you very much!

fenyvesi commented 6 years ago

@oeuviz What are the node.js and node-red versions?

torinnguyen commented 6 years ago

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.

fenyvesi commented 6 years ago

I installed 0.3.18 version with npm. No input node to alexa, connected debug output shows nothing, discovery from browser finds nothing. A stupid question: The node-red runs on a wire-connected server, the Echo is wirelessly connected to an Access Point. The router is not the AP that Echo connects to. Both addresses are 192.168.0.X. I think it should work. May be not?

torinnguyen commented 6 years ago

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.

fenyvesi commented 6 years ago

Strange. The discovery status is set 10 minutes (!) after initiating discovery. Seems to be a router/ networking setup problem.

oeuviz commented 6 years ago

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~exp1+rpi19+stretch, 4.9.51-1+rpi3), libcurl3:armhf (7.52.1-5, 7.52.1-5+deb9u4), libapt-inst2.0:armhf (1.4.7, 1.4.8), libldap-2.4-2:armhf (2.4.44+dfsg-5, 2.4.44+dfsg-5+deb9u1), openssl:armhf (1.1.0f-3, 1.1.0f-3+deb9u1), libwbclient0:armhf (2:4.5.8+dfsg-2+deb9u1, 2:4.5.12+dfsg-2+deb9u1), apt:armhf (1.4.7, 1.4.8), nodered:armhf (0.17.4, 0.18.4), cpp-6:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), dbus:armhf (1.10.18-1, 1.10.24-0+deb9u1), dhcpcd5:armhf (1:6.10.1-1+rpi3, 1:6.11.5-1+rpt4), libsqlite3-0:armhf (3.16.2-5, 3.16.2-5+deb9u1), libicu57:armhf (57.1-6, 57.1-6+deb9u1), pi-bluetooth:armhf (0.1.6, 0.1.7), bind9-host:armhf (1:9.10.3.dfsg.P4-12.3+deb9u2, 1:9.10.3.dfsg.P4-12.3+deb9u4), perl-modules-5.24:armhf (5.24.1-3+deb9u1, 5.24.1-3+deb9u2), raspi-copies-and-fills:armhf (0.5-1, 0.6), libncurses5:armhf (6.0+20161126-1, 6.0+20161126-1+deb9u1), python3-pip:armhf (9.0.1-2+rpt1, 9.0.1-2+rpt2), openssh-sftp-server:armhf (1:7.4p1-10+deb9u1, 1:7.4p1-10+deb9u2), libk5crypto3:armhf (1.15-1, 1.15-1+deb9u1), libisc160:armhf (1:9.10.3.dfsg.P4-12.3+deb9u2, 1:9.10.3.dfsg.P4-12.3+deb9u4), libasan3:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), firmware-atheros:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt2), xkb-data:armhf (2.19-1, 2.19-1+deb9u1), libapt-pkg5.0:armhf (1.4.7, 1.4.8), gcc-6-base:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), libncursesw5:armhf (6.0+20161126-1, 6.0+20161126-1+deb9u1), firmware-libertas:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt2), raspberrypi-kernel:armhf (1.20170811-1, 1.20171029-1), libgcc1:armhf (1:6.3.0-18+rpi1, 1:6.3.0-18+rpi1+deb9u1), libperl5.24:armhf (5.24.1-3+deb9u1, 5.24.1-3+deb9u2), raspberrypi-bootloader:armhf (1.20170811-1, 1.20171029-1), libisc-export160:armhf (1:9.10.3.dfsg.P4-12.3+deb9u2, 1:9.10.3.dfsg.P4-12.3+deb9u4), libgcc-6-dev:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), libubsan0:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), g++-6:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), libtinfo5:armhf (6.0+20161126-1, 6.0+20161126-1+deb9u1), firmware-brcm80211:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt2), libkrb5support0:armhf (1.15-1, 1.15-1+deb9u1), libgfortran3:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), ssh:armhf (1:7.4p1-10+deb9u1, 1:7.4p1-10+deb9u2), samba-common:armhf (2:4.5.8+dfsg-2+deb9u1, 2:4.5.12+dfsg-2+deb9u1), bluez-firmware:armhf (1.2-3+rpi2, 1.2-3+rpt3), libldap-common:armhf (2.4.44+dfsg-5, 2.4.44+dfsg-5+deb9u1), gcc-6:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), liblwres141:armhf (1:9.10.3.dfsg.P4-12.3+deb9u2, 1:9.10.3.dfsg.P4-12.3+deb9u4), gpgv:armhf (2.1.18-6, 2.1.18-8~deb9u1), ncurses-term:armhf (6.0+20161126-1, 6.0+20161126-1+deb9u1), libgomp1:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), wpasupplicant:armhf (2:2.4-1, 2:2.4-1+deb9u1), xxd:armhf (2:8.0.0197-4, 2:8.0.0197-4+deb9u1), libraspberrypi0:armhf (1.20170811-1, 1.20171029-1), ncurses-bin:armhf (6.0+20161126-1, 6.0+20161126-1+deb9u1), openssh-server:armhf (1:7.4p1-10+deb9u1, 1:7.4p1-10+deb9u2), apt-utils:armhf (1.4.7, 1.4.8), iproute2:armhf (4.9.0-1, 4.9.0-1+deb9u1), openssh-client:armhf (1:7.4p1-10+deb9u1, 1:7.4p1-10+deb9u2), libdb5.3:armhf (5.3.28-12, 5.3.28-12+deb9u1), firmware-misc-nonfree:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt2), libdns162:armhf (1:9.10.3.dfsg.P4-12.3+deb9u2, 1:9.10.3.dfsg.P4-12.3+deb9u4), ncurses-base:armhf (6.0+20161126-1, 6.0+20161126-1+deb9u1), libxml2:armhf (2.9.4+dfsg1-2.2+deb9u1, 2.9.4+dfsg1-2.2+deb9u2), libgnutls30:armhf (3.5.8-5+deb9u2, 3.5.8-5+deb9u3), perl:armhf (5.24.1-3+deb9u1, 5.24.1-3+deb9u2), rsync:armhf (3.1.2-1, 3.1.2-1+deb9u1), libisccc140:armhf (1:9.10.3.dfsg.P4-12.3+deb9u2, 1:9.10.3.dfsg.P4-12.3+deb9u4), wget:armhf (1.18-5, 1.18-5+deb9u1), libatomic1:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), libbind9-140:armhf (1:9.10.3.dfsg.P4-12.3+deb9u2, 1:9.10.3.dfsg.P4-12.3+deb9u4), libssl1.1:armhf (1.1.0f-3, 1.1.0f-3+deb9u1), libtasn1-6:armhf (4.10-1.1, 4.10-1.1+deb9u1), libcc1-0:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), raspberrypi-sys-mods:armhf (20170717, 20180103), libstdc++6:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1), curl:armhf (7.52.1-5, 7.52.1-5+deb9u4), python-pip-whl:armhf (9.0.1-2+rpt1, 9.0.1-2+rpt2), libidn2-0:armhf (0.16-1, 0.16-1+deb9u1), libcurl3-gnutls:armhf (7.52.1-5, 7.52.1-5+deb9u4), sensible-utils:armhf (0.0.9, 0.0.9+deb9u1), base-files:armhf (9.9+rpi1+deb9u1, 9.9+rpi1+deb9u3), tzdata:armhf (2017b-1, 2017c-0+deb9u1), libstdc++-6-dev:armhf (6.3.0-18+rpi1, 6.3.0-18+rpi1+deb9u1)

syaoyou commented 6 years ago

I just installed it on the latest version of node red and tested it with a alexa echo ( Japanese):

Node-RED version: v0.18.4 node-red-contrib-alexa-local:v0.3.18.

the node detects that alexa is looking for devices (discovery") but it is not found. Is there the environment or settings required to use node-red-contrib-alexa-local?

asitobv commented 6 years ago

I'm running Node-RED on Ubuntu 16.04.4 LTS.

18 Mar 17:00:50 - [info] Node-RED version: v0.18.4 18 Mar 17:00:50 - [info] Node.js version: v8.10.0 18 Mar 17:00:50 - [info] Linux 4.4.0-116-generic x64 LE

My Echo Plus software level: image

In my flow I've created a node called "Kitchen": image

Node-red is listening on the port: image

There is no firewall enable: image

Alexa doesn't discover the device(s) in Node-RED.

torinnguyen commented 6 years ago

Unfortunately Echo Plus is not supported at the moment

m0rph2k commented 6 years ago

Hi

Same problem Echo Dot Gen2 works. Echo Spot --> the node detects that alexa is looking for devices (discovery") but it is not found.

torinnguyen commented 6 years ago

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 notifications@github.com 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 https://github.com/originallyus/node-red-contrib-alexa-local/issues/47#issuecomment-376470573, or mute the thread https://github.com/notifications/unsubscribe-auth/AAu1WHqMwwThDtAA5W5sgK5z4efh3PHLks5tig-igaJpZM4R6CfS .

-- http://originally.us

m0rph2k commented 6 years ago

here a photo but for what ? Photo --> Echo Dot Gen2 works

Echo Spot --> Unsupported?

LennartHennigs commented 6 years ago

Hey @torinnguyen, I updated your node to 0.3.19, restarted the Dot and still no luck. Any ideas?

LennartHennigs commented 6 years ago

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?

m0rph2k commented 6 years ago

Hi, yes my Echo Spot and Dot Gen2 find Devices with node-red-contrib-wemo-emulator

torinnguyen commented 6 years ago

great. I'll see what I can do.

torinnguyen commented 6 years ago

@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? I made some minor changes but I don't have the actual Echo to test.

ArnieX commented 6 years ago

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.

m0rph2k commented 6 years ago

Hi. Dot 2 discovered devices but now with 0-100% bar, old version On / Off (alexa app) Echo Spot same problem discovery not working :(

LennartHennigs commented 6 years ago

Hi, unfortunately the Echo 2 did not find a new device. Removed and reinstalled the node. Stopped and restarted node-red. Reboot the Echo 2 but no avail. Sorry.

Cheers l.

IDmedia commented 6 years ago

It works if you have a Echo Dot 2 in the same network, but not otherwise.

clarkdv commented 6 years ago

Echo Dot 2 on same wifi network as iMac running node red, Dot is not recognized.

hermann1514 commented 6 years ago

Hi, is there any news regarding this problem? I have the same Problem with my echo v2....

haaslukas commented 6 years ago

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.

DocMors commented 5 years ago

What do we have to do to fix this? I'd be happy to get involved, especially to make this work for Echo Plus.

haymaan commented 5 years ago

ive ds218+ with Habridge and alexa 2Gen ,alexa can't dinf anything.HAbridge works great (5.2.1).but no discovery

JDrewes commented 5 years ago

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?

hammondb4 commented 5 years ago

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.... Does this mean Echos should be able to discover other devices?

BloodWorkXGaming commented 5 years ago

Any update on the discovery of the EchoPlus?

patwiken commented 5 years ago

Any update? Does not work for me too with Echo Gen 2

fke222 commented 5 years ago

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.

Barabba11 commented 5 years ago

Hi! Plz don't stop development, we need Echo plus support, thank you a lot!

Barabba11 commented 5 years ago

Working solution for Echo Plus: https://github.com/datech/node-red-contrib-amazon-echo/issues/5

JNLA2 commented 5 years ago

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. A call to Philips revealed this is a known issue. Philips says it is a deficiency of the Echo Plus bridge. Philips discussed this issue and a fix with the Amazon Developer Team more than a year ago. Apparently Amazon would rather frustrate customers than fix the issue in their product. According to Philips the Echo Plus can not clear the old connection from the bulb so they remain in sync to the previous Gen. 1 unit. Philips recommends their Hue bridge which will sync the bulb to the new Echo Plus (as well as provide many more features). Philips and myself wonder why Amazon is keeping this from their customers? They spend endless hours wasting their time and the customers time doing the same troubleshooting over and over expecting a different result.

Barabba11 commented 5 years ago

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

JNLA2 commented 5 years ago

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 notifications@github.com 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 https://github.com/originallyus/node-red-contrib-alexa-local/issues/47#issuecomment-485150564, or mute the thread https://github.com/notifications/unsubscribe-auth/AL4CQUX4X6V6VA2IJ66CJYTPRNQS3ANCNFSM4EPIE7JA.

JNLA2 commented 5 years ago

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 notifications@github.com 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 https://github.com/originallyus/node-red-contrib-alexa-local/issues/47#issuecomment-485150564, or mute the thread https://github.com/notifications/unsubscribe-auth/AL4CQUX4X6V6VA2IJ66CJYTPRNQS3ANCNFSM4EPIE7JA.

Barabba11 commented 5 years ago

Mate, it's ok, just say that u're looking for extra support here. Try what I suggested

JNLA2 commented 5 years ago

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":"https://github.com/originallyus/node-red-contrib-alexa-local/issues/47#issuecomment-485180837"}}} [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/originallyus/node-red-contrib-alexa-local/issues/47#issuecomment-485180837", "url": "https://github.com/originallyus/node-red-contrib-alexa-local/issues/47#issuecomment-485180837", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

jeffl78 commented 5 years ago

Does this work with echo dot gen 3? I have this issue with my new one and suspect I'm missing something software wise.

JNLA2 commented 5 years ago

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": "https://github.com/originallyus/node-red-contrib-alexa-local/issues/47?email_source=notifications\u0026email_token=AL4CQUQICDXESFHPKAZNDVLPYLURJA5CNFSM4EPIE7JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXJC6Q#issuecomment-497979770", "url": "https://github.com/originallyus/node-red-contrib-alexa-local/issues/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" } } ]