Oops, where did I go...?

Finally, since last time, I jumped back to the Java world. A little world called "Android" caught me, with the idea of developing this little UI widget I miss so much on my HTC Legend smartphone. Since at work I also have to switch projects and join a "fun/demo" project linked to the Android platform, I though this was a good idea to do the same in my home evening hours.
So, no more C++ for the moment, but I am sure I will soon find a good reason to install and try out the native SDK; there are probably some stuff to be done there.
In the meantime, let's try to get this widget out!

Comments

Post a Comment

Popular posts from this blog

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

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

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 dataChangeCallba...
Read more