Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix [WhatsApp] send_message tool: "No home channel set" even when WHATSAPP_HOME_CHANNEL is configured [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#17295•Fetched 2026-04-30 06:48:37
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
john-data-chenjohn-data-chen
Participants
alt-glitchalt-glitchjohn-data-chenjohn-data-chen
Timeline (top)
labeled ×5commented ×1cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #17449: fix(gateway): load WhatsApp home channel from env overrides

Description (problem / solution / changelog)

Summary

Load WHATSAPP_HOME_CHANNEL and WHATSAPP_HOME_CHANNEL_NAME into GatewayConfig during env override application.

Before this change, WhatsApp only honored WHATSAPP_ENABLED in gateway/config.py, but did not map the home-channel env vars into PlatformConfig.home_channel. That meant WhatsApp could be enabled while config.get_home_channel(Platform.WHATSAPP) still returned None, unlike the other messaging platforms.

Fix

  • add WhatsApp home-channel env override handling in gateway/config.py
  • add a regression case to TestHomeChannelEnvOverrides in tests/gateway/test_config.py

Why this matters

Several gateway paths use config.get_home_channel(...) as the source of truth for delivery/context behavior. Without this mapping, WhatsApp home-channel state could be present in env but effectively invisible to those code paths after config load.

Testing

Ran targeted gateway config tests:

  • tests/gateway/test_config.py

Result:

  • 33 passed, 0 failed

Changed files

  • gateway/config.py (modified, +8/-1)
  • tests/gateway/test_config.py (modified, +9/-0)
RAW_BUFFERClick to expand / collapse

Bug Description

The send_message tool always returns "No home channel set" for WhatsApp, even when WHATSAPP_HOME_CHANNEL is correctly configured in config.yaml.

Environment

  • macOS
  • Hermes Gateway running (via launchd)
  • WhatsApp: connected

Reproduction Steps

  1. Set WHATSAPP_HOME_CHANNEL in config.yaml: WHATSAPP_HOME_CHANNEL: xxxxxxxxxxxxxx@lid
  2. Restart gateway: hermes gateway restart
  3. Try to send a message via send_message tool

Expected Behavior

Message should be sent to the WhatsApp home channel.

Actual Behavior

"No home channel set for whatsapp to determine where to send the message. Either specify a channel directly with 'whatsapp:CHANNEL_NAME', or set a home channel via: hermes config set WHATSAPP_HOME_CHANNEL <channel_id>"

Additional Context

  • Gateway logs show WhatsApp connected and working
  • Channel directory shows 1 target
  • Messages between user and agent flow correctly
  • Only the send_message tool fails

extent analysis

TL;DR

The issue may be resolved by verifying the WHATSAPP_HOME_CHANNEL configuration value and ensuring it matches the expected format.

Guidance

  • Check the config.yaml file to confirm that the WHATSAPP_HOME_CHANNEL value is correctly set and formatted as xxxxxxxxxxxxxx@lid.
  • Verify that the hermes gateway restart command successfully reloads the configuration changes.
  • Review the gateway logs to ensure there are no errors related to loading the config.yaml file.
  • Test sending a message using the send_message tool with the whatsapp:CHANNEL_NAME syntax to see if it works as expected.

Example

No code snippet is provided as it's not necessary for this issue.

Notes

The issue seems to be specific to the send_message tool and the WHATSAPP_HOME_CHANNEL configuration. The fact that messages flow correctly between the user and agent suggests that the WhatsApp connection is working.

Recommendation

Apply workaround: Use the whatsapp:CHANNEL_NAME syntax with the send_message tool to specify the channel directly, as this may bypass the issue with the WHATSAPP_HOME_CHANNEL configuration.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#device allocation#model download#tokenizer error#prompt formatting#chain error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING