[BUG]配置飞书之后发消息没有反应

[zhang-sir029]

Quick Summary

Environment & Tools

• PicoClaw Version: (e.g., v0.1.2 or commit hash)
• Go Version: (e.g., go 1.22)
• AI Model & Provider: (e.g., GPT-4o via OpenAI / DeepSeek via SiliconFlow)
• **Operating System:Android Termux
• **Channels:Feishu
• 我的硬件型号是小米路由器3G，系统是openwrt 24版本，支持的指令集是mipsel_24kc_softfloat

📸 Steps to Reproduce

1.书的APP ID和secret都配置了，后台也能看到收到的消息，但就是不回复。我用那个agent杠m的命令发单条消息是有回复的，证明我的模型配置没问题，而且飞书上本身的各种权限都设置好了，我这个APPID和secret放在open claw上，飞书都是能回音的
如图：

2.建立长连接，这个appid和sec，发送信息有响应

3.添加接收信息，并发布

对比：同样的app id和sec配置在openclaw里就没问题，openclaw配置并启动了发飞书就有回复，请帮忙看看如何处理

[alexhoshina]

看报错是心跳超时相关的问题，我简单查看了代码，飞书channel使用的是飞书官方的go sdk，但是没有配置心跳时长。
具体问题如果没有飞书相关的开发者跟进的话，我会尝试去跟进，但是对于飞书的sdk和api我并不熟悉，可能需要的时间比较长。

[nikolasdehor]

Your hardware is the key issue here. You mentioned running on a Xiaomi Router 3G with mipsel_24kc_softfloat instruction set — this is a 32-bit MIPS architecture.

The Feishu channel has two implementations selected by build tags:

• pkg/channels/feishu/feishu_64.go — full implementation (build tag: amd64 || arm64 || riscv64 || mips64 || ppc64)
• pkg/channels/feishu/feishu_32.go — stub (build tag: \!amd64 && \!arm64 && \!riscv64 && \!mips64 && \!ppc64)

On your 32-bit MIPS platform, feishu_32.go is compiled instead of feishu_64.go. The stub returns nil for the channel and all methods are no-ops:

func NewFeishuChannel(cfg config.FeishuConfig, bus *bus.MessageBus) (*FeishuChannel, error) {
    return nil, errors.New(
        "feishu channel is not supported on 32-bit architectures (armv7l, 386, etc.)")
}

This is because the Feishu SDK (github.com/larksuite/oapi-sdk-go/v3) depends on packages that do not compile on 32-bit architectures (likely protobuf/grpc-related 64-bit integer alignment issues).

The channel likely initializes without a visible error because pkg/channels/manager.go treats channel init failures as warnings rather than fatal errors — it logs the error but continues starting other channels. This explains why "the backend can see received messages" (Feishu servers deliver webhooks) but PicoClaw never replies (the channel stub cannot send).

Options:

1. Use a 64-bit MIPS device (mips64 build tag would enable the full Feishu channel)
2. Run PicoClaw on a different device (e.g., a Raspberry Pi with arm64) and expose it to your network
3. Use OpenClaw (which has full Feishu support) as you mentioned works — the difference is OpenClaw runs on Node.js which does not have this 32-bit limitation

Check your startup logs for a line like "feishu channel is not supported on 32-bit architectures" to confirm this diagnosis.