Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - domoticz-git

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: domoticz-git r5051-1

Git Clone URL: https://aur-dev.archlinux.org/domoticz-git.git (read-only)
Package Base: domoticz-git
Description: Web based home automation
Upstream URL: http://www.domoticz.com
Keywords: domoticz openzwave
Licenses: GPL
Conflicts: domoticz-svn
Submitter: IanDury
Maintainer: IanDury (melvinvermeeren)
Last Packager: IanDury
Votes: 5
Popularity: 0.002232
First Submitted: 2015-08-23 18:43
Last Updated: 2016-04-11 20:08

Latest Comments

1 2 3 4 5 Next › Last »

IanDury commented on 2017-02-03 20:47

@fxeon It looks like the upstream open-zwave needs to update the openzwave.spec file. The Changelog shows version 1.5 whereas the spec file still has version 1.4

fxeon commented on 2017-02-02 17:50

@IanDury hello why is openzwave reported as:
Version: 1.4-2382-g450c4a50-dirty
in domoticz-git, when to my understanding current openzwave is 1.5-1? thx for the great work

ImNtReal commented on 2016-10-02 22:52

@IanDury, maybe, but it builds, and runs fine against stable. It would be nice to give the user the choice since depending on openzwave would allow it to build against openzwave or openzwave-git since openzwave-git provides openzwave.

IanDury commented on 2016-10-02 20:01

@lmNtReal - It is my understanding that the latest beta of Domoticz (domoticz-git) should be build with the latest beta of OpenZWave (openzwave-git) and not with the stable version (openzwave).

ImNtReal commented on 2016-08-31 01:21

Can this depend on openzwave instead of openzwave-git, since openzwave-git provides openzwave? That way we can decide which we'd prefer to run.

IanDury commented on 2016-06-26 08:17

I prefer using nginx as I'm having multiple web servers running on my target:

That's why I did not add the option -sslwww 443 in the domoticz package. I've changed my local domoticz.service and use -sslwww 0 to avoid the following startup error messages:

Error: WebServer(SSL) startup failed on address with port: 443: use_certificate_chain_file: No such file or directory
Error: WebServer(SSL) check privileges for opening ports below 1024

fxeon commented on 2016-06-24 20:58

Edit: Solved generating a certificate with reference to these pages:

Hi, i modified domoticz service like this a while ago:

Description=Domoticz Daemon

ExecStart=/opt/domoticz/domoticz -www 8080 -sslwww 443 -daemon


it used to work ok now i can't access my domoticz with ssl, current version is Domoticz V3.5269.
Is it an upstream problem or did i miss something?

IanDury commented on 2016-04-11 20:11

Thanks trishika. PKGBUILD updated as you suggested.

trishika commented on 2016-04-11 13:57

The sed about openzwave is not needed anymore.
Just add the option -DUSE_STATIC_OPENZWAVE=NO to the cmake line.

pschmitt commented on 2016-03-02 13:28

Yeah turns out this requires wiringPi to be statically linked. The wiringPi lib from the alarm/ repo is dynamically linked.

To fix it one needs to remove the alarm/wiringPi package and install wiringPi by hand:

make static
sudo make install-static

Ref: https://www.domoticz.com/forum/viewtopic.php?t=7678