In a previous post I showed how I installed domoticz in a docker container using the documentation on the WIKI.
Since I now need to start using domoticz for ‘real’ (since the razberry daughterboard on my ‘production’ PI seems to have died on me) I wanted to update the container with the latest version. Although I no longer have to do the two part install (see my previous post) I searched for an alternative which would be simpler to use and also up-to-date. That is when I came across the linux server.io site which also has a domoticz image available. I tried to install that and it all seems a lot simpler than the one from Joshuacox. Well at least for a domoticz/docker beginner like me!
Since I am using docker on a Raspberry PI3 I needed the ARM version of the domoticz image which can be found here.
As I mentioned in my previous post I already have a mount to my NAS in which I want to store my domoticz data. The mount on the PI is
After removing the old domoticz container and images and cleaning up the mapped config folder on the NAS, I then installed the new domoticz instance.
sudo docker run --name=domoticz \ --restart unless-stopped \ -d \ -t \ -p 1443:1443 \ -p 6144:6144 \ -p 8080:8080 \ -v /home/pi/dockerdata/domoticz:/config \ -e TZ=Europe/Amsterdam \ --device=/dev/ttyUSB0 \ lsioarmhf/domoticz
I no longer use the –privileged flag now because it’s more secure. Mapping the USB device seems to work just as fine.
After starting the container I checked the running domoticz instance on
Unfortunately domoticz seemed not to be running. After inspecting the container logs, it turned out that an SSL key was generated for domoticz so it could be accessed using SSL. However, generating such a key on a Raspberry PI 3 takes quite a long time (in my case it took about 30-45 minutes!).
After I drank a nice cup of tea, and such…, domoticz was finally up.
So I now can start to reset all my ZWave nodes (since they can’t be removed from a dead ZWave controller) and include the in my new ZWave ‘production’ environment.