Setting up your existing Home Assistant for habbb

Step 1 of 4 · ~5 min

Add the trusted-proxies block to your configuration

Without this, Home Assistant returns HTTP 400 to every request that comes through our Cloudflare tunnel. Add it once, then forget about it.

1. In the Home Assistant UI, go to Settings → Add-ons and install the File Editoradd-on if you don't already have it (search for it, click Install, click Start).
2. Open File Editor (sidebar). Open /config/configuration.yaml.
3. If there's no http: block at the top level, paste this anywhere in the file (top of the file is conventional):

   http:
     use_x_forwarded_for: true
     trusted_proxies:
       - 172.30.32.0/23

4. If there is already an http: block, merge the two keys (use_x_forwarded_for and trusted_proxies) into the existing block. Don't create a second http:block — YAML treats that as an error and HA won't restart.
5. Save the file. Then go to Developer Tools → YAML and click Restart → Restart Home Assistant. Wait until HA is back (usually 30–60 seconds).

Step 2 of 4 · ~3 min

Create an admin user for habbb + generate a token

We use a dedicated user account (not yours) to install our add-ons remotely. You can revoke this account at any time and it'll cut off our access instantly.

1. Go to Settings → People → Users tab → Add user.
2. Display name: habbb. Username: habbb-ops. Password: anything secure (you can use the "suggest" button — we don't need to know it).
3. Tick the Administrator box. Click Create.
4. Log out, then log back in as the new habbb-ops user using the password you just set.
5. In the bottom-left, click your profile (now habbb-ops) → Security tab.
6. Scroll to Long-lived access tokens → Create token. Name it habbb-onboarding.
7. Copy the token immediately— Home Assistant only shows it once. Send it to us via the email reply we sent you when you signed up. We'll only use it to do the install in Step 4 below.
8. Log out of habbb-ops and back into your normal account.

Step 3 of 4 · ~5 min

Install the Cloudflared add-on with the token we sent you

This opens the secure tunnel from your HA out to Cloudflare. Once it's running, we can reach your HA at the URL we provisioned for you (something like yourname.habbb.com — exact URL is in your welcome email).

1. In the HA UI, go to Settings → Add-ons → Add-on Store.
2. Click the three-dot menu (top right) → Repositories.
3. Add this repository:

   https://github.com/brenner-tobias/ha-addons

   Click Add, then Close.
4. Back in the Add-on Store, scroll to find Cloudflared (under the brenner-tobias repo). Click it → Install. Wait ~1 min.
5. Once installed, click the Configuration tab. Find the tunnel_tokenfield and paste the token we sent you in your welcome email (it's a long base64 string, starts with eyJ...).
6. Make sure additional_hosts is set to an empty list: [] (the default). Click Save.
7. Switch to the Info tab. Toggle Start on boot and Watchdog on. Click Start.
8. Wait ~30 seconds, then check the Log tab. You should see Connection ... registered messages four times (one per Cloudflare data centre). If you see errors instead, double-check the token and reach out to us.
9. Open the URL we sent you (yourname.habbb.com) in a new browser tab. You should see the Home Assistant login page. If you do, the tunnel is up.

Step 4 of 4 · we do this

We finish the setup

Once you've sent us the long-lived access token from Step 2, we run a short script on our side that:

• Confirms we can reach your HA via the tunnel
• Adds the habbb add-on repository to your add-on store
• Installs habbb-backup-sync with your dedicated AWS credentials (the backups go to a per-customer S3 prefix only your hub can write to)
• Configures and starts it
• Smoke-tests everything and confirms the unit is live

Total time on our end: about 2 minutes. We'll email you when it's done. The first backup will land in S3 within an hour.

After setup is complete

That's it. From this point forward:

• Daily backupsland automatically in our managed S3 storage. You don't need to do anything.
• Monitoring runs every 5 minutes. If your tunnel drops for more than 15 minutes, we get an alert and start investigating before you notice.
• Updatesget tested by us first, then rolled out on a schedule we communicate with you. We don't auto-update without warning.
• Fixes and tweaks are part of your subscription. Email us when something breaks or you want a small change to an existing automation.

What's NOT included:building wholly new automations, adding new device categories you didn't have before, large refactors. Those are quoted separately as one-off projects. We'll always tell you up front before charging anything beyond the £30/month.

To cancel:email us. We'll remove our cloudflared addon and the habbb-ops user, and you're back to a self-managed HA exactly where you were before signing up. No lock-in, no data hostage situation.

Help — something went wrong

• HA won't restart after Step 1— almost always a YAML indentation error. Open File Editor, check the configuration.yaml block looks like the one above (spaces only, no tabs, exactly 2-space indent). If you can still log into HA, the error is in the System log. If you can't, you can undo the change by editing the file via the host SSH or by booting the SD card in another machine.
• Cloudflared shows tunnel errors in the log — the most common cause is a typo in the token. Copy-paste it again from the welcome email; it should start with eyJ and be ~250 characters long. Restart the addon after saving.
• Your habbb URL shows "Bad Gateway" or 502— the tunnel is up but Home Assistant isn't responding. Check that HA itself is running; if it is, there's a chance the trusted_proxies config from Step 1 wasn't saved. Restart HA Core.
• Anything else— email us. We'd rather you reach out at step 1 than spend an hour stuck.