Device discovery about node-red-contrib-amazon-echo

[Barabba11]

I don't understand well your English, by the way if can't find new divides how that can work?

[wongnam]

@scargill Echo Dot 3rd gen only work on port 80, if you chose to use port different to 80 (eg port:8000 >1024) then you have to use NAT solution to forward the port 8000 to 80, if your system or your Pi already used the port:80 that maybe it's difficult to deal with.

FYR #7

My case:

1. Wiki to fix "Error: listen EACCES: permission denied 0.0.0.0:80" issue.
   Solution:

• Amazon Echo Hub use port:80 which requires Node-Red process to be started with root user. Wiki page for Troubleshooting https://github.com/datech/node-red-contrib-amazon-echo/wiki/Troubleshooting

Another solution:

• for Echo Dot 1 or Echo Dot 2 : Amazon-Echo-Hub use port: >1024

• for Echo Dot 3 : Amazon-Echo-Hub use port:>1024 and use NAT port:80 to port:>1024 eg: port:8000

  • to checked it the port is in use already: sudo iptables -L -n (it was empty, so ok I proceeded)
  • to added a listening port: sudo iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
  • sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8000
  • To save the table and have them automatically after reboot: sudo apt-get install iptables-persistent

2- Can "Amazon Echo Hub" node work with HTTPS enabled Node-Red? Yes
3- Can "Amazon Echo Hub" node work if I have Echo or Echo Dot with multi generation

• Echo Dot 1st gen -> Yes, but color capabilities are missing, maybe relate to Echo itself. (I think this node probably works with the Amazon Echo 1st gen)
• Echo Dot 2nd gen -> Yes, but color capabilities are missing, maybe relate to Echo itself.
• Echo Dot 3rd gen -> Yes. Full function.

[datech]

@scargill I'm constantly testing the module by adding new devices and asking Alexa to run the discovery procedure again. Was the flow deployed?

[scargill]

IU'm running this constantly now, once we resolved the tables issue - I have it on port 8980... translated to 80. Its great. If only it could to temperature properly instead of having to cludge light values. Turn heating up/down, set hesting to 15c... etc would be great. Mind you it does work better with gen 3 dot rather than old gen1.

[datech]

Yep, I understand, but I don't have any control over this one. Echo device is selecting what to send ot the hub for each voice command.

What about to adding a range node on the output of the device node?

[scargill]

I WILL do that, I have a requirement that, it seems none of the fancy stats out there meet...

a) The heating is air source heat punp and should only vary temperature by a small amount - ie a few degrees. Heating up in cold seather takes a long time. (s) whenour home is used for holiday rental in the summer (as we clear off to Spain) I need remote contol - but guest should get short term control only, within the limits we set. They must not be able to mess up timers... AND operation for guests must be trivial. If the remote stat and sensor (WIFI) fail, the box at th heater end must be able to keep heat within reaonable limits. The SALUScontrol we got with the system is utterly useless.

I'm coming to the conclusion I'll have to make my own stat - and ading Alexa overrides would be great.

[datech]

I see. Alexa is always a good addition :)

May we consider this issue as resolved?

[scargill]

Not resolved but not major. As you add more devices to the hub, Alexa "find new devices" says no new devices - but they work (yes, in Alexa).

[datech]

Hm, this could be, because you have multiple devices in your network responding on Alexa SSDP messages or you have a large number of devices linked to the Amazon Echo Node. Discovery process should be completed for 20 sec and if it doesn't Alexa will report that "there are no new devices found". Actually, in the background, the process will continue and at the end, all new devices will be listed in the mobile app.

[scargill]

Thanks Datech - that make sense as they DO work.