Skip to content
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

Device is unresponsive #130

Closed
EspElement opened this issue Jun 24, 2020 · 5 comments
Closed

Device is unresponsive #130

EspElement opened this issue Jun 24, 2020 · 5 comments

Comments

@EspElement
Copy link

All custom devices are now all the sudden unresponsive. I suspect Echos had an update? I do not see anything new in HA or Node Red to indicate update needs.

I have tried many things in my network, and all points to loss of the Node Red function of the custom commands. Example, my hue lights still work.

I have Echo Gen 2 and two Echo Gen 3 Dots. I am running HA thru Docker and Node Red add on, so I should be free to pull anything as needed, just need the commands.

Thanks!
Joshua

@Barabba11
Copy link

Did you restored a backup recently? When you do that the devices will have a new ID, so the old ID Alexa learned become unresponsive.
Try to search for new devices. Or, delete all, unassociate device from your account and reset Echo, search again. Be sure that the device discovery is enabled in hub, default is disabled.

@EspElement
Copy link
Author

EspElement commented Jun 27, 2020

Yes and no, I have restored a backup but it worked fine then. Here is what I have tried now.

Tried removing all from Alexa App and readd, not getting the connection when discovering devices.
Tried using iptables to change port to 8080 to see if that works (in node red, it says the hub is connected with or without doing this, so not sure what the deal is).
Tried adding a new device node with a brand new name with no dice.
I have discovery checked, and right now it is set to process (not sure what the differences are in the selections process, process output, process output on state change). I do have it processing input to change state of tasmota devices

Something ODD. I changed it to a no name port and it says it is online... I cannot see this being possible? Maybe that is my issue?

Running on RP4 with Raspberry PI OS and running Hassio Root thru Docker. It has worked just fine until recently, not sure why I am experiencing it. I may consider installing HassOS just to be sure but it is nice to overclock the RP4 and I cannot with HassOS. I have another card coming today, so I may give that a shot just to see.

@EspElement
Copy link
Author

So after an install of HassOS and restoring a backup, I tried to put a new one in, and what do you know, it worked! Thanks guys

Cheers
Joshua

@Barabba11
Copy link

Since the author will not introduce the unique ID for devices never restore any backup, our you will have your device unresponsive. You better copy the flow files and restore them manually

@EspElement
Copy link
Author

Had to replace nodes with new ones and new names for Alexa to detect new device. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants