This is an old revision of the document!

Install HOOBS on Fedora 33 as Unraid Virtual Machine

This will guide you through the setup of HOOBS on an installation of Fedora 33 as an Unraid Virtual Machine.

VM Settings

Autostart: Yes
Name: hoobs.33vX
Description: Hoobs
CPU Mode: Host Passthrough
Logical CPUs: 2
Internal Memory: 1024
Max Memory: 1024
Machine: Q35-4.1
BIOS: OVMF
USB Controller: 2.0 (EHCI) (I don't have USB 3.0 on current hardware)
OS Install ISO: select the fedora33 iso
OS Install CDRom Bus: SATA
Primary vDisk Location: Auto if on the array, below options for ssd
- /mnt/disks/samsung_ssd/hoobs.33vX/vdisk1.img –> This one is vDisk on SSD (Current setup uses this)
- /dev/disk/by-id/ata-“ID OF DRIVE” –> This one is passthrough
Primary vDisk Size: 10G
Primary vDisk Type: raw
Primary vDisk Bus: VirtIO if on the array, below options for ssd
- VirtIO –> This one is vDisk on SSD (Current setup uses this)
- SATA –> This one is passthrough
Graphics Card: VNC
VNC Video Driver: QXL (best)
VNC Password: leave this blank (or set password if concerned folks will get access to unraid!)
VNC Keyboard: English-United States
Sound Card: none
Network MAC: whatever it is
Network Bridge: br0
USB Devices: none
Other PCI Devices: none

sudo yum update

In home directory
```
mkdir .ssh
```
authorized_keys file needs to have keys in them. Copy over from harddrive, external drive, or create them.

Turn off Password Auth

sudo vim /etc/ssh/sshd_config

UsePAM yes
PasswordAuthentication no

ChallengeResponseAuthentication no

Also had to make similar changes in the file that is included in /etc/ssh/sshd_config.d/*.conf
- but had to change folder permissions first to get in, then edit, then change back
Then had to make sure the user home folder was 700 (which it was), the .ssh folder was 700 (which it wasn't), and the authorized_keys file was 600 (which it wasn't).

sudo hostnamectl set-hostname hoobs

sudo yum install -y nss-mdns avahi

sudo systemctl enable avahi-daemon.service

sudo reboot

wget -q -0 - http://bit.ly/get-hoobs | sudo bash -

Open a Chrome browser tab in Incognito Mode (or clear your cache).
Open Developer Tools (View/Developer/Developer Tools).
Click on 'Network' tab. Make sure 'Preserve Log' is checked.
In the 'Filter' box, enter issueToken
Go to home.nest.com, and click 'Sign in with Google'. Log into your account.
One network call (beginning with iframerpc) will appear in the Dev Tools window. Click on it.
In the Headers tab, under General, copy the entire Request URL (beginning with https://accounts.google.com, ending with nest.com). This is your “issueToken” in config.json.
In the 'Filter' box, enter oauth2/iframe
Several network calls will appear in the Dev Tools window. Click on the last iframe call.
In the Headers tab, under Request Headers, copy the entire cookie (include the whole string which is several lines long and has many field/value pairs - do not include the cookie: name). This is your “cookies” in config.json.
In the 'Filter' box, enter issue_jwt
Click on the last issue_jwt call.
In the Headers tab, under Request Headers, copy the entire x-goog-api-key (do not include the x-goog-api-key: name). This is your “apiKey” in config.json.
Do not log out of home.nest.com, as this will invalidate your credentials. Just close the browser tab.