Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Moose]

If HA-Bridge is on port 80 at the top of the HA-Bridge page is a tab "My Echo" click on it and log in then add devices.

I am in my echo, but now what? I tried discovering devices from here but no result.

[Tuicemen]

What echo devices and version #s are you using?
if you click on the test on button for a configured device in the bridge does it turn on?

[Moose]

What echo devices and version #s are you using?
if you click on the test on button for a configured device in the bridge does it turn on?

An echo dot version 3. Yes, the Test On/Off work for the 2 lights configured in HABridge.

[Tuicemen]

OK I'm not sure if BWSSystems has Ha-Bridge working with the 3rd gen dots yet.
Since HA-bridge is sending commands correctly now the issue appears to be interfacing with the 3rd gen dot,
all my dots are 1st generation.
You may wish to post to the HA-Bridge issues section https://github.com/bwssytems/ha-bridge/issues about not getting the 3rd generation Dot working with the bridge. Prior to that check to see if there other issues posted for 3rd gen Dots to see if a solution was found.
I do remember reading a issue with the 2nd or 3rd gen dots but don't remember if it was resolved.

[Moose]

I have not found anything useful on 3rd gen dots. To not miss the obvious, is there a Skill I need to install for this?

[Tuicemen]

no skill required. It may be worth posting on the HA-Bridge issues a question to others that may be using a 3rd gen dot to see if you need to do an extra step for it to see devices in the Bridge as yours can't.
Bwssystems may have you run some debugging tests as he is working on a new build currently I believe.

[Tuicemen]

Reading through some of the issues on the Bridge GitHub page I found a few things you may wish to try.
1:
One is to use the link button. this is disabled by default so you have to enable it. To enable go to the Bridge control page and click on Update security Settings then check the "Use Link button" and click update and close the security window.
Once that has been done go to the Bridge Devices screen and click the link button then put Alexa into discovery mode.
2:
If Alexa still fails try it again after waiting for 5 seconds some users have reported a second attempt works. try it with and with out the link button option.
3:
Try port 81

[Moose]

I did stumble upon this and tried it but with no effect. I found a 1st gen dot on line, so I will try that when it arrives.

[Tuicemen]

What wifi band is your echo and Alexa set to? The newer devices allow 5 GHZ but should be set to use 2 to be fully compatible with all older stuff. Also check that your pi is set to use 2 Ghz.

[Moose]

Everything is on the 2.4 Ghz network band. I now have an echo gen 1. Is the info in the "Manage Links" field important? This is what I have...

test_ha_bridge#192.168.0.136   2020-03-07T12:27:30   This is my main PC's address
test_ha_bridge   2020-03-25T11:15:47

I have tried discovery with the Link button pushed, no difference.   I did update the ha-bridge.jar file.

[Tuicemen]

If your HA-Bridge is installed on your pi then the ip for it is your Pi's. If you updated the HA-Bridge jar file tou need to be sure it is the correct name (no version# in the jar file name)

[Moose]

If your HA-Bridge is installed on your pi then the ip for it is your Pi's. If you updated the HA-Bridge jar file tou need to be sure it is the correct name (no version# in the jar file name)

Yes, the Bridge is on the Pi. How do I ensure that the PI's address is used?

After the update I executed mv ha-bridge-5.3.0.jar ha-bridge.jar
to rename it. Correct?

[Tuicemen]

You need to stop the habridge service then rename the  downloaded  file to ha-bridge.jar then restart the service. Prior to restarting the service go into the ha-bridge/data folder and be sure there are no files  so you have a clean slate.

[Moose]

This is the procedure I followed from the Github site. Does this procedure not rename the jar file?

We need to stop the habridge service (if running):
$ sudo systemctl stop habridge
Navigate to where you installed ha-bridge, (use your folder name if not “habridge”):
$ cd habridge
Then rename the existing ha-bridge.jar to something you’ll remember or understand:
$ mv ha-bridge.jar ha-bridge-ARCHIVE.jar
Download the release you wish to update to, (where {VERSION} is the version number):
$ wget https://github.com/bwssytems/ha-bridge/releases/download/v{VERSION}/ha-bridge-{VERSION}.jar
Now rename the downloaded file, (where {VERSION} is the version number):
$ mv ha-bridge-{VERSION}.jar ha-bridge.jar
Lastly we need to restart the habridge service:
$ sudo systemctl start habridge

[Tuicemen]

Yes that does rename the file correctly. However if your previous configuration was compromised your new install will not work. Thats why you need to clear your device and config files. If you wish you can just rename them.