-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Enable OH to communicate with signal messenger #10913
Comments
Hi @DerOetzi!
That's unfortunately indeed a problem as the (A)GPL is not compatible with the EPL. This means that the code of such an add-on would need to be released under (A)GPL as well. As a result, we couldn't include it in the openhab-addons repo, nor include it in the official distro.
I share the same problem - would love to do it, but I doubt to find the time for it anytime soon. So let's hope we find somebody who wants to give it a try! |
Maybe one option would be if someone can help me do get my extended container image updated to new structure of the official Dockerimage and we can extend the readme howto use signal-cli with different rules. |
@kaikreuzer there is a rest Service wrap arround the Signal-Cli available in docker hub . Would it be an Option to Release an Action add-on for this? |
There's a Marketplace add-on nowadays: https://community.openhab.org/t/signal-binding/138795 Maybe @dalgwen also wants to contribute the code to this repo? |
Hello, Thanks wborn for the ping. I made the marketplace signal binding. Some licenses thought before : In the first draft of the binding, I used some custom code with the official libsignal client to send and receive message. I had many issues with this, as the signal API is extremely hard to understand, and as the signal server continuously shifted with new versions, breaking compatibility. I wasn't aware of the license issue, I'm a little bit disappointed as I was hoping to make a pull request in several weeks/months. Next, about the nature of the integration. By making this addon, I had one thing in mind : avoiding the installation of any other third party software. So the integration with a signal-cli process running somewhere else is not my main goal. But I'm not opposed to it, as it will fullfill some use case and could help some users with compatibility issue. |
Signal messenger is now one of the most popular messengers beside WhatsApp, Threema, Telegramm, which is Open Source.
It would be nice to add a binding for the possibility to send and receive messages by signal.
I'm running a extended docker image for a few years which uses signal-cli to give a option via exec binding. But this project is stucked now because of new travis license model. That is why I thought now, maybe it would be possible to integrate as a action binding.
There is a java library(https://github.com/signalapp/libsignal-client) but I'm not sure about the AGPL-license is compatible to use it inside OH, maybe @kaikreuzer can give us a hint? And the second problem is I don't have the time to do the binding by myself but I hope there is someone in the community who is although interested in doing this. I can give support with use cases and testing.
The text was updated successfully, but these errors were encountered: