Connect via Multi-Device API.
Send a status using the standard top-level options for Companions:
javascript
const sendOptions = {
broadcast: true,
participant: sock.user.id.replace(/:.@/, "@"), // Forces the P2P Companion Tag
statusJidList: [ ...targetJids, sock.user.id.replace(/:.@/, "@") ]
};
await sock.sendMessage("status@broadcast", { text: "Test Status", backgroundColor: "#075e54" }, sendOptions);
Observe the server response: No 503 Service Unavailable is thrown (the P2P injection works).
Observe the local listener: An upsert event is successfully fired back from the server with remoteJid: "status@broadcast" and fromMe: true (indicating WhatsApp accepted and propagated the message).
Open the paired WhatsApp App on your phone: The status is nowhere to be seen under the "My Status" screen.
Expected Behavior: The broadcasted status should display seamlessly in the user's primary mobile device under "My Status", just as it used to natively behave.
Additional Context:
We verified that the fallback to native P2P relayMessage using additionalNodes containing avoids the strict stream crash (503), but it still suffers from this UI silence on the phone client.
Seems that Baileys/WSocket needs to implement newer binary meta-tags or protocol handshakes explicitly designed for V2/V3 Companion Device Histories to prevent the mobile app from flagging them as spam or dummy nodes.
Connect via Multi-Device API.
Send a status using the standard top-level options for Companions:
javascript
const sendOptions = {
broadcast: true,
participant: sock.user.id.replace(/:.@/, "@"), // Forces the P2P Companion Tag
statusJidList: [ ...targetJids, sock.user.id.replace(/:.@/, "@") ]
};
await sock.sendMessage("status@broadcast", { text: "Test Status", backgroundColor: "#075e54" }, sendOptions);
Observe the server response: No 503 Service Unavailable is thrown (the P2P injection works).
Observe the local listener: An upsert event is successfully fired back from the server with remoteJid: "status@broadcast" and fromMe: true (indicating WhatsApp accepted and propagated the message).
Open the paired WhatsApp App on your phone: The status is nowhere to be seen under the "My Status" screen.
Expected Behavior: The broadcasted status should display seamlessly in the user's primary mobile device under "My Status", just as it used to natively behave.
Additional Context:
We verified that the fallback to native P2P relayMessage using additionalNodes containing avoids the strict stream crash (503), but it still suffers from this UI silence on the phone client.
Seems that Baileys/WSocket needs to implement newer binary meta-tags or protocol handshakes explicitly designed for V2/V3 Companion Device Histories to prevent the mobile app from flagging them as spam or dummy nodes.