#/sethome not working?
1 messages · Page 1 of 1 (latest)
That screenshot is not expected if the same gateway process handled both messages.
When /sethome succeeds on Signal, Hermes should save a SIGNAL_HOME_CHANNEL value and use it immediately. If the next message still says no Signal home channel is set, the first thing I’d check is whether the gateway that replied to /sethome is the same gateway/profile handling the next message.
Please run these:
grep '^SIGNAL_HOME_CHANNEL=' ~/.hermes/.env
pgrep -af "hermes.*gateway run"
If you are using a Hermes profile, check that profile’s env instead:
grep '^SIGNAL_HOME_CHANNEL=' ~/.hermes/profiles/<profile>/.env
Then restart the gateway once:
hermes gateway restart
If SIGNAL_HOME_CHANNEL is missing, /sethome likely wrote to a different Hermes home/profile or failed to persist even though it replied success.
If SIGNAL_HOME_CHANNEL is present and there is only one gateway process running, this looks like a Signal /sethome bug. In that case, please send a fresh hermes debug share right after reproducing it, plus the redacted output of the two checks above.
Were you able to get this resolved?