Feature Request - New group chat

[tschuse]

I want to use a group chat, but I can't add this client to a group. The message: "user must update the client" This is a problem regarding the new group type.

[SilvainLouis]

Same question, when I receive a message from a group, the senderNumber is the same that a personnal message

[tschuse]

I can‘t add my number to a new group. 🙁

[soleous]

Also interested in this :)

[Hagbard235]

I could add the number to a group, but there is no way of telling whether the message is from a group or an individual

[EngDiego]

Same msg here: "user must update the client".

[Hagbard235]

"user must update the client" is maybe a problem with the group? I've add the numer directly as first client in the group, no problem. Existing groups may be a problem?

[tschuse]

This is a problem with new groups. Signal changed the Type of groups. You can add this Client only in Groups from old types

[JamborJan]

Hey @gausma are you still maintaining this repository? Can we be of any help keeping it alive? It's a great contribution to Node Red and I would love to use it in new group chats. Would be great to see some progress or to help making progress possible.

[JamborJan]

I dug a bit into that. You could add your account to a group with a hack via signal-cli like described here: https://ctrl.alt.coop/en/post/signal-without-a-smartphone/. Basically, register & verify with signal-cli add some profile info - that's the important part. After that, you can add the account to groups via signal-cli with a login link.

Further reading for signal-cli commands: https://github.com/AsamK/signal-cli/blob/master/man/signal-cli.1.adoc

After that, you can log in with the Node-Red process.

But then you still can only send messages to contacts and not to groups. The way this node is currently implemented is not allowing it by e.g. extending the payload (which is understandable):

https://github.com/gausma/nodered-contrib-signal-client/blob/c6d17db4bf57597e7fd2fffd80eee22b29830f55/src/signal-client.js#L295-L315

So without any core changes nothing will go forward here.

Workarounds that come to my mind:

• is it possible somehow to put the signal-cli into the Node-Red instance and trigger it via a node?
• slap an API over the CLI and put it into a container. Send dto's via POST nodes to this container. This would not solve receiving messages, only sending.