The above comment encapsulates the core of the issues. You say you chose the wrong model but I ask why on earth were you asked to choose a model in the first place? You shouldn’t be asked to choose a make, a model or any such thing. The core of the ZWave protocol means that when the embedded ZWave chip in the Vera includes a new device, the muanufacturer code, the make and model of the specific device that has been added becomes available to the Vera software. These codes are unambiguous and unique to the device. Vera should therefore know exactly what device has been added, who made it, and exactly what capabilities it has. Its right there in the protocol and always has been. A couple of dozen lines of code is all it takes.
If you add a device Vera can access that device’s capabilities and embedded components by asking the device simple questions about itself. Are you a basic switch (on / off), a multi-level switch (dimmer / blind controller), a colour changing switch (RGB / RGBW), a binary sensor (movement, moisture etc), a multi-level switch (temperature, UV), and are you battery powered etc? Also, how many embedded components have you got, ie are you a double light switch or a single light switch? All simple stuff, even if ZWave makes it a little more convoluted than it needs to be at a messaging level.
With the above info immediately available directly from the device when it is included, there should be absolutely no need to ask the user to select a device type, make model or any such thing. Additionally there should be no need to wait for Vera to release new firmware to support the basic features of any new zwave device, unless that device contains manufacturer specific command classes and even then all of the other device capabilities should work immediately.
So how do I know this?
I walked away 2 years ago after a FW updated bricked my Vera and support kindly offered to sell me a full price replacement. It was the final straw and forced me to make some difficult decisions. Years of reboots, chlunky scripting, and out of contol device and network management was written off. I looked around for a replacement and it just so happened that the ZWave protocol was released to the public. I had a play with witing some code and was amazed how simple it was to talk to ZWave devices. Tell them to turn on, off, up, down, and get status information from sensors etc. So I wrote me own ZWave controller which does pretty much everything that Vera does but it does it 24/7 without any restarts, delays etc.
ZWave as a protocol has some significant flaws and the public documentation is pretty bad (incomplete) and some of these flaws are things that the application designer (Vera etc) cannot necessarily overcome as they are inate to the chip level communications. However as a one man band building an app from scratch to control a ZWave network I can tell you that instability is not something that you should expect or tollerate. Devices and their underlying components are either included in the network or they are not. Included devices are stored on the ZWave chip itself while the app simply maintains metadata about the included devices. As such the devices shouldn’t appear or disappear. They can be included or excluded. They can change state. They can become non-communicardo. But they should never disappear unless the user wants them to be hidden.
I share this info with you not because I think most of you will be interested in building your own, and not because I want you to give up on Vera, and not because I want you to use any other system. I give you this information to help ask Vera the questions that need to be asked about the core of their product design. You can put lipstick on a pig but its still a pig. Likewise if Vera keeps building layers of fluffy stuff on top of the core design issues then reliability, stability and usability are only to be found in the marketing documents.
Years on all the same issues exist. I glad a chose to take a different path but that is not an option for everybody. For the person who doesn’t like reading about other people’s problems, I’m a little confused as to why you come to a forum like this. That is exactly the purpose of a forum, ie to talk about problems, discuss ideas, seek help and make enough noise that product development takes note and prioritises core issues above fluffy new marketable features.[/quote]
What platform did you put this on?
What language did you use to program it?
How does the device you use as a controller talk to Z-Wave devices?
Can this be expanded to talk to ZigBee devices and others that run through HTTP, such as Harmony and Autelis Pool Control?
Thanks!