Troubleshooting

No connection

First check that the URL uses HTTPS, the device online entity is true and revision/ACK advance. For Handshake failed, check device date/time, CA trust, DNS and routing. On a routed device set the connection host to a reachable HA IP. Enable the insecure certificate option only on an isolated legacy network. If the app reports a changed key, verify and confirm the displayed fingerprint; repeated reconnect is deliberately paused meanwhile.

Configuration or preview

Parse errors appear in the JSON editor. Publication fails for duplicate IDs, an unknown tab_order ID, a secret field or a missing provider. For wrong layout select the device, orientation and Fit zoom. Preview shows fixed Android geometry; small font and native-control differences are normal. Missing images use neutral placeholders and do not change the grid.

Assist

Check microphone permission, voice_assistant.enabled, pipeline, wake-word engine and selected active_wake_words. If a long phrase never reaches HA, check control-channel online status and the separate voice stream; transport pings are disabled while application heartbeats must continue. For very quiet output check media volume, audio_route, TTS output and status-sound volume.

Camera, Immich and MA

Camera needs permission and enabled camera configuration; a physically covered wall camera is expected to return black. Test direct LAN mode when tunnel mode fails. Immich HTTP 400 usually indicates URL/API version or search filters; test the provider connection server-side. For MA first check the official integration, target player and provider binding.

Logs and diagnostics

HA: Settings → System → Logs, logger custom_components.rustyhama; device status and redacted diagnostics from the integration card. Android with ADB: adb logcat --pid=$(adb shell pidof net.spittank.home.rustyhama). Never include credentials, pairing tokens, provider keys or complete private URLs in a report.