It is about the avmfritz binding. I have configured through the addons.cfg file. The point where I am hanging is: In the addon.cfg file I only give the name of the binding and not its location:
# A comma-separated list of bindings to install (e.g. "sonos,knx,zwave")
binding = avmfritz,km1001,weather1,weatherunderground,zwave
How do I tell OH2 not to use the binding coming with the distribution but to use instead the one given in the addons folder?
EDIT: My addons folder is normally empty. Actually I do not know where OH2 gets the addons from as I thought they should be there Anyway ā¦ I assume that I would put the new beta version of the binding into the addons folder and now I need to understand how to tell OH2 to use this instead off the official one.
Or can it be that the beta version has a different name???
Hello all,
I would like to get some advice. I run openHAB on RPi2, and a second on a Banana Pro on an SSD drive. I only recently i came across docker and started to familiarize me with it.
I have a two questions. Using the tutorial in this tread i was able to get openhab running in a container with the config, addons and log files on the host file system. That works perfectly. Rich, thank you very much for this tutorial!
But my environment consists of Z-Wave and Sonoff devices.
My first question regards the z-wave config in a docker container. I use a Aeon Gen5 USB z-wave stick. Does anyone know if the USB/ttyACM0 device on the host will be available in the docker container? (I have not tried it yet, because i have only one stick and that is in useā¦)
My second question regards the use on mqtt (for Sonoff). The via this tut installed openHAB does not includes eg mosquitto.
Is it possible to add mosquitto to the openHAB container, either by installing it by hand in the openhab container and then save this as a new container? Or make use of docker-compose file and make a new container including the missing parts?
Or is it better to make a separate container for mosquitto (and for InfluxDb and for Grafana)? According to the docker directions one should create a separate container for every process that one uses.
But for me, it would be nice when i can backup one container with everything i use in openhab, this including InfluxDb, Grafana and mosquitto.
I am looking forward to your suggestions.
Btw, which containers for these products do you use for openhab? On the hub.docker.com i find multiple containersā¦
You have to make it available. --device=/dev/ttyUSB0 as an argument to docker run will make that device available in the container. See the command in āRunning the container as a serviceā in the OP.
This is counter to the purpose of Docker and considered a very bad practice. Each service should have its own container.
However, if you want to get into the business of building your own Docker images, there is nothing stopping you from creating such an image yourself.
You CAN write a docker-compose file that starts OH and Mosquitto in two separate containers which is not only supported but the expected way one would use docker-compose. I donāt use docker-compose so canāt help with the specifics. But docker-compose is used to start up and manage one or more docker containers, not build new Docker images.
This.
You should not be backing up containers. You should mount volumes into your container to keep the data that needs to be backed up and/or persisted. Containers are ephemeral. They are designed to be replacable and you need to treat all the files inside the container as temporary. Anything that needs to stick around even when a new container is created needs to be saves in a mounted volume. This is why you must mount your conf and userdata folder into the container. Otherwise there would be no way to upgrade the container because upgrading the image means changing the image and creating a new containerā¦
I always use the official images. So for Mosquitto I use eclipsesā image. For InfluxDB I use InfluxDBās image. For Grafana I use Grafanaās image. There is only one image I build myself (Calibre) and that is because there isnāt an official image and the existing images either didnāt work for me or worked in ways I didnāt like.
Hi Rich, Thank you for answering my questions.
I will forget about my idea to combine multiple services in one container. I have the eclipse-mosquitto now running as a separate container next to the openhab container.
Bert
Currently planing my installation. I prefer docker, but I am not sure if everything will work.
I would for example like to shutdown my PC with Openhab. In another post they said that you need to install samba to do that. But in docker container there is no samba.
I just donāt want to limit myself. So this is a hard decision.
Any help? What wonāt work with official docker container?
This makes no sense at all. Can you point me to that post?
Samba has nothing to do with oneās ability to shutdown the PC.
However, the whole point of a Docker Container is to isolate the container from the host machine. I would be shocked if you can call shutdown or reboot the host from inside the container. That would break the whole reason containers exist.
Just tried it. It wonāt work. The shutdown and reboot commands cannot talk to the init daemon from inside the container. And Iād still argue that even if you could, you shouldnāt.
Iād also question the wisdom for OH to directly reboot the machine it is running on directly, but lots of people do it.
Generally, you will have to run as root and use host networking to use Network bindingās DHCP listen. You cannot use arping or system pings from the Network bindings, though there is an open issue to add that which I hope to work on this weekend. The exec binding and executeCommandLine will be pretty useless to you as there isnāt much installed in the Docker Image, is it should be, you want Containers to have as little installed as feasible. Iām sure there are other things that cannot be used as well.
However, given the nature of the question, Iām going to guess you donāt know much about Linux yet. Given that Iām going to strongly recommend using openHABian. You donāt have to be running on a RPi to use it. See the Manual Installation instructions.
I think there was a misunderstanding, I donāt want to restart the serverā¦ I want to restart my PC.
And the explanation why samba was required is because then you have an rpc package installed.
Hello,
I am trying to move from a KVM VM to a docker container. The last feature missing is sending mails, apart from that everything works ok.
In addition to the openhab container packages I needed to install mysql-client.
On the VM I installed postfix and used localhost in the openhab mail config as I remember I had troubles there as well.
When I use my mail server directly (self signed certificate) I get:
17:46:50.807 [ERROR] [org.openhab.action.mail.internal.Mail] - Could not send e-mail to āā¦@ā¦ā.
org.apache.commons.mail.EmailException: Sending the email to the following server failed 192.168.xx.xx:25
.
.
.
Caused by: javax.mail.MessagingException: Could not convert socket to TLS
.
.
.
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
If you are using a self-signed cert you must add your CA to the JVM running inside the container. Java maintains its own collection of trusted CAs and will not trust your self-signed cert until you add your CA to the list.
I donāt know how to do this with Zulu which Iām pretty sure is the Java that comes in the docker image.
I solved it by building a customised image with https://github.com/openhab/openhab-docker as a starting point.
I added postfix and bsd-mailx into print_basepackages() of the update.sh script.
The postfix config was changed, the hostname in mail.cfg points to localhost and that the docker container was restarted. This is the same setup as on the VM before.
A few questions came up:
how to put the custom postfix config already into the docker image during built? This would avoid changing
/etc/postfix/main.cf on the running container and restart it after a fresh build
Connecting to knxd works with the -net=host option but not with --publish 3671:3671
If multiple instances of openhab might run I guess the publish option is needed
I needed to add āservice postfix startā to entrypoint_debian.sh, is that the recommended way?
You would have to add it to the Dockerfile to copy the config into the image during the build.
Alternatively, you can and probably should just mount your custom file as a volume. You can mount single files in addition to folders using the --volume flag.
I donāt know anything about KNX so I canāt answer about that. But I can say that OH is not really designed to have multiple instances running on the same machine at the same time. And there are a bunch of other ports that would need to be moved around to make it work. Finally, if port 3671 is for the knxd then publishing that port on the Docker container is backwards. The container needs to be able to access that port, not accept connections on that port. What might be the problem is when you run without --net=host that your container has a different IP address from your host machine so you may need to use the IP address of your host if you are using localhost in the binding config.
Well, the proper way would be to run postfix in a separate container and connect your containers with a custom network configuration. Containers are really intended to only run one service at a time. That is one of the distinctions between containers and VMs. I know it is possible to run multiple services inside a container but I donāt know how that is done. Iād say to try it and see what happens.
Anyway ā¦ I assume that I would put the new beta version of the binding into the addons folder and now I need to understand how to tell OH2 to use this instead off the official one.