haberda / signal-addon Goto Github PK

View Code? Open in Web Editor NEW

9.0 9.0 7.0 341 KB

Signal addon docker files

Dockerfile 52.19% Shell 47.81%

signal-addon's People

Contributors

Stargazers

Watchers

Forkers

manzari robin-thoni aneisch alas89 fujexo theblackmini vneno

signal-addon's Issues

No longer able to send messages

Addon stopped working a couple of hours ago. I am no longer able to send messages. There are no error messages in the logs but when I try to send a message using Home Assistant's Developer tools/Services it complains: Failed to call service notify.signal_ha_test. Unknown error

No addon repository?

I run Home Assistant supervised.
I swear I installed your addon (0.42.0) using the Addon Store.
But I'm trying to update (issue) but am getting an error.
https://github.com/haberda/signal-addon is not a valid add-on repository

Are you missing the repository.json file?

can run this docker image on arm64

Hi, I installed this docker image through home assistant on my raspberry pi 4 with ubuntu (arm64). When I check the /var/log/signal-cli-json-rpc-1/out.log

it says:


OpenJDK Server VM warning: You have loaded library /tmp/sqlite-3.36.0.3-ac8623a3-aee1-4fa5-a340-971b59c6f6be-libsqlitejdbc.so which might have disabled stack guard. The VM will try to fix the
 stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
Failed to load native library:sqlite-3.36.0.3-ac8623a3-aee1-4fa5-a340-971b59c6f6be-libsqlitejdbc.so. osinfo: Linux/aarch64
java.lang.UnsatisfiedLinkError: /tmp/sqlite-3.36.0.3-ac8623a3-aee1-4fa5-a340-971b59c6f6be-libsqlitejdbc.so: /tmp/sqlite-3.36.0.3-ac8623a3-aee1-4fa5-a340-971b59c6f6be-libsqlitejdbc.so: wrong E
LF class: ELFCLASS64 (Possible cause: can't load AARCH64 .so on a ARM platform)
ERROR HikariPool - HikariPool-1 - Exception during pool initialization.
java.sql.SQLException: Error opening connection
        at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:244)
        at org.sqlite.SQLiteConnection.<init>(SQLiteConnection.java:61)
        at org.sqlite.jdbc3.JDBC3Connection.<init>(JDBC3Connection.java:28)
        at org.sqlite.jdbc4.JDBC4Connection.<init>(JDBC4Connection.java:21)
        at org.sqlite.JDBC.createConnection(JDBC.java:115)
        at org.sqlite.JDBC.connect(JDBC.java:90)
        at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:121)
        at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:359)
        at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201)
        at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:470)
        at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561)
        at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:100)
        at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:81)
        at org.asamk.signal.manager.storage.Database.getHikariDataSource(Database.java:94)
        at org.asamk.signal.manager.storage.Database.initDatabase(Database.java:32)
        at org.asamk.signal.manager.storage.AccountDatabase.init(AccountDatabase.java:23)
        at org.asamk.signal.manager.storage.SignalAccount.lambda$getAccountDatabase$21(SignalAccount.java:1062)
        at org.asamk.signal.manager.storage.SignalAccount.getOrCreate(SignalAccount.java:1348)
        at org.asamk.signal.manager.storage.SignalAccount.getAccountDatabase(SignalAccount.java:1060)
        at org.asamk.signal.manager.storage.SignalAccount.initDatabase(SignalAccount.java:263)
        at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:88)
        at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:64)
        at org.asamk.signal.App.loadManager(App.java:337)
        at org.asamk.signal.App.handleLocalCommand(App.java:272)
        at org.asamk.signal.App.init(App.java:213)
        at org.asamk.signal.Main.main(Main.java:58)
Caused by: java.lang.Exception: No native library found for os.name=Linux, os.arch=aarch64, paths=[/org/sqlite/native/Linux/aarch64:/usr/java/packages/lib:/lib:/usr/lib]
        at org.sqlite.SQLiteJDBCLoader.loadSQLiteNativeLibrary(SQLiteJDBCLoader.java:389)
        at org.sqlite.SQLiteJDBCLoader.initialize(SQLiteJDBCLoader.java:68)
        at org.sqlite.core.NativeDB.load(NativeDB.java:63)
        at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:240)
        ... 25 common frames omitted
Error loading state file for user +4xxxxxxx: Failed to initialize pool: Error opening connection (PoolInitializationException)
OpenJDK Server VM warning: You have loaded library /tmp/sqlite-3.36.0.3-16d91112-4326-4d6d-be79-bb44fa1805bb-libsqlitejdbc.so which might have disabled stack guard. The VM will try to fix the
 stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
Failed to load native library:sqlite-3.36.0.3-16d91112-4326-4d6d-be79-bb44fa1805bb-libsqlitejdbc.so. osinfo: Linux/aarch64
java.lang.UnsatisfiedLinkError: /tmp/sqlite-3.36.0.3-16d91112-4326-4d6d-be79-bb44fa1805bb-libsqlitejdbc.so: /tmp/sqlite-3.36.0.3-16d91112-4326-4d6d-be79-bb44fa1805bb-libsqlitejdbc.so: wrong E
LF class: ELFCLASS64 (Possible cause: can't load AARCH64 .so on a ARM platform)
ERROR HikariPool - HikariPool-1 - Exception during pool initialization.
java.sql.SQLException: Error opening connection
        at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:244)
        at org.sqlite.SQLiteConnection.<init>(SQLiteConnection.java:61)
        at org.sqlite.jdbc3.JDBC3Connection.<init>(JDBC3Connection.java:28)
        at org.sqlite.jdbc4.JDBC4Connection.<init>(JDBC4Connection.java:21)
        at org.sqlite.JDBC.createConnection(JDBC.java:115)
        at org.sqlite.JDBC.connect(JDBC.java:90)
        at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:121)
        at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:359)
        at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201)
        at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:470)
        at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561)
        at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:100)
        at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:81)
        at org.asamk.signal.manager.storage.Database.getHikariDataSource(Database.java:94)
        at org.asamk.signal.manager.storage.Database.initDatabase(Database.java:32)
        at org.asamk.signal.manager.storage.AccountDatabase.init(AccountDatabase.java:23)
        at org.asamk.signal.manager.storage.SignalAccount.lambda$getAccountDatabase$21(SignalAccount.java:1062)
        at org.asamk.signal.manager.storage.SignalAccount.getOrCreate(SignalAccount.java:1348)
        at org.asamk.signal.manager.storage.SignalAccount.getAccountDatabase(SignalAccount.java:1060)
        at org.asamk.signal.manager.storage.SignalAccount.initDatabase(SignalAccount.java:263)
        at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:88)
        at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:64)
        at org.asamk.signal.App.loadManager(App.java:337)
        at org.asamk.signal.App.handleLocalCommand(App.java:272)
        at org.asamk.signal.App.init(App.java:213)
        at org.asamk.signal.Main.main(Main.java:58)
