Allow saving settings and enabling wake word without OpenClaw connection - #728
Merged
yuga-hashimoto merged 1 commit intoJun 17, 2026
Conversation
Two changes to support using Wake Hermes Claw with a Hermes API Server backend (e.g. via p2p/phyo-OS) without needing an OpenClaw gateway or HTTP connection manually configured: 1. SettingsActivity.kt: Remove the gateway/HTTP host requirement from the Save button's enabled state so wake word preferences can be saved without an OpenClaw connection. Guard connectManual() against empty host to avoid attempting a connection to nothing. 2. MainActivity.kt: In toggleHotwordService(), also check BackendManager for any configured backend (Hermes API Server, etc.) before blocking wake word enablement. Previously only checked gateway manual host or HTTP URL settings. Also fixes two pre-existing lint errors (StringFormatInvalid) that were blocking CI: adds missing %%s format placeholder to operator_offline_command and approve_command_format strings across all 9 locale files.
Lloyd-Jackman-UKPL
force-pushed
the
fix/wake-word-without-openclaw
branch
from
June 16, 2026 21:14
d5ab196 to
b10e777
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two changes to support using Wake Hermes Claw with a Hermes API Server backend (e.g. via p2p/phy-OS) without needing an OpenClaw gateway or HTTP connection manually configured:
SettingsActivity.kt:enabledstate — users who only need to save wake word preferences shouldn't be forced to configure an OpenClaw connection firstconnectManual()against an empty host so saving with no gateway configured doesn't attempt a pointless connectionMainActivity.kt:toggleHotwordService(), also checkBackendManager.chatTargets()for any configured backend (Hermes API Server, etc.) before blocking wake word enablementruntime.manualHostorsettings.httpUrl, which meant wake word was impossible to enable without an OpenClaw gateway or HTTP connection even when a fully-working Hermes API Server backend was already configured and showing as "Connected" on the home screenLines changed: 7 insertions, 4 deletions across 2 files.