node-red-contrib-amazon-echo: Still unable to discover new devices
SUMMARY
Recently got an Echo Dot g3. I have HA installed on a Pi, with NodeRed as an Add-On. My Pi is on my main LAN (vlan 1). My Echo Dot is on my IoT vlan (vlan 10). I have confirmed that both can talk to each other, and I successfully access the hub with:
curl http://192.168.1.xx/api/pi/lights
This works from both the LAN and IoT subnets.
When I ask Alexa to discover devices, nothing is ever found.
I have a Unifi USG, and multicast DNS and UPnP are both on.
ECHO DEVICES
Echo Dot 3rd generation
MODULE VERSION
CONFIGURATION
0.1.10
CONSOLE OUTPUT
None
STEPS TO REPRODUCE
- Create Amazon Echo Hub with all defaults
- Create “Office Lights” echo device and link to hub
- Deploy
- Verify that /api/pi/lights is returning Office Lights info from LAN and IoT
- “Alexa, discover devices” - try from Dot on the IoT and iOS app which is on the LAN.
My Office Lights device is never discovered.
EXPECTED RESULTS
Expected my Office Lights device to be discovered.
ACTUAL RESULTS
Alexa declares that no devices were found.
About this issue
- Original URL
- State: open
- Created 4 years ago
- Comments: 71 (2 by maintainers)
Ok, barabba11, Whatever you say. I’ve been writing software for 30+ years, CTO of several companies. I understand how TCP/IP works. Tried running NR as root and not as root, neither worked. I know how to scan if a process is using port 80 (none were). Tried same VLAN, different VLAN — didn’t work. Tried a Pi, Ubuntu NUC, Windows PC, installed NR directly or with Docker for all — none worked. Removed all firewall and iptables rules — didn’t work.
Bottom line is that multicast and discovery work fine for all devices except this plugin on NR for me.
You need to back off your high horse. You’re not smarter than everyone else.
You probably guys have lack of knownledge how protocol TCP/IP works and how to debug it. I’m reading who is trying to run NR as root (as been told here many times to don’t do that) or who can’t figure out how another service already running on 80.
you simply have a common network problem, there are different people here who asked and find solutions, I suggest you to read all topics