Caused by: java.lang.Exception: No native library found for os.name=Linux, os.arch=aarch64, paths=[/org/sqlite/native/Linux/aarch64:/usr/java/packages/lib:/lib:/usr/lib]
        at org.sqlite.SQLiteJDBCLoader.loadSQLiteNativeLibrary(SQLiteJDBCLoader.java:389)
        at org.sqlite.SQLiteJDBCLoader.initialize(SQLiteJDBCLoader.java:68)
        at org.sqlite.core.NativeDB.load(NativeDB.java:63)
        at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:240)
        ... 25 common frames omitted
Error loading state file for user +4xxxxxxxx: Failed to initialize pool: Error opening connection (PoolInitializationException)

Is there an easy way to fix this?

cannot send images

I'm using the add-on on

Home Assistant 2023.10.5
Supervisor 2023.10.1
Operating System 11.1
Frontend 20231005.0 - latest

I can send plaintext-messages without problems. However, when I try to attach images the messages are not sent.

The image I want to send is created dynamically in the www-folder /root/config/www.

This is my action-section inside a notification. I use the /local-shortcut for the path.

service: notify.signal
data:
  message: 🤖 Der Staubsauger legt jetzt los
  data:
    attachments:
      - /local/snapshot_rockrobo.png

When triggered, Homeassistant logs the following errors:

While executing automation automation.staubsauger_fertig_signal
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/pysignalclirestapi/api.py", line 202, in send_message
    with open(filename, "rb") as ofile:
         ^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/local/snapshot_rockrobo.png'

OK, here I assumed to have found the error (www is somehow not mapped to /local inside the add-on) and have changed the path in my automation accordingly.

service: notify.signal
data:
  message: 🤖 Der Staubsauger legt jetzt los
  data:
    attachments:
      - /root/config/www/snapshot_rockrobo.png

When sending now, I get EXACTLY the same error, complaining about No such file or directory: '/local/snapshot_rockrobo.png'.
I'm confused now :-)

HoAss Addon: Can only connect from remote

For me the rest-api does only work with an IP from the outside. The local IP or localhost as suggested in the examples do not work. I guess this relates to the docker image. So right now the API is exposed to everyone in my local network, instead of restricted to the local machine.
The following works from anywhere in the local network.
curl -X GET -H "Content-Type: application/json" '192.168.0.123:8080/v1/groups/<number>'

The following:
curl -X GET -H "Content-Type: application/json" '127.0.0.1:8080/v1/groups/<number>'
curl -X GET -H "Content-Type: application/json" 'localhost:8080/v1/groups/<number>'
both return:
curl: (7) Failed to connect to localhost port 8080 after 0 ms: Couldn't connect to server

Is this expected behaviour?
Any chance I can change this behaviour to expose the API only on the local machine?

Pairing an Android device is not possible

I installed the signal addon on a new HA installation. Then I tried to register my number using:

curl -X GET -H "Content-Type: application/json" 'http://homeassistant.local:8080/v1/qrcodelink?device_name=signalapi' --output qr.png

I can scan the resulting QR code with my signal app on android and it says: Device paired. But if I look into the paired devices menu there is nothing to see. And the HA installation says: User not registered.

What do I do wrong?

instructions for adding desktop app

install desktop app
use a qr scanner app on a phone to translate QR to URI
install/run portainer on HASS
open console on addon_signal_messenger container

su signal-api
signal-cli --config /data -u "+15555555555" addDevice --uri "sgnl://linkdevice?uuid=xyz&pub_key=xyz2"

json-rpc mode issues, high CPU

The change in the Signal client seemed very promising. I was getting responses within 2-3 seconds regularly, so anything better would be a nice enhancement (I use it for the doorbell for instance). However, json-rpc seems to be slower. I call the notify.signal service in Home Assistant (via Node Red).

Results with native mode:

Mode:
native
AUTO RECEIVE SCHEDULE:
0 22 * * *
Signal-cli command timeout:
60
+ set -e
+ [ -z /data ]
+ chown 1000:1000 -R /data
+ cat
+ cap_prefix=-cap_
+ cat /proc/sys/kernel/cap_last_cap
+ seq -s ,-cap_ 0 40
+ caps=-cap_0,-cap_1,-cap_2,-cap_3,-cap_4,-cap_5,-cap_6,-cap_7,-cap_8,-cap_9,-cap_10,-cap_11,-cap_12,-cap_13,-cap_14,-cap_15,-cap_16,-cap_17,-cap_18,-cap_19,-cap_20,-cap_21,-cap_22,-cap_23,-cap_24,-cap_25,-cap_26,-cap_27,-cap_28,-cap_29,-cap_30,-cap_31,-cap_32,-cap_33,-cap_34,-cap_35,-cap_36,-cap_37,-cap_38,-cap_39,-cap_40
+ [ native = json-rpc ]
+ exec setpriv --reuid=1000 --regid=1000 --init-groups --inh-caps=-cap_0,-cap_1,-cap_2,-cap_3,-cap_4,-cap_5,-cap_6,-cap_7,-cap_8,-cap_9,-cap_10,-cap_11,-cap_12,-cap_13,-cap_14,-cap_15,-cap_16,-cap_17,-cap_18,-cap_19,-cap_20,-cap_21,-cap_22,-cap_23,-cap_24,-cap_25,-cap_26,-cap_27,-cap_28,-cap_29,-cap_30,-cap_31,-cap_32,-cap_33,-cap_34,-cap_35,-cap_36,-cap_37,-cap_38,-cap_39,-cap_40 signal-cli-rest-api -signal-cli-config=/data
time="2021-12-28T17:07:24+01:00" level=info msg="Started Signal Messenger REST API"
[GIN] 2021/12/28 - 17:07:53 | 200 |      57.862µs |    192.168.1.17 | GET      "/v1/about"
[GIN] 2021/12/28 - 17:07:58 | 201 |  4.561670208s |    192.168.1.17 | POST     "/v2/send"
[GIN] 2021/12/28 - 17:08:00 | 200 |      21.759µs |    192.168.1.17 | GET      "/v1/about"
[GIN] 2021/12/28 - 17:08:02 | 201 |  2.003697769s |    192.168.1.17 | POST     "/v2/send"
[GIN] 2021/12/28 - 17:08:05 | 200 |      19.922µs |    192.168.1.17 | GET      "/v1/about"
[GIN] 2021/12/28 - 17:08:07 | 201 |  1.693064491s |    192.168.1.17 | POST     "/v2/send"
[GIN] 2021/12/28 - 17:09:30 | 200 |      21.438µs |    192.168.1.17 | GET      "/v1/about"
[GIN] 2021/12/28 - 17:09:33 | 201 |  3.287141804s |    192.168.1.17 | POST     "/v2/send"
[GIN] 2021/12/28 - 17:10:30 | 200 |      21.114µs |    192.168.1.17 | GET      "/v1/about"

Results with json-rpc:

Mode:
json-rcp
+ set -e
+ [ -z /data ]
+ chown 1000:1000 -R /data
+ cat
+ cap_prefix=-cap_
+ cat /proc/sys/kernel/cap_last_cap
+ seq -s ,-cap_ 0 40
+ caps=-cap_0,-cap_1,-cap_2,-cap_3,-cap_4,-cap_5,-cap_6,-cap_7,-cap_8,-cap_9,-cap_10,-cap_11,-cap_12,-cap_13,-cap_14,-cap_15,-cap_16,-cap_17,-cap_18,-cap_19,-cap_20,-cap_21,-cap_22,-cap_23,-cap_24,-cap_25,-cap_26,-cap_27,-cap_28,-cap_29,-cap_30,-cap_31,-cap_32,-cap_33,-cap_34,-cap_35,-cap_36,-cap_37,-cap_38,-cap_39,-cap_40
+ [ json-rcp = json-rpc ]
+ exec setpriv --reuid=1000 --regid=1000 --init-groups --inh-caps=-cap_0,-cap_1,-cap_2,-cap_3,-cap_4,-cap_5,-cap_6,-cap_7,-cap_8,-cap_9,-cap_10,-cap_11,-cap_12,-cap_13,-cap_14,-cap_15,-cap_16,-cap_17,-cap_18,-cap_19,-cap_20,-cap_21,-cap_22,-cap_23,-cap_24,-cap_25,-cap_26,-cap_27,-cap_28,-cap_29,-cap_30,-cap_31,-cap_32,-cap_33,-cap_34,-cap_35,-cap_36,-cap_37,-cap_38,-cap_39,-cap_40 signal-cli-rest-api -signal-cli-config=/data
time="2021-12-28T17:11:30+01:00" level=info msg="Started Signal Messenger REST API"
[GIN] 2021/12/28 - 17:12:36 | 200 |      53.236µs |    192.168.1.17 | GET      "/v1/about"
[GIN] 2021/12/28 - 17:12:41 | 201 |  5.174422383s |    192.168.1.17 | POST     "/v2/send"
[GIN] 2021/12/28 - 17:12:44 | 200 |      21.142µs |    192.168.1.17 | GET      "/v1/about"
[GIN] 2021/12/28 - 17:12:49 | 201 |  4.312247366s |    192.168.1.17 | POST     "/v2/send"
[GIN] 2021/12/28 - 17:13:05 | 200 |      21.207µs |    192.168.1.17 | GET      "/v1/about"
[GIN] 2021/12/28 - 17:13:10 | 201 |  4.713009094s |    192.168.1.17 | POST     "/v2/send"
[GIN] 2021/12/28 - 17:13:12 | 200 |      26.549µs |    192.168.1.17 | GET      "/v1/about"
[GIN] 2021/12/28 - 17:13:17 | 201 |  4.979252887s |    192.168.1.17 | POST     "/v2/send"
[GIN] 2021/12/28 - 17:13:17 | 200 |      32.515µs |    192.168.1.17 | GET      "/v1/about"
[GIN] 2021/12/28 - 17:13:22 | 201 |  4.341918651s |    192.168.1.17 | POST     "/v2/send"

In the Configuration options and logging there is also a typo (json-rcp).

Java exception in 0.65

After updating to v0.65 no more messages could be sent. Downgraded to v0.64 and everything is back to normal operation.

Home Assistant 2022.11.5
Supervisor 2022.12.1
Operating System 9.3
Frontend 20221108.0 - latest

Logs:

