mirror of
https://github.com/bwssytems/ha-bridge.git
synced 2025-12-19 16:41:53 +00:00
Compare commits
2 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
51ce10cfc7 | ||
|
|
b5f7144c9c |
38
README.md
38
README.md
@@ -21,10 +21,10 @@ Then locate the jar and start the server with:
|
|||||||
ATTENTION: This requires JDK 1.8 to run
|
ATTENTION: This requires JDK 1.8 to run
|
||||||
|
|
||||||
```
|
```
|
||||||
java -jar ha-bridge-2.0.5.jar
|
java -jar ha-bridge-2.0.6.jar
|
||||||
```
|
```
|
||||||
### Automation on Linux systems
|
### Automation on Linux systems
|
||||||
To have this conigured and running automatically ther eare a few resources to use. One is using Docker and a docker container has been built for this and can be gotten here: https://github.com/aptalca/docker-ha-bridge
|
To have this configured and running automatically there are a few resources to use. One is using Docker and a docker container has been built for this and can be gotten here: https://github.com/aptalca/docker-ha-bridge
|
||||||
|
|
||||||
For next gen Linux systems, here is a systemctl unit file that you can install. Here is a link on how to do this: https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units
|
For next gen Linux systems, here is a systemctl unit file that you can install. Here is a link on how to do this: https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units
|
||||||
```
|
```
|
||||||
@@ -35,11 +35,43 @@ After=network.target
|
|||||||
|
|
||||||
[Service]
|
[Service]
|
||||||
Type=simple
|
Type=simple
|
||||||
ExecStart=/usr/bin/java -jar -Dconfig.file=/home/pi/amazon-echo/data/habridge.config /home/pi/amazon-echo/ha-bridge-2.0.5.jar
|
ExecStart=/usr/bin/java -jar -Dconfig.file=/home/pi/amazon-echo/data/habridge.config /home/pi/amazon-echo/ha-bridge-2.0.6.jar
|
||||||
|
|
||||||
[Install]
|
[Install]
|
||||||
WantedBy=multi-user.target
|
WantedBy=multi-user.target
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Basic script setup to run the bridge on a pi.
|
||||||
|
|
||||||
|
Create the directory and make sure that ha-bridge-2.0.6.jar is in your /home/pi/habridge directory.
|
||||||
|
```
|
||||||
|
pi@raspberrypi:~ $ mkdir habridge
|
||||||
|
pi@raspberrypi:~ $ cd habridge
|
||||||
|
pi@raspberrypi:~/habridge $ wget https://github.com/bwssytems/ha-bridge/releases/download/v2.0.6/ha-bridge-2.0.6.jar
|
||||||
|
```
|
||||||
|
Edit the shell script for starting:
|
||||||
|
```
|
||||||
|
pi@raspberrypi:~/habridge $ nano starthabridge.sh
|
||||||
|
```
|
||||||
|
Then cut and past this, modify any locations that are not correct
|
||||||
|
```
|
||||||
|
cd /home/pi/habridge
|
||||||
|
rm /home/pi/habridge/habridge-log.txt
|
||||||
|
nohup java -jar /home/pi/habridge/ha-bridge-2.0.6.jar > /home/pi/habridge/habridge-log.txt 2>&1 &
|
||||||
|
chmod 777 /home/pi/habridge/habridge-log.txt
|
||||||
|
```
|
||||||
|
Exit and save the file with ctrl-X and follow the prompts and then execute on the command line:
|
||||||
|
```
|
||||||
|
pi@raspberrypi:~/habridge $ chmod u+x starthabridge.sh
|
||||||
|
```
|
||||||
|
Then execute the script:
|
||||||
|
```
|
||||||
|
pi@raspberrypi:~/habridge $ ./starthabridge.sh
|
||||||
|
```
|
||||||
|
You should now be running the bridge. Check for errors:
|
||||||
|
```
|
||||||
|
pi@raspberrypi:~/habridge $ tail -f habridge-log.txt
|
||||||
|
```
|
||||||
## Available Arguments
|
## Available Arguments
|
||||||
Arguments are now deprecated. The ha-bridge will use the old -D arguments and populate the configuration screen, Brisge Control Tab, which can now be saved to a file and will not be needed. There is only one optional argument that overrides and that is the location of the configuration file. The default is the relative path "data/habridge.config".
|
Arguments are now deprecated. The ha-bridge will use the old -D arguments and populate the configuration screen, Brisge Control Tab, which can now be saved to a file and will not be needed. There is only one optional argument that overrides and that is the location of the configuration file. The default is the relative path "data/habridge.config".
|
||||||
### -Dconfig.file=`<filepath>`
|
### -Dconfig.file=`<filepath>`
|
||||||
|
|||||||
2
pom.xml
2
pom.xml
@@ -5,7 +5,7 @@
|
|||||||
|
|
||||||
<groupId>com.bwssystems.HABridge</groupId>
|
<groupId>com.bwssystems.HABridge</groupId>
|
||||||
<artifactId>ha-bridge</artifactId>
|
<artifactId>ha-bridge</artifactId>
|
||||||
<version>2.0.6</version>
|
<version>2.0.7</version>
|
||||||
<packaging>jar</packaging>
|
<packaging>jar</packaging>
|
||||||
|
|
||||||
<name>HA Bridge</name>
|
<name>HA Bridge</name>
|
||||||
|
|||||||
@@ -988,7 +988,6 @@ app.controller('HarmonyController', function ($scope, $location, $http, bridgeSe
|
|||||||
};
|
};
|
||||||
|
|
||||||
$scope.buildButtonUrls = function (harmonydevice, onbutton, offbutton) {
|
$scope.buildButtonUrls = function (harmonydevice, onbutton, offbutton) {
|
||||||
bridgeService.clearDevice();
|
|
||||||
var currentOn = $scope.device.onUrl;
|
var currentOn = $scope.device.onUrl;
|
||||||
var currentOff = $scope.device.offUrl;
|
var currentOff = $scope.device.offUrl;
|
||||||
var actionOn = angular.fromJson(onbutton);
|
var actionOn = angular.fromJson(onbutton);
|
||||||
@@ -999,6 +998,7 @@ app.controller('HarmonyController', function ($scope, $location, $http, bridgeSe
|
|||||||
$scope.device.offUrl = currentOff.substr(0, currentOff.indexOf("]")) + ",{\"device\":\"" + harmonydevice.device.id + "\",\"button\":\"" + actionOff.command + "\"}]";
|
$scope.device.offUrl = currentOff.substr(0, currentOff.indexOf("]")) + ",{\"device\":\"" + harmonydevice.device.id + "\",\"button\":\"" + actionOff.command + "\"}]";
|
||||||
}
|
}
|
||||||
else if ($scope.device.mapType == null || $scope.device.mapType == "") {
|
else if ($scope.device.mapType == null || $scope.device.mapType == "") {
|
||||||
|
bridgeService.clearDevice();
|
||||||
$scope.device.deviceType = "button";
|
$scope.device.deviceType = "button";
|
||||||
$scope.device.targetDevice = harmonydevice.hub;
|
$scope.device.targetDevice = harmonydevice.hub;
|
||||||
$scope.device.name = harmonydevice.device.label;
|
$scope.device.name = harmonydevice.device.label;
|
||||||
|
|||||||
Reference in New Issue
Block a user