ZWay: notification on event (continued)

After getting your hand on a Z-Wave data holder in the ZWay library, the next step is to register a listener for getting notified when a change occurs on this data.
The ZWay library provides the following methods for managing data holder listeners:

  • zway_data_add_callback()
  • zway_data_remove_callback()
  • zway_data_add_callback_ex()
  • zway_data_remove_callback_ex()

 zway_data_acquire_lock(aZWay);
 ZDataHolder dataHolder = zway_find_device_instance_cc_data(aZWay, 2, 0, COMMAND_CLASS_SENSOR_BINARY, "level");
 if (dataHolder != NULL) {
  zway_data_add_callback_ex(aZWay, dataHolder, &dataChangeCallback, TRUE, this);
 } else {
  cerr << "No data holder for deviceId=" << (int) mDeviceId << endl;
 }
 zway_data_release_lock(aZWay);

The following code will register the following "dataChangeCallback" function in the ZWay stack and make sure it is invoked when the Z-Wave binary sensor with node ID 2 gets triggered. 


void dataChangeCallback(ZWay aZWay, ZWDataChangeType aType, ZDataHolder aData, void * apArg) {
 bool level;
 ZWBOOL value;
 zway_data_get_boolean(aZWay, aData, &value);
 switch (value) {
 case 0:
  level = false;
  break;
 case 1:
  level = true;
  break;     
 default:
  cerr << "Invalid value for level: " << value << endl;
  return;
 }
[...]

Comments

  1. Unknown27 April 2014 at 12:30

    Hello, I've just compiled the z-way-test sample downloaded from z-wave.me and I'm still facing an issue with dataHolder whixh always return 0. Same with your examples.
    Are you able to share a whole main.c content file in order to give me the opportunity to test a well-running code ?

    Thanks
    Gilles

    ReplyDelete
  2. Vincent27 April 2014 at 20:09

    Hi,
    I will see what I can do... These days when I got time and motivation, I work more on the Ruby side than on the C++ side :-)
    And the C++ code is not in a state I can share, split between my library/application code is still ugly.

    ReplyDelete
  3. Unknown28 April 2014 at 08:37

    Hi,

    thanks for your reply. Eventually, I succeed to move on, thanks to one of your last update, the one explaining that "level" value is now obtained with "1.level".

    Have you got some more detailled documentation regarding the C API from z-wave.me ? ...I'm very frustrating by the lake of comments and Doc.

    My next step is to try moving to C# with mono.

    Good luke with Ruby :-)

    ReplyDelete
  4. Vincent28 April 2014 at 08:56

    The only documentation for the C API I am aware of is the set of header files.
    :-( Not much but well, enough to start with.

    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

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/li
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