GithubHelp home page GithubHelp logo

gausma / nodered-contrib-signal-client Goto Github PK

View Code? Open in Web Editor NEW
33.0 33.0 13.0 842 KB

Signal communicator client nodes for Node-RED

License: GNU General Public License v3.0

JavaScript 69.21% HTML 30.79%

nodered-contrib-signal-client's People

Contributors

gausma avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

cephos zinnchen mlocode cameo69 michaldck buzz-tee fanuch photoangell it-vbfk deralff nearservices rgstephens n-b-dy

nodered-contrib-signal-client's Issues

I cannot send Signal but I can receive message.

Node red on Home Assistant can only receive message but it can't send it.
Here the error :
"Signal client error: {"successfulIdentifiers":[],"failoverIdentifiers":[],"errors":[{"name":"UnregisteredUserError","identifier":"(here my phone number)","code":404,"reason":"Failed to create or send message"}],"unidentifiedDeliveries":[],"dataMessage":{"type":"Buffer","data":[10,13,67,39,101,115,116,32,117,110,32,116,101,115,116,50,5,188,50,195,75,204,56,252,159,202,155,185,47]}}"

Thanks for your help.

Autodelete disables with new messages

Hi, i have ist in use on my node-red pi, all sending works fine, so i moved from Telegram to Signal.

It would be a great help that the auto-delete feature (after 1 day or so) works.
With evrey first new message after activation of auto-delte on my Android phone there is an information, that the auto-delete is turned off.

Regards

Registration problem

After send request-sms or request-voice I get this message and sms code is not send:
"Signal client error: {"name":"HTTPError","code":402,"response":"<html>\n<head>\n<meta http-equiv=\"Content-Type\" content=\"text/html;charset=utf-8\"/>\n<title>Error 402 Payment Required</title>\n</head>\n<body><h2>HTTP ERROR 402 Payment Required</h2>\n<table>\n<tr><th>URI:</th><td>/v1/accounts/sms/code/+48*********</td></tr>\n<tr><th>STATUS:</th><td>402</td></tr>\n<tr><th>MESSAGE:</th><td>Payment Required</td></tr>\n<tr><th>SERVLET:</th><td>io.dropwizard.jersey.setup.JerseyServletContainer-289cf7db</td></tr>\n</table>\n\n</body>\n</html>\n"}"

Can't send messages since approximately 6 weeks

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?

feature request: request voice node

Amazing project. Really nice documentation. I was stunned when I saw that you created this project just 2 days ago. That's a really nice way to have push notifications out of NodeRed. Even chatbots are possible 👍

I'm trying to register a fixed line number where I can't receive an sms. I saw the library supports voice verification (https://github.com/gausma/libsignal-service-javascript/blob/a197c985628694a66c151b4ffa0a2ec20de45f2b/src/AccountManager.js#L45). Am I correct that it shouldn't be much more then a copy of RequestSMSNode (maybe RequestVoiceNode) with this line (

nodered-contrib-signal-client/src/signal-client.js

Line 57 in 64ac5a3

await accountManager.requestSMSVerification();
) changed to requestVoiceVerification()?

I just started with using NodeRed 5 days ago but I'm willing to provide a PR if you would accept.

Receiving message does not work because of lost connection.

I have this simple example flow

grafik

After some time this node loses connection with signal servers. When I send a message to the number it listens from another signal app, I see that the message isn't delivered to recipient. When I disable the Node und re-enable message is received again.

Can you please have a look?

Registration-Error: Credentials are required to access this resource

I followed your registration procedure but got stuck on the final "register" action, when I receive the following error:

"Signal client error: {"name":"HTTPError","code":401,"response":"Credentials are required to access this resource."}"

These are the steps I performed:

  1. Created a new account configuration wiith a fixed-line phonenumber and a random password
  2. Gathered a captcha code as described and filled that into your example "request-voice" node.
  3. Deployed config and triggered the "requst-voice" node.
  4. Received automated voice call and noted the verification code.
  5. Filled in account and verification code into the "register" node.
  6. Deployed confg and triggered "register" node, which provided the error message above.

Did I miss anything, or is this a bug on client or service side?

Node-RED package installaion problem

I have a problem with installation of this package on the Node-RED,
Could you have a look what is going on here?

2021-01-14T08:44:24.689Z Install : nodered-contrib-signal-client 2.0.1

2021-01-14T08:44:24.892Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production [email protected]
2021-01-14T08:45:20.151Z [out]
2021-01-14T08:45:20.151Z [out] > [email protected] install /config/node-red/node_modules/fs-ext
2021-01-14T08:45:20.151Z [out] > node-gyp configure build
2021-01-14T08:45:20.151Z [out]
2021-01-14T08:45:22.891Z [err] gyp
2021-01-14T08:45:22.891Z [err]
2021-01-14T08:45:22.892Z [err] ERR! build error
2021-01-14T08:45:22.893Z [err] gyp
2021-01-14T08:45:22.894Z [err] ERR!
2021-01-14T08:45:22.894Z [err] stack Error: not found: make
2021-01-14T08:45:22.894Z [err] gyp ERR! stack
2021-01-14T08:45:22.895Z [err] at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
2021-01-14T08:45:22.895Z [err] gyp ERR!
2021-01-14T08:45:22.895Z [err] stack
2021-01-14T08:45:22.895Z [err] at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
2021-01-14T08:45:22.895Z [err] gyp ERR! stack
2021-01-14T08:45:22.895Z [err] at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
2021-01-14T08:45:22.895Z [err] gyp ERR!
2021-01-14T08:45:22.896Z [err] stack at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
2021-01-14T08:45:22.896Z [err] gyp ERR!
2021-01-14T08:45:22.896Z [err] stack at /usr/lib/node_modules/npm/node_modules/isexe/index.js:42:5
2021-01-14T08:45:22.896Z [err] gyp ERR! stack
2021-01-14T08:45:22.897Z [err] at /usr/lib/node_modules/npm/node_modules/isexe/mode.js:8:5
2021-01-14T08:45:22.897Z [err] gyp ERR! stack at FSReqCallback.oncomplete (fs.js:168:21)
2021-01-14T08:45:22.897Z [err] gyp
2021-01-14T08:45:22.898Z [err] ERR! System Linux 4.15.0-123-generic
2021-01-14T08:45:22.898Z [err] gyp ERR! command
2021-01-14T08:45:22.898Z [err] "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "build"
2021-01-14T08:45:22.898Z [err] gyp
2021-01-14T08:45:22.898Z [err] ERR! cwd /config/node-red/node_modules/fs-ext
2021-01-14T08:45:22.898Z [err] gyp
2021-01-14T08:45:22.898Z [err] ERR! node -v
2021-01-14T08:45:22.899Z [err] v12.18.4
2021-01-14T08:45:22.899Z [err] gyp
2021-01-14T08:45:22.899Z [err] ERR! node-gyp -v v5.1.0
2021-01-14T08:45:22.899Z [err] gyp ERR!
2021-01-14T08:45:22.899Z [err] not ok
2021-01-14T08:45:22.953Z [out]
2021-01-14T08:45:22.953Z [out] > [email protected] install /config/node-red/node_modules/bufferutil
2021-01-14T08:45:22.953Z [out] > node-gyp-build
2021-01-14T08:45:22.953Z [out]
2021-01-14T08:45:23.617Z [out]
2021-01-14T08:45:23.617Z [out] > [email protected] install /config/node-red/node_modules/utf-8-validate
2021-01-14T08:45:23.617Z [out] > node-gyp-build
2021-01-14T08:45:23.617Z [out]
2021-01-14T08:45:24.261Z [out]
2021-01-14T08:45:24.261Z [out] > [email protected] install /config/node-red/node_modules/node-webcrypto-ossl
2021-01-14T08:45:24.261Z [out] > node-gyp rebuild
2021-01-14T08:45:24.261Z [out]
2021-01-14T08:45:27.308Z [err] gyp
2021-01-14T08:45:27.309Z [err]
2021-01-14T08:45:27.309Z [err] ERR!
2021-01-14T08:45:27.309Z [err] build error
2021-01-14T08:45:27.311Z [err] gyp
2021-01-14T08:45:27.313Z [err] ERR! stack Error: not found: make
2021-01-14T08:45:27.313Z [err] gyp ERR! stack
2021-01-14T08:45:27.316Z [err] at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
2021-01-14T08:45:27.316Z [err] gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
2021-01-14T08:45:27.316Z [err] gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
2021-01-14T08:45:27.316Z [err] gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
2021-01-14T08:45:27.316Z [err] gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/isexe/index.js:42:5
2021-01-14T08:45:27.316Z [err] gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/isexe/mode.js:8:5
2021-01-14T08:45:27.316Z [err] gyp ERR! stack at FSReqCallback.oncomplete (fs.js:168:21)
2021-01-14T08:45:27.316Z [err] gyp
2021-01-14T08:45:27.316Z [err] ERR! System Linux 4.15.0-123-generic
2021-01-14T08:45:27.317Z [err] gyp
2021-01-14T08:45:27.317Z [err] ERR! command
2021-01-14T08:45:27.317Z [err] "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
2021-01-14T08:45:27.317Z [err] gyp
2021-01-14T08:45:27.317Z [err] ERR!
2021-01-14T08:45:27.317Z [err] cwd /config/node-red/node_modules/node-webcrypto-ossl
2021-01-14T08:45:27.317Z [err] gyp
2021-01-14T08:45:27.317Z [err] ERR!
2021-01-14T08:45:27.318Z [err] node -v v12.18.4
2021-01-14T08:45:27.318Z [err] gyp ERR!
2021-01-14T08:45:27.318Z [err] node-gyp -v v5.1.0
2021-01-14T08:45:27.318Z [err] gyp ERR!
2021-01-14T08:45:27.318Z [err] not ok
2021-01-14T08:45:30.761Z [err] npm
2021-01-14T08:45:30.761Z [err] WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fs-ext):
2021-01-14T08:45:30.761Z [err] npm WARN optional
2021-01-14T08:45:30.761Z [err] SKIPPING OPTIONAL DEPENDENCY: [email protected] install: node-gyp configure build
2021-01-14T08:45:30.761Z [err] npm WARN
2021-01-14T08:45:30.761Z [err] optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
2021-01-14T08:45:30.763Z [err]
2021-01-14T08:45:30.794Z [err] npm
2021-01-14T08:45:30.795Z [err] ERR! code ELIFECYCLE
2021-01-14T08:45:30.795Z [err] npm
2021-01-14T08:45:30.795Z [err] ERR! errno 1
2021-01-14T08:45:30.806Z [err] npm
2021-01-14T08:45:30.807Z [err] ERR! [email protected] install: node-gyp rebuild
2021-01-14T08:45:30.807Z [err] npm ERR! Exit status 1
2021-01-14T08:45:30.807Z [err] npm
2021-01-14T08:45:30.807Z [err] ERR!
2021-01-14T08:45:30.807Z [err] npm ERR!
2021-01-14T08:45:30.807Z [err] Failed at the [email protected] install script.
2021-01-14T08:45:30.807Z [err] npm ERR!
2021-01-14T08:45:30.807Z [err] This is probably not a problem with npm. There is likely additional logging output above.
2021-01-14T08:45:30.878Z [err]
2021-01-14T08:45:30.878Z [err] npm ERR! A complete log of this run can be found in:
2021-01-14T08:45:30.878Z [err] npm ERR! /root/.npm/_logs/2021-01-14T08_45_30_859Z-debug.log
2021-01-14T08:45:30.919Z rc=1

self signed certificate in certificate chain

Hello,

got this error and cannot find anything on it. Is it this node-specific error or is it node-red? Can I add the self-signed certificate so that the request does not fail? can I add the trusted certificate to node-red so it works everywhere? or is the trust coming from linux OS certificates store?

thanks a lot

Signal client error: {"name":"HTTPError","code":-1,"response":"FetchError: request to https://textsecure-service-staging.whispersystems.org/v1/accounts/sms/code/+xxxxxxxxxx?captcha=abcdefgh failed, reason: self signed certificate in certificate chain"}

Nodes dissappear and cannot be used

I migrated my Home Assistant OS installation from a Raspberry Pi2 to a Pi 4. I imported the snapshot during the onboarding.

Unfortunately my Signal nodes stopped working.
I tried to uninstall and reinstall nodered-contrib-signal-client but with no success. The nodes appear for a short period of time but cannot be used. I receive a message saying the node has not been registered.

The logs look like this:

26 May 17:53:26 - [info] Waiting for missing types to be registered:
26 May 17:53:26 - [info] - account
26 May 17:53:26 - [info] - register
26 May 17:53:26 - [info] - request-sms
26 May 17:53:26 - [info] - send
26 May 17:53:26 - [info] - receive

What can I do?

Installation fails on current NodeRed v3.0.2

The package reads really great in the package manager, unfortunately it cannot be installed with the current version of Node-RED (Node-RED v.3.0.2 / NodeJS v18.17.1). I get the following error message:

Is there any chance that the package can be made workable again?

