if new devices are added to an existing structure, they are no longer recognized

[ArchGithub]

Good evening,
I have been using the Amazon Eco device Palette for some time now.

I could detect two problems.
1, I have over 360 devices in my system.
Many devices seem to be recognized twice or three times from old shortcuts. Therefore all old devices have to be removed after a function test by hand using the Alexa app. Can the system be cleaned completely.

2. if new devices are added to an existing structure, they are no longer recognized. How can I retrigger the search.

[a-bailey]

Had the same problem, I noticed there is a new config on the Amazon Echo Hub Node "Device discovery" if thats not enabled the device discovery server will not be started. Check that node you might have the same problem.

[Barabba11]

Let me know please if your problema was "no new devices discovered" answer from Alexa or that simply she returns a bad sound after telling the command (error inside her).

[truresma]

it's a pity no one here writes the answer...

1. sudo iptables -t nat -L --line-numbers (if it doesn't say anything about 8083/your port, then it's clear that it doesn't work)
2. sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
3. sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8083
4. For the Node-Red Adapter insert port 8083 at the "Amazon Echo Hub" node and click deploy in the upper right corner and it works or it finds the devices and it is green.
5. Another time sudo iptables -t nat -L --line-numbers (see if it says 8083, if it does then it should work)
   Now the whole thing must be saved permanently if the device is restarted
6. sudo apt-get install iptables-persistent
7. sudo bash -c "iptables-save > /etc/iptables/rules" | or service iptables save | if the 1 does not work, in any case the problem is the saving

It does not work with most of them because it is not saved permanently and the port forwarding is gone again at the next restart. Therefore save the iptable or port forwarding at the end.

---

Ich finde es schade, dass keiner hier die Lösung schreibt...

1. sudo iptables -t nat -L --line-numbers (wenn hier nichts von 8083/euren Port steht, dann ist es klar, dass es nicht geht)
2. sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
3. sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8083
4. Bei dem Node-Red Adapter bei dem "Amazon Echo Hub" Node den Port 8083 einfügen und oben rechts deploy klicken und es funktioniert bzw. er findet nun die Geräte und es ist grün.
5. Nochmal sudo iptables -t nat -L --line-numbers (gucken ob da nun 8083 steht, wenn ja dann sollte es gehen)
   Nun muss das Ganze noch dauerhaft gespeichert werden falls das Gerät neugestartet wird
6. sudo apt-get install iptables-persistent
7. sudo bash -c "iptables-save > /etc/iptables/rules" | oder service iptables save falls das 1 nicht gehen sollte, auf jeden Fall ist die Speicherung das Problem

Es geht bei den meisten nicht da es so nicht dauerhaft gespeichert wird und beim nächsten Neustart die Portweiterleitung wieder weg ist. Deshalb am Ende das iptable bzw. die Portweiterleitung speichern.

[ArchGithub]

Hello BlackRedM,

i.e. you use port 8083 and not port 8080.
I had always used port 80 and Process. As requested in the interface for newer devices.
DEVICE DISCOVERY has now created the same device 5 times for me.

If I may ask, how do the settings look exactly at your place?

That means I have to save the port forwarding once or every time I change it in node-red?

Many greetings

[truresma]

I thought alexa couldn't find the newly added devices.
If you don't use Port 80 already that is another problem.

[ArchGithub]

A detailed description of my approach

1. I used port 80 and set Process. As it should be done with newer devices.

2. many devices were found but not all. Also no more devices were found when new ones were added in Node-RED. (now about 300 devices). But in Node-RED the devices are online.

3. then I turned on device recovery. After that I had many devices double, triple or quadruple. (Display approx. 640 devices) However, many devices with the same name do not work. Probably from older shortcuts, because I tried something.
   So I deactivated and removed the not working devices from old shortcuts via the app. The devices basically worked again if only one name was available.
   Unfortunately, it seems that I also got some working devices.

4. now I have the problem that some devices are missing. These are not found after about one week.

[Barabba11]

maybe your echo does not support 300 devices?
As told many times, you probably need to remove all devices, remove all echos fro alexa account, reset hardware the echo, add again echo to account, search for devices. Wait 1-2 hours, it happened to me some devices were discover later, this is a problem of echo, not the module.
Remember that if you restore a backup in the NR flow you will have all devices unresponsive. Do again reset.

[ArchGithub]

maybe your echo does not support 300 devices?
As told many times, you probably need to remove all devices, remove all echos fro alexa account, reset hardware the echo, add again echo to account, search for devices. Wait 1-2 hours, it happened to me some devices were discover later, this is a problem of echo, not the module.
Remember that if you restore a backup in the NR flow you will have all devices unresponsive. Do again reset.

I have already removed devices (commands), there were already considerably more. I don't think this is the problem. According to Amazon the number of devices is not limited either.

[ArchGithub]

Es wird immer interessanter, mein System findet immer mehr Geräte mit dem gleichen Namen!