The glasses relay the charging case's state on UX_GLASSES_CASE_APP_ID
(sid 0x81): GlassesCaseDataPackage{commandId=CASE_INFO, magicRandom,
caseInfo{soc, chargeStatus, lidStatus, inCaseStatus, errorCode}}, the
schema in g2-kit-unofficial's glasses_case.proto. The Even app reads it
with an empty caseInfo (ProtoBaseSettings.getGlassesCaseInfo).
Observed on G2 2.3.0.24 / Faceclaw/38: while docked the right temple
pushes a GlassesCaseInfo (flag 0x01, its own magic) on every change --
docking, lid, USB, each 1% -- and answers a read with full data; out of
the case a read comes back with an empty caseInfo. Docking pushes
{inCaseStatus=1} before the level, and proto3 drops zero fields, so a
missing soc means no level rather than 0%.
So read it once at session start (docked glasses may be fully charged
and never enter charging mode) and again on entering charging mode,
which clears the queue; pushes carry every later change. Every 0x81
frame is taken as state in onNotification (pushes skip the ack path by
flag). New readings reach TypeScript through
FaceclawBleCommunicatorListener.onCaseState (level, case-charging), on
Android and iOS. Captured frames are tests.
Node cannot hand gradlew.bat to CreateProcess (EINVAL); run the wrapper
through a shell there. Two tests also assumed a POSIX checkout's
trailing newline and path separators.
A "Hermes agent" assistant model talks to a Hermes Agent gateway's
OpenAI-compatible API server (streamed /v1/chat/completions), with Hermes URL
and key settings under Assistant. Hermes keeps the conversation: each
assistant session maps to one X-Hermes-Session-Id and only the latest user
message is sent. Faceclaw's own tools are not offered to it, and its reasoning
stream is not shown on the glasses. See notes/hermes-assistant.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>