`

2023-09-04T21:54:18.840Z Installieren : nodered-contrib-signal-client 2.4.2

2023-09-04T21:54:21.071Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2023-09-04T21:54:21.319Z [err] npm
2023-09-04T21:54:21.319Z [err] WARN
2023-09-04T21:54:21.319Z [err] config production Use --omit=dev instead.
2023-09-04T21:54:33.808Z [err] npm
2023-09-04T21:54:33.808Z [err] WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
2023-09-04T21:54:34.135Z [err] npm
2023-09-04T21:54:34.135Z [err] WARN deprecated [email protected]: node-webcrypto-ossl has been deprecated. This module was created in 2015 because at the time the Node team did not feel the need to have two crypto interfaces and they already had one before WebCrypto was defined
2023-09-04T21:54:34.857Z [err] npm WARN
2023-09-04T21:54:34.857Z [err] deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
2023-09-04T21:54:38.070Z [err] npm
2023-09-04T21:54:38.071Z [err] ERR! code 1
2023-09-04T21:54:38.071Z [err] npm ERR! path
2023-09-04T21:54:38.071Z [err] /opt/iobroker/iobroker-data/node-red/node_modules/node-webcrypto-ossl
2023-09-04T21:54:38.072Z [err] npm ERR! command failed
2023-09-04T21:54:38.072Z [err] npm ERR! command sh -c node-gyp rebuild
2023-09-04T21:54:38.072Z [err] npm ERR!
2023-09-04T21:54:38.072Z [err] make: Entering directory '/opt/iobroker/iobroker-data/node-red/node_modules/node-webcrypto-ossl/build'
2023-09-04T21:54:38.072Z [err] npm ERR! CXX(target) Release/obj.target/nodessl/src/main.o
2023-09-04T21:54:38.072Z [err] npm
2023-09-04T21:54:38.072Z [err] ERR!
2023-09-04T21:54:38.072Z [err] CXX(target) Release/obj.target/nodessl/src/core/key_exp.o
2023-09-04T21:54:38.072Z [err] npm ERR!
2023-09-04T21:54:38.072Z [err] make: Leaving directory '/opt/iobroker/iobroker-data/node-red/node_modules/node-webcrypto-ossl/build'
2023-09-04T21:54:38.072Z [err] npm ERR! gyp info it worked if it ends with ok
2023-09-04T21:54:38.072Z [err] npm ERR! gyp info using [email protected]
2023-09-04T21:54:38.072Z [err] npm
2023-09-04T21:54:38.072Z [err] ERR! gyp info using [email protected] | linux | x64
2023-09-04T21:54:38.072Z [err] npm ERR! gyp info find Python using Python version 3.11.2 found at "/usr/bin/python3"
2023-09-04T21:54:38.072Z [err] npm
2023-09-04T21:54:38.072Z [err] ERR! gyp info spawn /usr/bin/python3
2023-09-04T21:54:38.072Z [err] npm ERR!
2023-09-04T21:54:38.072Z [err] gyp info spawn args [
2023-09-04T21:54:38.072Z [err] npm ERR!
2023-09-04T21:54:38.072Z [err] gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
2023-09-04T21:54:38.072Z [err] npm ERR! gyp info spawn args 'binding.gyp',
2023-09-04T21:54:38.072Z [err] npm ERR! gyp info spawn args '-f',
2023-09-04T21:54:38.072Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] gyp info spawn args 'make',
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] gyp info spawn args '-I',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '/opt/iobroker/iobroker-data/node-red/node_modules/node-webcrypto-ossl/build/config.gypi',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '-I',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '-I',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/18.17.1/include/node/common.gypi',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '-Dlibrary=shared_library',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '-Dvisibility=default',
2023-09-04T21:54:38.073Z [err] npm ERR! gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.17.1',
2023-09-04T21:54:38.073Z [err] npm ERR! gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.17.1/<(target_arch)/node.lib',
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/iobroker-data/node-red/node_modules/node-webcrypto-ossl',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '-Dnode_engine=v8',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '--depth=.',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '--no-parallel',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '--generator-output',
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] gyp info spawn args 'build',
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args '-Goutput_dir=.'
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! gyp info spawn args ]
2023-09-04T21:54:38.073Z [err] npm ERR! gyp info spawn make
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] In file included from ../../nan/nan.h:60,
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] from ../src/node/../core/common.h:8,
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] from ../src/node/common.h:4,
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! from ../src/main.cpp:1:
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:1014:7: warning: cast between incompatible function types from 'void ()(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)' {aka 'void ()(v8::Localv8::Object)'} to 'node::addon_register_func' {aka 'void ()(v8::Localv8::Object, v8::Localv8::Value, void)'} [-Wcast-function-type]
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! 1014 | (node::addon_register_func) (regfunc),
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2023-09-04T21:54:38.073Z [err] npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:1048:3: note: in expansion of macro 'NODE_MODULE_X'
2023-09-04T21:54:38.073Z [err] npm ERR! 1048 | NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage)
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] | ^~~~~~~~~~~~~
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! ../src/main.cpp:93:1: note: in expansion of macro 'NODE_MODULE'
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! 93 | NODE_MODULE(nodessl, InitModule);
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! | ^~~~~~~~~~~
2023-09-04T21:54:38.073Z [err] npm ERR! ../src/core/key_exp.cpp: In function 'Handle<std::__cxx11::basic_string > KEY_export_spki(EVP_PKEY*)':
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] ../src/core/key_exp.cpp:41:33: error: invalid conversion from 'int ()(BIO, const EVP_PKEY*)' {aka 'int ()(bio_st, const evp_pkey_st*)'} to 'int ()(BIO, EVP_PKEY*)' {aka 'int ()(bio_st, evp_pkey_st*)'} [-fpermissive]
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] 41 | return KEY_export(pkey, &i2d_PUBKEY_bio);
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! | ^~~~~~~~~~~~~~~
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! | |
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! | int ()(BIO, const EVP_PKEY*) {aka int ()(bio_st, const evp_pkey_st*)}
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.073Z [err] ERR! ../src/core/key_exp.cpp:5:60: note: initializing argument 2 of 'Handle<std::__cxx11::basic_string > KEY_export(EVP_PKEY*, int ()(BIO, EVP_PKEY*))'
2023-09-04T21:54:38.073Z [err] npm ERR! 5 | static Handlestd::string KEY_export(EVP_PKEY pkey, int(i2d_function_bio)(BIO bp, EVP_PKEY key)) {
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] | ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] ../src/core/key_exp.cpp: In function 'Handle<std::__cxx11::basic_string > KEY_export_pkcs8(EVP_PKEY)':
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] ../src/core/key_exp.cpp:54:33: error: invalid conversion from 'int ()(BIO, const EVP_PKEY)' {aka 'int ()(bio_st, const evp_pkey_st*)'} to 'int ()(BIO, EVP_PKEY*)' {aka 'int ()(bio_st, evp_pkey_st*)'} [-fpermissive]
2023-09-04T21:54:38.073Z [err] npm ERR!
2023-09-04T21:54:38.073Z [err] 54 | return KEY_export(pkey, &i2d_PKCS8PrivateKeyInfo_bio);
2023-09-04T21:54:38.073Z [err] npm
2023-09-04T21:54:38.074Z [err] ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
2023-09-04T21:54:38.074Z [err] npm ERR!
2023-09-04T21:54:38.074Z [err] | |
2023-09-04T21:54:38.074Z [err] npm
2023-09-04T21:54:38.074Z [err] ERR! | int ()(BIO, const EVP_PKEY*) {aka int ()(bio_st, const evp_pkey_st*)}
2023-09-04T21:54:38.074Z [err] npm
2023-09-04T21:54:38.074Z [err] ERR! ../src/core/key_exp.cpp:5:60: note: initializing argument 2 of 'Handle<std::__cxx11::basic_string > KEY_export(EVP_PKEY*, int ()(BIO, EVP_PKEY*))'
2023-09-04T21:54:38.074Z [err] npm ERR! 5 | static Handlestd::string KEY_export(EVP_PKEY *pkey, int(*i2d_function_bio)(BIO *bp, EVP_PKEY *key)) {
2023-09-04T21:54:38.074Z [err] npm
2023-09-04T21:54:38.074Z [err] ERR! | ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2023-09-04T21:54:38.074Z [err] npm ERR! make: *** [nodessl.target.mk:150: Release/obj.target/nodessl/src/core/key_exp.o] Error 1
2023-09-04T21:54:38.074Z [err] npm ERR! gyp ERR! build error
2023-09-04T21:54:38.074Z [err] npm
2023-09-04T21:54:38.074Z [err] ERR! gyp ERR! stack Error: make failed with exit code: 2
2023-09-04T21:54:38.074Z [err] npm
2023-09-04T21:54:38.074Z [err] ERR! gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
2023-09-04T21:54:38.074Z [err] npm
2023-09-04T21:54:38.074Z [err] ERR! gyp ERR! stack at ChildProcess.emit (node:events:514:28)
2023-09-04T21:54:38.074Z [err] npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:291:12)
2023-09-04T21:54:38.074Z [err] npm
2023-09-04T21:54:38.074Z [err] ERR! gyp ERR! System Linux 5.15.111-1-pve
2023-09-04T21:54:38.074Z [err] npm ERR!
2023-09-04T21:54:38.074Z [err] gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
2023-09-04T21:54:38.074Z [err] npm ERR! gyp ERR! cwd /opt/iobroker/iobroker-data/node-red/node_modules/node-webcrypto-ossl
2023-09-04T21:54:38.074Z [err] npm ERR! gyp ERR! node -v v18.17.1
2023-09-04T21:54:38.074Z [err] npm ERR!
2023-09-04T21:54:38.074Z [err] gyp ERR! node-gyp -v v9.3.1
2023-09-04T21:54:38.074Z [err] npm ERR!
2023-09-04T21:54:38.074Z [err] gyp ERR! not ok
2023-09-04T21:54:38.075Z [err]
2023-09-04T21:54:38.075Z [err] npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-09-04T21_54_21_296Z-debug-0.log
2023-09-04T21:54:38.094Z rc=1`

