1
0
Fork 0
mirror of https://github.com/iiab/iiab.git synced 2025-02-13 11:42:08 +00:00
iiab/roles/remoteit
2021-10-28 18:43:55 -05:00
..
defaults #3008 2021-10-28 18:15:16 -05:00
tasks full path 2021-10-28 18:43:55 -05:00
README.md roles/remoteit/README.md: Claim code clarif 2021-10-28 12:40:47 -04:00

Remote support of an Internet-in-a-Box using https://remote.it

Remote.it can be a great way to remotely support an Internet-in-a-Box (IIAB).

For other approaches, please see http://FAQ.IIAB.IO -> "How can I remotely manage my Internet-in-a-Box?"

To install remote.it onto an IIAB:

  1. Set remoteit_install and remoteit_enabled to True in your IIAB's /etc/iiab/local_vars.yml

  2. Install and enable it (remote.it) on your IIAB, by running:

    cd /opt/iiab/iiab
    sudo ./runrole remoteit
    
  3. To obtain this IIAB's 8-letter remote.it claim code, allowing you to make a remote connection to this IIAB, run:

    sudo grep claim /etc/remoteit/config.json
    

    The claim code must be used within 24 hours, per: https://docs.remote.it/device-package/installation#2.-update-your-package-manager-and-install

    If not used before then, here is an example (version & architecture can change in the .deb filename below!) to re-run this installation command, to get a new claim code:

    sudo apt reinstall /opt/iiab/downloads/remoteit-4.13.5.armhf.rpi.deb
    
  4. After you've installed the https://remote.it client software onto a separate computer or device (e.g. your own laptop) click on the '+' icon, then enter the remote.it claim code (for the IIAB that you need to connect to).

    As shown in the screenshot here: https://docs.remote.it/device-package/installation#3.-claim-and-register-the-device

Advanced

For "auto-registration" of remote.it, and other more advanced configuration options, please review:

Known Issues

  • 2021-10-27: This needs to be enhanced rather urgently, so remote.it also works when IIAB is installed on Raspberry Pi OS 11 (Bullseye), Ubuntu, Mint and Debian: #3006
  • 2021-10-28: The above OS issues should be resolved by PR #3007, but this needs final testing!