openclaw - 💡(How to fix) Fix WhatsApp: message tool send fails with 'No active WhatsApp Web listener' while channel is connected and replies work [4 comments, 4 participants]

Gateway logs show WhatsApp connected and listening:

[whatsapp] [default] starting provider (+15615039444)
[whatsapp] Listening for personal WhatsApp inbound messages.

But sends fail:

[ws] ⇄ res ✗ send 9ms errorCode=UNAVAILABLE errorMessage=Error: No active WhatsApp Web listener...

Fix Plan

To resolve the issue with the message tool's send action failing due to "No active WhatsApp Web listener," we need to ensure the listener registry is properly populated for the send path.

Step-by-Step Solution:

1. Update Listener Registry Check: Modify the auth-profiles-*.js, reply-*.js, and model-selection-*.js files to correctly populate the listener registry for the send path.
2. Verify WhatsApp Connection: Before sending a message, ensure the WhatsApp connection is active by checking the gateway logs for the "Listening for personal WhatsApp inbound messages" message.
3. Code Changes: Update the send path logic to use the same mechanism as the reply path to reach the WhatsApp connection.

Example Code Snippet (JavaScript):

// Assuming 'listener' is the variable checked for WhatsApp listener availability
if (!listener) {
  // Instead of throwing an error, try to establish or retrieve the WhatsApp connection
  listener = getWhatsAppListener(); // Implement getWhatsAppListener() to return the active listener
  if (!listener) {
    throw new Error('No active WhatsApp Web listener');
  }
}

// Function to retrieve the WhatsApp listener, similar to how the reply path works
function getWhatsAppListener() {
  // Logic to retrieve or establish the WhatsApp listener, potentially using the same method as the reply path
  // For demonstration purposes, assume 'whatsappConnection' is the established connection
  const whatsappConnection = getEstablishedWhatsAppConnection();
  return whatsappConnection.listener;
}

// Example function to establish or retrieve the WhatsApp connection
function getEstablishedWhatsAppConnection() {
  // Implement logic to establish or retrieve the WhatsApp connection
  // This could involve checking the gateway logs, the channel status, or directly querying the WhatsApp API
  // For simplicity, assume the connection is already established and stored
  return {
    listener: {
      // Properties and methods of the listener
    }
  };
}

Verification

To verify the fix worked:

• Run the message tool with action=send, channel=whatsapp, target=<phone> again.
• Check the gateway logs for successful send operations.
• Test proactive message sending through cron jobs or other automated processes.

Extra Tips

• Ensure all dependencies and libraries are up-to-date, as regressions can sometimes be caused by version mismatches.
• Review the WhatsApp API documentation and the library or framework used for WhatsApp integration to ensure compliance with the latest requirements and best practices.
• Consider implementing additional logging or monitoring to detect and diagnose similar issues more efficiently in the future.