Suggestion - Open dource the z-wave device drivers

[Guest sgbirch]

IMHO it is a terrible shame that Fibaro will not open source the HC2 but since that seems to be a firm decision, how about open sourcing the device drivers? It seems that many of Fibaro's problems stem from bugs and incompatibilities in the drivers, it would be cool if technically savvy end users could scratch their own itch and release working drivers back to Fibaro.

[Guest jrkalf]

As far as I can see it's not a "driver" issue where it comes to certain devices (aeon 4-in-1 for example) to be working. It's a zwave protocol stack and all devices have a fixed set of commands which are approved by the z-wave alliance in order to work.

So, theoretically it should all be templates in the database work to get it working properly. If you set the right commands to the right device template, it should auto-configure most of it and users should be able to manage some part of the user configuration themselfs.

_should_ ...

This is way it always says in the manual which Zwave commandsets are used. Developers should be able to use these default command sets against the devices and be able to communicate with them.

So, as far as I've figured out..., there aren't any specific device drivers.

And opening the source to the HC2, that would defeat the whole purpose of having the HC2 device. It's linux with a few Fibaro binaries and webpages to make it have the awesome sauce it has.

[Guest sgbirch]

Well, I am just trying to come up with some ideas. I have about 10 devices plus a discarded Vera and a new HC2, the whole experience is an exercise in complete frustration. I want this to work, I really do. But ....

I have a temp sensor that works sometimes but mostly tells me the room is at zero degrees. Even when it does give a temperature there is no way of knowing when the reading was taken without digging, what the hell use is that.

I have a key fob remote which only works when close to the HC2, so much for the wonderful mesh.

There are several devices that mysteriosly fail to comminicate but there is no way to find out why because nothing lets me see the routing tables. There aren't even log files on the HC2, it is opaque. Yes, I know I can change the root password and break in but why the should I. We have been telling Fibaro to give us eyes and the tools to debug our configurations but they are more interested in playing with voice recognition and tracking kids. This would be fine if the basic system could be dialled in. But it can't.

Also in my house is a Danfoss radiator valve which takes an hour to respond once it is told to heat the room, unless you press a button on it. How on earth is that home automation. My wife thinks it is a joke and wants me to rip it all out.

We can't look at any source code, either from Fibaro or from Zensis because its all a bloody big secret. We have no way of reading logs or sniffing packets so we are reduced to playing Shirlock Holmes and wasting hours of our time. Fibaro engineers can see inside the system and cannot possible empathise with the nightmare experience most users have.

I moved to zwave because X10 only worked 99% of the time but right now that is much much better than this immature technology.

Sorry, but it really does not work well and I have no way of finding out why. Give me eyes so that I can see.

So, I guess its on to Insteon next, or I may just give up and have the house wired for home automation because RF sure isn't working out.

Frankly, I'm fed up with fiddling and not being able to get any real information because it is all top secret.

Steve