Devices not discoverable on large network

[miefda]

Hi,

in the last months i read nearly all the issues reported regarding this topic and i couldnt find anything that helped.. Here is my setup:

My network is 192.168.0.0/16

node-red inside Docker with direct Host network running on 192.168.1.252/16

• port 80 - description.xml can be reached from every device in the network Alexa native and Alexa Sonos devices in 192.168.240.X/16

Phillips Hue Bridge in 192.168.2.16/16

the Philipls Hue devices get discovered by Alexa Nodered Device dont get discovered.

any ideas ?

[Barabba11]

what is nodered device? What it is useful for? I only have Philips Hue devices

[Barabba11]

Another important info, the network 192.168.x.x is defined as class C, not as class B /16 as you pretend it works. NOt all devices will accept to broadcast on /16 if the net should be /24. On the other side a network A 10.x.x.x could be restricted as B, so I strongly suggest you to use 10.x addresses

[miefda]

CIDR 192.168.0.0/16 is a valid subnet.

I can even receive the ssdp broadcasts and the xml from my smarthphone

[Barabba11]

it is just not natural, you can't be sure all devices will work properly. For such trubles you can loose days before discovering that didn't work because of that, I prefer avoid such cases. I've read back your first post, seems your node red can't be discovered by Alexa at all, you probably have problem in Docker, there are lot of topics with the same problem, have a deep read and you will find solutions

[miefda]

as i said, i can see every broadcast message from the ssdp, and i can also get the xml and api access. what i dont know: is the xml data correct? or is there a compatibility issue with with my devices (Alexa Echo gen 1 and SONOS ONE)

[Barabba11]

what is the ssdp device? You told you have real philips bulbs and one Docker too, where broadcast coming from? Bulbs or Docker? Are you sure your Docker works? Have you tried power out all real Philips devices and let only Docker? Have you deep reset Echo as written in many posts here? Have you read troubleshooter too?

[miefda]

• SSDP is the service used by node-red-contrib-amazon-echo to send the broadcast messages
• the node-red-contrib-amazon-echo SSDP Service is received by my notebook (wireshark) and my Phone (upnp discover)
• the Port 80 XML data is retrievable from within the network
• the broadcast is from 192.168.1.252 which is my node-red docker container (host network)
• another broadcast in the network from my original phillips hue bridge is also present
• i factory reset all 8 Alexa capable devices including a smart TV
• discovery is not working for node-red-contrib-amazon-echo devices
• discovery is working with original phillips hue bridge
• node-red-contrib-amazon-echo is using port 80
• node-red is running in privileged mode
• i have only one network interface on the node-red machine (no Wifi) (no multiple IPs)

and just jet i tried discovery while having the original hue bridge unpowered - nope doesn't work -.- I think i have to try out some alternatives -.-

[Barabba11]

well, now is pretty clear :) NR is recomended to don't install with root privileges, neither load it with sudo, I suggest you to try reinstall all following their guide. Seems stupid but it's not.. it uses other paths for install and it can not manage correctly files

[Barabba11]

Pls report us the results

[nighknight]

You wrote that you tested it with the original hue bridge unpowered, but maybe there is some caching effect?

Source: https://www.philips-hue.com/en-us/support/friends-of-hue#Can_I_add_two_Hue_Bridges_to_Alexa