To make changing the colour of a bulb easier.

A simpler name, typing gozwctl is a pain...

Also, the binary should be called gozwd, as it is a server and will be mainly run as a daemon.

Because if you already have the page loaded, and it looks like its connected, you expect a submit to do something.

Hi, I noticed some code related to associations that was commented out.
Do you plan to add support for associations and neighbors?

Thanks

When the enums are printed as strings they are preceded by their type, they shouldn't as it is normally clear what type they are.

The latest version of the library contains a lot of changes from v1.5 that this Go wrapper utilises. These changes contain updates thanks to the public release of the ZWave spec and numerous updates to the device database.

For godoc to show...

Add a file: goopenzwave_test.go

Add something(s) like this:

func Example_basic() {
    err := foo.Bar()
    if err != nil {
        panic(err)
    }
}

More info

First, thank you for this very interesting library. I'm trying to get it to work on Ubuntu 17.04 for a home automation project, but run into a build problem.

Following the instructions in the readme

1. git submodule update --init
2. cd open-zwave
3. PREFIX=$(pwd)/../.lib/ make install

Step 3 results in "install: cannot create directory ‘//usr/local/lib/x86_64-linux-gnu’: Permission denied"
This is because it is not run as root, I thought the use of PREFIX would install it locally. I realize this is an openzwave thing and maybe this is fine, if so, it would be nice to have a comment in the doc.

Ignoring that error for now, after installing gominozw running
go run gominozw.go there is a linking error:
"/usr/bin/ld: cannot find -lopenzwave"

Looking into gooopenzwave_linux.go the #cgo LDFLAGS contains the library "-L${SRCDIR}/.lib/lib -l openzwave", however the library folder created by openzwave's make install is called lib64 instead of lib.

Can you suggest the best way to solve this?
Thanks!

Check it out. Also, the ValueID is weird. Looks like a Group value...

Mostly for the OpenZWave method wrappers. Copy them from the OpenZWave docs.

Hi, thanks again for this library. It works well for my purposes and I'd love to share the MQTT binding if you're interested.

It looks like openzwave 1.6 is out and devices for 1.4 are no longer updated (https://github.com/OpenZWave/open-zwave/wiki/OpenZWave-1.6-Release-Notes). I tried it but ran into some errors like homeId being 0.

Do you have any plans on supporting 1.6?
Cheers
Henk

When an update to a node comes in from the server (after the initial scan) display a notification on the screen.

The current goopenzwave package is very cluttered and could probably benefit from pushing the various files into their own packages and then splitting the files appropriately.

To allow easy toggle of lights/switches/etc.

The C++ OpenZWave returns a bool in some cases to indicate success/failure. It is idiomatic in Go to return the error type to represent this.

Functions that return a bool to show success/failure should instead use error.

This repository used to live on GitLab, now it lives here on GitHub.

Rename all instances of gitlab.com/jimjibone/gozwave with github.com/jimjibone/goopenzwave.

Also look for any remaining gozwave strings and replace with goopenzwave.

Think I'll go for the MIT license.

The MIT License (MIT)

Copyright (c) 2015 James Reuss <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Fix it as the API has changed a lot recently.

As suggested in #21, switch to a system installation of OZW.

Original reason to bundle OZW as a submodule was to use a fixed version with goopenzwave, however this is not necessary as recent releases of OZW have shown to be backwards compatible.

Using an up-to-date system installation of OZW would be preferable as this library will benefit from the improvements and it can share configuration, etc. with other OZW based software such as the open-zwave-control-panel.