Downstream proxy-agent dependency causing issues with other modules

I'm the developer of node-red-contrib-matrix-chat and someone reported an issue with HTTP requests failing. It was redirecting their HTTP requests to 127.0.0.1:443 instead of the actual requested URL.

I use the got library in my module which is also what Node-RED uses. It is a known issue that http[s]-agent-proxy packages can break URLs (which proxy-agent depends on). See here: sindresorhus/got#1572

After the person having the issue uninstalled nodered-contrib-signal-client from Node-RED the requests started working again.

Unable to Install the package on Node-red add-on (under home-assistant)

So trying to install this on node-red add-on version 8.0.1 (running on home-assistant supervisor 2021.1.5). I saw a previous "closed issue" referencing alpine-sdk, so i installed it and restarted the whole system. Still when I try and install the package, i am met with this error:
image

Upgrade needed

Hi,

Node Red now won't let you install this addon and shows the following request for it to be updated:
npm WARN deprecated [email protected]: node-webcrypto-ossl has been deprecated. This module was created in 2015 because at the time the Node team did not feel the need to have two crypto interfaces and they already had one before WebCrypto was defined npm WARN deprecated [email protected]: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js. npm ERR! code 1 npm ERR! path /config/node-red/node_modules/utf-8-validate npm ERR! command failed npm ERR! command sh -c node-gyp-build npm ERR! gyp info it worked if it ends with ok npm ERR! gyp info using [email protected] npm ERR! gyp info using [email protected] | linux | arm64 npm ERR! gyp info find Python using Python version 3.9.5 found at "/usr/bin/python3" npm ERR! gyp info spawn /usr/bin/python...

typo in help for some nodes

Just to report a small typo in help text nodes:

request-sms
request-voice
receive

... Singnal Messenger.

Signal is mistyped

Other nodes are OK.

Sent messages receipt/reading status ?

Hello !
Nice node here !
We try to find a way to be notified of a sent message's receipt and reading by the recipient (just like we see in the Signal app, but we'd like a corresponding NodeRED node to trigger some actions from these notifications), or at least to be able to request such sent message status.
We could be up to extending your library to add such node, but surely we'd need a bit of directions here.

I see this library uses this one: https://github.com/gausma/libsignal-service-javascript , which seems to make ajax calls to "textsecure-service.whispersystems.org".
If this is right, a couple questions:

  • is textsecure-service.whispersystems.org still actually used to use the Signal system?
  • I couldn't find any API description for textsecure-service.whispersystems.org... any hint?

