agileek / hassio-addons

Some home assistant addons I manage

Hass.io plugins

Pre-built images

Signal

Signal cli wrapper

Syncthing

Forked from https://github.com/bestlibre/hassio-addons

hassio-addons's Issues

Signal addon will not run

I had the signal add on working previously, but due to some unrelated problems I had to restore a backup of my homeassistant install. It hasn't worked since then.

I've tried uninstalling the add on, rebooting my pi, reinstalling the add on and starting, but I get this same error from the logs. :
[FATAL tini (6)] exec main failed: No such file or directory

This is the only log in the "Log" tab from the Home Assistant Supervisor interface. I'm not sure where else to see any relevant logs to this add on. Let me know if there's a better place to look to see what's going on.

Acknowledge alerts from signal

Syncthing stops due to auto-update

The Synchting addon keeps on dropping due to an update that's available. Log:

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [start] 2022/12/17 10:55:22 INFO: syncthing v1.22.1 "Fermium Flea" (go1.19.2 linux-arm64) [email protected] 2022-11-02 06:27:53 UTC [start] 2022/12/17 10:55:22 INFO: Upgrade available (current "v1.22.1" < latest "v1.22.2") [start] 2022/12/17 10:55:25 INFO: Upgraded to "v1.22.2", exiting now. [monitor] 2022/12/17 10:55:25 INFO: Restarting monitor... [monitor] 2022/12/17 10:55:25 WARNING: Restart: no such file or directory s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped

Improvement: Support for attachments

Hello and thank's once again!

I'm using this hassio addon and it works great since the first day. What I'm actually missing is the support to attach one or more files. It would be pictures and/or videos in my case but should not need to limited to this file types. 📁

After update to HASS Signal 10.18.1, messages are not being sent

After update to HASS Signal 10.18.1, messages are not being sent, error in logs: :

Error org.freedesktop.dbus.exceptions.DBusExecutionException: Error Executing Method org.asamk.Signal.sendMessage: Cannot invoke "java.util.Locale.getLanguage()" because "locale" is null

• Home Assistant OS 7.1
• supervisor-2021.12.2
• core-2021.12.10

Perhaps it has to do with: AsamK/signal-cli@7d93574

Please help. THX!

The Synching addon keeps on restarting due to a repeated update that is being executed

The Synching addon keeps on restarting due to an update that's available.
It successfully updates, but after a restart it's back on the old version and starts the whole process again.
Log:

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [start] 2023/07/06 04:44:50 INFO: syncthing v1.23.5 "Fermium Flea" (go1.20.4 linux-arm64) [email protected] 2023-06-06 07:06:51 UTC [GSNLI] 2023/07/06 04:44:52 INFO: Connected to device XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX with a newer version (current "v1.23.5" < remote "v1.23.6"). Checking for upgrades. [GSNLI] 2023/07/06 04:44:52 INFO: Automatic upgrade (current "v1.23.5" < latest "v1.23.6") [GSNLI] 2023/07/06 04:44:54 WARNING: Automatically upgraded to version "v1.23.6". Restarting in 1 minute.

Originally posted by @thefoxmangit in #52

Signal addon does not start anymore on aarch64 architecture

The addon does not start anymore on my system since a few days/weeks(?). It could have come from from the last update, but I had auto-updates enabled and thus cannot tell for sure. Reinstalling did not resolve it.

It did work flawlessly before, thanks for making Signal on Home Assistant possible so far!

Configuration

phone_number: '+0123456789012'
signal_config_path: /config/.signal
log_level: trace

File structure

/config/
    .signal/
        data/
            +0123456789012.d/
            +0123456789012

Addon Log

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Signal
 Addon for wrapping signal inside docker
-----------------------------------------------------------
 Add-on version: 10.9.0
 You are running the latest version of this add-on.
parse error: Expected string key before ':' at line 1, column 4
[20:45:51] ERROR: Unknown HTTP error occured
 System:   (aarch64 / raspberrypi4-64)
 Home Assistant Core: 0.110.5
 Home Assistant Supervisor: 227
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to TRACE
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2020-06-08 20:45:53 +0200] [307] [INFO] Starting gunicorn 20.0.4
[2020-06-08 20:45:53 +0200] [307] [INFO] Listening at: http://0.0.0.0:5000 (307)
[2020-06-08 20:45:53 +0200] [307] [INFO] Using worker: sync
[2020-06-08 20:45:53 +0200] [309] [INFO] Booting worker with pid: 309
[2020-06-08 20:45:54 +0200] [307] [INFO] Shutting down: Master
[2020-06-08 20:45:54 +0200] [307] [INFO] Reason: Worker failed to boot.
[cmd] /run.sh exited 3
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Signal: WS error when sending messages to Home Assistant