`Logger: homeassistant.components.automation.testsignalmessenger
Source: components/signal_messenger/notify.py:104
Integration: Automatisierung (documentation, issues)
First occurred: 20:21:50 (2 occurrences)
Last logged: 20:21:50

TestSignalMessenger: Error executing script. Unexpected error for call_service at pos 1: Failed to load native library:sqlite-3.40.0.0-092410ba-a44b-41b8-b020-8af14cfc7e8a-libsqlitejdbc.so. osinfo: Linux/x86_64 java.lang.UnsatisfiedLinkError: Can't load library: /tmp/sqlite-3.40.0.0-092410ba-a44b-41b8-b020-8af14cfc7e8a-libsqlitejdbc.so at com.oracle.svm.core.jdk.NativeLibrarySupport.loadLibraryAbsolute(NativeLibrarySupport.java:104) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:54) at java.lang.Runtime.load0(Runtime.java:755) at java.lang.System.load(System.java:1953) at org.sqlite.SQLiteJDBCLoader.loadNativeLibrary(SQLiteJDBCLoader.java:280) at org.sqlite.SQLiteJDBCLoader.extractAndLoadLibraryFile(SQLiteJDBCLoader.java:237) at org.sqlite.SQLiteJDBCLoader.loadSQLiteNativeLibrary(SQLiteJDBCLoader.java:350) at org.sqlite.SQLiteJDBCLoader.initialize(SQLiteJDBCLoader.java:68) at org.sqlite.core.NativeDB.load(NativeDB.java:63) at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:278) at org.sqlite.SQLiteConnection.(SQLiteConnection.java:65) at org.sqlite.jdbc3.JDBC3Connection.(JDBC3Connection.java:28) at org.sqlite.jdbc4.JDBC4Connection.(JDBC4Connection.java:19) at org.sqlite.JDBC.createConnection(JDBC.java:104) at org.sqlite.JDBC.connect(JDBC.java:77) at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:121) at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:359) at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201) at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:470) at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561) at com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:100) at com.zaxxer.hikari.HikariDataSource.(HikariDataSource.java:81) at org.asamk.signal.manager.storage.Database.getHikariDataSource(Database.java:101) at org.asamk.signal.manager.storage.Database.initDatabase(Database.java:32) at org.asamk.signal.manager.storage.AccountDatabase.init(AccountDatabase.java:32) at org.asamk.signal.manager.storage.SignalAccount.lambda$getAccountDatabase$38(SignalAccount.java:1236) at org.asamk.signal.manager.storage.SignalAccount.getOrCreate(SignalAccount.java:1649) at org.asamk.signal.manager.storage.SignalAccount.getAccountDatabase(SignalAccount.java:1234) at org.asamk.signal.manager.storage.SignalAccount.lambda$getRecipientStore$30(SignalAccount.java:1209) at org.asamk.signal.manager.storage.SignalAccount.getOrCreate(SignalAccount.java:1649) at org.asamk.signal.manager.storage.SignalAccount.getRecipientStore(SignalAccount.java:1206) at org.asamk.signal.manager.storage.recipients.RecipientTrustedResolver$RecipientTrustedResolverWrapper.resolveSelfRecipientTrusted(RecipientTrustedResolver.java:28) at org.asamk.signal.manager.storage.SignalAccount.load(SignalAccount.java:639) at org.asamk.signal.manager.storage.SignalAccount.load(SignalAccount.java:181) at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:92) at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:79) at org.asamk.signal.App.loadManager(App.java:355) at org.asamk.signal.App.handleLocalCommand(App.java:288) at org.asamk.signal.App.init(App.java:229) at org.asamk.signal.Main.main(Main.java:60) ERROR HikariPool - HikariPool-1 - Exception during pool initialization. java.sql.SQLException: Error opening connection at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:281) at org.sqlite.SQLiteConnection.(SQLiteConnection.java:65) at org.sqlite.jdbc3.JDBC3Connection.(JDBC3Connection.java:28) at org.sqlite.jdbc4.JDBC4Connection.(JDBC4Connection.java:19) at org.sqlite.JDBC.createConnection(JDBC.java:104) at org.sqlite.JDBC.connect(JDBC.java:77) at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:121) at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:359) at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201) at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:470) at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561) at com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:100) at com.zaxxer.hikari.HikariDataSource.(HikariDataSource.java:81) at org.asamk.signal.manager.storage.Database.getHikariDataSource(Database.java:101) at org.asamk.signal.manager.storage.Database.initDatabase(Database.java:32) at org.asamk.signal.manager.storage.AccountDatabase.init(AccountDatabase.java:32) at org.asamk.signal.manager.storage.SignalAccount.lambda$getAccountDatabase$38(SignalAccount.java:1236) at org.asamk.signal.manager.storage.SignalAccount.getOrCreate(SignalAccount.java:1649) at org.asamk.signal.manager.storage.SignalAccount.getAccountDatabase(SignalAccount.java:1234) at org.asamk.signal.manager.storage.SignalAccount.lambda$getRecipientStore$30(SignalAccount.java:1209) at org.asamk.signal.manager.storage.SignalAccount.getOrCreate(SignalAccount.java:1649) at org.asamk.signal.manager.storage.SignalAccount.getRecipientStore(SignalAccount.java:1206) at org.asamk.signal.manager.storage.recipients.RecipientTrustedResolver$RecipientTrustedResolverWrapper.resolveSelfRecipientTrusted(RecipientTrustedResolver.java:28) at org.asamk.signal.manager.storage.SignalAccount.load(SignalAccount.java:639) at org.asamk.signal.manager.storage.SignalAccount.load(SignalAccount.java:181) at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:92) at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:79) at org.asamk.signal.App.loadManager(App.java:355) at org.asamk.signal.App.handleLocalCommand(App.java:288) at org.asamk.signal.App.init(App.java:229) at org.asamk.signal.Main.main(Main.java:60) Caused by: java.lang.Exception: No native library found for os.name=Linux, os.arch=x86_64, paths=[/org/sqlite/native/Linux/x86_64:/usr/lib64:/lib64:/lib:/usr/lib] at org.sqlite.SQLiteJDBCLoader.loadSQLiteNativeLibrary(SQLiteJDBCLoader.java:375) at org.sqlite.SQLiteJDBCLoader.initialize(SQLiteJDBCLoader.java:68) at org.sqlite.core.NativeDB.load(NativeDB.java:63) at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:278) ... 30 common frames omitted Error loading state file for user XXXXXXXXXXXX: Failed to initialize pool: Error opening connection (PoolInitializationException)
While executing automation automation.testsignalmessenger
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 451, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 684, in _async_call_service_step
await service_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1744, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1781, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/components/notify/legacy.py", line 258, in _async_notify_message_service
await self.async_send_message(**kwargs)
File "/usr/src/homeassistant/homeassistant/components/notify/legacy.py", line 234, in async_send_message
await self.hass.async_add_executor_job(
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/signal_messenger/notify.py", line 109, in send_message
raise ex
File "/usr/src/homeassistant/homeassistant/components/signal_messenger/notify.py", line 104, in send_message
self._signal_cli_rest_api.send_message(
File "/usr/local/lib/python3.10/site-packages/pysignalclirestapi/api.py", line 221, in send_message
raise exc
File "/usr/local/lib/python3.10/site-packages/pysignalclirestapi/api.py", line 216, in send_message
raise SignalCliRestApiError(json_resp["error"])
pysignalclirestapi.api.SignalCliRestApiError: Failed to load native library:sqlite-3.40.0.0-092410ba-a44b-41b8-b020-8af14cfc7e8a-libsqlitejdbc.so. osinfo: Linux/x86_64
java.lang.UnsatisfiedLinkError: Can't load library: /tmp/sqlite-3.40.0.0-092410ba-a44b-41b8-b020-8af14cfc7e8a-libsqlitejdbc.so
at com.oracle.svm.core.jdk.NativeLibrarySupport.loadLibraryAbsolute(NativeLibrarySupport.java:104)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:54)
at java.lang.Runtime.load0(Runtime.java:755)
at java.lang.System.load(System.java:1953)
at org.sqlite.SQLiteJDBCLoader.loadNativeLibrary(SQLiteJDBCLoader.java:280)
at org.sqlite.SQLiteJDBCLoader.extractAndLoadLibraryFile(SQLiteJDBCLoader.java:237)
at org.sqlite.SQLiteJDBCLoader.loadSQLiteNativeLibrary(SQLiteJDBCLoader.java:350)
at org.sqlite.SQLiteJDBCLoader.initialize(SQLiteJDBCLoader.java:68)
at org.sqlite.core.NativeDB.load(NativeDB.java:63)
at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:278)
at org.sqlite.SQLiteConnection.(SQLiteConnection.java:65)
at org.sqlite.jdbc3.JDBC3Connection.(JDBC3Connection.java:28)
at org.sqlite.jdbc4.JDBC4Connection.(JDBC4Connection.java:19)
at org.sqlite.JDBC.createConnection(JDBC.java:104)
at org.sqlite.JDBC.connect(JDBC.java:77)
at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:121)
at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:359)
at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201)
at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:470)
at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561)
at com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:100)
at com.zaxxer.hikari.HikariDataSource.(HikariDataSource.java:81)
at org.asamk.signal.manager.storage.Database.getHikariDataSource(Database.java:101)
at org.asamk.signal.manager.storage.Database.initDatabase(Database.java:32)
at org.asamk.signal.manager.storage.AccountDatabase.init(AccountDatabase.java:32)
at org.asamk.signal.manager.storage.SignalAccount.lambda$getAccountDatabase$38(SignalAccount.java:1236)
at org.asamk.signal.manager.storage.SignalAccount.getOrCreate(SignalAccount.java:1649)
at org.asamk.signal.manager.storage.SignalAccount.getAccountDatabase(SignalAccount.java:1234)
at org.asamk.signal.manager.storage.SignalAccount.lambda$getRecipientStore$30(SignalAccount.java:1209)
at org.asamk.signal.manager.storage.SignalAccount.getOrCreate(SignalAccount.java:1649)
at org.asamk.signal.manager.storage.SignalAccount.getRecipientStore(SignalAccount.java:1206)
at org.asamk.signal.manager.storage.recipients.RecipientTrustedResolver$RecipientTrustedResolverWrapper.resolveSelfRecipientTrusted(RecipientTrustedResolver.java:28)
at org.asamk.signal.manager.storage.SignalAccount.load(SignalAccount.java:639)
at org.asamk.signal.manager.storage.SignalAccount.load(SignalAccount.java:181)
at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:92)
at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:79)
at org.asamk.signal.App.loadManager(App.java:355)
at org.asamk.signal.App.handleLocalCommand(App.java:288)
at org.asamk.signal.App.init(App.java:229)
at org.asamk.signal.Main.main(Main.java:60)
ERROR HikariPool - HikariPool-1 - Exception during pool initialization.
java.sql.SQLException: Error opening connection
at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:281)
at org.sqlite.SQLiteConnection.(SQLiteConnection.java:65)
at org.sqlite.jdbc3.JDBC3Connection.(JDBC3Connection.java:28)
at org.sqlite.jdbc4.JDBC4Connection.(JDBC4Connection.java:19)
at org.sqlite.JDBC.createConnection(JDBC.java:104)
at org.sqlite.JDBC.connect(JDBC.java:77)
at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:121)
at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:359)
at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201)
at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:470)
at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561)
at com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:100)
at com.zaxxer.hikari.HikariDataSource.(HikariDataSource.java:81)
at org.asamk.signal.manager.storage.Database.getHikariDataSource(Database.java:101)
at org.asamk.signal.manager.storage.Database.initDatabase(Database.java:32)
at org.asamk.signal.manager.storage.AccountDatabase.init(AccountDatabase.java:32)
at org.asamk.signal.manager.storage.SignalAccount.lambda$getAccountDatabase$38(SignalAccount.java:1236)
at org.asamk.signal.manager.storage.SignalAccount.getOrCreate(SignalAccount.java:1649)
at org.asamk.signal.manager.storage.SignalAccount.getAccountDatabase(SignalAccount.java:1234)
at org.asamk.signal.manager.storage.SignalAccount.lambda$getRecipientStore$30(SignalAccount.java:1209)
at org.asamk.signal.manager.storage.SignalAccount.getOrCreate(SignalAccount.java:1649)
at org.asamk.signal.manager.storage.SignalAccount.getRecipientStore(SignalAccount.java:1206)
at org.asamk.signal.manager.storage.recipients.RecipientTrustedResolver$RecipientTrustedResolverWrapper.resolveSelfRecipientTrusted(RecipientTrustedResolver.java:28)
at org.asamk.signal.manager.storage.SignalAccount.load(SignalAccount.java:639)
at org.asamk.signal.manager.storage.SignalAccount.load(SignalAccount.java:181)
at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:92)
at org.asamk.signal.manager.SignalAccountFiles.initManager(SignalAccountFiles.java:79)
at org.asamk.signal.App.loadManager(App.java:355)
at org.asamk.signal.App.handleLocalCommand(App.java:288)
at org.asamk.signal.App.init(App.java:229)
at org.asamk.signal.Main.main(Main.java:60)
Caused by: java.lang.Exception: No native library found for os.name=Linux, os.arch=x86_64, paths=[/org/sqlite/native/Linux/x86_64:/usr/lib64:/lib64:/lib:/usr/lib]
at org.sqlite.SQLiteJDBCLoader.loadSQLiteNativeLibrary(SQLiteJDBCLoader.java:375)
at org.sqlite.SQLiteJDBCLoader.initialize(SQLiteJDBCLoader.java:68)
at org.sqlite.core.NativeDB.load(NativeDB.java:63)
at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:278)
... 30 common frames omitted
Error loading state file for user XXXXXXXXXX: Failed to initialize pool: Error opening connection (PoolInitializationException)
`

