-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation unclear #53
Comments
Never mind, it just took a really long time for your addon to show up after adding the custom repo! |
That's strange that it took a really long time, usually it's almost instant... |
For me the installation is unclear too. I am running Home Assistant on an RPi3 and I did a manual installation using a Python virtual environment. Due to that it seems that I do not have the usual "Addon-store" in the settings. I also do not have docker running. I managed to install some integrations using HACS. |
I'm sorry I don't really understand your message, it's a little unclear too
(notice the irony ;)).
I don't think python is involved here, you have 3 steps to do:
- make signal-cli working (and it seems you did that)
- install the custom component (or use the official signal integration)
- install the hassio Addon (with the signal-cli folder copied at the right
location)
Le ven. 3 févr. 2023 à 19:09, Lothar ***@***.***> a écrit :
… For me the installation is unclear too. I am running Home Assistant on an
RPi3 and I did a manual installation using a Python virtual environment.
Due to that it seems that I do not have the usual "Addon-store" in the
settings. I also do not have docker running. I managed to install some
integrations using HACS.
I also have a working signal-cli available. With this, I am able to send
messages via the command line.
How do I have to proceed in order to install this Signal addon so that I
can use "notify.signal" in my automations?
—
Reply to this email directly, view it on GitHub
<#53 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADFHMRCR2YAF4YI6IKJBETWVVCWHANCNFSM6AAAAAATFU4UAI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
To be honest, I am new at homeassistant - so maybe I am not asking the right questions - sorry for that. |
Thanks, I think I understand better. From the documentation:
I think you should stick to the "official Home Assistant Operating System" installation so you would be able to have hacs addons, updates and stuff which will make your home assistant experience a lot better. But if you cannot do that, then you can look at what this file does : https://github.com/agileek/hassio-addons/blob/master/signal/Dockerfile and replicate it on your system, that way you may be able to have the equivalent of this addon running outside of docker. I'm sorry I won't be able to help you further though, that's why we use hacs, so we have a "standard" way of doing this through docker to prevent having to have to debug every user setup ;) |
Now I have HACS installed and running. How do I install this repository via HACS? When I try to install it as a custom component (providing the url of this repo) I get the error message |
HACS is only here to help you install my python plugin, which I think you do not really need. What you have to do is install the docker addon, the one that allows communication between the home assistant official signal integration (or my custom_component) and the signal-cli written in java. |
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!
The text was updated successfully, but these errors were encountered: