In October Jen and I bought a 2024 Thor Chateau 22E on a Chevy chassis. It came with a thick binder of manuals for everything bolted inside it. What it didn't come with was any way to know what was going on in there when I wasn't standing in it.

At home, Home Assistant runs pretty much everything, and I've gotten spoiled. The RV is a rolling house with its own batteries, water, propane, generator and internet, and from my couch I knew none of it. A few weeks back I was on the Home Assistant Podcast talking about my house and all the stuff I have on there, I may need to make another appearance talking about the RV.

So the RV got its own Home Assistant. I named it Roam Assistant, because of course I did.

This is the tour, not the how-to. Pretty much every section here is going to get its own post, so consider this the table of contents.

The box in the cabinet

Roam Assistant is a Raspberry Pi running Home Assistant OS, sitting on a Geekworm X728 UPS board. If you take one thing from this post, take the UPS. RVs lose 12V power constantly (battery disconnect, shore power swaps, converter hiccups), and a Pi that loses power mid-write is a Pi with a corrupted card. Now it tells me when it's on battery and shuts itself down cleanly if it has to.

It's on Tailscale like everything else I own, so I can poke at it from anywhere the RV has internet. I also swapped the Pi's built-in Bluetooth for a USB adapter, because it turns out a lot of this coach talks Bluetooth.

What it watches

  • The chassis. A WiCAN Pro in the OBD-II port reads the Chevy's engine data over Wi-Fi. Fuel, coolant, chassis battery, odometer, and a pile of oxygen sensor values I will never look at. I got this idea straight from SmartyVan's video, and it worked exactly like he said it would.
  • The internet. The coach came with a Winegard gateway, and there was no Home Assistant integration for it. So Claude and I built one. It exposes way more than I expected, including a GPS fix. I might open source it once I know it's working well.
  • The house side. A few Shelly BLU sensors for temperature, humidity and the side door. One lives in the network cabinet, because a closed cabinet in a parked RV in a SoCal August is how you cook a Pi.
  • The generator. Yes, that one. I wrote a whole post about teaching Home Assistant to read my RV generator without starting it. It's still read-only, on purpose.

Home is wherever we park it

SmartyVan also pointed me at GeoLocator, one of his Community Projects. It moves Home Assistant's location based on GPS. The catch: we didn't have GPS. Not until the Winegard integration started reporting one. Now weather, sunrise and sunset, and everything else location-based follows the coach instead of thinking we're still at home.

Then it gets nerdy. That same list introduced me to Public Lands, which tells me who manages the land we're parked on: BLM, Forest Service, state or private. Parked in my driveway right now, it reports "Private Land." Correct, and kinda funny.

Public Lands got me thinking about campgrounds. I had Claude fork it, scrape every KOA location into a private database, and turn that into a sensor for nearby KOAs and whether we're checked into one.

The binder became a to-do list

This is the part I didn't plan on, and it might be the most useful thing in the whole build. We downloaded every manual for everything in the coach and saved them to Google Drive. In another project those became a quick-lookup manual for us, so "how do I reset the water heater" is a question, not a binder dig.

Then every maintenance interval in those PDFs went into Home Keeper, a maintenance and chore tracker for Home Assistant. Each task has a due date and cites the manual and page number it came from. We bought it used with no service history, so a bunch of those lit up as due on day one. Fun. That one's getting its own post too, because I think anyone who buys a used RV should do this.

Dashboards and alerts

Every device we've uncovered so far has a full dashboard: chassis, network, power, generator, environment. I'm sure we'll find more hiding in this coach soon. Across the top there's a notification bar for whatever is currently yelling at me.

Behind it there are about a dozen automations for the stuff you'd expect: power lost, internet down, things too hot or too cold, door opened, and a Pi that reboots itself if it loses the router. Because "the Pi fell off Wi-Fi and never came back" is the most homelab failure there is. It's janky in the best possible way, and it's built for an audience of one.

What's next

  • Power. I'll most likely end up with a Victron setup and ha-victron-mqtt, which sounds awesome and is (you guessed it) also on SmartyVan's Community Projects list.
  • Media in the rig. Jellyfin and Syncthing are already on the Pi. The plan is to sync the handful of shows we actually watch from home so we're not burning data on the road.
  • Internet on the road. Right now the gateway rides on our home Wi-Fi in the driveway. Out there, what should I use? Tether my phone? Turn on the Winegard's LTE? Swap it out for Winegard Starlink setup? I honestly don't know yet. Got any ideas, leave a comment!
  • Safety. A smart CO detector that actually talks to Home Assistant.

Big thanks to SmartyVan. A good chunk of this build exists because he showed his work first. If you're into RV or van automation, go subscribe.

Do you run Home Assistant in your rig? What did you wire in first, and what do you wish you'd done sooner? And if you've solved RV internet, tell me what you went with. Let me know, I'm curious. More on this soon.