Troubleshooting

Answers take a while

That's the trade for running privately on a Raspberry Pi. The local model writes about two words a second, so a short answer usually takes tens of seconds and a long one can run past a minute. The first word usually lands within a few seconds. Questions about the device itself (is this private, what's left the box, how's the system, what time is it) come back almost instantly, because the device answers them directly. If you want speed and depth for a hard task, that's what Boosted mode is for.

The first answer after a quiet spell is slow

When the device has been idle it frees memory, and the model reloads on your next question. That first answer is slower; after that it's back to normal.

The screen is dark but it's still talking

Give it a minute. If it stays dark, pull the power and plug it back in. It's an appliance, and power cycling is a supported move. From your paired phone you can also try ≡ → Fix screen.

My phone can't reach it

• The phone and the device must be on the same network. There's no cloud relay, so it doesn't work from outside your home.
• Guest networks and "AP isolation" block devices from reaching each other. Use your normal network, or connect the device by Ethernet.
• If a .local address doesn't open, use the IP address shown on the device's screen.

The clock or a reminder is off after a power cut

There's no clock battery inside. Time comes from your network. After a power cut with no internet, the clock starts from the last shutdown, and reminders set by wall-clock time may be off until the network time returns.

It switched to a smaller model

With 8 GB of memory, if RAM gets tight it drops to the local Llama 3.2 3B fallback, and it tells you when that happens. Everything still stays on the device.

Getting help

Email [email protected] with the serial from the back of your business card. If it helps, attach the diagnostics bundle from the phone app. It contains logs only, never conversations, memories or credentials.