Skip to content

INSTALLATION.md

Latest commit

 

History

History
277 lines (188 loc) · 9.19 KB

INSTALLATION.md

File metadata and controls

277 lines (188 loc) · 9.19 KB

Requirements

Compatability

  • Pod 1 - ❌ NOT COMPATIBLE

  • Pod 2 - ❌ NOT COMPATIBLE

  • Pod 3 - (With SD card) - ✅ most people who have tried this have gotten it working

    • USE LINUX FOR THIS
      • Option 1:
        • Follow the steps here to get root
        • Start from step 11 (SKIP step 12)
        • It's important you run step 11 ASAP after you ssh in, or else your pod will auto update firmware and kick you out
      • Option 2:
        • Try this script to modify 8 sleeps SD card (I have not personally tested this)

  • Pod 3 - (No SD card) - ✅ FCC ID: 2AYXT61100001 (The FCC ID is located in the back of the pod where you plug in the water tubes)

  • Pod 4 ✅

  • Pod 5 ✅

Tools required

  • TC2070-IDC ($50) - You can also solder the 3 required wires to the JTAG header instead
  • FTDI FT232RL ($13)
  • Dupont wires ($7)
  • PSA - The instructions contained here are specific to mac and linux. If you have Windows, you'll have to figure that out yourself (it's do-able, I just refuse to use Windows)

How to revert changes and go back to using your Eight Sleep through their app

  1. If you already had your pod added to your 8 sleep account in your app, go to your 8 sleep app and manage your pod, remove the pod from your account
  2. Reset the firmware
    1. Pod 3
    2. Pod 4
  3. Set up the pod as a new pod in the app

Installation Steps

1. Access the circuit board

  1. Pod 5 users only: you must first setup your pod with the 8 sleep app, then proceed
  2. Follow the steps to teardown your device and get access to the circuit board
    1. Pod 3
    2. Pod 4
      1. Pod 4 written instructions

2. Connect to device

  1. Your pod should be unplugged at this point. It doesn't need a connection to the mattress cover OR power at this point
  2. Using dupont wires, connect your tag-connect cable to your FTDI FT232RL following the images in docs/jtag/
  3. Connect your tag-connect cable to the circuit board
    1. Pod 3
    2. Pod 4
  4. Connect your FTDI FT232RL to your computer

3. Get the minicom session ready on your computer

  • The baud rate is 921600
  • Run ls /dev/tty*, you should see your FT232RL listed under something like tty.usbserial-B0010NHK
minicom -b 921600 -o -D /dev/tty.usbserial-B0010NHK
  • You should see this screen (at least on Mac), if you don't run ls /dev/tty*, your device might be under something else

docs/installation/0_minicom.png

4. Plug the power into the pod

Get ready to interrupt the boot when you see Hit any key to stop autoboot. (I just hit CTRL + C)

Interrupt

If you did it correctly, you'll see this

Interrupt success

5.Modify the boot environment, this allows us to get root access

# VERIFY your current_slot = a, if not, go back and firmware reset your pod
# If it's still not = a, create an issue in github 
printenv current_slot

# If you have current_slot=a
setenv bootargs "root=PARTLABEL=rootfs_a rootwait init=/bin/bash"

run bootcmd

6. Mount the file system

# Mount /proc for process and system information
mount -t proc proc /proc

# Mount /sys for hardware and system-level information
mount -t sysfs sysfs /sys

# Mount /dev for device files (e.g., /dev/mmcblk0)
mount -t devtmpfs devtmpfs /dev

# Mount /run (optional but useful for some runtime scripts)
mount -t tmpfs tmpfs /run

# Mount the file system in read write mode (BE CAREFUL EDITING MODIFYING FILES)
mount -o remount,rw /

7. Update password for root & rewt

passwd root
passwd rewt

8. Sync the file changes

sync

9. Reboot (DO NOT INTERRUPT BOOT THIS TIME)

reboot -f

10. Login as root with the password we set

On the pod 4 & 5, this screen will be slightly different, that's OK

Login

11. Disable software updates

You may see some failures saying these services were not loaded or do not exist, that's ok

# Disables the software updates
systemctl disable --now swupdate-progress swupdate defibrillator eight-kernel telegraf vector frankenfirmware dac swupdate.socket

