Signal Binding [4.0.0.0;5.0.0.0)

I need some help

  • Binding installed from marketplace
  • Created a linked account, entered my phone number, QR gets displayed
  • I use the App to scan the QR code
  • App shows “Unable to pair device”, thing shows IOException: Connection closed

any idea?

Hello,

Strange, I just made a test and I could link a new thing to my account without any issue.

Can you please show me the log ?

When creating the thing, did you use the same number as the phone’s one, and in international format ? (e.g. with a prefix like +XX, XX being the country identifier). I think you can find it just under your name in the “settings” of the signal application.

Hi,

in my OpenHAB 4.2.1 (AddOn from 9. Juli 2024 00:55) the Accountlinking to my Signal phone number doesn’t work.
I get a Error " MissingCapabilitiesException 409" on scanning the QR Code.
this is exactly this Issue: linking account is failed (exceptions.MissingCapabilitiesException: StatusCode: 409) · Issue #1556 · AsamK/signal-cli · GitHub

Will there be a new AddOn version with newest signal-cli?

Hi,

So it seems that new registration for the link account mode is broken since july ?
Thanks for telling me and sorry for the issue.
I really hope signal will consider to stabilize and open/document its API. There is at least two broken version per year, it’s annoying.

Anyway, new version uploaded. Could you try it and tell me if it’s OK ? (seems good for me)

Hi,

I tested the new version but it didn’t work on my system.

The signal “add-on” gave me following error on the things-page:

**HANDLER_INITIALIZING_ERROR**

/var/lib/openhab/tmp/libsignal2713855046520776408/libsignal_jni_amd64.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /var/lib/openhab/tmp/libsignal2713855046520776408/libsignal_jni_amd64.so)

The system I have is a debian 11 “bullseye”, which support ended. Beacuse of this I can’t update to “libc” > 2.31

So I have to update to Debian 12 first, I think.
Am I correct?

Greetings

To save (my) time, I don’t compile the libraries that I include in the release. I use those from exquo, listed here.
(By the way, the listing seems to not be up to date, because it says glibc v2.28 despite not working on your 2.31 system)
Other library releases from the other listed repositories should, maybe, have different requirement and could work. Theorically, it just means replacing the lib in the .kar file by another one to test, but right now every time I tried to do some tinkering like that, it ended badly (don’t know why, but I never managed to install a working .kar without using the marketplace as an intermediary).
So, building/testing consumes time and I honestly prefer not to risk downgrading version.

Unless you have another compatibility issue preventing from doing so, upgrading to debian 12 is probably for the best.
I use a debian 12 system myself.