Page 1 of 1

General terminology

Posted: 28 Sep 2015 12:22
by burnersk
I own a Razberry and using the included Z-Way web interface. It was nice in the first place but when it comes to complexe scenes or rules the complete system fails (e.g. not smooth transitions).

I would like to create a Perl software that binds to the /dev/ttyAMA0 and does the job in the way I want it.

Before starting with the project I would like to clarify the terminology.

The socket /dev/ttyAMA0 represents the communication endpoint as known as the Z-Wave Serial API, right?

The webservice the Z-Way web interface is providing is known as the Z-Way JavaScript API and Z-Wave API (not serial), right?

The system behind the socket /dev/ttyAMA0 (in direction to the RaZberry) is the API which is under the NDA, right?

As far as I understand and when my assumptions are correct, the Z-Wave Serial API (the socket) is "free and open" and not under the NDA. So I can implement against the socket, right?

Re: General terminology

Posted: 02 Oct 2015 20:51
by pofs
NOTE: For some reason this post has replaced a post by pofs. I don't understand how this happened. Sincere apologies
burnersk wrote:4) Use some other software, like OpenZWave-based things, OpenRemote, etc.
OpenRemote has been wrestling with Z-Wave since 2012, and still far from complete as far as I can judge from public documents. So the task is definitely not trivial as pofs stated.... Better spend your time on adding smartness to these devices.