# Blocks the software updates if we ever restart or power off the device
systemctl mask swupdate-progress swupdate defibrillator eight-kernel telegraf vector frankenfirmware dac swupdate.socket

12. Setup internet access

# Replace WIFI_NAME and PASSWORD with your actual WiFi credentials
# (WIFI_NAME appears twice)
# 
# DO NOT USE A GUEST NETWORK OR TRY TO DO ANYTHING FANCY TO PREVENT IT FROM TALKING TO THE INTERNET
#   If you want to block internet access to the pod, we can do that with firewall rules later

nmcli connection add type wifi con-name WIFI_NAME ifname wlan0 ssid WIFI_NAME wifi-sec.key-mgmt wpa-psk wifi-sec.psk "PASSWORD" ipv4.method auto ipv6.method auto

# (OPTIONAL) This will take your Pod out of the "waiting to be setup" state, and will allow you to turn off the blue blinking LED.
sed -i 's/uuid=.*/uuid=700a7a76-2105-4f46-b1b4-c9f3c791c440/' /persistent/system-connections/*.nmconnection

# Reload the network manager
nmcli connection reload

13. Install the free-sleep app, this will set up a systemctl service that auto runs on boot

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/throwaway31265/free-sleep/main/scripts/install.sh)"

14. Get your pod's IP address

# Yours will be different, that's okay
nmcli -g ip4.address device show wlan0
192.168.1.50/24

15. With a device connected to the SAME Wi-Fi network you set up in step 12, navigate to your pod's IP address (port 3000)

SET YOUR TIME ZONE, OR ELSE SCHEDULING WILL NOT WORK! This can be done on the settings page of the web app. See screenshot below. The site should appear but it should be loading and dulled out. (Unless you have the pod plugged into the cover)

http://192.168.1.50:3000/

Web App

16. Save the website to your home screen on your mobile device

  • Apple devices:
    • Navigate to the website in safari
    • Click the share icon in the bottom toolbar
    • Select 'Add to Home Screen'
    • Edit the name if you’d like, then tap Add.
    • The shortcut will now appear on your home screen like an app icon.
  • Android devices:
    • Open the website in Chrome (or your default browser).
    • Tap the three-dot menu in the top-right corner.
    • Select “Add to Home screen” (sometimes shown as “Install app”).
    • Edit the name if you’d like, then tap Add.
    • The shortcut will now appear on your home screen like an app icon.

17. Validation

Verify the site is still up

  1. Unplug the power from your device and plug it back in
  2. Wait up to 4 minutes or so, ensure you can still access the site from another device
  3. If the site is still up, you should be good. NOTE - The website will not fully load until the Pod is connected to the mattress cover. Once it's plugged in to the cover the site should load and work correctly.

Verify the controls work

  1. I would recommend setting up steps 17 and 18 below (block WAN traffic & setup SSH access for debugging & upgrading free-sleep)
  2. Disconnect the tag-connect cable and power from your pod
  3. Connect your pod to the cover as you normally would
  4. Using the free-sleep site, set a temperature. (I would suggest the highest temp on one side and the lowest temp on the other side)
  5. Physically verify the temps change (lay on the cover, use a thermometer, whatever)
  6. If the temps change, you're all set!
  7. If it's not working, reach out in Discord and share the output of fs-debug

18. Add an ssh config

  • This will ask for a public key, ssh access is on port 8822 (ex: `ssh root@<POD_IP> -p 8822')
  • This allows you to set up remote access to your Pod
sh /home/dac/free-sleep/scripts/setup_ssh.sh

19. Add firewall rules to block access to the internet (optional, but recommended)

sh /home/dac/free-sleep/scripts/block_internet_access.sh

# You can undo this with 
sh /home/dac/free-sleep/scripts/unblock_internet_access.sh

Free sleep commands available (run this in the terminal through an SSH session on your pod)

  • fs-debug - Prints a debug report for the pod & free sleep
  • fs-restart - Restarts the free sleep service
  • fs-reset-db - Deletes the biometrics DB and recreates it (helpful for corrupted DB files)
  • fs-reset - Wipes free-sleep data and does a fresh install (can fix corrupted DB or issues switching from beta branch to main branch (requires confirmation in a prompt before executing)
  • fs-update - Manually runs the update script
  • fs-dev-server - Run express server with nodemon (for devs)