Describe the bug
New year, new home assistant, new WS error :)

This is what I see in the addon logs when I send a message to home assistant:

2023-01-13 17:54:54,382 - root - INFO - message received {'sender': '+XXX', 'message': 'ASDFF'}
2023-01-13 17:54:54,383 - root - INFO - Sending message to ws://supervisor/core/websocket
2023-01-13 17:54:54,430 - root - ERROR - Unexpected error 'speech'
2023-01-13 17:54:54,431 - root - INFO - Sending "Something bad happened" to +XXX

I have no idea what this "speech" exception is.

To Reproduce
Setup intent script and send any message to home assistant

Runtime (please complete the following information):
Hardware: ODroid N2
OS: HASS OS
Architecture: arm64
Home assistant version:
Home Assistant Core 2023.1.1
Home Assistant Supervisor 2022.12.1
Home Assistant OS 9.4
Addon Version: 10.20.1

Add manifest.json to custom_component

Warning from core: 2021-05-10 20:21:42 ERROR (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'signalmessenger'. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of 'signalmessenger'
see https://developers.home-assistant.io/docs/creating_integration_manifest/
and https://www.home-assistant.io/blog/2021/03/03/release-20213/#breaking-changes

Sync thing fails to start after hassio update

Describe the bug

[start] 20:41:52 INFO: syncthing v1.7.1 "Fermium Flea" (go1.14.4 linux-arm64) [email protected] 2020-07-11 18:17:41 UTC
[start] 20:41:52 WARNING: Failed to initialize config: config file version (32) is newer than supported version (31). If this is expected, use -allow-newer-config to override.
[monitor] 20:41:52 INFO: Syncthing exited: exit status 1
[monitor] 20:41:53 WARNING: 4 restarts in 4.387341527s; not retrying further

Runtime (please complete the following information):

• Hardware: rpi 4b
• OS: hassos 4.13
• Architecture: arm64
• Home assistant version: 0.114.4
• Addon Version 1.7.1

Config file version (33) is newer than supported version (32)

Describe the bug
Syncthing no longer starting

[start] 20:41:28 INFO: syncthing v1.12.1 "Fermium Flea" (go1.15.6 linux-arm64) [email protected] 2020-12-06 12:46:27 UTC
[start] 20:41:28 WARNING: Failed to initialize config: config file version (33) is newer than supported version (32). If this is expected, use -allow-newer-config to override.
[monitor] 20:41:28 INFO: Syncthing exited: exit status 1

To Reproduce
Install Syncthing

Expected behavior
Add-on should start

Screenshots
If applicable, add screenshots to help explain your problem.

Runtime (please complete the following information):

• Hardware: RPi4
• OS: hassos
• Architecture: arm64
• Home assistant version: 2021.02.0
• Addon Version: 1.12.1

Additional context
N/A

Message metadata unavailable in intent_script

Describe the bug
I am using intents to trigger actions when receiving Signal messages. However, I have been unable to use any of the message metadata in these scripts. Looking through the code, it seems that several things are passed on, but I cannot seem to access these variables in my intent_script. I have tried doing so with the following syntax:

intent_script:
  Test:
    action:
      - service: script.signal_assistant
        data_template:
          sender: "{{ sender }}"

But sender remains empty.

Am I incorrect in assuming I can access these variables, am I doing something wrong, or is there a bug somewhere?

Use latest method to retrieve groups

From here: https://community.home-assistant.io/t/use-signal-messenger-for-notifications/80214/174?u=mbitard

Addon doesn't receive messages

The addon can send messages and it can be see in the log, however , it doesn't receive messages and there is nothing in the log indicating reception. The addon's log with configuration is below:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 

-----------------------------------------------------------
 Add-on: Signal
 Addon for wrapping signal inside docker
-----------------------------------------------------------
 Add-on version: 10.8.0
 You are running the latest version of this add-on.
parse error: Expected string key before ':' at line 1, column 4
[21:48:26] ERROR: Unknown HTTP error occured
 System:   (amd64 / intel-nuc)
 Home Assistant Core: 0.109.6
 Home Assistant Supervisor: 222
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2020-05-11 21:48:28 -0400] [301] [INFO] Starting gunicorn 20.0.4
[2020-05-11 21:48:28 -0400] [301] [INFO] Listening at: http://0.0.0.0:5000 (301)
[2020-05-11 21:48:28 -0400] [301] [INFO] Using worker: sync
[2020-05-11 21:48:28 -0400] [303] [INFO] Booting worker with pid: 303
2020-05-11 21:48:30,009 - root - INFO - Init
2020-05-11 21:48:30,028 - root - INFO - Process started and listening on 4a36bbd1-signal
2020-05-11 21:48:40,402 - root - INFO - Sending test3 to +XXXXXXXXXX, with attachment 
2020-05-11 21:48:40,875 - root - INFO - <subprocess.Popen object at 0XXXXXXXXXX>

