-
Notifications
You must be signed in to change notification settings - Fork 25
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
new devices are no longer found, existing ones do not react anymore #99
Comments
same here :( |
1 similar comment
same here :( |
Same here, too. |
bei mir auch das gleiche |
same here seems happen after an firmware update of my echo dot 2 |
And another one. |
Same here. MQTT direct to devices works fine, but Alexa is not recognising devices, and shows them as unresponsive. Does anyone have an interim workaround? |
Same here as well! Glad other people are having this - thought I had broken something |
Switching to Alexa Home helped for me. Be sure to read the (short) documentation thoroughly regarding port 80. |
I got all mine working again by doing this for each 'alexa-local' node:
|
Nope, didn't work for me. Got the new p:# in Step 3, but then in Step 6, Alexa does not discover the new node. I believe that Amazon may have changed the way discovery works, and it's incompatible with the way this node skill functions, hence it's just stopped working. So we're probably in the lap of either the original skill developer or someone with a little more time than me right now to route out and fix the problem. I'm reluctant to switch over to the "port 80" route, as I have other things running on the same machine (Pi!) that would get nobbled if I did. |
@belialboy I'm sorry it didn't work for you - as you can see from my video, everything's back working here. |
Sadly the same thing here, copied the nodes and saw them getting a new ID, but Alexa (Echo Dot, by the way) isn't finding any 'soft' devices anymore. Currently don't have the time to look into the other package using the port 80 route (don't really understand it yet based on the brief explanation). Hopefully some update will make it work automatically again.. :) |
What i've noticed is that for 'hard' switches using @3ative procedure, Alexa is able to find the switches, however this procedure is not able to get 'soft' switches to be recognized same as @hbeekhuis mentions above.
Update: I reverted to changing node to 'node-red-contrib-amazon-echo' as suggested in the other thread and this worked for me. |
look here |
So what is the solution of the Problem? None of my Devices with Alexa-Local in Red Node are working anymore Is the Fix the hole Port reroute thing like @Jibbonator mentioned in a diffrend thread the Solution?
|
Before you post here... |
Cool finaly i understood how it works for now... |
Please refer to my comment in another issue |
For some days I have the phenomenon that my equipment can not be reached. If I delete these from Alexa and try to find new devices, there is unfortunately nothing more.
The text was updated successfully, but these errors were encountered: