hi everyone,
did anyone notice that node-red-contrib-alexa-local stopped working. no discovery of new devices and existing devices dont fucntion anymore.
(everything here is up to date)
there is already an issue on github.
anyone can confirm it or has a solution?
bye,
j.
Amazon apparently has pushed a new firmware updated that breaks it.
More ppl are now reporting this issue. Probably due to rolling updates. Mine went out over three weeks ago.
Still haven’t found a solution but some are saying you can change the listening port to 80 and it will work again. I’ve read mixed results about that though. Seems to work for some and not others.
Had the same problem. For some reason, I was able to delete and relearn some of my alexa devices, and it worked for a week or so, then stopped working again a couple days ago.
I switched to this:
node-red-contrib-alexa-home-skill
Downside is you need to create an account on their site, and define the devices there, but works fine for me after doing that and following the directions there. One tip was when you need to link and search for Node-RED with the app, I got multiple hits. Picked the first choice, and it was the right one.
I did have to change any switch nodes I had tied to an alexa node in node red. Changed them to use ifTrue and ifFalse and then the switch logic works fine with home-skill. The output from the home-skill node is boolean for turning on a light or switch. With Alexa, I mostly just turn things on, so I was just using on/off, so boolean works for me instead.
An advantage is discovery seems to work better. With local discovery was always a pain for me, often had to try multiple times before alexa would find it. With home-skill, seems to find on first try.
One downside I noticed when I tried to turn on a light in the middle of the night was I had to try a few times before it turned on. But after that, it worked on first try.
Will need to see how that goes.
Randy