Neues Modul: Signalbot (Integration für den Signal Messenger) via signal-cli

[HarryT]

Looks like something in your environment does not work with my check for the Protocol::Dbus, but as it only affects the check script, it is probably safe to ignore. All I'm doing is

Code Auswählen Erweitern

#!/usr/bin/perl -w
use strict;
use warnings;

use Protocol::DBus;
print \$Protocol::DBus::VERSION."\n";
Thanks again. If I run your script the answer is
SCALAR(0x558dd3bd40)

No idea what it is. 

Anyway, to night trying to reregister gives me first an
  Failed to register: StatusCode: 502 (ExternalServiceFailureException)
and the second time
  Failed to register: [429] Rate Limited (RateLimitException)

So no luck yet, I have to wait another day.

[HarryT]

Hi all,

I guess I am stupid but don't see what I might do wrong.

My steps:

systemctl stop signal

In firefox and chromium I tried:

https://signalcaptchas.org/registration/generate

I copied the link of the response page

Then I paste it in the command with as result:

Code Auswählen Erweitern

sudo -E /opt/signal/bin/signal-cli --config /var/lib/signal-cli -u +31xxxxxxxx register --reregister --captcha signalcaptcha://signal-hcaptcha.5fad97ac-4e44-b18a-b950b20148ff.registration.P1_eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.haJwZACjZXhwzmnfezOncGFzc2tlecUFSikWaW3xRzETPW0brJMts9_Pl3PQPAz5OlHQypsb9BuOsBVjvGrLk672Qff_5Os8nnUR9zCwzrNrhnAobstzeUhkbD645vU7yN-UK0wzlrjfLbLQPAX-0Cfo6Z6ExW8Di63APjywaET3N2VaMxh-SyXaXjIN-cVCr5uglL8B6UMbaPImUsxxNHVsfgPWwKR5mntA6NQ9IFnxsOMCxYaYU3bySorGzjaEcRVB0WDUNT-lkcvPYdvRPq-BldRsX5NdxAeukyMigFSoUNvfkzIoe0mw82Wi230QdGkTPubrdQxORNoTP-4oxVP2Qe8BwVbn_PfCRNPNU5YEXpmK4wDYdoQTk-zisOwUGj0Ge4EIilwcF2vHp7U5HcSTFKl62gmbb0NKWtg_gJr1B-cdBdgagFVlL_ZjL9fJCZEEie_9DRT4J9XOSPfcvKICHUrHn9e2nMunJHrxxuNCHRuVdLAxdObeelqgkCxjzGZgScc4h2t_Ub_Bm-MzxTe08W7JC4Q7wjgavWTrUki-2riqUAuuavkqti2Oge98e5mjKc4VZzt0LS9sEjHdrCSLfEtB0ttpUbfALwjCiOKex0PTtc_ZD3jcAUBk_YSVurT17QLqyxZXxEYIhmRGoj1U7HQ4cNiL4JJARUNx4LC8BGP6aI_68dkRDqlndfNQUIc2oAOpl1kTVxQ21LDrxCgrt5o5wHIfzZWOhci_Op1l9_XRkPG0LLHdX0AweWZcDfwrIVnjLoQ-BQVD05Ck2t0OxPhmeAKIN1A-s2SWc02j26Ed7F8IIHpeNWMEbRGVx3Ibp6dpMVDp4lpCFUzAr7aligvzFIBN7UX_lHD9XoMwIRud_-MnohkXyIoIvHFyxd9KGpBiJfFzYFQavzEY7DUrp0PaV3yKtgA8zh2lNmLyQwK-Z-oyiUVomFlQW1HeMitI5dqvdyLmjNVp75BSSR5wqi1uG8n1R325txvkU5AJ4fH-JZ__g7H8Q34ed7Zn-8gzffIa_XxGYZRqBHg2-Bd4YQRyBeTumHN64Htbw2J1jLLK_SW6oIsAf9xaHzndLc56zySHfQhwgG9kxsBiztZmKx9bLPlXUR2MYam8TYnDP1CMlIK3HiY0rexoJwT-sQcd2RDcGJiT-ORwwnhCTPHSHISw9nNrW9KMPt80UsXTV52t9KU781z8T1eNiJELf2Ba7H_Iidlc19DdjL2Viio03qBhw_Y5OLJ37m6yunAyixyai5KgKBns_vJIROXfQwmLCe4-qd0l71buDrlUOsZGbRAL8fG0qvoz_XrlcgwjHKhxvFqhtPuUKRo-vEU5KbdI0KJNC5eLjx6ptOY3-BZZ-j1oL_cJeALBo7vuiwWVzIAIR-wsIo4Ada8sVYdSOGEA72ooX1u3gFScEfX8QDmJsaDAXWVFb9X2MaY3HlojTC9iAYMqr7JwjNJqa0jB6gnI8IO8RYnGKArQCTpzrMsj2Z_50K-p-iKCMnSCGLKMm-KSZ07Znc1ZGbx5-uxTrR8yAfkpjj36qwcPDbvtfv1zOcbuA60_bl0Iq4oJRPdrZvqAwogQs9D8MZWUDF6Dhrro3mwybTx9estROfPLzk0oS8XTXFLsNhN_-FpmvEX1HZ1R-NEdXLBkM2odQhfNf0TB5ng0moxvFEjsbbNmjwRGZG7bWYniBOgWLHS1pkNz5K3NGea7iVlxzA_q3c-wprUh9GQC9nW8pE8xjqM5zcvZNl42DGZba3VM_fPR1YPvDzNKmgYwHuwRu3jDX2Mq-KChxTNtvKFTd12MmY9iMCTptkZ8_IDvmk55BoLDS1jlREGia3KoMzk1ZmQ5ZGWoc2hhcmRfaWTOAzGDbw.3o1TrkJo4ZuZfSyjO66Uc5NWD93V1F4uTfbXN-Tt27Y