Signal: Cannot send message to self

Describe the bug
Not sure if this is a bug or by design, but according to AsamK/signal-cli#397, signal-cli should support sending messages to itself. I've been trying to create a signal self-test automation in home assistant, which entails sending a signal message using the addon to the same number it was registered as. However the addon is not receiving messages sent from itself. I don't see any errors in the addon's logs. Wondering if anyone has tried this before.

To Reproduce
Steps to reproduce the behavior:

1. Add signal receipt using the same number the addon uses to send messages
2. Send test message to self

Expected behavior
Signal addon receives message sent from self

Actual behavior
Signal addon does not receive test message. No errors in logs.

Runtime (please complete the following information):

• Hardware: ODroid N2
• OS: HassOS
• Architecture: arm64
• Home assistant version: 2022.10.2
• Addon Version 10.20.1

Consider adding signalmessenger custom component to docker ignore

There shouldn't be a reason to include the custom component in the addon docker container.

I'd be happy to send a PR setting it up if you're interested.

Unable to execute "notify.signal"

I have successfully configured this addon to receive messages and reply to them based on the configuration of intent_script: and conversation: in configuration.yaml. I get a successful Hello there! back as expected.

However, I am unable to use notify.signal successfully to send a message. I am also unable to run signalmessenger.get_groups.

I get the following error when running notify.signal:

