Update README.md

Added usbip remote service.

Author: sincze

README.md

@@ -39,7 +39,8 @@ This integration has been tested with JA-80K /JA-82K central units, JA-81F keypa
 Tested sensors include wired/wireless PIRs & door sensors and wired/wireless fire alarms.
 
 ## Remote Support
-The JA-80T serial cable setup can work with remote serial devices using a device address of 'socket://[ipaddress:socket]' (e.g. socket://192.168.0.1:23) , see section at bottom of page for more details. This can be made to work even without a JA-80T serial cable (as these are hard to source)
+The JA-80T serial cable setup can work with remote serial devices using a device address of 'socket://[ipaddress:socket]' (e.g. socket://192.168.0.1:23) , see section at bottom of page for more details. This can be made to work even without a JA-80T serial cable (as these are hard to source).
+It does also work with a tool called usbipd, 'duplicating' the /dev/hidraw0 device from a server connected to the jablotron alarm to the homeassistant client machine.
 
 ## Examples & configuration
 
@@ -290,6 +291,97 @@ Serial Port to be setup as `9600 baud, 8 bit, no partity, 1 stop bit`. Must be s
 Additional expected similar solutions could be constructed from USR-TCP232-306, USR-TCP232-304 connected directly to the control panel or
 USR-TCP232-302 conected to an existing JA-80T serial cable.
 
+Another solution for remote usage could be via the use of USBIP that needs to be installed on the server (jablotron alarm side) and the client (homeassistant running this repo.)
+
+Using the following command on the server to check if (in this case JA-82T) is visible:
+```
+dmesg | grep hid
+
+[8740307.349070] hid-generic 0003:16D6:0007.0002: hiddev96,hidraw0: USB HID v1.11 Device [JABLOTRON ALARMS JA-82T PC Interface] on usb-0000:01:00.0-1.3/input0
+```
+Now we know the device we are looking for is hidraw0 and the ID **16D6:0007** the id can also be optained if the command ```lsusb``` is executed
+
+Installation of usbip needs to be done on the **CLient** and **Server** via:
+After the above command on the Server execute:
+```
+sudo apt install usbip hwdata usbutils
+modprobe usbip_host
+echo 'usbip_host' >> /etc/modules
+
+# Create a systemd service
+nano /lib/systemd/system/usbipd.service
+```
+
+The file usbipd.service should contain. 
+```
+[Unit]
+Description=usbip host daemon
+After=network.target
+
+[Service]
+Type=forking
+ExecStart=/usr/sbin/usbipd -D
+ExecStartPost=/bin/sh -c "/usr/sbin/usbip bind --$(/usr/sbin/usbip list -p -l | grep '#usbid=16d6:0007#' | cut '-d#' -f1)"
+ExecStop=/bin/sh -c "/usr/sbin/usbip unbind --$(/usr/sbin/usbip list -p -l | grep '#usbid=16d6:0007#' | cut '-d#' -f1); killall usbipd"
+
+[Install]
+WantedBy=multi-user.target
+```
+Only change the #usbid=16d6:0007# if necessary.
+Save the file and execute:
+
+```
+# reload systemd, enable, then start the service
+sudo systemctl --system daemon-reload
+sudo systemctl enable usbipd.service
+sudo systemctl start usbipd.service
+```
+The server setup is now complete, move over to the client
+```
+sudo apt install usbip hwdata usbutils
+modprobe vhci-hcd
+echo 'vhci-hcd' >> /etc/modules
+```
+Much like we did on the server, we’re going to need to modify the ExecStart and ExecStop lines below to search for the correct USB device ID that’s being presented by your USB/IP server. Likewise, change the IP 192.168.0.10 to match your USB server.
+
+```
+nano /lib/systemd/system/usbip.service
+```
+
+```
+[Unit]
+Description=usbip client
+After=network.target
+
+[Service]
+Type=oneshot
+RemainAfterExit=yes
+ExecStart=/bin/sh -c "/usr/sbin/usbip attach -r 192.168.0.10 -b $(/usr/sbin/usbip list -r 192.168.0.10 | grep '16d6:0007' | cut -d: -f1)"
+ExecStop=/bin/sh -c "/usr/sbin/usbip detach --port=$(/usr/sbin/usbip port | grep '<Port in Use>' | sed -E 's/^Port ([0-9][0-9]).*/\1/')"
+
+[Install]
+WantedBy=multi-user.target
+
+```
+Save that file, then run the following commands in your shell:
+
+```
+# reload systemd, enable, then start the service
+sudo systemctl --system daemon-reload
+sudo systemctl enable usbip.service
+sudo systemctl start usbip.service
+```
+
+You should now be able to access the USB device on the client as if the device was plugged in locally, ```(ls -l /dev/hidraw0)``` and you have an auto-starting systemd service to control things.)
+
+Thanks to [derushadigital.com](https://derushadigital.com/other%20projects/2019/02/19/RPi-USBIP-ZWave.html) 
+
+For Docker users we need to add the following to the docker_compose file to enable homeassistant to use this device:
+
+    devices:
+      - /dev/hidraw0
+
+
 ## Troubleshooting
 
 Additional logging can be enabled in configuration.yaml