Running OpenZwave on Your Cubieboard
Before running off to play in the unknown (to me) land of the Cubie, I figured it would be a good idea to try out OpenZwave, my Aeon Lab Z-stick and the OpenZwave Socket servers. So far the Cubieboard is running well with the last compiled version of OpenZwave with Conrad’s Lights Control, OpenZwave Control Panel and my Basic Zwave web interface. All of the applications run at about the same speed as they do on the Raspberry Pis.
My CubieBoard Setup:
- Cubieboard 1gb RAM version 2012-09-09
- This Debian Wheezy image with the device specific bootloader. (This is a very clean minimal install that is headless only. You MUST ssh into the Cubieboard.)
- A 8gb microSD card that came out of a HTC Evo Phone. The card is slow.
- Aeon Labs Z-stick 2
OpenZwave Info and Starting the Socket Server
The image below contains exactly the same version of the OpenZwave library, clients and servers as the last Raspberry Pi image. The host name has changed to cubie-openzwave (cubie-openzwave.local on bonjour). DHCP is enabled by default and the host name is set to broadcast and announce services on Avahi. The image contains three applications for playing with Zwave: OpenZwave Control Panel, Lights Control and Basic. Lights Control and Basic run with nginx with PHP, curl, APC, and sqlite. The OpenZwave Control Panel uses libmicrohttpd and magic. Start up instructions will come up as the ‘message/motto of the day’ when you ssh into your Cubieboard. You can also see the instructions on this Rasberry Pi OpenZwave post. Only one OpenZwave application can run at one time – so make sure to run killOZW before switching between Basic and Lights Control. I tested with a multilevel switch, binary switch and a thermostat.
The username is ‘root’ and the password is ‘password’. Type ‘passwd’ to change it.
Download: cubie-openzwave-2013-05-09-4gb.img.7z (240ish mb)
Notes: I used 7zip on Mint and had some issues writing the image on Windows. The image worked correctly on Debian and Mint. Please let me know if you have any issues.
If moving the files to your own Linux image – I had problems with the ‘basic-server’ not finding the dynamically linked libraries. It would give me an error saying that no file or directory existed by the name basic-server (file was there with correct permissions). The command ‘ldd’ would spit out an error that it was “not a dynamic executable”. To fix the problem, I had to copy ld-linux.so.3 to its old location of ‘/lib/’ (yeah, I guess I could have recompiled – always a time crunch) from its new location ‘/lib/arm-linux-gnueabihf/’. The command is ‘cp /lib/arm-linux-gnueabihf/ld-linux.so.3 /lib’. From the information I gathered in a couple of minutes of research, this runtime linker location was a big deal last August and probably impacts a lot of other programs running on Debian and Ubuntu.