If this API offers a method to request a sent message status, then one would have to extend your libsignal-service-javascript library first (to leverage the API method) and then the nodered-contrib-signal-client library: does that seem right?
If this API does not offer the method, would there be any option?

Thank you so much for your help and your work!

Feature Request - New group chat

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.

receive node loses registration

Hi, I have noticed that if my internet connection drops (for a short time), the receive nodes don't then receive any messages from signal once the internet is back up.
I have to change something in the receive nodes and re-deploy and then it works again.

Anyone have a fix/workaround for this?
Thanks

The sending function stopped for me since friday 08/27/21. I did not change anything on an existing config, just using the sender module in node-red to send a message per day. On friday it stopped. Re-Registering is not possible, got the error-message from @cameo69. With a completly new fixed number, i could get the captcha, could receive the Code via phone. But if i try to register i get "Signal client error: {"name":"HTTPError","code":401,"response":"Credentials are required to access this resource."}"

The sending function stopped for me since friday 08/27/21. I did not change anything on an existing config, just using the sender module in node-red to send a message per day. On friday it stopped. Re-Registering is not possible, got the error-message from @cameo69. With a completly new fixed number, i could get the captcha, could receive the Code via phone. But if i try to register i get "Signal client error: {"name":"HTTPError","code":401,"response":"Credentials are required to access this resource."}"

Originally posted by @Heiner629 in #29 (comment)

I have the same Problem. Please help.

Feature Request

Would it be possible to ad a Node registring it as an Additional Device to an existing Account/number?
At the moment we only have two handynumbers and I'm not willing to remove the account of my wife nor mine, let alone purchasing another number.

Dependency Issue with agent-base <6.0.0 and Node-RED 2.0

Hi,

We've detected that your node has a dependency on an old version of agent-base (<6.0.0) ,
These old versions were patching a core node.js function in a way that could break other libraries - including one we started using in Node-RED 2.0 for the HTTP Request node.
Therefore any users that upgrade to Node-RED 2.0 and have your node installed (or later try to install it) will get errors when using the http-request node.

Could you please take a look at your dependencies and see if you can update the versions so that you are no longer dependent on agent-base before version 6.0.0

Note this could be a module that you are using has a dependency on agent-base so you might need to check for updates to that module, to help you we've attached your nodes dependency tree below

More details on this issue and the warning message that is now displayed in Node-RED 2.0.2 are on the forum at link https://discourse.nodered.org/t/node-red-2-0-2-released/48767

