fix: add missing Platform.SIGNAL to toolset mappings, update test + config docs
Platform.SIGNAL was missing from default_toolset_map and platform_config_key in gateway/run.py, causing Signal to silently fall back to hermes-telegram toolset (same bug as HomeAssistant, fixed in PR #538). Also updates: - tests/test_toolsets.py: include hermes-signal and hermes-homeassistant in the platform core-tools consistency check - cli-config.yaml.example: document signal and homeassistant platform keys
This commit is contained in:
parent
ee4008431a
commit
1aa7badb3c
3 changed files with 12 additions and 6 deletions
|
|
@ -2402,6 +2402,7 @@ class GatewayRunner:
|
|||
Platform.DISCORD: "hermes-discord",
|
||||
Platform.WHATSAPP: "hermes-whatsapp",
|
||||
Platform.SLACK: "hermes-slack",
|
||||
Platform.SIGNAL: "hermes-signal",
|
||||
Platform.HOMEASSISTANT: "hermes-homeassistant",
|
||||
}
|
||||
|
||||
|
|
@ -2424,6 +2425,7 @@ class GatewayRunner:
|
|||
Platform.DISCORD: "discord",
|
||||
Platform.WHATSAPP: "whatsapp",
|
||||
Platform.SLACK: "slack",
|
||||
Platform.SIGNAL: "signal",
|
||||
Platform.HOMEASSISTANT: "homeassistant",
|
||||
}.get(source.platform, "telegram")
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue