search

armzilla / amazon-echo-ha-bridge

emulates philips hue api to other home automation gateways
Apache License 2.0
732 stars 168 forks source link

echo bridge not working on wired lan devices #15

Open megamalain opened 9 years ago

megamalain commented 9 years ago

Amazon Echo will only detect devices if the echo bridge host machine is connected to the LAN wirelessly with the same SSID. echo bridge doesn't seem to support host machines connected to LAN wired (i.e. through ethernet cable). Also, no device detection if a network has 2.5GHz and 5GHz wireless networking with different SSIDs, and Amazon Echo and host are on them respectively.

craigwitter commented 9 years ago

I have mine on the wired network and it detects fine.

On Mon, Jun 29, 2015 at 9:15 AM, megamalain notifications@github.com wrote:

Amazon Echo will only detect devices if the echo bridge host machine is connected to the LAN wirelessly with the same SSID (e.g. no device detection if a network has 2.5GHz and 5GHz wireless networking with different SSIDs, and Amazon Echo and host are on them respectively). Also, echo bridge doesn't seem to support host machines connected to LAN wired (i.e. through ethernet cable).

— Reply to this email directly or view it on GitHub https://github.com/armzilla/amazon-echo-ha-bridge/issues/15.

megamalain commented 9 years ago

@craigwitter I tried this on Pi B+ and Pi 2 on Raspian and Arch with echobridge v0.1.1,v0.1.2,v0.1.3 on wired network with no success until I used wireless networking. What hardware, platform, echobridge version are you using?

okachobi commented 9 years ago

I had a similar problem, and it turned out to be that my wireless AP was not bridging broadcast/multicast traffic between the LAN connection and Wireless interface. Once I enabled multicast bridging, it worked flawlessly.

markfalk commented 9 years ago

Exactly. It’s all done via multicast. The bridge must get traffic destined for the multicast address 239.255.255.250. The echo solicits information by sending to that multicast address, if the bridge doesn’t see it, it can’t respond.

From: okachobi [mailto:notifications@github.com] Sent: Monday, June 29, 2015 7:30 AM To: armzilla/amazon-echo-ha-bridge Subject: Re: [amazon-echo-ha-bridge] echo bridge not working on wired lan devices (#15)

I had a similar problem, and it turned out to be that my wireless AP was not bridging broadcast/multicast traffic between the LAN connection and Wireless interface. Once I enabled multicast bridging, it worked flawlessly.

— Reply to this email directly or view it on GitHub https://github.com/armzilla/amazon-echo-ha-bridge/issues/15#issuecomment-116704672 . https://github.com/notifications/beacon/AG95bK4lTESI8u5UzAef80S-rb3gvJzMks5oYU3ogaJpZM4FOHDA.gif

shanekuz commented 9 years ago

Hi have me echo and amazon-echo-ha-bridge pc on a different subnet and it still works fine, every now and then when I issue a command the echo says it could not contact the device but the device still turns on or off. I will put them on the same subnet and see if that goes away.

okachobi commented 9 years ago

I believe only the initial discovery occurs over multicast. Once the Echo discovers the bridge and queries the services, it appears to save the information and do direct TCP requests to the bridge. I discovered my problem by moving the echo to a different wireless access point that I knew was bridging. It was then discovered and continued to work when it connected with the AP that did not bridge. But running the discovery again would fail.

maddox commented 9 years ago

I have all Airport devices for WLAN at my house:

All devices are set to Bridged mode, as my FIOS router handles DHCP on my network.

I can't, for the life of me, get my Echo or my Harmony hub to see the bridge. Has anyone figured this out? Should the Hue iOS app be able to see the bridge too?

I have Enable IGMP Snooping enabled on my Airport Extreme base station, but I've still had no luck.

maddox commented 9 years ago

OK, ignore me!

I had misspelled --upnp.config.address as --upnp.config.adress

It's working like it should now!!

gbarnabic commented 8 years ago

I had everything working fine on my ubuntu linux computer for a few months when the power supply died. Once I got it back up running again the echo bridge did not work. After a little bit of hair pulling I realized that the IP address on the LAN had changed. So I had to not only change the --upnp.config.address=192.168.1.## parameter when starting the hue echo bridge I also had to change all the device ON and OFF triggers, updating them with the new IP address. Just posting this here for others to see down the road.