(the phone number and the captcha code is intential damaged)

I enter this as a command in the terminal (raspbianOS 64 bit trixie)

I always get the answer:
Failed to register: [403] Authorization failed! (AuthorizationFailedException)

Is this just bad luck or do I make a stupid mistake somewhere?

[enno]

Moin HarryT,

as Jörg wrote in his post. The first answer for SMS register will come back with an error. This is what you get. Now you have to wait 1 minute. Than you register with voice option. See the -v behind "register"

Code Auswählen Erweitern

sudo -E /opt/signal/bin/signal-cli --config /var/lib/signal-cli -u +49..... register -v --reregister --captcha signalcaptcha://......
Is this the way you tried? Or do you always use the same command?


Gruss
  Enno

[HarryT]

Hi Enno

Is this the way you tried? Or do you always use the same command?

No in the second command I use  ...register -v --reregister --captcha.....

And the answer is:

Code Auswählen Erweitern

2026-04-15T16:35:42.866+0200 [main] DEBUG org.asamk.signal.App - Starting signal-cli 0.14.2
2026-04-15T16:35:44.291+0200 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2026-04-15T16:35:44.656+0200 [main] INFO  com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.sqlite.jdbc4.JDBC4Connection@5ca17ab0
2026-04-15T16:35:44.664+0200 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2026-04-15T16:35:49.091+0200 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
2026-04-15T16:35:49.106+0200 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.
Failed to register: Invalid verification method: Before requesting voice verification you need to request SMS verification and wait a minute.
org.asamk.signal.manager.api.VerificationMethodNotAvailableException: Invalid verification method
at org.asamk.signal.manager.util.NumberVerificationUtils.handleVerificationSession(NumberVerificationUtils.java:66)
at org.asamk.signal.manager.internal.RegistrationManagerImpl.register(RegistrationManagerImpl.java:135)
at org.asamk.signal.commands.RegisterCommand.register(RegisterCommand.java:81)
at org.asamk.signal.commands.RegisterCommand.handleCommand(RegisterCommand.java:52)
at org.asamk.signal.commands.CommandHandler.handleRegistrationCommand(CommandHandler.java:33)
at org.asamk.signal.App.handleRegistrationCommand(App.java:268)
at org.asamk.signal.App.handleCommand(App.java:177)
at org.asamk.signal.App.init(App.java:147)
at org.asamk.signal.Main.main(Main.java:56)


I thought it was mentioned that the first call would abort with error 400 or something. So I guess 403 is a real error/problem. But I am out of ideas what can be wrong


Greetings

[tomcat.x]

I thought it was mentioned that the first call would abort with error 400 or something. So I guess 403 is a real error/problem.

Think you're right. I also had the 403 in one of my tries, don't know why and don't know why it worked the next day (when I had the expected 400 error).

[Adimarantis]

Have you tried with the updated Signalbot (3.23) as I made it ignore that first error and thus it should hopefully now go through the process correctly
And I'd appreciate a tester, as I did not....

[HarryT]

Have you tried with the updated Signalbot (3.23) as I made it ignore that first error and thus it should hopefully now go through the process correctly
And I'd appreciate a tester, as I did not....

I tried it without installing anything to be sure nothing interferes on my system.

But I am willing to test. So I made fhem install on my test system and tried.
HOME_JAVE was wrongly set in signale.service, but maybe that was from a previous test. I will look at that later.

I tried to register from Signalbot in FHEM. I used  https://signalcaptchas.org/registration/generate to get a captcha. (Would be nice to display this link when the captcha is asked.)

Anyway, it did not help. I got no error message in the signalbot screen, but in the signalbot logging I get:   

Code Auswählen Erweitern

2026-04-15_23:03:12 SignalBot lastError: Error in getIdentity:The method `org.asamk.Signal.getIdentity' does not exist on this object.
2026-04-15_23:03:29 SignalBot register +31xxxxxxx
2026-04-15_23:04:09 SignalBot lastError: Error in registerWithCaptcha:AuthorizationFailedException [403] Authorization failed!
If I can be helpfull in testing a newe version I am happy to do so.

-I have test machines so it would not destroy my home automation.
-I have scripts to install my systems so it is easy to generate a fresh installation

Greetings
 Harry