I’m running ha-bridge-1.2.2.jar and this is my option string (I don’t have a harmony hub)
pi is 148
vera is 140
-Dupnp.config.address=192.168.1.148 -Dvera.address=192.168.1.140 -Dupnp.device.db=/home/share/echobridge/data/device.db
If I don’t specify the dupnp.config.address IP things don’t work right.
[quote=“boykster”]I’m running ha-bridge-1.2.2.jar and this is my option string (I don’t have a harmony hub)
pi is 148
vera is 140
-Dupnp.config.address=192.168.1.148 -Dvera.address=192.168.1.140 -Dupnp.device.db=/home/share/echobridge/data/device.db
If I don’t specify the dupnp.config.address IP things don’t work right.[/quote]
Have you tried to discover devices in the last couple days? The issue is that the Echo is not able to find ANY devices lately. I lost my entire setup by forgetting and trying to re-learn yesterday.
Amazon claims there has been no update pushed to the Echo in over a month, but this is definitely a new issue.
UPDATE:
I added the Dupnp.device.db line to specify the location of the device.db and added a few devices however they still are not being found by Alexa… ???
Has anyone actually been able to get Alexa to discover a new device in the last week or so?
So, it seems many issues with discovery. We’ll need to do a couple of things to debug.
The traces in the log file will be the only thing we can look at and see the queries for upnp.
[Edit]
FYI - I will not be able to look at these until middle of next week. Sorry… vacation comes first 
FWIW, I’m running 1.2.1 and Alexa s/w 2723 and just tested adding a device with no issues. I only have 11 devices. I use the command below to run the bridge.
nohup java -jar -Dvera.address= -Dupnp.config.address= -Dharmony.address= -Dharmony.user= -Dharmony.pwd=<harmony p/w> ha-bridge-1.2.1.jar&
ETA, on UI5, if that matters
[quote=“tb001, post:1145, topic:187039”]FWIW, I’m running 1.2.1 and Alexa s/w 2723 and just tested adding a device with no issues. I only have 11 devices. I use the command below to run the bridge.
nohup java -jar -Dvera.address= -Dupnp.config.address= -Dharmony.address= -Dharmony.user= -Dharmony.pwd=<harmony p/w> ha-bridge-1.2.1.jar&
ETA, on UI5, if that matters[/quote]
For the heck of it, I modified my RC to run this exactly as you have with the 1.2.1 jar, I can see the server running via port 8080, but NO discovery of Alexa devices… the Server still has my old device list also so truly nothing has changed except the lack of Alexa finding devices.
FWIW, I received my Echo on Christmas and proceeded to set it up the following day, and it is working w/o issue for device discovery, all of this is within the last few days since I just received the device.
Bridge version 1.2.3
Running on Windows 7
~25 devices
Startup command: java -jar -Dupnp.strict=true -Dvtwo.compatibility=false -Dvera.address=192.168.1.128 -Dupnp.config.address=192.168.1.113 -Dserver.port=8081 crush-ha-bridge.jar
Echo Software Version: 2723
Selfish side note, also built out a nice custom Alexa Skill for Directv control: Amazon Echo DirecTV Control via Custom Alexa Skill - YouTube
Thanks for continuing to refine this code Crush157.
@Crush…
a) log file
b) the ha-bridge version <1.2.3>
c) Your hardware host type and OS version <Synology DSM 5.0>
d) the number of devices you have <30 Wink & 175 Vera>
e) list of your ip addresses for your devices… the Vera, The Echo, The host (PI2), the harmony
f) the router or routers you have. <HP Procurve, no firewall>[/quote]
#!/bin/sh
nohup java -jar -Dtrace.upnp=true -Dupnp.strict=true -Dvera.address=192.168.2.71 -Dupnp.config.address=192.168.2.50 -Dserver.port=8099 -Dupnp.response.port=50099 /volume1/@appstore/HAbridge/HAbridge.jar 2>&1 | tee /volume1/@appstore/HAbridge/HAbridge.log &
exit 0
[quote=“tb001, post:1145, topic:187039”]FWIW, I’m running 1.2.1 and Alexa s/w 2723 and just tested adding a device with no issues. I only have 11 devices. I use the command below to run the bridge.
nohup java -jar -Dvera.address= -Dupnp.config.address= -Dharmony.address= -Dharmony.user= -Dharmony.pwd=<harmony p/w> ha-bridge-1.2.1.jar&
ETA, on UI5, if that matters[/quote]
So our second echo arrived today, sooner than expected. Just finished setting it up and no issues discovering devices. This one is also on version 2723. Sorry for those who are having issues. Hopefully something here will be helpful. We use the Comcast xfinity modem that has a dual band network–I know that’s caused issues for us in the past.
[quote=“Aaron, post:1148, topic:187039”]@Crush…
a) log file
b) the ha-bridge version <1.2.3>
c) Your hardware host type and OS version <Synology DSM 5.0>
d) the number of devices you have <30 Wink & 175 Vera>
e) list of your ip addresses for your devices… the Vera, The Echo, The host (PI2), the harmony
f) the router or routers you have. <HP Procurve, no firewall>[/quote]
#!/bin/sh
nohup java -jar -Dtrace.upnp=true -Dupnp.strict=true -Dvera.address=192.168.2.71 -Dupnp.config.address=192.168.2.50 -Dserver.port=8099 -Dupnp.response.port=50099 /volume1/@appstore/HAbridge/HAbridge.jar 2>&1 | tee /volume1/@appstore/HAbridge/HAbridge.log &
exit 0
[/quote]
Is the IP address for your echo 192.168.2.148?
If so it asked all the right requests to the bridge.
So, you also have a lot of devices. There have been some issues on the number of devices the echo can deal with. For the vera, can you just put in 5 devices in the bridge and test it.
Thanks
[quote=“crush157, post:1144, topic:187039”]So, it seems many issues with discovery. We’ll need to do a couple of things to debug.
The traces in the log file will be the only thing we can look at and see the queries for upnp.
[Edit]
FYI - I will not be able to look at these until middle of next week. Sorry… vacation comes first :)[/quote]
a) log file (see attachment)
b) the ha-bridge version - 1.2.3
c) Your hardware host type and OS version - RPI on Debian ver 7.8
d) the number of devices you have- 54
e) list of your ip addresses for your devices… the Vera-192.168.1.24, The Echo-192.168.1.4, The host (PI2)-192.168.1.51, the harmony-192.168.1.11
f) the router or routers you have.-- Netgear WNDR3700
[quote=“lemrock, post:1151, topic:187039”][quote=“crush157, post:1144, topic:187039”]So, it seems many issues with discovery. We’ll need to do a couple of things to debug.
The traces in the log file will be the only thing we can look at and see the queries for upnp.
[Edit]
FYI - I will not be able to look at these until middle of next week. Sorry… vacation comes first :)[/quote]
a) log file (see attachment)
b) the ha-bridge version - 1.2.3
c) Your hardware host type and OS version - RPI on Debian ver 7.8
d) the number of devices you have- 54
e) list of your ip addresses for your devices… the Vera-192.168.1.24, The Echo-192.168.1.4, The host (PI2)-192.168.1.51, the harmony-192.168.1.11
f) the router or routers you have.-- Netgear WNDR3700[/quote]
Correction: My Vera address is 192.168.1.2
a) log file
b) the ha-bridge version: 1.2.3
c) Your hardware host type and OS version: RPi 2, Raspian
d) the number of devices you have: only registered 10 w/ Server right now.
e) list of your ip addresses for your devices… the Vera, The Echo, The host (PI2), the harmony
Vera: 192.168.1.84. Echo; 192.168.1.112: RPi: 192.168.1.135. Harmony 192.168.1.141.
f) the router or routers you have. Netgear R6700 running DD-WRT v24-sp2 (03/23/15) kongac - build 26500M
. I have WIFI off on this and running a Ubiquit AC-LR access point.
RC.LOCAL:
#!/bin/sh -e
#
# rc.local
#
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
# Print the IP address
_IP=$(hostname -I) || true
if [ "$_IP" ]; then
printf "My IP address is %s\n" "$_IP"
fi
#The following is for multiple emulators on the same machine
echo "Starting the Echo Bridge Emulators"
Amazon_Echo_IP=192.168.1.112
echo "Amazon Echo address is: $Amazon_Echo_IP"
ISY_IP=192.168.1.135
NUMBER_OF_BRIDGES=1
BASE_PATH=/home/pi/echobridge
#Linked File
JAR_FILE=${BASE_PATH}/ha-bridge.jar
STARTING_PORT=8081
STARTING_UPNP_PORT=50001
HARMONY_PORT=8090
HARMONY_IP=192.168.1.141
HARMONY_USER=xxx
HARMONY_PWD=xxx
DATA_PATH=${BASE_PATH}/data
LOG_PATH=${BASE_PATH}/logs
# Make directoris if they don't exist
[ ! -d ${DATA_PATH} ] && mkdir -p ${DATA_PATH}
[ ! -d ${LOG_PATH} ] && mkdir -p ${LOG_PATH}
echo "Starting the Echo Bridge Emulators"
for i in $(seq 1 ${NUMBER_OF_BRIDGES})
do
nohup java -jar -Dvera.address=${ISY_IP} -Dupnp.config.address=${_IP} -Dserver.port=${STARTING_PORT} \
-Dupnp.response.port=${STARTING_UPNP_PORT} -Dtrace.upnp=true -Dupnp.strict=false -Dupnp.device.db=${DATA_PATH}/device_${STARTING_PORT}.db \
${JAR_FILE} > ${LOG_PATH}/log_${STARTING_PORT}.txt 2>&1 &
STARTING_PORT=$((STARTING_PORT + 1))
STARTING_UPNP_PORT=$((STARTING_UPNP_PORT + 1))
done
#Running Harmony emulator separately
#Remove the # if you have Harmony Hub
echo "Starting Harmony emulator at $HARMONY_PORT"
nohup java -jar -Dupnp.config.address=${_IP} -Dharmony.address=${HARMONY_IP} -Dharmony.user=${HARMONY_USER} -Dharmony.pwd=${HARMONY_PWD} -Dserver.port=${HARMONY_PORT} -Dupnp.response.port=${STARTING_UPNP_PORT} -Dupnp.device.db=${DATA_PATH}/device_${HARMONY_PORT}.db ${JAR_FILE} >${LOG_PATH}/log_${HARMONY_PORT}.txt 2>&1 &
echo "the rc.local script has completed."
exit 0
Hi All,
I’m using BWS Systems’ HA Bridge v1.2.3 and works perfectly with my Amazon Echo.
However, I’m trying to use it with Sleep As Android, release 20150909 for it’s SmartLight feature and it’s not connecting. SmartLight allows you to use your Hue to do sunrise wakeups and other neat tricks.
Wireshark sees my phone successfully finding the HA Bridge with SSDP and sends GET http://{hostIP}/api/p4wRzZXQosjoQhC3 , to which the bridge responds with HTTP/1.0 404 NOT FOUND
The application never proceeds beyond this and doesn’t download the description.xml or may any further connections.
From my reading of the Hue specs, /api/p4wRzZXQosjoQhC3 is an authentication request and the Hue hub will respond favorabily if the link button is pressed.
My command line is java -jar -Dvera.address=192.168.42.86 -Dserver.port=8082 -Dtrace.upnp=true -Dupnp.strict=false ha-bridge-1.2.3.jar
I’ve tried -Dupnp.strict=true and false with the same result
Help please? upnp log and packet captures are attached.
[quote=“kchung, post:1154, topic:187039”]Hi All,
I’m using BWS Systems’ HA Bridge v1.2.3 and works perfectly with my Amazon Echo.
However, I’m trying to use it with Sleep As Android, release 20150909 for it’s SmartLight feature and it’s not connecting. SmartLight allows you to use your Hue to do sunrise wakeups and other neat tricks.[/quote]
OK i figured out the problem; the application along with the official Hue app is hard set to use 80/tcp instead of following what was advertised via the SSDP response. Turns out Skype was listening on 80/tcp and sending the 404’s. The app was able to see my HA Bridge once I terminated Skype and relaunched the HA bridge with -Dserver.port=80. I’ll contact the developer…
Got a new weird one for you!
I can setup a new device using the configurator (i’m on 1.2.2) using the dimming (percentage) selection.
This works great on my Leviton dimmers, but not on my GE dimmers. Confirmed across multiple devices.
So to be clear, on/off and dimming works great on Leviton dimmers.
Only on/off works on my GE dimmers. If I say “alexa, dim hallway to 25%” (GE dimmer)… she responds “OK”, but nothing happens.
[quote=“tomgru”]Got a new weird one for you!
I can setup a new device using the configurator (i’m on 1.2.2) using the dimming (percentage) selection.
This works great on my Leviton dimmers, but not on my GE dimmers. Confirmed across multiple devices.
So to be clear, on/off and dimming works great on Leviton dimmers.
Only on/off works on my GE dimmers. If I say “alexa, dim hallway to 25%” (GE dimmer)… she responds “OK”, but nothing happens.[/quote]
If the on off commands for the different devices are exactly the same in the configurator, then it’s an issue with your vera and how your ge devices are set up on your vera. If they are set up as dimmable lights, it should work but if they are set up as switches, then it won’t work because vera only controls on and off for them.
I have dimmable ge lights set up on my vera and echi can dim then just fine. I have a non dimmable ge switch as well and it is recognized as a basic switch by the vera. No dimming.
In summary, do your ge devices have the dimming slider in the vera interface? Or just an on off switch?
Friend of mine came across this Echo → SmartThings Hub → Harmony Hub tutorial and just told me about it. Essentially is allows you to control your Harmony Hub with your Echo, anyone else know about this or tried it?
Well we are already doing that now with VERA and this bridge.
Echo----> VERA -----> Harmony Hub
Only difference they are using smarthings hub vs. vera hub.
I got my Hunter Douglas PowerView blinds working with the Amazon to Vera bridge. Works very nicely.
I’m not sure how/why buy Alexa understands Turn On/Turn Off due to the Philips Hue bulbs, but she also understands Open/Close.
I’m able to say something like “Open Family Room Blinds” and it will trigger the OnUrl specified in the bridge app device entry.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules