Closed Radstake closed 7 years ago
Isn't 0.0.0.0 the bind address for the service? And doesn't discovery use multicast and not broadcast?
Maybe it is a fallback when multicast doesn’t work? Nothing worked, when I changed it to 192.168.178.255 - my channel - everything worked fine!
Op 25 sep. 2017 om 18:21 heeft Mat Phillips notifications@github.com het volgende geschreven:
Isn't 0.0.0.0 the bind address for the service? And doesn't discovery use multicast and not broadcast?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
so strange, since today everthing stoped working, even when using master, with the local changes I made. Could some remote service have changed. Whatever I do, what ever I put in index.js, it always listens to 0.0.0.0
In cases where the network can't find the light, it is due to a non supported broadcast address. E.g my network didn't find the light, but when I hardcoded changed the
0.0.0.0
to my*.255
, it worked. Therefore made the broadcast address optional in the config.When a platform is defined AND
"broadcastAddress"
is set, it will used that one. In all other cases it will use the default0.0.0.0