I also had issues with invalid captcha or invalid confirmation code. Stuck with rate limits because of that issues.
So, eventually I just put the SIM into another phone, installed signal, registered with the new phone number and added linked device through QR code generated image. Now it works as expected. This is the easiest way to register new number, don’t understand why it’s not documented anywhere
Also I finished writing websocket integration for HA core and able to use json2rpc with websocket to receive messages. Will test whether it works fine and some day plan to share it to public
Hello all,
i am trying to install and run the send of messages with signal_messanger with integration HAOS.
First i try with debian, not really work for me.
Now i am having a better progres with Ubuntu, ALL in Raspberry Pi 5:
root@raspi5:/usr/share/hassio/addons# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04 LTS
Release: 24.04
Codename: noble
My HAOS: ha info
arch: aarch64
channel: stable
docker: 26.1.3
features:
I tested signal-cli by command worked fine:
signal-cli -u +49xxxxxxx register
signal-cli -a +49xxxxxxx verify 677373
Now i integrated and use the addon signal.
signal-cli --version
0.13.3
javac -version
javac 21.0.3
But here i have 2 questions: changed the really phone number
a) is this configuration.yaml correct?
signalmessenger:
notify:
b) When i started the addon signal from agileek/hassio-addons in HAOS
i have following issue in Logs
May 26 13:11:38 raspi5 hassio_supervisor[1050]: 2024-05-26 13:11:38.562 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on agileek/hassio-aarch64-signal with version 10.25.0
May 26 13:11:38 raspi5 addon_4a36bbd1_signal[1050]: mkdir: cannot create directory ‘/var/run/dbus’: File exists
May 26 13:11:38 raspi5 addon_4a36bbd1_signal[1050]: [2024-05-26 13:11:38 +0200] [14] [INFO] Starting gunicorn 21.2.0
May 26 13:11:38 raspi5 addon_4a36bbd1_signal[1050]: [2024-05-26 13:11:38 +0200] [14] [INFO] Listening at: http://0.0.0.0:5000 (14)
May 26 13:11:38 raspi5 addon_4a36bbd1_signal[1050]: [2024-05-26 13:11:38 +0200] [14] [INFO] Using worker: sync
May 26 13:11:38 raspi5 addon_4a36bbd1_signal[1050]: [2024-05-26 13:11:38 +0200] [15] [INFO] Booting worker with pid: 15
May 26 13:11:38 raspi5 addon_4a36bbd1_signal[1050]: SETTING LOG LEVEL TO 10
May 26 13:11:38 raspi5 addon_4a36bbd1_signal[1050]: 2024-05-26 13:11:38,929 - root - INFO - Init
May 26 13:11:38 raspi5 addon_4a36bbd1_signal[1050]: 2024-05-26 13:11:38,930 - root - INFO - Listening to incoming messages
May 26 13:11:38 raspi5 addon_4a36bbd1_signal[1050]: 2024-05-26 13:11:38,930 - root - INFO - Process started and listening on 4a36bbd1-signal
May 26 13:11:39 raspi5 avahi-daemon[747]: Joining mDNS multicast group on interface vetheda1fa9.IPv6 with address fe80::241d:9aff:feb0:15d7.
May 26 13:11:39 raspi5 systemd-networkd[732]: vetheda1fa9: Gained IPv6LL
May 26 13:11:39 raspi5 avahi-daemon[747]: New relevant interface vetheda1fa9.IPv6 for mDNS.
May 26 13:11:39 raspi5 avahi-daemon[747]: Registering new address record for fe80::241d:9aff:feb0:15d7 on vetheda1fa9.*.
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: Error loading state file for user +49xxxxxxxxx : Config file was created by a more recent version: 9 (IOException)
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: 2024-05-26 13:11:40,402 - root - DEBUG - receiving new line “”
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: 2024-05-26 13:11:40,402 - root - DEBUG - receiving new line “”
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: 2024-05-26 13:11:40,402 - root - DEBUG - receiving new line “”
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: 2024-05-26 13:11:40,402 - root - DEBUG - receiving new line “”
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: 2024-05-26 13:11:40,407 - root - DEBUG - receiving new line “”
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: 2024-05-26 13:11:40,407 - root - DEBUG - receiving new line “”
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: 2024-05-26 13:11:40,407 - root - ERROR - signal has been terminated, check the logs for more information
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: 2024-05-26 13:11:40,407 - root - ERROR - signal logs printed
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: [2024-05-26 13:11:40 +0200] [14] [ERROR] Worker (pid:15) exited with code 4
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: [2024-05-26 13:11:40 +0200] [14] [ERROR] Shutting down: Master
May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: [2024-05-26 13:11:40 +0200] [14] [ERROR] Reason: App failed to load.
I can’t really begin with this error ==> May 26 13:11:40 raspi5 addon_4a36bbd1_signal[1050]: Error loading state file for user +49xxxxxxxxx : Config file was created by a more recent version: 9 (IOException)