First steps with the ZWay library

The Z-Wave "RaZberry" installation comes with everything needed to be able to do some custom development in C; everything is installed in the /opt/z-way-server directory.
There, one can find:
  • A set of (documented, nice!) C header files found in /opt/z-way-server/libzway-dev:
    • CommandClassesPublic.h
    • FunctionClassesPublic.h
    • ZDataPublic.h
    • ZDefsPublic.h
    • ZErrors.h
    • ZPlatform.h
    • ZWayLib.h
  • A set of libraries found in /opt/z-way-server/libs:
    • libmicrohttpd.so
    • libv8.so
    • libzwayhttp.so
    • libzwayjs.so
    • libzway.so
For the ZWay stack to run properly, it is needed to provide the necessary configuration files. Instead of using these directly from the installation folder, I made a copy in order not to mess up too much with my working/configured setup. The following directories from the ZWay installation folder are needed:
  • config
  • translations
  • ZDDX
For experimenting I made a small Makefile in order to build and run.
 main.out: main.c  
     gcc -I/opt/z-way-server/libzway-dev -L/opt/z-way-server/libs -L/lib/arm-linux-gnueabihf -L/usr/lib/arm-linux-gnueabihf -lzway -lxml2 -lpthread -lcrypto -o main.out main.c  
   
 clean:  
     rm -f main.out  
   
 run:  main.out  
     export LD_LIBRARY_PATH=/opt/z-way-server/libs && ./main.out

Now it is time to start experimenting...

Comments

  1. Endre Stølsvik7 September 2013 at 17:46

    How has this worked out? Have you made any source code you want to share, github?

    Have you checked out OpenRemote?
    http://www.openremote.org/display/docs/OpenRemote+2.0+How+To+-+Z-Wave+with+Razberry

    ReplyDelete
  2. Vincent10 September 2013 at 18:48

    This worked well so far, my "prototype" is moving further, just lacking time :) No there is not yet source code available, but I guess after I get to something decent to share, I will.

    About OpenRemote, I saw the announcement on the Razberry pages but I did not look into the details as it was based on the HTTP/JScript APIs of ZWay.

    ReplyDelete
  3. Zone24 October 2013 at 17:02

    Hey Vincent,
    I tried to build my file like you showed in top. But my compiler cannot find -lxml2. When I try to install lxml2 with apt-get install, it is said that the package lxml2 is unable to locate
    What can I do?

    ReplyDelete
  4. Vincent24 October 2013 at 17:07

    The package you miss is normally "libxml2".
    "-l" is a "shortcut" for "lib"

    ReplyDelete
  5. Zone24 October 2013 at 17:13

    Yeah I know. "libxml2" is already installed, when I install "xm21" it still isn't working

    ReplyDelete
  6. Vincent24 October 2013 at 17:25

    /usr/lib/arm-linux-gnueabihf/libxml2.so.2 should be installed; you probably only miss the symbolic links to it e.g.
    lrwxrwxrwx 1 root root 12 Mar 16 2013 libxml2.so -> libxml2.so.2
    lrwxrwxrwx 1 root root 16 Mar 9 2013 libxml2.so.2 -> libxml2.so.2.8.0
    -rw-r--r-- 1 root root 1196108 Mar 9 2013 libxml2.so.2.8.0

    ReplyDelete
  7. Zone24 October 2013 at 18:29

    How can I fix the problem?

    ReplyDelete

Post a Comment

Popular posts from this blog

ZWay: getting the device list.

Back after a while... and a son! Here is a piece of code that can be used with the latest version of the ZWay library. It makes it possible to retrieve the Z-Wave device list and display the device names and associated XML file (each recognized device can be associated to an XML that contains a bunch of meta-data: name, description etc.). int main(int argc, char ** argv) { ZWay theZWay; ZWError result; memset(&theZWay, 0, sizeof(theZWay)); result = zway_init(&theZWay, "/dev/ttyAMA0", "/home/pi/src/razberry-proxy/config", "/home/pi/src/razberry-proxy/translations", "/home/pi/src/razberry-proxy/ZDDX", stdout, Warning); if (result == NoError) { result = zway_start(theZWay, &terminationCb); if (result == NoError) { printf("Discovering...\n"); result = zway_discover(theZW
Read more

Libcurl: perform a REST HTTP PUT

The libcurl library does not provide a clear example on how to issue HTTP PUT operations in a REST context; the examples are mainly about file transfers . For my proxy application this is not really what I need: I want to perform a REST HTTP PUT, keep it simple, meaning without using the "Expect" and "Transfer-Encoding" that libcurl adds by default. After some struggling I discovered that this behavior can be changed by using the following code: CURL * pCurl; struct curl_slist *headers = NULL; headers = curl_slist_append(headers, "Content-Type: application/json "); headers = curl_slist_append(headers, "Content-Length: 12345 "); headers = curl_slist_append(headers, "Expect:"); headers = curl_slist_append(headers, "Transfer-Encoding:"); pCurl = curl_easy_init(); curl_easy_setopt(pCurl, CURLOPT_VERBOSE, 1); curl_easy_setopt(pCurl, CURLOPT_PUT, 1); curl_easy_setopt(pCurl, CURLOPT_URL, " https://your-server.app
Read more