Installing Domoticz with OpenZWave 1.4+ on Raspberry Pi

For our last hackathon @ Luminis Rotterdam, we wanted to experiment with Z-Wave, raspberry Pi’s and some IOT stuff.
So we bought some nice z-wave sensors from Fibaro, a Danalock v2 z-wave doorlock and a
Z-Wave Razberry-Pi GPIO Daughter Card.

Because there were some problems with the openzwave – danalock combination, we decided to “Use the Source Luke” and compile domoticz and openzwave ourselfs on the pi. We’re running Raspian 8 Jessie.

Install z-wave / z-way server

wget -q -O – razberry.z-wave.me/install | sudo bash
— This will disable bluetooth automatically for raspberrypi3 (!)

Install some stuff we need later

$sudo apt-get install build-essential -y
$sudo apt-get install cmake libboost-dev libboost-thread-dev libboost-system-dev libsqlite3-dev subversion curl libcurl4-openssl-dev libusb-dev zlib1g-dev libssl-dev git
$sudo apt-get install libudev-dev

Build the latest OpenZwave lib

git clone https://github.com/OpenZWave/open-zwave.git
-- symbolic link needed so domoticz build can find the openzwave lib:
ln -s open-zwave open-zwave-read-only
cd open-zwave
make
sudo make install
cd ..

check
/usr/local/bin/MinOZW /dev/ttyAMA0

Build Domoticz

git clone https://github.com/domoticz/domoticz.git domoticz-source
cd domoticz-source
-- cmake -DCMAKE_BUILD_TYPE=Release -DBOOST_LIBRARYDIR=/usr/lib/x86_64-linux-gnu -DBoost_USE_MULTITHREADED=OFF .
-- cmake -DCMAKE_BUILD_TYPE=Release .
cmake -USE_STATIC_OPENZWAVE -DCMAKE_BUILD_TYPE=Release CMakeLists.txt
-- check that your output contains something like :
-- LIBUSB found at: /usr/lib/arm-linux-gnueabihf/libusb.so
-- /home/pi/domoticz/open-zwave-read-only/libopenzwave.a
make -j3
-- grab some coffee, in fact go to lunch,diner and than grab another coffee.

Then, finally, start the beast

./domoticz

Domoticz razzberry OpenZwave 1.5
Yes! we got a > 1.4 version of OpenZwave !

Note: for Raspberry Pi3 i also need to do:

  • enlarge your swap ,
  • raspi-config
    Enable Serial (this makes  ttyAMA0 available as serial device)
  • edit /boot/cmdline.txt: remove console=serial0,115200.
    Change :
    dwc_otg.lpm_enable=0 console=tty1 console=serial0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
    to
    dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
  • power off (not just reboot)

Used resources:

JBoss Fuse 6.3.0 is out!

Today, 10 months after the 6.2.1 release, JBoss Fuse 6.3.0 came out!
With a whopping 962 issues (bugs,enhancements,feature requests, etc) fixed. You can download a copy here.
For those who don’t know yet, JBoss Fuse is integration middleware software by RedHat.

jboss fuse 6.3 issue tracker
Almost done ….

Some highlights:

  • Camel is upgraded from 2.15.2 to 2.17. Besides a lot of bug & security fixes, dependency updates and what more, this also adds some very nice new components:
  • a very welcome bug fix for a pesky problem we had in our JBoss Fuse 6.2.0 install and submitted to RedHat.
    (“After restart of instance: No component found with scheme: amq”)
  • Apache CXF 3.1
  • Jetty 9
  • And some API updates:
    • JMS 2.0
    • Servlet 3.1

Use the migration guide to upgrade. Happy fuse’ing!

 

BTW JBoss Fuse 6.2.1 was released december 7th, 2015 (and contained camel 2.15.2) and 6.2.0 was released june, 23th, 2015 (and contained camel 2.15.1)