Google Home

The SCCS appears in the Google Home app and enables Gemini support once configured. Lights, relays, scenes, door reeds, temperatures and the water tank are exported. Google Home is off by default — turn it on from installer menu 10 or enable it from config file, restarting the SCCS service after saving the change.

HomeKit and Google Home can run at the same time. They are two front doors onto the same lighting engine. Last write wins if Siri and Gemini both touch a light.

Your phone needs to be connected to the LAN/Wi-Fi to pair and to control things locally. You can not access Google Home/Gemini through the uplink Cloudflare tunnel. Remote Gemini away from the caravan/camper needs a Nest Hub or Nest Mini on the LAN/Wi-Fi.

Google Home needs IPv6 on the LAN/Wi-Fi. Installer menu 6 sets the LAN/Wi-Fi to IPv6 link-local only — no IPv6 default route, no ISP IPv6 required.

Sliders, Gemini and the Google Home app all count as a manual override: they stick until a reed or phase change clears them (relays keep their last on/off until you toggle them again). Reed-closed lights stay off except the usual rooftop-tent safety clamp.

Important Note - Google Home can't start listening on the wired network card until the Raspberry Pi is connected to the local LAN/Wi-Fi ethernet switch. This will be shown on the Google Home settings tile until it detects a LAN connection.

Enable

Turn it on from installer menu 10 (or sudo ~/sccs/install.sh --voice), or set enabled = true in the config file and restart the SCCS service. Menu 10 can enable HomeKit and Google Home in one go and checks discovery and Node.js.

The Google Home tile will be visible once Google Home is enabled in the config. Once it is on then use the tile to pair or reset.

You can still edit config/sccs.conf by hand (sudo nano, or \\10.10.10.1\sccs\config\sccs.conf on the Samba share):

[matter]
enabled = true
name = SCCS
port = 5540
bind_address = 10.10.10.1
persist_file = config/matter.state

bind_address should be the Raspberry Pi's LAN/Wi-Fi IP (default 10.10.10.1). Do not set 0.0.0.0 or the WAN / USB-hotspot address — that would advertise Google Home on the internet side.
After a hand-edit, restart:

sudo systemctl restart sccs

Pair

Join the phone to the LAN/Wi-Fi (not the upstream hotspot/Starlink).
Open the SCCS Settings tab → Google Home tile. You should see Waiting to Pair, a QR code, and the setup code.
In the Google Home app: Set up device → New device → Matter-enabled device → scan the QR (or type the code).

After pairing the tile shows Connected to Google Home.

What appears in Google Home

Same set as HomeKit: PWM dimmers, Bug Mode switches on rgb_bug lights, floodlights as on/off lights, other relays as switches, scenes as a momentary on (“Hey Google, turn on Bedtime”), reeds as contact sensors, temperatures, water tank as a humidity % (Matter has no tank type).

Screens, Sonos, GPS and Day/Evening/Night are not exported.

Everyday behaviour matches the web UI and HomeKit: Siri/Gemini/sliders are manual overrides until a reed or phase change; rooftop tent safety still applies.

Reset pairing

On Settings → Google Home, tap Reset pairing then Confirm reset. That forgets the current pairing and shows a new QR.

Every Google Home that had SCCS must remove the old device and add it again. HomeKit pairing is not affected.

Remote access

Local control only works while the phone is on the LAN/Wi-Fi.

For “Hey Google, turn the kitchen lights on” from the supermarket you need a Nest Hub or Nest Mini left on the LAN/Wi-Fi. This functionality is generally not required as the lighting is automated.