search

mabunixda / node-red-contrib-alexa-home

MIT License
32 stars 10 forks source link

Discovery of new devices does not work #53

Closed guardiande closed 4 years ago

guardiande commented 5 years ago

Describe the bug I used to have the Alexa Local Node Red flow until it stopped working yesterday.

After some time I found this flow and understood that it seems to have to do with firmware changes on the Alexa side.

Here's my setup:

History:

Today:

I tried to follow all advices from issue 16.

To Reproduce Steps to reproduce the behavior:

Expected behavior Alexa should find the newly created Alexa Home node.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

mabunixda commented 4 years ago

@jaburges can you post your docker run commandline and flow? alexa and node-red are in the same lan ?

@Tranquility76 yeah it is hard to follow this issues if i am not able to reproduce the issue and there is no other dev available which is able to shed more light into that issue :-(

I know that this is frustrating situation - also on my end as developer of this module

Tranquility76 commented 4 years ago

Hi Martin,

I really appreciate your work and I guess it is not easy to hold the speed Amazon is changing things.

I am curious – what is https://github.com/datech/node-red-contrib-amazon-echo doing different? Because this node works…

jaburges commented 4 years ago

@mabunixda docker:

sudo docker run -it -p 1880:1880 -p 60000:60000 -p 80:80 --user root --name nodered --restart always -v /home/name/docker/node-red/data:/data nodered/node-red-docker:0.20.8-v8 or sudo docker run -it --net host --user root --name nodered --restart always -v /home/name/docker/node-red/data:/data nodered/node-red-docker:0.20.8-v8

flow is just alexa controller tried with 80 or 60000 and node into a debug node (full msg) - but devices are discovered yet by Alexa

jaburges commented 4 years ago

Hi Martin, I really appreciate your work and I guess it is not easy to hold the speed Amazon is changing things. I am curious – what is https://github.com/datech/node-red-contrib-amazon-echo doing different? Because this node works…

i've just tried this node and it has the same issue. I've also tried:

sudo docker run -it -p 1880:1880 -p 80:80 --user root --name nodered --restart always -v /home/name/docker/node-red/data:/data nodered/node-red:latest

Same problem :(

Tranquility76 commented 4 years ago

I am running https://github.com/datech/node-red-contrib-amazon-echo on a Raspi and it just works.

All(!) devices are discovered and react on commands as expected. (Although the node output is slightly different so I had to modify my flows a little bit.)

jaburges commented 4 years ago

are your devices new (port 80) or older, and are you running node-red in a docker?

Tranquility76 commented 4 years ago

Gen2 and Gen3 devices and as written running on a Raspi and not in docker.

Am 17.11.2019 um 10:46 schrieb jaburges notifications@github.com:



are your devices new (port 80) or older, and are you running node-red in a docker?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/mabunixda/node-red-contrib-alexa-home/issues/53?email_source=notifications&email_token=AAYDOERG7N6S7CFH6NPSMNTQUEHHZA5CNFSM4IUQ2OWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIH7CI#issuecomment-554729353, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAYDOEVEMQ33MBP3SJNM7EDQUEHHZANCNFSM4IUQ2OWA.

jaburges commented 4 years ago

switched to https://github.com/datech/node-red-contrib-amazon-echo and that DOES work now on network_mode=host with nodered/node-red:latest

mabunixda commented 4 years ago

closing this one - either you moved to another node or nobody posted problem updates since long time