Cannot receive messages

I’m able to send messages to my phone using the integration. But I can’t get receiving messages to work. I set everything up like in the manual. The integration is running in json-rpc mode.
- resource: "http://127.0.0.1:8080/v1/receive/<number>" headers: Content-Type: application/json sensor: - name: "Signal message received" value_template: "" #this will fetch the message json_attributes_path: $[0].envelope json_attributes: - source #using attributes you can get additional information, in this case, the phone number.

and
`...
trigger:

platform: state
entity_id:
- sensor.signal_message_received
  attribute: source
  to: ""
  action:
service: notify.signal
data:
message: "Message received!"`

Looking in the logs is giving me the following errors
2024-02-13 19:40:19.985 DEBUG (MainThread) [homeassistant.components.rest.data] Updating from http://127.0.0.1:8080/v1/receive/{mynumber} 2024-02-13 19:40:20.002 DEBUG (MainThread) [homeassistant.components.rest] Finished fetching rest data data in 0.017 seconds (success: True) 2024-02-13 19:40:20.002 DEBUG (MainThread) [homeassistant.components.rest.data] Data fetched from resource: Bad Request {"error":"websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header"} 2024-02-13 19:40:20.002 WARNING (MainThread) [homeassistant.components.rest.util] REST result could not be parsed as JSON 2024-02-13 19:40:20.003 DEBUG (MainThread) [homeassistant.components.rest.util] Erroneous JSON: Bad Request {"error":"websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header"}

