Issue fixes

Thanks to @hellracer, a few improvements have been made.
See issues #8, #9, #10, #12 and #13.

Rework of wake-up interval cache

In this release there has been a complete rework of the wake-up interval cache, as well as some other small fixes.
There was a problem in the code that when a device was added, the cache would update the wake-up interval to an inpossible state. The device would set the value to the maximal interval, but the cache still wants to update the value, therefore getting stuck in a loop.
This loop is no longer possible.

I feel like this rework is not worth a patch version, therefore I arrived at version 0.2.0. Yay.
There is loads to do still and this is just a hobby project, so things are moving quite slowly.
Any patches, issues or pull requests are welcome :-)

Latest OZW version and some more improvements

In this release, OZWSS works with the latest version of OZW.
The installation instructions have changed, so please have a look.
As always, open new issues if you have any problems.

JSON messages

New in this release:

• The server now sends JSON messages to the client in response to the (still customly formed) requests.
  You to install Jsoncpp for this to work (see install.md)
• I started working on authentication (another release will soon follow)
• Some minor bugfixes
• Update documentation

Wake-up Interval Cache

New in this release:

• Wake-up Interval cache to set the wake-up interval to the proper value, when a new battery is inserted.
• A new version of Polymer is released, so a few minor fixes for that
• Small changes in the Makefile (make clean also cleans out the open-zwave build dir and the final binary is called openzwave-server instead of test)
• Removed a lot of old code and comments for that and also updated the comments for some functions
• Switch now broadcasts and update to multiple clients

64 bit support

There was a problem when in the creation of threads on 64 bit machines.
Thanks to Frank, this build should work on 64 bit.

Scene init fix

I messed up again.
In the previous release, I removed the if statement such that it would not fail on startup if no scenes were set.
This also removed retrieving the list of scenes from open-zwave.
In this release, the scenes initialize properly again.

This release also supports binary switches (got myself a christmas present)

Scene init fix

Upon first start, the no scenes were created yet.
I copied the scene initialisation from another part, but I forgot to remove some code.
This latest release should fix some more things.

v0.1.1 Hotfix

messed up this check
all valueID's that changed were calling the getvalueasfloat function.
In the latest OZW release this causes exceptions.

Initial release

This is the first release of the Open-Zwave-Socket-Server.
The server is pretty stable, but if you still have any issues, please create an issue.
A client is included based on Polymer web components.
I'm planning on including more features in future releases.

Please note that the PHP client is not updated anymore.
The websocket client was used to test the websocket, which is now included in Polymer.
The websocket client will still work, but lacks the features that the Polymer client provides.

If anyone is interested in updating the older clients, feel free to do so.
A pull request is welcome.

Hope you like this project.