Thank you very much guys, after reading and reading the whole threat and among all of you I could make it work in HA in docker, it’s the first configuration I did with HomeAssistant and I am enjoying it a lot 
!!
3 Likes
For those interested, I think I’ll work on sending messages to groups, then add the capacity to send message to homeassistant via signal
3 Likes
Awesome! Is it christmas already? 
And I don’t know if it’s really possible - but hacs could be the missing link to automate the install further more (skipping the manual steps of copying the custom_component folder). But still registering the number and transferring the config files needs to be done somehow… so maybe it’s not the real thing… specially thinking that their is the signal hass.io addon already 
1 Like
IMHO hacs could simplify the setup, but it could be done after we setup a correct registration process. (I say ‘we’, because It’s not my priority right now and if somebody else is willing to do it, it could speed things up 
)
2 Likes
But then the signal hass.io addon would have a additional hacs component just to get the custom_component files in place? Maybe in the end that’s not to convenient. 
Maybe our employ of the month @frenck (congrats btw. for your new office 
) has the missing link how this would be possible to manage all inside the hass.io addon. And if he doesn’t, it’s not possible 
2 Likes
Sending to groups is available! See the README to know how to retrieve groupIds
2 Likes
Great to See that I missed 3(!) updates in a row! You doing a great job @mbitard ! Thank you for sharing it with the community!
Btw: Heads up for @frenck for giving a little advise/idea to pack all necessary files to get this hassio add-on running standalone!
1 Like
Just stumbled upon this. Great work!
Just like to point out another project (Disclaimer: I’m the author) for people who don’t like Java (like me)
https://morph027.gitlab.io/signal-web-gateway/installation/
which has an example section for home assistant:
https://morph027.gitlab.io/signal-web-gateway/usage/examples/hass/
2 Likes
That’s really cool, I may give this a go, looks like this will use less memory compared to running signal-cli
And another implementation arrived, this time a official one (ha 0.104) https://www.home-assistant.io/integrations/signal_messenger/
I will stay with @mbitard implementation now because I like the convinince as hassio add-on very much. I just wonder (didn’t updated yet to 0.104) if their is any interference with the custom_component now as they use the same name?
Maybe the hassii add-on could be even updated to use the (now) official upstream notify component?
1 Like
That’s a great news!
I’ll try to reach the developer of this official integration to see if I can help, maybe like you said using the hassio addon to simplify the setup
3 Likes
Does it work with hassio? Or is it for docker, external installations of home assistant?
Which one? The signal hassio addon from @mbitard works only with hassio 
For the other two ones (from @morph027 and the one from bbernhard you need to brew something yourself with docker I think)…
I’ll try to make the hassio addon compatible with the official integration.
2 Likes
You should be able to use both plugins, because on is signalmessenger and the other one is signal_messenger
2 Likes
I updated the hassio addon, but I’m not able to send messages yet. It seems the official integration still have some problems: https://github.com/home-assistant/home-assistant/issues/30838
2 Likes
@mbitard, Great add-on! Thank you so much for writing it!
When I try to create a hassio snapshot, the signal backup ends up being rather large:
tar -tvf 6ad2973f.tar
drwx------ root/root 0 2020-01-23 21:03:00 ./
-rw-r--r-- root/root 164192076 2020-01-23 21:02:59 ./4a36bbd1_signal.tar.gz
-rw-r--r-- root/root 145 2020-01-23 21:02:59 ./addons_local.tar.gz
-rw-r--r-- root/root 858 2020-01-23 20:56:30 ./core_check_config.tar.gz
-rw-r--r-- root/root 1130 2020-01-23 20:56:30 ./core_configurator.tar.gz
-rw-r--r-- root/root 6945 2020-01-23 20:56:30 ./core_ssh.tar.gz
-rw-r--r-- root/root 35411 2020-01-23 21:03:00 ./homeassistant.tar.gz
-rw-r--r-- root/root 138 2020-01-23 21:02:59 ./share.tar.gz
-rw-r--r-- root/root 1119 2020-01-23 21:03:00 ./snapshot.json
-rw-r--r-- root/root 3146 2020-01-23 21:02:59 ./ssl.tar.gz
Looking deeper into signal.tar.gz, it looks like it’s including many top-level directories:
tar --exclude='*/*' -tvf layer.tar
drwxrwxr-x 0/0 0 2020-01-23 20:41 etc/
drwxr-xr-x 0/0 0 2019-12-02 03:06 lib/
drwxr-xr-x 1000/1000 0 2020-01-23 20:42 libmatthew-java-0.8.1/
drwxr-xr-x 0/0 0 2020-01-23 20:41 run/
drwxrwxrwt 0/0 0 2020-01-23 20:42 tmp/
drwxr-xr-x 0/0 0 2020-01-23 20:40 usr/
drwxr-xr-x 0/0 0 2019-12-02 03:06 var/
Any ideas?
@waybeyond, It appears I need to add snapshot_exclude to the config.json and exclude all the not needed stuff.
I did not know about that, thanks!
I created an issue here to track that
1 Like
Excellent! Thank you! Again, great add-on