I'm sorry for the layout, i can't seem to fix it.
For better reading I also posted it here https://community.home-assistant.io/t/unable-to-receive-messages-using-signal-messenger-integration/689580

Constant high CPU for the addon

The signal messenger addon uses a constant 26% of CPU resources, while all my other addons use barely no CPU resources whatsoever. No notifications are being sent at the times that I checked. The percentage remais, even after restats and waiting and coming back to the addon later on.

Platform is an RPI4, running version 0.59.0 using json-rpc mode and running on HA version 2022.5.3

Java Error When Using the Add-On, CLI (curl) Works

Calling notify.signal service results in the following Java error (see logs below).
- Add-on worked without issue until now
Calling the REST api from console works as expected (register, message send/receive, groups, etc)

Error log:

Logger: homeassistant.helpers.script.websocket_api_script
Source: components/signal_messenger/notify.py:76
First occurred: 1:00:14 AM (1 occurrences)
Last logged: 1:00:14 AM

websocket_api script: Error executing script. Unexpected error for call_service at pos 1: Exception in thread "main" java.lang.NumberFormatException: For input string: "51196591+72" at java.lang.Long.parseLong(Long.java:692) at java.lang.Long.parseLong(Long.java:817) at org.whispersystems.signalservice.internal.contacts.crypto.ContactDiscoveryCipher.buildQueryData(ContactDiscoveryCipher.java:65) at org.whispersystems.signalservice.internal.contacts.crypto.ContactDiscoveryCipher.createDiscoveryRequest(ContactDiscoveryCipher.java:28) at org.whispersystems.signalservice.api.SignalServiceAccountManager.getRegisteredUsers(SignalServiceAccountManager.java:425) at org.asamk.signal.manager.Manager.getRegisteredUsers(Manager.java:1601) at org.asamk.signal.manager.Manager.getSignalServiceAddresses(Manager.java:1568) at org.asamk.signal.manager.Manager.sendMessage(Manager.java:1286) at org.asamk.signal.dbus.DbusSignalImpl.sendMessage(DbusSignalImpl.java:101) at org.asamk.signal.commands.SendCommand.handleCommand(SendCommand.java:122) at org.asamk.signal.commands.DbusCommand.handleCommand(DbusCommand.java:15) at org.asamk.signal.App.handleLocalCommand(App.java:214) at org.asamk.signal.App.init(App.java:174) at org.asamk.signal.Main.main(Main.java:51)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 371, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 571, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1491, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1526, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/components/notify/__init__.py", line 159, in _async_notify_message_service
    await self.async_send_message(**kwargs)
  File "/usr/src/homeassistant/homeassistant/components/notify/__init__.py", line 136, in async_send_message
    await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/signal_messenger/notify.py", line 79, in send_message
    raise ex
  File "/usr/src/homeassistant/homeassistant/components/signal_messenger/notify.py", line 76, in send_message
    self._signal_cli_rest_api.send_message(message, self._recp_nrs, filenames)
  File "/usr/local/lib/python3.9/site-packages/pysignalclirestapi/api.py", line 83, in send_message
    raise exc
  File "/usr/local/lib/python3.9/site-packages/pysignalclirestapi/api.py", line 79, in send_message
    raise SignalCliRestApiError(json_resp["error"])
pysignalclirestapi.api.SignalCliRestApiError: Exception in thread "main" java.lang.NumberFormatException: For input string: "51196591+72"
	at java.lang.Long.parseLong(Long.java:692)
	at java.lang.Long.parseLong(Long.java:817)
	at org.whispersystems.signalservice.internal.contacts.crypto.ContactDiscoveryCipher.buildQueryData(ContactDiscoveryCipher.java:65)
	at org.whispersystems.signalservice.internal.contacts.crypto.ContactDiscoveryCipher.createDiscoveryRequest(ContactDiscoveryCipher.java:28)
	at org.whispersystems.signalservice.api.SignalServiceAccountManager.getRegisteredUsers(SignalServiceAccountManager.java:425)
	at org.asamk.signal.manager.Manager.getRegisteredUsers(Manager.java:1601)
	at org.asamk.signal.manager.Manager.getSignalServiceAddresses(Manager.java:1568)
	at org.asamk.signal.manager.Manager.sendMessage(Manager.java:1286)
	at org.asamk.signal.dbus.DbusSignalImpl.sendMessage(DbusSignalImpl.java:101)
	at org.asamk.signal.commands.SendCommand.handleCommand(SendCommand.java:122)
	at org.asamk.signal.commands.DbusCommand.handleCommand(DbusCommand.java:15)
	at org.asamk.signal.App.handleLocalCommand(App.java:214)
	at org.asamk.signal.App.init(App.java:174)
	at org.asamk.signal.Main.main(Main.java:51)

