Error connection refused in logs about ha-bridge HOT 11 CLOSED

So, there is a bug in url generation that needs to be fixed. It will be coming soon.

Thanks

The Support Team

--------- Original Message --------- Subject: [ha-bridge] Error connection refused in logs (#13)
From: "ckhyatt" [email protected]
Date: 11/30/15 3:40 pm
To: "bwssytems/ha-bridge" [email protected]

First--thanks for the great work on this app!
I have posted this issue on the thread in Vera but I am a new user so I am waiting for a moderator to approve my post. Apologies for the cross post.
I am seeing the same issues as xeinth--Error Calling out to HA Gateway, connection refused (to my VE)--multiple times. It then eventually connects. The UI correctly detects all Devices and Scenes and displays them. It is displaying Devices and Scenes in the UI even as the log shows repeated instances of Connection Refused. Devices generate URLs and test properly. I enabled UPNP on both my routers.
Scenes do not generate URLs. If I manually add a scene (http://vera:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=) I either get a a popup with a 404 error or a popup with command ran successfully but the scene doesn't fire.
The scenes run fine in Vera Ui 7. I have done everything I can think of including deleting all devices and adding them again. At present I have (11) zwave switches/outlets that test successfully and work through Echo.
I am running this on an rpi 2, with Raspbian Jessie. I am running the most recent Vera firmware--1.7.1598 that was released last week.
Thanks!

Reply to this email directly or view it on GitHub.

from ha-bridge.

Excellent--thanks! What about the Error Calling out to HA Gateway, connection refused?

from ha-bridge.

What is your command line? The call is a direct calm to the vera you specify on the command line.
Thanks
On Dec 1, 2015 9:32 AM, ckhyatt [email protected] wrote:Excellent--thanks! What about the Error Calling out to HA Gateway, connection refused?

—Reply to this email directly or view it on GitHub.

from ha-bridge.

This is the command line in the .sh:

ps -ef | grep "ha-bridge" | awk '{print $2}' | xargs kill
java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

This is in the crontab:

@reboot java -jar java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

Thanks!

from ha-bridge.

Ahh yes, you need to supply the vera IP address. Add this -Dvera.address= and you will be in business.
Please read the readme at HTTPS://github.com/bwssytems/ha-bridge as it will explain all the command line items and why you may need them.
The support team
On Dec 1, 2015 9:53 AM, ckhyatt [email protected] wrote:This is the command line in the .sh:

ps -ef | grep "ha-bridge" | awk '{print $2}' | xargs kill
java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

This is in the crontab:

@reboot java -jar java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

Thanks!

—Reply to this email directly or view it on GitHub.

from ha-bridge.

I originally had the IP and it made no difference. The readme indicates the IP is not necessary as it uses the default IP of the host. Is the readme incorrect? To be clear, the bridge is running and I can control 11 devices through Echo.

Thanks!

On Dec 1, 2015, at 11:11 AM, bwssytems [email protected] wrote:

Ahh yes, you need to supply the vera IP address. Add this -Dvera.address= and you will be in business.
Please read the readme at HTTPS://github.com/bwssytems/ha-bridge as it will explain all the command line items and why you may need them.
The support team
On Dec 1, 2015 9:53 AM, ckhyatt [email protected] wrote:This is the command line in the .sh:

ps -ef | grep "ha-bridge" | awk '{print $2}' | xargs kill
java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

This is in the crontab:

@reboot java -jar java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

Thanks!

—Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

from ha-bridge.

That is the upnp.config.address. If you want the vera helpers, you will need to add it.
On Dec 1, 2015 10:21 AM, ckhyatt [email protected] wrote:I originally had the IP and it made no difference. The readme indicates the IP is not necessary as it uses the default IP of the host. Is the readme incorrect? To be clear, the bridge is running and I can control 11 devices through Echo.

Thanks!

On Dec 1, 2015, at 11:11 AM, bwssytems [email protected] wrote:

Ahh yes, you need to supply the vera IP address. Add this -Dvera.address= and you will be in business.
Please read the readme at HTTPS://github.com/bwssytems/ha-bridge as it will explain all the command line items and why you may need them.
The support team
On Dec 1, 2015 9:53 AM, ckhyatt [email protected] wrote:This is the command line in the .sh:

ps -ef | grep "ha-bridge" | awk '{print $2}' | xargs kill
java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

This is in the crontab:

@reboot java -jar java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

Thanks!

—Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

—Reply to this email directly or view it on GitHub.

from ha-bridge.

My apologies, I copied this incorrectly from my configuration doc. Here is how it is configured:

ps ­ef | grep "ha­bridge" | awk '{print $2}' | xargs kill
java ­jar ­Dvera.address=192.168.1.135 ­Dupnp.device.db=/usr/local/habridge/devices.db /usr/local/habridge/ha­bridge­1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

On Dec 1, 2015, at 11:24 AM, bwssytems [email protected] wrote:

That is the upnp.config.address. If you want the vera helpers, you will need to add it.
On Dec 1, 2015 10:21 AM, ckhyatt [email protected] wrote:I originally had the IP and it made no difference. The readme indicates the IP is not necessary as it uses the default IP of the host. Is the readme incorrect? To be clear, the bridge is running and I can control 11 devices through Echo.

Thanks!

On Dec 1, 2015, at 11:11 AM, bwssytems [email protected] wrote:

Ahh yes, you need to supply the vera IP address. Add this -Dvera.address= and you will be in business.
Please read the readme at HTTPS://github.com/bwssytems/ha-bridge as it will explain all the command line items and why you may need them.
The support team
On Dec 1, 2015 9:53 AM, ckhyatt [email protected] wrote:This is the command line in the .sh:

ps -ef | grep "ha-bridge" | awk '{print $2}' | xargs kill
java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

This is in the crontab:

@reboot java -jar java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

Thanks!

—Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

—Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

from ha-bridge.

Ahh, looking through my notes, and updates for the next release, I have changed how the bridge connects to the vera. I have run into that before as well.

Comming soon.

Thanks

--------- Original Message --------- Subject: Re: [ha-bridge] Error connection refused in logs (#13)
From: "ckhyatt" [email protected]
Date: 12/1/15 9:25 am
To: "bwssytems/ha-bridge" [email protected]
Cc: "bwssytems" [email protected]

My apologies, I copied this incorrectly from my configuration doc. Here is how it is configured:

ps ­ef | grep "ha­bridge" | awk '{print $2}' | xargs kill
java ­jar ­Dvera.address=192.168.1.135 ­Dupnp.device.db=/usr/local/habridge/devices.db /usr/local/habridge/ha­bridge­1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

On Dec 1, 2015, at 11:24 AM, bwssytems [email protected] wrote:

That is the upnp.config.address. If you want the vera helpers, you will need to add it.
On Dec 1, 2015 10:21 AM, ckhyatt [email protected] wrote:I originally had the IP and it made no difference. The readme indicates the IP is not necessary as it uses the default IP of the host. Is the readme incorrect? To be clear, the bridge is running and I can control 11 devices through Echo.

Thanks!

On Dec 1, 2015, at 11:11 AM, bwssytems [email protected] wrote:

Ahh yes, you need to supply the vera IP address. Add this -Dvera.address= and you will be in business.
Please read the readme at HTTPS://github.com/bwssytems/ha-bridge as it will explain all the command line items and why you may need them.
The support team
On Dec 1, 2015 9:53 AM, ckhyatt [email protected] wrote:This is the command line in the .sh:

ps -ef | grep "ha-bridge" | awk '{print $2}' | xargs kill
java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

This is in the crontab:

@reboot java -jar java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

Thanks!

-Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.

-Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.

from ha-bridge.

Thanks! I just wanted to be sure I hadn't made a mistake.

Thanks again for all your work on this app. It is an excellent solution.

Regards,

Craig

On Dec 1, 2015, at 11:47 AM, bwssytems [email protected] wrote:

Ahh, looking through my notes, and updates for the next release, I have changed how the bridge connects to the vera. I have run into that before as well.

Comming soon.

Thanks

--------- Original Message --------- Subject: Re: [ha-bridge] Error connection refused in logs (#13)
From: "ckhyatt" [email protected]
Date: 12/1/15 9:25 am
To: "bwssytems/ha-bridge" [email protected]
Cc: "bwssytems" [email protected]

My apologies, I copied this incorrectly from my configuration doc. Here is how it is configured:

ps ­ef | grep "ha­bridge" | awk '{print $2}' | xargs kill
java ­jar ­Dvera.address=192.168.1.135 ­Dupnp.device.db=/usr/local/habridge/devices.db /usr/local/habridge/ha­bridge­1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

On Dec 1, 2015, at 11:24 AM, bwssytems [email protected] wrote:

That is the upnp.config.address. If you want the vera helpers, you will need to add it.
On Dec 1, 2015 10:21 AM, ckhyatt [email protected] wrote:I originally had the IP and it made no difference. The readme indicates the IP is not necessary as it uses the default IP of the host. Is the readme incorrect? To be clear, the bridge is running and I can control 11 devices through Echo.

Thanks!

On Dec 1, 2015, at 11:11 AM, bwssytems [email protected] wrote:

Ahh yes, you need to supply the vera IP address. Add this -Dvera.address= and you will be in business.
Please read the readme at HTTPS://github.com/bwssytems/ha-bridge as it will explain all the command line items and why you may need them.
The support team
On Dec 1, 2015 9:53 AM, ckhyatt [email protected] wrote:This is the command line in the .sh:

ps -ef | grep "ha-bridge" | awk '{print $2}' | xargs kill
java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

This is in the crontab:

@reboot java -jar java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

Thanks!

-Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.

-Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

from ha-bridge.

I confirmed my device IDs and Scene IDs are duplicates. I suspect this is the reason it doesn't work when I manually copy the scene URL into the UI. Looks like both issues will be fixed in the next release.

Thanks again for all your hard work on this app.

Craig

On Dec 1, 2015, at 11:47 AM, bwssytems [email protected] wrote:

Ahh, looking through my notes, and updates for the next release, I have changed how the bridge connects to the vera. I have run into that before as well.

Comming soon.

Thanks

--------- Original Message --------- Subject: Re: [ha-bridge] Error connection refused in logs (#13)
From: "ckhyatt" [email protected]
Date: 12/1/15 9:25 am
To: "bwssytems/ha-bridge" [email protected]
Cc: "bwssytems" [email protected]

My apologies, I copied this incorrectly from my configuration doc. Here is how it is configured:

ps ­ef | grep "ha­bridge" | awk '{print $2}' | xargs kill
java ­jar ­Dvera.address=192.168.1.135 ­Dupnp.device.db=/usr/local/habridge/devices.db /usr/local/habridge/ha­bridge­1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

On Dec 1, 2015, at 11:24 AM, bwssytems [email protected] wrote:

That is the upnp.config.address. If you want the vera helpers, you will need to add it.
On Dec 1, 2015 10:21 AM, ckhyatt [email protected] wrote:I originally had the IP and it made no difference. The readme indicates the IP is not necessary as it uses the default IP of the host. Is the readme incorrect? To be clear, the bridge is running and I can control 11 devices through Echo.

Thanks!

On Dec 1, 2015, at 11:11 AM, bwssytems [email protected] wrote:

Ahh yes, you need to supply the vera IP address. Add this -Dvera.address= and you will be in business.
Please read the readme at HTTPS://github.com/bwssytems/ha-bridge as it will explain all the command line items and why you may need them.
The support team
On Dec 1, 2015 9:53 AM, ckhyatt [email protected] wrote:This is the command line in the .sh:

ps -ef | grep "ha-bridge" | awk '{print $2}' | xargs kill
java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

This is in the crontab:

@reboot java -jar java -jar -Dupnp.device.db=/usr/local/habridge/devices.db
/usr/local/habridge/ha-bridge-1.1.0.jar 2>&1 | tee /usr/local/habridge/habridge.log &

Thanks!

-Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.

-Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

from ha-bridge.