openclaw - 💡(How to fix) Fix WhatsApp: message tool send fails with 'No active WhatsApp Web listener' while channel is connected (duplicate of #49345) [2 comments, 3 participants]

Error: No active WhatsApp Web listener (account: default)

Fix Plan

To resolve the issue of the message tool's proactive send path failing with "No active WhatsApp Web listener," we need to synchronize the listener registries between the proactive send path and the auto-reply path.

Steps to Fix

• Merge the listener registries into a single, shared registry.
• Update the message tool to use the shared registry for sending proactive messages.
• Ensure the shared registry is properly initialized and updated when the WhatsApp Web listener status changes.

Example Code

# Create a shared registry
shared_registry = {}

# Initialize the shared registry with the WhatsApp Web listener status
def init_shared_registry():
    shared_registry['whatsapp_web_listener'] = False

# Update the shared registry when the WhatsApp Web listener status changes
def update_shared_registry(status):
    shared_registry['whatsapp_web_listener'] = status

# Use the shared registry in the message tool
def send_proactive_message(message):
    if shared_registry['whatsapp_web_listener']:
        # Send the message using the WhatsApp Web listener
        pass
    else:
        # Handle the case where the WhatsApp Web listener is not active
        pass

Verification

To verify the fix, run the following tests:

• Send a proactive WhatsApp message using the message tool.
• Check the WhatsApp Web listener status using openclaw channels status --probe.
• Verify that the message is sent successfully and the listener status is updated correctly.

Extra Tips

• Ensure that the shared registry is properly synchronized across all components that use it.
• Consider adding logging and error handling to the shared registry updates to detect and handle any issues that may arise.