update

what are the chances of getting this updated to the latest version?

process killed as timeout reached (In HA 2021.7.2)

Since update to latest HA: 2021.7.2 I see those errors:

2021-07-14 16:17:28 ERROR (SyncWorker_15) [homeassistant.components.signal_messenger.notify] process killed as timeout reached
2021-07-14 16:17:28 ERROR (MainThread) [homeassistant.core] Error executing service: <ServiceCall notify.signal_to_sister (c:3b8666508650253f82c827d7172605dc): message=Template("Jongejans GP, # 4, €: 4.99")>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 1507, in catch_exceptions
    await coro_or_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1526, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/components/notify/__init__.py", line 159, in _async_notify_message_service
    await self.async_send_message(**kwargs)
  File "/usr/src/homeassistant/homeassistant/components/notify/__init__.py", line 136, in async_send_message
    await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/signal_messenger/notify.py", line 79, in send_message
    raise ex
  File "/usr/src/homeassistant/homeassistant/components/signal_messenger/notify.py", line 76, in send_message
    self._signal_cli_rest_api.send_message(message, self._recp_nrs, filenames)
  File "/usr/local/lib/python3.9/site-packages/pysignalclirestapi/api.py", line 83, in send_message
    raise exc
  File "/usr/local/lib/python3.9/site-packages/pysignalclirestapi/api.py", line 79, in send_message
    raise SignalCliRestApiError(json_resp["error"])
pysignalclirestapi.api.SignalCliRestApiError: process killed as timeout reached

2021-07-14 18:17:27 ERROR (SyncWorker_1) [homeassistant.components.signal_messenger.notify] process killed as timeout reached
2021-07-14 18:17:27 ERROR (MainThread) [homeassistant.core] Error executing service: <ServiceCall notify.signal_to_sister (c:c433c1133a700e6b05b998ad58fc131d): message=Template("Le Pain Quotidien GP, # 2, €: 4.99")>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 1507, in catch_exceptions
    await coro_or_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1526, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/components/notify/__init__.py", line 159, in _async_notify_message_service
    await self.async_send_message(**kwargs)
  File "/usr/src/homeassistant/homeassistant/components/notify/__init__.py", line 136, in async_send_message
    await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/signal_messenger/notify.py", line 79, in send_message
    raise ex
  File "/usr/src/homeassistant/homeassistant/components/signal_messenger/notify.py", line 76, in send_message
    self._signal_cli_rest_api.send_message(message, self._recp_nrs, filenames)
  File "/usr/local/lib/python3.9/site-packages/pysignalclirestapi/api.py", line 83, in send_message
    raise exc
  File "/usr/local/lib/python3.9/site-packages/pysignalclirestapi/api.py", line 79, in send_message
    raise SignalCliRestApiError(json_resp["error"])
pysignalclirestapi.api.SignalCliRestApiError: process killed as timeout reached

QR Code - 'Device approved' but doesn't work.

Sorry I couldn't really figure out if this was an issue with addon or not :(

I generated QR code with this command: http://192.168.100.156:8080/v1/qrcodelink?device_name=homeass
Scanned it with the app.
Got message: Device approved!
However, the device does not show up in the 'linked devices' section of the app.
And when I try to send notification with addon, nothing happens.

What could I do to fix this ?

Use latest upstream version

The current add-on version is using 0.60 from upstream. The current upstream release is 0.62, and there will be an update shortly to address bbernhard/signal-cli-rest-api#286

My add-on is experiencing this issue. With the add-on in "normal" mode, the following code allows it to resume operation

apt update && apt install -y zip unzip && \
cd /opt/signal-cli-0.10.8/lib/ && \
mkdir tmp && \
cd tmp/ && \
unzip ../signal-cli-0.10.8.jar && \
sed -i 's/Signal-Android\/5.22.3/Signal-Android\/5.51.7/g' org/asamk/signal/BaseConfig.class && \
zip -r ../signal-cli-0.10.8.jar org/ META-INF/ && \
cd .. && \
rm -rf tmp/ && \
exit

Can the HA addon please be brought up to date with upstream (when the upstream issue is resolved)?

Error: Couldn't read data for number : EOF. Is the number properly registered?

Hey!

So something has happened.
My addon is not working and there is a lot of:
time="2023-11-11T22:29:35+01:00" level=error msg="Couldn't read data for number : EOF. Is the number properly registered?"
in my log.
Everything was working fine until last week.

Probably the problem was figured out by bbernhard here

Any chance to fix the addon?
Thanks!

Container stuck on "Removal in Progress" after update

I tried to update the signal addon today and it wouldn't start again. When I went to the UI and clicked start I got this message:

It seems like the addon did not shut down properly and is now stuck. I can't really seem to get it unstuck either, here's what I've tried:

As you can see, no joy. Here's the logs from the dockerd service at the time I updated (around 2022-01-18T09:04:38-05:00) and when I tried to force kill it later (around 2022-01-18T11:52:47-05:00):

