gausma / nodered-contrib-signal-client

Signal communicator client nodes for Node-RED
GNU General Public License v3.0
33 stars 13 forks source link

Can't send messages since approximately 6 weeks #28

Open trasba opened 2 years ago

trasba commented 2 years ago

Hi, I had a working setup. Actually didn't notice that the send functionality broke at some point. 9. Jun. was the last time my phone received a message from the flow. However I thought it might be a registration or version issue so I reregistered the number and updated to the latest version but I am still stuck. Really odd is that receiving messages works.

7/26/2021, 10:57:58 AMnode: 96171439.167ef8
msg.payload : Object
object
receiverNumber: "+49xxx"
senderNumber: "+49xxx"
content: "Test"

Sending does not. But there is no error or anything alike

7/26/2021, 10:53:40 AMnode: b196724d.a8f87
msg.payload : Object
object
receiverNumber: "+49xxx"
senderNumber: "+49xxx"
content: "Hello MAG"

My setup is running in a docker container the log file gives me this a lot. But I think it's unrelated. #16

V1 session storage migration error: registrationId undefined for open session version undefined

This is from the log:

26 Jul 08:57:58 - [info] [send:e00c46a4.ff5ff8] Signal client message sent: {"successfulIdentifiers":["+49xxx"],"failoverIdentifiers":[],"errors":[],"unidentifiedDeliveries":[],"dataMessage":{"type":"Buffer","data":[10,4,84,101,115,116,50,3,90,213,96,56,249,252,163,144,174,47]}}

Any ideas?