HTTPConnectionPool(host='4a36bbd1-signal', port=5000): Max retries exceeded with url: /message (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0xad892270>: Failed to establish a new connection: [Errno -3] Try again'))

And the following error when running signalmessenger.get_groups:

HTTPConnectionPool(host='4a36bbd1-signal', port=5000): Max retries exceeded with url: /group (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0xad7497b0>: Failed to establish a new connection: [Errno -3] Try again'))

Documentation unclear

Hi, I'm following the install docs, but they seem unclear to me. If you can help me out, I wouldn't mind submitting a PR to make the docs a bit easier to follow.

After copying the signal-cli config files to my home assistant installation, the readme tells me to: "After that, you can install the hassio signal addon".

How do I do this? I cannot find an official Signal addon in the addon store. I have tried adding your repository as a custom repository, but I get nothing to install when I do that. I also cannot install it with HACS.

How should I install the Signal addon?

Thanks!

Update to signal-cli 0.13.0 panic

First time using jre from https://docs.bell-sw.com/liberica-jdk/21.0.2b14/general/install-guide/#linux since oracle does not support their jre for armv7 and such anymore

The service crashes with failed to initiate panic, error 9

Sending a file

Hello, thanks for the nice plugin,

2 things,
For the documentation, can you add that the structure of the signal data should look like that in home assistant:
/config/.signal/data/+6655456
As I spend 2 days trying to debug the code, as I was Using this structure:
/config/.signal/+6655456

Then, When i try to send a file:
Service notify.signal

message : fdedez
data:
   file: /config/www/doors/cam_2021_2_22_12_53.jpg

I get this log:

2021-02-22 14:05:25,572 - root - INFO - Sending fdedez to +33******, with attachment /tmp/tmpxakuzwyc
2021-02-22 14:05:27,204 - root - DEBUG - <subprocess.Popen object at 0x7f8777c6***>
2021-02-22 14:05:29,403 - root - DEBUG - receiving new line "Envelope from: +33******  (device: 1)"
2021-02-22 14:05:29,404 - root - DEBUG - receiving new line "Timestamp: 1613999126464 (2021-02-22T13:05:26.464Z)"
2021-02-22 14:05:29,405 - root - DEBUG - receiving new line "Got receipt."
2021-02-22 14:05:29,405 - root - DEBUG - receiving new line ""

The file is sent, but the received file is tmpxakuzwyc, without any extension and as such, is not shown as an image on signal app.
Screenshot in PJ

If I try to rename it, The file can be seen as a picture

Thanks for your help

Signal: Add-on config * deprecated

Describe the bug
The following is shown in the supervisor logs in HassOS

21-02-13 17:19:15 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'startup' with 'before' is deprecated. Please report this to the maintainer of Signal
21-02-13 17:19:15 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'devices' use a deprecated format, the new format uses a list of paths only. Please report this to the maintainer of Signal
21-02-13 17:19:15 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'startup' with 'before' is deprecated. Please report this to the maintainer of Signal
21-02-13 17:19:15 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'devices' use a deprecated format, the new format uses a list of paths only. Please report this to the maintainer of Signal

signal snapshots are huge

By default, an hassio snapshot will save the full docker image.

https://developers.home-assistant.io/docs/en/hassio_addon_config.html

adding snapshot_exclude should do the trick

Thank's!

Thank you very much @MichaelBitard for this great work! (and sorry for polluting the issue tracker 😛)

API Error on Node Red

I created a bunch of notifications and automations within Node Red running as a Home Assistant addon as well. However all notification to the signal addon result in an API Error in Node Red.
The thing is, some will get through and be sent some won't. There is no way of telling which makes the notifications kinda unreliable at this point.
Running the latest HA possible also updated all plugins I have automated my dryer and washing machine to send me a signal message when they are finished. It worked once despite the API error but then without changing anything to Node Red or HA it stopped working and now is not working whatsoever. I can tell that the trigger arrived at the notify node based on the time it'll update on this part. But no message arrives in Signal.
Maybe it is related to the API error now, but it cannot be seen at this level nor can I see what is going on "behind the curtain".
If there is anything I can do or provide, I'd be happy to and just need to know what and how to do so.
Thanks!

Syncthing - Update to 1.20.1 and Addons stop working

Describe the bug
addons doesn't run at all.

To Reproduce
Steps to reproduce the behavior:
Install addons and start it.

Expected behavior
addons doesn't run at all.

Screenshots

Runtime (please complete the following information):

• Hardware: proxmox VM
• OS: hassos 8.1
• Architecture: x86
• Home assistant version: 2022.5.5
• Addon Version : 1.20.1

Cannot update signal add-on to 10.10.0 from home assistant

Hello,

I've been running into a persistent error trying to update the signal add-on from 10.9.3 to 10.10.0. This is what I get in the logs

20-11-21 04:38:16 INFO (SyncWorker_0) [supervisor.docker.interface] Updating image agileek/hassio-armv7-signal:10.9.3 to agileek/hassio-armv7-signal:10.10.0
20-11-21 04:38:16 INFO (SyncWorker_0) [supervisor.docker.interface] Downloading docker image agileek/hassio-armv7-signal with tag 10.10.0.
20-11-21 04:38:17 ERROR (SyncWorker_0) [supervisor.docker.interface] Can't install agileek/hassio-armv7-signal:10.10.0 -> 404 Client Error: Not Found ("manifest for agileek/hassio-armv7-signal:10.10.0 not found: manifest unknown: manifest unknown").
20-11-21 04:38:17 INFO (SyncWorker_0) [supervisor.docker.interface] This error is often caused by not having enough disk space available. Available space in /data is: 21.9 GiB

In the end it says it's often caused by not having enought disk space, but I have 21.9GiB available so I don't think that's the reason in this case. I'm running Home Assistant 0.118.2 on Home Assistant OS 4.17 on a Raspberry Pi 4.

Any help would be apprecaited!

For two days, error in HA

Log:

Error while checking account xxx: signal-cli version is too old for the Signal-Server, please update.

Thank you

No problem... Thank you for forking and keeping this up to date. As a new HA user but a long time Syncthing user, this is a benefit to me.

Signal: WS authentication error when sending messages to Home Assistant

Describe the bug
When I send messages to home assistant for intent script, I get "Something bad happened" as the reply. This is what I see in the logs:

2022-07-04 01:25:13,981 - root - INFO - message received {'sender': '+1**********', 'message': '***'} 2022-07-04 01:25:13,984 - root - INFO - Sending message to ws://supervisor/core/websocket 2022-07-04 01:25:14,087 - root - ERROR - could not authenticate with home assistant {'type': 'auth_invalid', 'message': 'Invalid access'} 2022-07-04 01:25:14,096 - root - INFO - Sending "Something bad happened" to +**********

Unrelated but I also see this warning:
WARN ManagerImpl - No profile name set. When sending a message it's recommended to set a profile name wit the updateProfile command. This may become mandatory in the future.

To Reproduce
Setup intent script and send any message to home assistant

Runtime (please complete the following information):

• Hardware: ODroid N2
• OS: HASS OS
• Architecture: arm64
• Home assistant version:
  Home Assistant Core 2022.6.7
  Home Assistant Supervisor 2022.05.3
  Home Assistant OS 8.2
• Addon Version: 10.19.3

Signal doesn't work anymore - status cod 499

Please update: AsamK/signal-cli#1022