Summary

Issue Report: WhatsApp Gateway DNS Hiccup & Timeout Reconnects

Steps to reproduce

1. Not sure

should reconnect

Actual behavior

1. DNS Glitch: Experienced a disconnect at 02:02 CST with error EAI_AGAIN web.whatsapp.com. The gateway stayed disconnected until a manual restart later that morning.
2. Aggressive Heartbeat: Noticed that the gateway intentionally forces a reconnect (status 499) after exactly 30 minutes of message inactivity ("No messages received in 30m - restarting connection"). While it reconnects quickly, it causes a "gateway disconnected/connected" system alert loop for the user during quiet periods.

Suggested Improvements:

• Could the gateway be more resilient to transient DNS/EAI_AGAIN errors before staying down?
• Is the 30-minute hard-reconnect necessary if the WebSocket still appears healthy, or could that interval be configurable to reduce "disconnect" notification

Environment

• openclaw version: We are currently on version 2026.2.6-3 (build 85ed6c7).
• OS: Raspberry PI OS
• wizard install

Logs or screenshots

Paste relevant logs or add screenshots (redact secrets).