java-hdl-webserver | Using Google Home to control HDL Buspro smart home

First SSH into your Raspberry Pi. Type java -version to see which Java version you have. If it says something with 1.8 or later you are good to go. Just continue to the next step. If you don't have Java installed or a Java version before version 1.8, run the following commands and follow the setup: sudo apt-get update sudo apt-get upgrade sudo apt install default-jdk (old command: ~~sudo apt-get install oracle-java8-jdk~~). If you don't have the version-control system Git installed you can install it like this: sudo apt-get install git. First check out the code: cd ~ git clone https://github.com/roys/java-hdl-webserver.git. It can be smart to check that the server is working and getting data: cd java-hdl-webserver/releases java -cp hdlserver-LATEST.jar com.roysolberg.java.hdlserver.Application. You should see some output confirming that the server is starting up ok. Please note that it could take a few seconds to start up on hardware like one of the Raspberry Pi models. Use ctrl + c to exit the application. If you want to make the server run on startup then skip to 4b. If you want to just run the server in the background (even after you log out) you can enter the following command: nohup java -cp hdlserver-LATEST.jar com.roysolberg.java.hdlserver.Application &. The number that is printed out is the process number. You can use this number to stop the script. If you don't have the process number you can find it using ps aux | grep hdlserver. To kill/stop the script just enter the following command: kill [process number]. The server can be run as a cron job that starts on reboot of the Raspberry Pi. To edit the cron jobs: crontab -e. Add the following line at the end: @reboot /bin/sh ~/java-hdl-webserver/launcher.sh. Use ctrl + x to exit, press Y to save the cron setup and enter to confirm the filename. Restart the device using sudo shutdown -r now and check out if there's stuff going on in releases/logs/hdl-bus.log. releases/logs/hdl-server.log and releases/logs/nohup.out will also contain output and any error messages running the server. Please note that there is a delay of 30 seconds when running the server from the launcher.sh script (to ensure that network interfaces are up and IP address is assigned, etc). You can easily tap in to what's going by running tail: tail -f hdl-bus.log tail -f hdl-server.log. This will let you follow the file and the contents that's written to it. To end the session just press ctrl + c.
Give the computer running the server a static IP address in your router
Forward a port (please use some other high number port than 4567) from Internet to port 4567 to the computer running the server
Set up some kind of dynamic DNS (can often be done on the router itself, or you can use the computer running the server) to get a static hostname for IFTTT
Use the hostname and external port number when setting up IFTTT (described later)