Experienced using signal-cli-rest-api
Details below copied from bbernhard/signal-cli-rest-api#876
When sending a message to the sending number and causing the message to be received as a 'Note to Self', no payload is received on the websocket.
The message and notification is received on the device (using an iPhone) logged into the Signal account, but there's no payload, including when reading the message.
Using signal-cli-rest-api v0.100 (signal-cli v0.14.5) Docker Container in JSON-RPC-Native Mode on x86-64 architecture
Release notes for v0.14.6 and v0.14.7 don't appear to have anything related to this issue, but let me know if I should test with v0.14.7.
The message also appears as though it was sent by someone else, appearing from the left side, rather than the right side and in blue.
Sending a 'Note to Self' using the iPhone and official Signal client triggers a payload to be received on the websocket for the message content, as well as the read receipt.
Other payloads are also received as expected, such as when receiving a message sent from a different number using the same signal-cli-rest-api instance.
Might be related to #1930 (fixed in signal-cli v0.14.0)
I use signal-cli-rest-api paired with Node-RED to detect and forward Signal messages received on an on-call phone to a group chat with the potential on-call staff, as sometimes the on-call person does not physically have the on-call phone.
Phone calls and texts are forwarded via other means.
The Node-RED flow sends regular heartbeats to healthchecks.io to confirm the forwarding service is active, if the websocket connection status between Node-RED and signal-cli-rest-api is live and the last payload was received <7 days ago.
Shortly before the 7 day window of no payloads is reached, a Note to Self is sent. This resulting in a payload being received verifies that there has not been a silent failure and that messages can continue to be forwarded.
As a workaround, the Note to Self is currently being sent using a signal-cli-rest-api connection to a different Signal account.
Experienced using signal-cli-rest-api
Details below copied from bbernhard/signal-cli-rest-api#876
When sending a message to the sending number and causing the message to be received as a 'Note to Self', no payload is received on the websocket.
The message and notification is received on the device (using an iPhone) logged into the Signal account, but there's no payload, including when reading the message.
Using signal-cli-rest-api v0.100 (signal-cli v0.14.5) Docker Container in JSON-RPC-Native Mode on x86-64 architecture
Release notes for v0.14.6 and v0.14.7 don't appear to have anything related to this issue, but let me know if I should test with v0.14.7.
The message also appears as though it was sent by someone else, appearing from the left side, rather than the right side and in blue.
Sending a 'Note to Self' using the iPhone and official Signal client triggers a payload to be received on the websocket for the message content, as well as the read receipt.
Other payloads are also received as expected, such as when receiving a message sent from a different number using the same signal-cli-rest-api instance.
Might be related to #1930 (fixed in signal-cli v0.14.0)
I use signal-cli-rest-api paired with Node-RED to detect and forward Signal messages received on an on-call phone to a group chat with the potential on-call staff, as sometimes the on-call person does not physically have the on-call phone.
Phone calls and texts are forwarded via other means.
The Node-RED flow sends regular heartbeats to healthchecks.io to confirm the forwarding service is active, if the websocket connection status between Node-RED and signal-cli-rest-api is live and the last payload was received <7 days ago.
Shortly before the 7 day window of no payloads is reached, a Note to Self is sent. This resulting in a payload being received verifies that there has not been a silent failure and that messages can continue to be forwarded.
As a workaround, the Note to Self is currently being sent using a signal-cli-rest-api connection to a different Signal account.