└─ [email protected]
   ├─ [email protected]
   │  └─ [email protected]
   ├─ [email protected]
   │  └─ [email protected]
   │     ├─ [email protected]
   │     ├─ [email protected]
   │     └─ [email protected]
   └─ @gausma&#x2F;[email protected]
      ├─ [email protected]
      ├─ [email protected]
      ├─ [email protected]
      ├─ [email protected]
      │  └─ [email protected]
      │     └─ [email protected]
      ├─ [email protected]
      │  └─ [email protected]
      ├─ @sindresorhus&#x2F;[email protected]
      │  └─ [email protected]
      ├─ [email protected]
      ├─ [email protected]
      ├─ [email protected]
      ├─ [email protected]
      │  └─ [email protected]
      ├─ [email protected]
      ├─ [email protected]
      │  ├─ [email protected]
      │  │  ├─ [email protected]
      │  │  └─ [email protected]
      │  ├─ [email protected]
      │  │  ├─ [email protected]
      │  │  └─ [email protected]
      │  ├─ [email protected]
      │  └─ [email protected]
      ├─ [email protected]
      │  ├─ [email protected]
      │  ├─ [email protected]
      │  │  └─ [email protected]
      │  ├─ [email protected]
      │  └─ [email protected]
      │     └─ [email protected]
      ├─ [email protected]
      │  ├─ [email protected]
      │  └─ [email protected]
      │     └─ [email protected]
      ├─ [email protected]
      │  ├─ @protobufjs&#x2F;[email protected]
      │  ├─ @protobufjs&#x2F;[email protected]
      │  ├─ @protobufjs&#x2F;[email protected]
      │  ├─ @protobufjs&#x2F;[email protected]
      │  ├─ @protobufjs&#x2F;[email protected]
      │  │  ├─ @protobufjs&#x2F;[email protected]
      │  │  └─ @protobufjs&#x2F;[email protected]
      │  ├─ @protobufjs&#x2F;[email protected]
      │  ├─ @protobufjs&#x2F;[email protected]
      │  ├─ @protobufjs&#x2F;[email protected]
      │  ├─ @protobufjs&#x2F;[email protected]
      │  ├─ @types&#x2F;[email protected]
      │  ├─ [email protected]
      │  ├─ @protobufjs&#x2F;[email protected]
      │  └─ @types&#x2F;[email protected]
      ├─ [email protected]
      ├─ [email protected]
      ├─ [email protected]
      │  └─ [email protected]
      │     ├─ [email protected]
      │     │  ├─ [email protected]
      │     │  ├─ [email protected]
      │     │  │  └─ [email protected]
      │     │  └─ [email protected]
      │     ├─ [email protected]
      │     │  ├─ [email protected]
      │     │  └─ [email protected]
      │     └─ [email protected]
      ├─ [email protected]
      │  ├─ [email protected]
      │  │  ├─ [email protected]
      │  │  └─ [email protected]
      │  │     └─ [email protected]
      │  ├─ [email protected]
      │  │  └─ [email protected]
      │  │     └─ [email protected]
      │  ├─ [email protected]
      │  ├─ [email protected]
      │  │  └─ [email protected]
      │  ├─ [email protected]
      │  │  ├─ [email protected]
      │  │  └─ [email protected]
      │  │     └─ [email protected]
      │  ├─ [email protected]
      │  │  ├─ [email protected]
      │  │  │  ├─ [email protected]
      │  │  │  ├─ [email protected]
      │  │  │  │  ├─ [email protected]
      │  │  │  │  └─ [email protected]
      │  │  │  │     ├─ [email protected]
      │  │  │  │     ├─ [email protected]
      │  │  │  │     ├─ [email protected]
      │  │  │  │     └─ [email protected]
      │  │  │  ├─ [email protected]
      │  │  │  ├─ [email protected]
      │  │  │  ├─ [email protected]
      │  │  │  └─ [email protected]
      │  │  │     ├─ [email protected]
      │  │  │     ├─ [email protected]
      │  │  │     ├─ [email protected]
      │  │  │     ├─ [email protected]
      │  │  │     ├─ [email protected]
      │  │  │     │  └─ [email protected]
      │  │  │     ├─ [email protected]
      │  │  │     └─ [email protected]
      │  │  ├─ [email protected]
      │  │  ├─ [email protected]
      │  │  ├─ [email protected]
      │  │  ├─ [email protected]
      │  │  ├─ [email protected]
      │  │  │  ├─ [email protected]
      │  │  │  ├─ [email protected]
      │  │  │  │  ├─ [email protected]
      │  │  │  │  │  ├─ [email protected]
      │  │  │  │  │  ├─ [email protected]
      │  │  │  │  │  ├─ [email protected]
      │  │  │  │  │  ├─ [email protected]
      │  │  │  │  │  │  ├─ [email protected]
      │  │  │  │  │  │  ├─ [email protected]
      │  │  │  │  │  │  ├─ [email protected]
      │  │  │  │  │  │  ├─ [email protected]
      │  │  │  │  │  │  │  └─ [email protected]
      │  │  │  │  │  │  ├─ [email protected]
      │  │  │  │  │  │  └─ [email protected]
      │  │  │  │  │  │     ├─ [email protected]
      │  │  │  │  │  │     └─ [email protected]
      │  │  │  │  │  └─ [email protected]
      │  │  │  │  ├─ [email protected]
      │  │  │  │  └─ [email protected]
      │  │  │  │     └─ [email protected]
      │  │  │  ├─ [email protected]
      │  │  │  ├─ [email protected]
      │  │  │  └─ [email protected]
      │  │  ├─ [email protected]
      │  │  └─ [email protected]
      │  │     ├─ [email protected]
      │  │     ├─ [email protected]
      │  │     │  ├─ [email protected]
      │  │     │  ├─ [email protected]
      │  │     │  ├─ [email protected]
      │  │     │  ├─ [email protected]
      │  │     │  └─ [email protected]
      │  │     ├─ [email protected]
      │  │     └─ [email protected]
      │  │        └─ [email protected]
      │  ├─ [email protected]
      │  └─ [email protected]
      │     ├─ [email protected]
      │     │  └─ [email protected]
      │     └─ [email protected]
      │        ├─ [email protected]
      │        └─ [email protected]
      ├─ [email protected]
      │  ├─ [email protected]
      │  │  └─ [email protected]
      │  ├─ [email protected]
      │  │  └─ [email protected]
      │  ├─ [email protected]
      │  │  ├─ [email protected]
      │  │  │  ├─ [email protected]
      │  │  │  │  ├─ [email protected]
      │  │  │  │  └─ [email protected]
      │  │  │  └─ [email protected]
      │  │  │     └─ [email protected]
      │  │  ├─ [email protected]
      │  │  └─ [email protected]
      │  │     ├─ [email protected]
      │  │     ├─ [email protected]
      │  │     └─ [email protected]
      │  ├─ [email protected]
      │  │  └─ [email protected]
      │  ├─ [email protected]
      │  │  └─ [email protected]
      │  └─ [email protected]
      ├─ [email protected]
      ├─ [email protected]
      ├─ [email protected]
      │  └─ [email protected]
      └─ @throneless&#x2F;[email protected]
         ├─ [email protected]
         ├─ [email protected]
         │  ├─ [email protected]
         │  ├─ [email protected]
         │  ├─ [email protected]
         │  │  └─ [email protected]
         │  ├─ [email protected]
         │  ├─ [email protected]
         │  └─ [email protected]
         ├─ [email protected]
         ├─ [email protected]
         ├─ [email protected]
         ├─ [email protected]
         │  ├─ [email protected]
         │  │  ├─ [email protected]
         │  │  └─ [email protected]
         │  ├─ [email protected]
         │  ├─ [email protected]
         │  │  ├─ [email protected]
         │  │  ├─ [email protected]
         │  │  │  ├─ [email protected]
         │  │  │  └─ [email protected]
         │  │  ├─ [email protected]
         │  │  ├─ [email protected]
         │  │  │  └─ [email protected]
         │  │  │     ├─ [email protected]
         │  │  │     └─ [email protected]
         │  │  ├─ [email protected]
         │  │  │  └─ [email protected]
         │  │  └─ [email protected]
         │  └─ [email protected]
         │     ├─ [email protected]
         │     ├─ [email protected]
         │     ├─ [email protected]
         │     │  ├─ [email protected]
         │     │  │  └─ [email protected]
         │     │  ├─ [email protected]
         │     │  └─ [email protected]
         │     │     ├─ [email protected]
         │     │     └─ [email protected]
         │     ├─ [email protected]
         │     │  └─ [email protected]
         │     │     └─ [email protected]
         │     ├─ [email protected]
         │     ├─ [email protected]
         │     │  ├─ [email protected]
         │     │  │  └─ [email protected]
         │     │  ├─ [email protected]
         │     │  └─ [email protected]
         │     └─ [email protected]
         └─ [email protected]

