search

armzilla / amazon-echo-ha-bridge

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

Bridge is up but echo doesn't see it? I have a mac and the bridge, the harmony hub and the echo are all on the 2.5GHZ wireless. What do I put into the configuration page? #57

Open synack23 opened 8 years ago

robwbartel commented 8 years ago

In my case the problem was caused by not having the correct —upnp.config.address set. It needs to be like --upnp.config.address=192.168.1.240 where the IP address is the address of the machine the bridge is running on. That wasn't obvious to me from the README. Also note there is what I believe to be a fork of this project at ha-bridge that has more recent activity and looks to me like the future of the project. That one attempts to guess the —upnp.config.address if you don't specify it.

synack23 commented 8 years ago

Thanks but I don't have an issue with the bridge, where my problem is is what do I put into the on and off url sections to access my harmony hub?

audiofreak9 commented 8 years ago

Sounds like you should use a fork of this repository which has a built in Harmony Hub configuration, it's found here: https://github.com/bwssytems/ha-bridge

synergicmind commented 8 years ago

I have similar problem. My bridge is still working fine but no longer discover-able by the echo. Also the existing "devices" in the bridge shows as offline in the alexa app. Any suggestions?

bubba198 commented 8 years ago

I was running my bridge on a Pi Zero using DHCP and whenever its IP changed I had to update --upnp.config.address=192.168.1.240 with the correct new address. Obviously the two much match meaning the upnp command line specified IP and the IP assigned to the eth0 interface. I've since figured how to configure the zero with static IP so the problem went away. This may or may not be the issue here.