2022-01-18T12:01:04-05:00	time="2022-01-18T17:01:04.398353222Z" level=error msg="Handler for DELETE /v1.41/containers/99d130465de0 returned error: container 99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a: driver \"overlay2\" failed to remove root filesystem: unlinkat /mnt/data/docker/overlay2/6e940ced0aba9ebc22e9be604af7ada8c5702a507e86b051d3d0f08ef85af887/merged: device or resource busy"
2022-01-18T12:01:04-05:00	time="2022-01-18T17:01:04.398033750Z" level=error msg="Error removing mounted layer 99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a: unlinkat /mnt/data/docker/overlay2/6e940ced0aba9ebc22e9be604af7ada8c5702a507e86b051d3d0f08ef85af887/merged: device or resource busy"
2022-01-18T11:52:47-05:00	time="2022-01-18T16:52:47.108876796Z" level=error msg="Handler for DELETE /v1.41/containers/99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a returned error: container 99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a: driver \"overlay2\" failed to remove root filesystem: unlinkat /mnt/data/docker/overlay2/6e940ced0aba9ebc22e9be604af7ada8c5702a507e86b051d3d0f08ef85af887/merged: device or resource busy"
2022-01-18T11:52:47-05:00	time="2022-01-18T16:52:47.108573033Z" level=error msg="Error removing mounted layer 99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a: unlinkat /mnt/data/docker/overlay2/6e940ced0aba9ebc22e9be604af7ada8c5702a507e86b051d3d0f08ef85af887/merged: device or resource busy"
2022-01-18T11:51:45-05:00	time="2022-01-18T16:51:45.816048998Z" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/b392b1e58a7f5a65bf62dba26669c1b6eb926c74301b862544d079fb9d3c4b06 pid=1246545
2022-01-18T11:51:41-05:00	time="2022-01-18T16:51:41.804681343Z" level=error msg="copy shim log" error="read /proc/self/fd/50: file already closed"
2022-01-18T11:51:41-05:00	time="2022-01-18T16:51:41.804386789Z" level=info msg="shim disconnected" id=4f0206b5d068c51114ea212c64a6a4be8edbc1819c23fcce9bbae4e772dc792e
2022-01-18T11:51:41-05:00	time="2022-01-18T16:51:41.804014147Z" level=info msg="ignoring event" container=4f0206b5d068c51114ea212c64a6a4be8edbc1819c23fcce9bbae4e772dc792e module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
2022-01-18T11:51:41-05:00	time="2022-01-18T16:51:41.755714583Z" level=info msg="Container 4f0206b5d068c51114ea212c64a6a4be8edbc1819c23fcce9bbae4e772dc792e failed to exit within 10 seconds of signal 15 - using the force"
2022-01-18T11:50:53-05:00	time="2022-01-18T16:50:53.499986503Z" level=error msg="Handler for DELETE /v1.41/containers/99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a returned error: container 99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a: driver \"overlay2\" failed to remove root filesystem: unlinkat /mnt/data/docker/overlay2/6e940ced0aba9ebc22e9be604af7ada8c5702a507e86b051d3d0f08ef85af887/merged: device or resource busy"
2022-01-18T11:50:53-05:00	time="2022-01-18T16:50:53.499445063Z" level=error msg="Error removing mounted layer 99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a: unlinkat /mnt/data/docker/overlay2/6e940ced0aba9ebc22e9be604af7ada8c5702a507e86b051d3d0f08ef85af887/merged: device or resource busy"
2022-01-18T11:49:35-05:00	time="2022-01-18T16:49:35.395935217Z" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/4f0206b5d068c51114ea212c64a6a4be8edbc1819c23fcce9bbae4e772dc792e pid=1245580
2022-01-18T11:49:34-05:00	time="2022-01-18T16:49:34.547006220Z" level=info msg="ignoring event" container=5eaaa6bc2163f0b37f10fdaaf7cd3ec12f6d06a64797ec8a96098a4d1b359d75 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
2022-01-18T11:49:34-05:00	time="2022-01-18T16:49:34.546799628Z" level=error msg="copy shim log" error="read /proc/self/fd/118: file already closed"
2022-01-18T11:49:34-05:00	time="2022-01-18T16:49:34.546643662Z" level=info msg="shim disconnected" id=5eaaa6bc2163f0b37f10fdaaf7cd3ec12f6d06a64797ec8a96098a4d1b359d75
2022-01-18T11:49:34-05:00	time="2022-01-18T16:49:34.416508311Z" level=info msg="Container 5eaaa6bc2163f0b37f10fdaaf7cd3ec12f6d06a64797ec8a96098a4d1b359d75 failed to exit within 10 seconds of signal 15 - using the force"
2022-01-18T09:04:38-05:00	time="2022-01-18T14:04:38.846817553Z" level=error msg="Handler for DELETE /v1.41/containers/99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a returned error: container 99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a: driver \"overlay2\" failed to remove root filesystem: unlinkat /mnt/data/docker/overlay2/6e940ced0aba9ebc22e9be604af7ada8c5702a507e86b051d3d0f08ef85af887/merged: device or resource busy"
2022-01-18T09:04:38-05:00	time="2022-01-18T14:04:38.846509373Z" level=error msg="Error removing mounted layer 99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a: unlinkat /mnt/data/docker/overlay2/6e940ced0aba9ebc22e9be604af7ada8c5702a507e86b051d3d0f08ef85af887/merged: device or resource busy"
2022-01-18T09:04:33-05:00	time="2022-01-18T14:04:33.517519874Z" level=error msg="Handler for DELETE /v1.41/containers/99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a returned error: container 99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a: driver \"overlay2\" failed to remove root filesystem: unlinkat /mnt/data/docker/overlay2/6e940ced0aba9ebc22e9be604af7ada8c5702a507e86b051d3d0f08ef85af887/merged: device or resource busy"
2022-01-18T09:04:33-05:00	time="2022-01-18T14:04:33.517165109Z" level=error msg="Error removing mounted layer 99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a: unlinkat /mnt/data/docker/overlay2/6e940ced0aba9ebc22e9be604af7ada8c5702a507e86b051d3d0f08ef85af887/merged: device or resource busy"
2022-01-18T09:04:28-05:00	time="2022-01-18T14:04:28.261937439Z" level=error msg="copy shim log" error="read /proc/self/fd/50: file already closed"
2022-01-18T09:04:28-05:00	time="2022-01-18T14:04:28.244749930Z" level=info msg="shim disconnected" id=99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a
2022-01-18T09:04:28-05:00	time="2022-01-18T14:04:28.243743135Z" level=info msg="ignoring event" container=99d130465de0ee5cbe3aee703b8126413585025bacdbe58e68232e494bf6b84a module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"

You may remember I submitted an issue for this a while ago when this addon was in the other repo ( haberda/hassio_addons#29 ). Truth be told it really never went away. I've just been restarting the host every update, it's the only way I've been able to get the addon going again after it gets stuck like this. I decided to submit the issue this time because its a bit annoying and I'm just hoping someone has an idea.

And it happens to me so consistently I feel like it must happen to someone else, right? Fwiw I actually have like 20 addons running at all times and this addon is the only one this seems to happen with, its very strange.

Unable to start container - Directory not empty

Getting the following when attempting to start the add-on:

mv: inter-device move failed: '/data/data' to '/config/data'; unable to remove target: Directory not empty