Thanks in advance for looking into this.

Sam

PS Sorry for the templated issue but we've got a number of nodes with the issue so I'm automating the issue creation.

Sending and receiving failure

I've been able to register a number with Signal with a separate landline number - at least the registration was successful. I do not get any notification in Signal though that my "contact" is now using Signal (not sure if that just takes time?)

However, I can neither send nor receive messages. It makes no difference if I use "non-live" mode or "live" mode.

I set up a simple node that sends to the same number as receiver - I also tried your example for a simple send/receive node with my own account and my number.

I press "send" and nothing happens on the receiving node. There is also no error message.

Now I'm not sure where the problem is...
Some questions from my side:
1 - Does that mean that Signal servers were actually contacted and they replied successful delivery?
2 - Is there a check if the receiver was started properly and is "waiting" for messages?
3 - Shouldn't I get some notification on my mobile phone that my contact with the used landline number now is on Signal?

I'm running Debian Buster on x64.

Not realy an issue - How to move Signal Client from one to another NodeRed

Hi,

i just want to move the Client from a fine working PI to a Synology HomeAssistant + zigbee2mqtt + nodered.
I imported my good working Signal-TestAndRegister-Flow from old to new machine.

As i want to register with the imported parameters and a new captcha i get something like this message in debug:
Signal client: registration code requested via voice call.

No Call or SMS comes in.

Is there an easy way to move from one computer to an other?

Thanks to gausma and andrew howe and fanuch for all previous written docs.

not able to activate a landline number

Hello all

I am not able to activate a landline number for the Signal Node in RedMatic version 7.2.1.

If I use "request-voice" and enter the landline number, the debugging also shows "Signal client: registration code requested via voice call", but no call is received. If I enter a cell phone number in "request-voice", I get an SMS (shouldn't there also be a voice call?).

If I enter the landline number on a mobile, a call comes and I can activate the landline number on the mobile.

An update of nodered-contrib-signal-client from 2.4.0 to 2.4.1 is unfortunately also not possible.

Multiple Recepients

Of course, we could replicate nodes, but is there a way to send to a list of numbers? I tried space and , as list delimiters but neither worked.

Is there a way now to do this?

If not can we please add this to the list? Is that similar to the groups request?

Feature Request - send an image

Hello,

Is there any chance in future releases to implement sending an image?
For example - TelegramBot has a property
msg.payload.type = "photo"
Is it possible to do something similar?

Signal and Nodered Docker

Hi, I am using NodeRed on a Synology NAS with the built in Docker system.
Can someone support me how to install the missing packages/dependencies that are needed to run Signal with NodeRed?

Thank you very much!

Registration problem

Hi,
my guess is, this issue and few previous are maybe related due to possible API change on the Signal server side. In my case first step with request-voice node (and captcha) went OK. I received call to my landline and I got registration code. The problem comes in registration node. After clicking on registration node for the first time I got the following message in Node-RED debug window:

9/8/2021, 1:05:54 PM node: haus registration
msg : string[23]
"Signal client error: {}"
9/8/2021, 1:05:55 PM node: http response
msg : error
"Error: Cannot set headers after they are sent to the client"
9/8/2021, 1:05:55 PM node: http response
msg : error
"Error: Cannot set headers after they are sent to the client"
9/8/2021, 1:05:55 PM node: http response
msg : error
"Error: Cannot set headers after they are sent to the client"
9/8/2021, 1:05:57 PM node: http response
msg : error
"Error: Cannot set headers after they are sent to the client"

Second and every other click on the registration node gives the following answer in debug window:

msg : string[107]
"Signal client error: {"name":"HTTPError","code":403,"response":{"code":403,"message":"HTTP 403 Forbidden"}}"

I also tried with simpler password but the result is the same. Hope this feedback will be helpful to fix Signal client in Node-RED. I can provide more data if needed.

Thank you very much for a such great Node-RED contribution and I hope this issue will be resolves soon.

Kind regards

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.